seo-audit
by AgriciDanielseo-audit runs a full website SEO audit with parallel subagent delegation, crawling up to 500 pages and detecting business type. It covers technical, content, schema, performance, visual, local, and geo signals, then returns a health score and prioritized fixes for site-wide review and SEO Content analysis.
This skill scores 82/100, which means it is a solid listing candidate for directory users who want a guided full-site SEO audit instead of a generic prompt. The repository gives enough operational detail to trigger and understand the workflow: it has a valid frontmatter trigger, a clear URL argument hint, a defined crawl-and-delegate process, and named specialist branches. Users should still expect some adoption friction because there are no companion scripts, references, or install command, so execution depends mainly on the skill text itself.
- Strong triggerability: the frontmatter explicitly says it is user-invokable, gives a [url] argument hint, and names common user intents like 'audit' and 'analyze my site'.
- Clear workflow leverage: the body describes a concrete process—fetch homepage, detect business type, crawl up to 500 pages, and delegate to up to 15 specialists.
- Broad SEO coverage: it covers technical, content, schema, sitemap, performance, visual, geo, local, and maps-related checks, which is useful for full-site audits.
- No support files or install command are present, so users do not get extra tooling, references, or setup guidance beyond SKILL.md.
- The subagent delegation appears conditional and partly environment-dependent ('if available'), which may reduce consistency across agents.
Overview of seo-audit skill
What seo-audit does
The seo-audit skill runs a full website SEO audit with parallel subagent delegation. It is built for users who need a structured site-wide review, not a one-off keyword critique. It can crawl up to 500 pages, detect business type, and produce a health score with issue coverage across technical, content, schema, performance, visual, local, and geo signals.
Who should use it
This seo-audit skill fits site owners, SEOs, content teams, and AI agents that need a practical audit starting from a URL. It is most useful when the goal is to assess an entire site, prioritize fixes, or verify whether a domain is ready for search and AI visibility. If you only need a rewrite of one page, this is usually more tooling than you need.
Why it stands out
The main advantage is workflow depth: the skill is designed to branch into specialized checks instead of treating SEO as one generic prompt. That makes it better for real audit work where crawlability, indexation, content quality, structured data, and business context all matter together. It is especially relevant for seo-audit for SEO Content because it can surface thin content, readability issues, E-E-A-T gaps, and AI citation readiness alongside technical findings.
How to Use seo-audit skill
Install and trigger it
Use the seo-audit install flow with the repo path and skill slug, then invoke it with a site URL as the primary input. The skill is user-invokable and expects a URL such as a homepage or canonical domain, so the agent can fetch the page and begin site discovery. A typical invocation is closest to: “Run seo-audit on https://example.com and prioritize technical blockers, content quality, and schema gaps.”
Give it the right input
The seo-audit usage pattern works best when you provide a clean URL, the site type if known, and the audit goal. Strong prompts include constraints like “focus on organic traffic loss,” “check local SEO for a multi-location business,” or “prepare fixes for an AI-content-heavy blog.” Weak prompts like “audit my site” leave too much room for generic output and reduce the value of the crawl and specialist delegation.
Read these files first
For the fastest setup, start with skills/seo-audit/SKILL.md, then inspect scripts/fetch_page.py to understand how the homepage is retrieved. Also check LICENSE.txt if you need reuse context. Because this repository is lean and has no extra rules/, resources/, or references/ folders, the key information is concentrated in the skill file itself.
Workflow tips that improve output
Treat the skill as a structured audit pipeline: homepage fetch, business-type detection, crawl, then delegated analysis. If you want better results, tell the agent what matters most before it starts, such as “prioritize indexation and canonical problems” or “rank fixes by impact and implementation effort.” For the strongest seo-audit guide outcome, ask for a summary plus a fix list, not just a score, so the output is actionable.
seo-audit skill FAQ
Is seo-audit only for full-site audits?
Yes, that is the intended fit. The seo-audit skill is optimized for a site-wide review with crawl logic and subagent checks, so it is a poor match for isolated tasks like writing a title tag or rewriting one article section.
How is this different from a normal SEO prompt?
A normal prompt usually produces one-pass advice. seo-audit is more decision-oriented: it crawls the site, detects business context, and routes analysis to specialists. That means less guesswork on whether you missed technical, content, schema, or performance issues.
Does it work for beginners?
Yes, if you can supply a website URL and want a practical audit summary. Beginners get the most value when they ask for prioritization, plain-language explanations, and next steps rather than raw diagnostics.
When should I not use it?
Do not use it if you only need a single-page content edit, a keyword list, or a quick metadata suggestion. It is also not ideal if you cannot allow crawling or if the site is too small and simple to justify a multi-step audit workflow.
How to Improve seo-audit skill
Specify the audit objective
The best seo-audit results come from a clear outcome, not just a URL. Say whether you want technical recovery, content refresh planning, local visibility, schema cleanup, or a health check for an AI-first content site. This helps the skill prioritize the right specialist paths and avoids generic recommendations.
Provide context the crawler cannot infer
Tell the agent about the site type, target market, CMS, and any known constraints such as JavaScript rendering, staging access, or a blocked robots setup. If you have a concern like “traffic dropped after a migration” or “we publish programmatic landing pages,” include it up front so the audit can focus on the real failure mode.
Ask for ranked fixes and proof
The most useful improvement loop is to request issues ranked by severity, effort, and expected impact, with page examples or patterns called out. For seo-audit for SEO Content, ask for thin pages, duplicate intent, missing entities, and AI-citation readiness so the output becomes a content operations plan, not just a diagnosis.