sitemap-audit

This process compares your website’s generated sitemap against actual public pages to find missing or stale URLs. It scans Next.js app-router routes, sitemap definitions, and layout metadata to identify indexing coverage gaps before search engines crawl your site.

Checking dynamic route coverage involves reviewing generated pages and helper data so parameterized routes like services or blog posts are not overlooked. This validates that all public dynamic URLs are correctly indexed and accessible in the sitemap.

Yes, this sitemap audit applies to Next.js app-router projects and similar codebases. It reads route files, sitemap definitions, and layout metadata to validate static pages, dynamic routes, and robots directives for accurate indexing coverage.

Validating Google Search Console verification tags and robots directives confirms your site is set up for crawlability. This audit checks these indexing signals to verify they align properly with your actual public pages and generated sitemap entries.

Sitemaps contain stale or incorrectly excluded URLs when indexing signals and robots rules drift out of sync with existing codebase pages. Comparing generated sitemaps against actual public routes detects these misconfigurations and reports the discrepancies.

Run an audit of your live and generated sitemap after shipping new pages. This quickly reports missing pages, stale entries, or indexing misconfigurations by comparing sitemap entries against your actual public app routes.