Next.js sitemap checker
Check every route in your Next.js sitemap for trailing-slash redirects, 404s from stale build-time sitemaps, wrong canonicals and missing metadata.
- No sign-up needed
- No subscription
- Full report from €2.99
Where is my Next.js sitemap?
/sitemap.xml from app/sitemap.ts or next-sitemap
In the App Router, app/sitemap.ts (or a static app/sitemap.xml) is served at /sitemap.xml. Many sites use the next-sitemap package instead, which writes sitemap files at build time.
Common Next.js sitemap problems
Trailing-slash redirects
If the sitemap lists /page but trailingSlash sends visitors to /page/ (or the other way round), every URL is a 308 redirect. We catch it on the first page.
Stale build-time sitemaps
Sitemaps generated at build time can list pages that have since been deleted. We flag every 404.
Canonicals pointing at the wrong host
A metadataBase or canonical left pointing at localhost or a preview deployment shows up as canonicals pointing elsewhere.
Missing titles and descriptions
Routes without metadata or generateMetadata fall back to the root layout's defaults, which then show up as duplicates.
Slow server-rendered pages
We time every response and list the slowest routes.
Quick fixes for Next.js
- Generate sitemap URLs with the same trailing-slash setting as next.config.js.
- Set metadataBase to your production URL.
- Regenerate the sitemap on deploy, not just at the first build.
Then run a re-check within 30 days of buying your report to confirm the fixes, at 50% off.
How healthy is your Next.js site?
Start free. We check the first 100 pages without sign-up, and up to 500 when you sign in.
Audit my Next.js site