Seo audit
Reusable AI-agent skills for planning, verification, security reviews, SEO audits, changelogs, CLIs, and multi-step coding loops.
npx -y skills add zgroves24/agent-operator-skills --skill seo-auditAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Audit websites, web apps, and local dev servers for technical SEO, crawlability, indexability, metadata, structured data, sitemap and robots hygiene, content coverage, freshness, and basic performance.
SKILL.md
3.5 KB, as published. Nobody here has run it
SEO Audit
Quick Start
Run the deterministic audit first when a site is accessible over HTTP:
python3 ~/.codex/skills/seo-audit/scripts/seo_audit.py --base-url http://localhost:3000 --sample-limit 80
For production:
python3 ~/.codex/skills/seo-audit/scripts/seo_audit.py --base-url https://www.example.com --sample-limit 120
For custom route maps, pass repeated path flags:
python3 ~/.codex/skills/seo-audit/scripts/seo_audit.py \
--base-url https://www.example.com \
--public-path / --public-path /pricing --public-path /blog \
--private-path /login --private-path /account \
--sample-prefix /blog/ --sample-prefix /docs/
Use the script output as evidence, then apply judgment for business relevance, keyword intent, conversion quality, and content gaps.
Workflow
- Confirm the target environment: local preview, staging, or production.
- Run the audit script and save the JSON or Markdown output if the work needs comparison over time.
- Check critical public pages manually or with a browser when visual or responsive risk matters.
- Prioritize fixes in this order: crawl blockers, noindex/canonical mistakes, sitemap gaps, private-page leakage, missing titles/descriptions/H1s, invalid structured data, weak internal linking, stale or inaccurate content, performance regressions.
- Re-run the audit after changes and report the before/after score, blockers fixed, remaining risks, and deployment-readiness judgment.
Scoring Standard
Use the score as a quality gate, not as vanity:
95-100: Excellent. Ship if analytics and conversion instrumentation are also intact.90-94: Strong. Ship, then fix remaining non-blocking issues.80-89: Good but not finished. Fix high-impact misses before a major launch.70-79: Risky. Important crawl, metadata, content, or performance gaps remain.<70: Do not ship as an SEO push unless there is a separate urgent reason.
The bundled script grades:
- Crawlability and indexing, including
robots.txt, sitemap, status codes, private route leakage, and canonical tags. - On-page metadata, including title, description, H1, Open Graph, internal links, viewport, and language.
- Structured data validity and rich-result eligibility risks.
- Content coverage, including expected public pages and sitemap-discovered content samples.
- Basic response-time and document-size signals.
Judgment Rules
- Treat a public SEO URL that redirects to login as a critical failure.
- Treat
robots.txtblocking a valuable public URL as a critical failure. - Prefer no structured data over invalid, unsupported, or misleading structured data.
- Do not add ratings, reviews, app availability, prices, or competitor claims unless they are real and current.
- Do not optimize only for crawlers. The page must answer the search intent and make the next user action obvious.
- For programmatic SEO, require crawlable hub pages that link to generated pages. A sitemap alone is not enough.
- For app SEO, verify web-to-app metadata, store links, and pricing copy against current live state.
Resources
scripts/seo_audit.py: deterministic HTTP/HTML/XML audit with a weighted score and prioritized findings.references/google-search-checklist.md: compact reference for Google-oriented SEO decisions.