sitemap-audit

Featured

XML sitemap audit — find and fix the sitemap problems that quietly waste crawl budget and slow indexing. Discovers the sitemap (robots.txt, /sitemap.xml, sitemap index), validates structure and size limits, and cross-checks the URLs it lists against reality: non-200 / redirected / noindex / canonicalized-away URLs that shouldn't be in a sitemap, plus indexable pages that are missing from it. Reviews lastmod accuracy, sitemap-index organization, and robots.txt reference. Use this skill whenever the user asks about sitemaps, sitemap errors in Search Console, "sitemap couldn't fetch / has errors", crawl budget, pages not getting indexed, or whether their sitemap is clean. Trigger on: "sitemap", "sitemap.xml", "XML sitemap", "sitemap errors", "sitemap audit", "couldn't fetch sitemap", "crawl budget", "pages not indexed sitemap", "sitemap index", "lastmod", "robots.txt sitemap", or any sitemap/crawl-coverage question. For a full-site SEO audit use /seo-analysis; for broken links use /broken-link-checker.

AI & Automation 3,344 stars 417 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 96/100

Stars 20%
100
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# XML Sitemap Audit You are a technical-SEO engineer. Your job is to make a site's XML sitemap a clean, trustworthy index of exactly the URLs Google should crawl and index — no more, no less — and to flag everything currently undermining that. A sitemap full of redirects, 404s, and noindex URLs teaches Google to distrust it and wastes crawl budget. A sitemap missing important pages slows their discovery. Both are common; both are fixable. > Credit: capability inspired by the open-source `claude-seo` project > (MIT, Agrici Daniel). Implementation is original to NotFair. --- ## Step 0 — Scope Collect the **site URL** (`$SITE_URL`). If the user gives a direct sitemap URL, use it; otherwise discover it in Phase 1. --- ## Phase 0 — Preflight & data Read and follow `../shared/preamble.md` for script discovery and GSC auth. If GSC is connected, pull the **Sitemaps** report and the **Index coverage** / Pages report. GSC tells you which sitemaps Google has, their last read status, any errors, and how many submitted URLs are actually indexed — the ground truth this audit reconciles against. --- ## Phase 1 — Discover all sitemaps 1. Fetch `robots.txt` and read every `Sitemap:` directive. 2. Fetch `/sitemap.xml`, `/sitemap_index.xml`, and any CMS-specific defaults (WordPress/Rank Math: `/sitemap_index.xml`; Yoast similar). 3. If it's a **sitemap index**, enumerate the child sitemaps and recurse. Record the full tree: index → child sitemaps → URL counts. Note whether the ...

Details

Author
nowork-studio
Repository
nowork-studio/notfair-plugin
Created
4 months ago
Last Updated
1 weeks ago
Language
TypeScript
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

Web & Frontend Listed

sitemap-audit

Audits a website's SEO discoverability by cross-referencing the codebase with live production. Catches sitemap, robots.txt, and canonical inconsistencies, framework-specific anti-patterns (Next.js App Router metadata cascade, Astro/Nuxt equivalents), redirect-chain issues, and Google Search Console stuck states. Produces a prioritized, evidence-backed report with suggested fixes. Use when Search Console shows "Couldn't fetch", pages aren't being indexed, or you want an SEO health check before a launch or after a routing refactor.

2 Updated 1 weeks ago
mostafa-drz
AI & Automation Featured

seo-analysis

Full SEO audit: Google Search Console data + URL Inspection API + PageSpeed Insights API + technical crawl + keyword research + metadata audit + schema markup audit + search intent analysis + Core Web Vitals monitoring. Feeds real GSC data and PageSpeed metrics into AI to surface quick wins, diagnose traffic drops, find content gaps, identify metadata mismatches, detect schema gaps, monitor page performance, and produce an actionable 30-day plan. Use this skill whenever the user asks about SEO, search rankings, organic traffic, Google Search Console, keyword performance, traffic drops, content gaps, search visibility, technical SEO, meta tags, schema markup, structured data, URL indexing, keyword research, indexing issues, page speed, performance, Core Web Vitals, LCP, INP, CLS, or Lighthouse scores. Also trigger on: "why is my traffic down", "what keywords am I ranking for", "improve my rankings", "check my search console", "SEO audit", "analyze my SEO", "technical SEO", "meta tags", "indexing issues", "craw

3,344 Updated 1 weeks ago
nowork-studio