Sitemap.xml
Checks that sitemap.xml exists at the root, is valid XML, and lists indexable URLs.
What this check measures
We fetch `/sitemap.xml` and validate XML syntax, URL format, and that listed URLs return 200 (not 301 or 404). We also check the sitemap size (under 50MB, under 50,000 URLs).
Why it matters
A sitemap tells Google about URLs you want indexed. Without it, Google has to discover pages through links only — slow for new sites and unreliable for JS-heavy apps. First-indexing time drops from weeks to days with a sitemap.
How our audit detects it
GET /sitemap.xml. Validate XML, check declared URLs respond 200. Cross-reference with robots.txt for Sitemap: directive.
Typical findings
- error_outline/sitemap.xml returns 404.
- error_outlineSitemap lists URLs that return 301 or 404.
- error_outlineSitemap includes login, admin, or noindex URLs that should not be there.
- error_outlinerobots.txt has no `Sitemap:` line pointing to the file.
How to fix
Generate /sitemap.xml listing all public, indexable URLs. For Next.js use `app/sitemap.ts`. For Lovable/Bolt/Vite drop a static file in `/public`. Submit in Google Search Console → Sitemaps.
Copy-paste fix prompt for your stack
Lovable · Cursor · Bolt · v0 · Replit · Windsurf · Claude Code · Base44
Frequently asked questions
How big can a sitemap be?expand_more
Do I need one for a 20-page site?expand_more
Want this checked on your site?
Pantra runs the full audit (SEO, Security, GEO, Performance, Schema, Technical, Images) in 10 seconds and generates stack-specific fix prompts.
Scan my siteRelated checks
Meta Title
Checks that every page has a unique, keyword-rich <title> tag between 10-60 characters.
SEOMeta Description
Checks that every page has a unique meta description between 50-160 characters.
SEOH1 Tag
Checks that every page has exactly one H1 tag containing the primary keyword.
SEOHeading Hierarchy
Checks heading order — H1 → H2 → H3 without skipping levels.