What is a sitemap and why does it matter?

A sitemap (sitemap.xml) is an XML file at your site root that lists URLs you want search engines to crawl and index. It helps Googlebot, Bingbot, and other crawlers discover content faster than relying on internal links alone — especially for new sites, large catalogs, deep pages, or pages with weak internal linking. Without a sitemap, Googlebot must follow links from page to page, missing orphans (pages with no internal links to them) entirely. With a sitemap, every listed URL is at least known to Google, even if not yet crawled or indexed. The format follows sitemaps.org spec: each ` ` element contains ` ` (URL), optional ` ` (last modified date), ` ` (deprecated and ignored by Google), and ` ` (also largely ignored). Sitemaps don't guarantee indexing — Google still decides what to crawl and index based on quality signals — but they substantially accelerate discovery for new content. Required for any site over 100 pages; useful even for small sites because they signal canonical URLs and update frequency.

What's the maximum size for a sitemap?

A single sitemap file can contain up to 50,000 URLs OR 50 MB uncompressed (whichever limit hits first). For larger sites, use a sitemap index file pointing to multiple sitemap files. Google supports sitemap indexes up to 50,000 nested sitemaps, theoretically allowing 2.5 billion URLs. Practical pattern for sites with 50,000+ URLs: organize sitemaps by content type — sitemap-products.xml, sitemap-blog.xml, sitemap-categories.xml, sitemap-images.xml — each containing relevant URLs, with sitemap_index.xml at the root referencing all. This makes diagnostics easier (you can see indexing rate by content type in GSC) and is what Yoast, RankMath, Shopify, and most major platforms generate by default. Compress sitemaps with gzip if file size approaches the 50MB limit; Google supports .xml.gz extensions. Don't exceed 50,000 URLs in a single file even if size is under 50MB — Google will reject the file with a parsing error.

How do I submit my sitemap to Google?

Two methods, ideally both. (1) Reference in robots.txt — add `Sitemap: https://yoursite.com/sitemap.xml` to your robots.txt file. Googlebot, Bingbot, and other crawlers automatically discover sitemaps listed in robots.txt. This is the modern best practice and works without any account setup. (2) Submit via Google Search Console — log into GSC, select your property, navigate to Sitemaps in the left menu, paste your sitemap URL, click Submit. GSC then crawls the sitemap and reports status. Why both: robots.txt method ensures all crawlers find it; GSC submission gives you status reporting (Success, Has errors, Could not fetch) and a URL count. After submission, GSC processes the sitemap within 24-72 hours and reports submitted vs indexed URL count. Repeat for Bing Webmaster Tools (similar workflow). For other engines (Yandex, Baidu, DuckDuckGo): mostly auto-discover via robots.txt; some have manual submission options. Submit your sitemap once and re-submit only after major structural changes; sitemaps update automatically as your site updates.

What does the lastmod tag actually do?

The ` ` element signals when a URL was last modified (in W3C datetime format: 2026-04-29T14:30:00+00:00 or 2026-04-29). Google uses lastmod as a hint for crawl prioritization — pages with recent lastmod values get re-crawled sooner than those that haven't changed in months. The crucial caveat: Google ignores lastmod if it doesn't match reality. If your sitemap shows every URL with today's date but page content hasn't actually changed, Google detects the deception via fingerprinting and discounts your sitemap signals. To use lastmod effectively: (1) Generate it dynamically from actual content modification timestamps in your CMS. (2) Don't bulk-update lastmod for cosmetic site refreshes — only update when content meaningfully changes. (3) For static pages that rarely change (About, Contact), keep lastmod set to the actual last edit date, even if years old. Google's John Mueller stated in 2022 that accurate lastmod is "really helpful" — accurate is the operative word. Most CMSes (WordPress with Yoast, Shopify, Webflow) generate lastmod correctly by default. Custom-built sitemaps need lastmod logic explicitly.

Should I include all my pages in the sitemap?

No — include only canonical, indexable pages you want to rank. Exclude: (1) Pages with noindex tags (Google will see the sitemap inclusion as a contradiction). (2) Pages blocked in robots.txt (waste of sitemap entries). (3) Non-canonical URLs (parameter URLs, alternate URLs). (4) Login, cart, checkout, account pages. (5) Internal search results. (6) Tag/category archive pages on blogs (often thin content). (7) Old URLs you redirect (sitemap should show the destination URL only). (8) Draft, scheduled, or unpublished content. The principle: every URL in the sitemap should be one you actively want indexed, with content worth ranking. A sitemap with 10,000 URLs of which 8,000 are noindexed is worse than a sitemap with 2,000 high-quality canonical URLs because Google evaluates submitted/indexed ratio as a quality signal. Most CMSes default to including everything; use sitemap exclusion settings or plugins to filter. Audit by exporting your sitemap, checking each URL category, and excluding the non-rankable ones.

How do I check sitemap status in Google Search Console?

GSC > Sitemaps shows three key metrics per submitted sitemap: (1) Status — "Success", "Has errors", "Couldn't fetch". Errors usually mean malformed XML, URL format issues, or unreachable sitemap. Fix immediately. (2) Submitted — total URL count Google parsed from your sitemap. Should match your expected total. If 1,500 URLs submitted but you have 3,000 published pages, your sitemap generation has a bug. (3) Last read — when GSC last fetched the sitemap. Should be recent (within 7 days for active sites; longer if site rarely changes). Below the table, GSC Coverage report shows submitted-and-indexed vs submitted-but-not-indexed URLs. The latter group is the actionable one — diagnose why those URLs aren't indexed (thin content, duplicate, soft 404, blocked by noindex, etc.). Aim for 80%+ submitted-to-indexed ratio for healthy sites. Below 50% indicates content quality issues or technical problems that need investigation. Re-submit sitemaps in GSC only when you've made structural changes; routine submissions don't accelerate indexing further.

Do priority and changefreq tags work?

Mostly no in 2026. Google's John Mueller and the Search Central documentation have repeatedly stated that ` ` and ` ` are ignored by Google's crawler. Bing claims to use them as hints but with low weight. The thinking: site owners systematically lie about priority (everyone marks their pages 1.0) and changefreq (everyone says daily even on static content), so the signals became useless. Google relies on its own crawl signals (lastmod when accurate, internal link count, content quality, historical change patterns) to prioritize crawling. You can include priority and changefreq in your sitemap — they don't hurt — but don't expect ranking or crawl-rate impact. Most CMSes auto-generate these with default values you can ignore. The only sitemap signal that meaningfully affects Google in 2026 is ` ` (URL inclusion) and ` ` when accurate. Specialized sitemaps (image, video, news) have additional fields that DO matter — see those sections.

What are image and video sitemaps?

Specialized sitemap formats for richer media indexing. Image sitemap: extends standard sitemap with ` ` elements containing image URL, caption, title, geographic location, license. Helps Google Images discover and rank your images, especially helpful for visual brands, ecommerce, real estate, and stock photo sites. Add to existing sitemap with xmlns:image="http://www.google.com/schemas/sitemap-image/1.1". Video sitemap: extends with ` ` containing thumbnail, title, description, content URL, duration, family-friendly tag, view count, rating. Helps videos rank in Google Video search and main SERPs. Use xmlns:video="http://www.google.com/schemas/sitemap-video/1.1". News sitemap: separate sitemap-news.xml for content published in last 48 hours, with ` ` containing publication name, language, publication date, title. Required for inclusion in Google News. Most large publishers maintain news sitemap, image sitemap, and standard sitemap separately. For most sites, standard sitemap is sufficient; add image/video sitemaps only if visual/video content is core to ranking strategy.

How often does Google re-crawl my sitemap?

Variable — depends on site size, change frequency, and authority. For high-authority active sites (publishers, ecommerce with daily new products), Google re-fetches sitemaps every 1-3 days. For mid-tier business sites, every 7-14 days. For low-traffic or rarely-updated sites, every 30+ days. You can't control this directly, but you can influence: (1) Update lastmod accurately when content changes — Google notices and re-fetches sooner. (2) Build domain authority through backlinks — high-authority sites get more frequent crawls. (3) Submit sitemap manually in GSC after major content batches — triggers immediate re-fetch. Don't spam re-submissions. Google rate-limits re-submission requests; submitting daily without changes hurts more than helps because GSC marks the sitemap as low-priority. Check GSC > Sitemaps > Last read to see actual re-fetch cadence. If "Last read" is over 30 days for an active site, your sitemap may have errors blocking re-fetch — investigate.

Submitted but not indexed — why?

When GSC shows URLs as "submitted but not indexed", common causes in order of frequency: (1) Crawled, currently not indexed — Google crawled but decided content is low-quality, duplicate, or insufficiently linked. Most common cause. Improve content depth, internal links, E-E-A-T signals. (2) Discovered, currently not indexed — Google found the URL via sitemap but hasn't crawled yet. Typical for new sites or low-priority pages. Build backlinks and internal links to signal importance. (3) Duplicate — URL is a duplicate of another canonical URL. Check rel=canonical settings. (4) Alternate page with proper canonical tag — URL is correctly canonicalized to a different URL. Expected behavior, no action needed. (5) Noindex tag — sitemap includes URL with noindex meta. Remove from sitemap or remove noindex. (6) Soft 404 — URL returns 200 but content looks like an error page. Add real content. (7) Blocked by robots.txt — sitemap includes URL that's blocked. Either unblock or remove from sitemap. Use GSC > Coverage > "Why pages aren't indexed" to see exact reason per URL.

How do I handle huge sitemaps for ecommerce sites?

For ecommerce with 100,000+ products: (1) Split by content type — sitemap-products.xml, sitemap-categories.xml, sitemap-blog.xml, sitemap-images.xml. (2) Within products, split by recency or authority — sitemap-products-current.xml (in-stock active products), sitemap-products-archive.xml (out-of-stock, low-traffic). Submit all to GSC. (3) Use sitemap_index.xml as the root referencing all. (4) Generate dynamically with proper lastmod values pulled from product update timestamps. (5) Compress with gzip if individual files approach 50MB. (6) For seasonal products (holiday items), keep them in sitemap year-round but adjust lastmod to reflect actual content updates. (7) Out-of-stock products: keep in sitemap with status=OutOfStock in Product schema rather than 404 — preserves accumulated link equity for restock. (8) Discontinued products: 410 (Gone) status, remove from sitemap, add to redirect map pointing to category page. Audit indexed-vs-submitted ratio in GSC monthly; aim for 80%+. Below 50% indicates many URLs being filtered out as low-quality (often thin product variants or duplicate filter combinations).

Is this sitemap status checker free, and what does it check?

Yes, completely free with no signup. Paste any sitemap URL (typically yoursite.com/sitemap.xml) and the checker validates: (1) HTTP response status (200 vs error). (2) Content-Type header (must be application/xml or text/xml). (3) XML parsing (catches malformed XML). (4) Sitemaps.org schema compliance. (5) URL count (warns if approaching 50,000 limit). (6) lastmod presence and format validation. (7) URL structure (canonical vs duplicate, http vs https mix). (8) Sitemap index detection and recursive checking of nested sitemaps. (9) Common errors (encoding issues, special characters, wrong namespaces). Output is a status report with errors flagged by severity. Pair with Google Search Console (for actual indexing data) and our Sitemap Visualizer (for structural analysis). Unlimited checks, no rate limits. After using these, try our AI Website Builder which generates SEO-clean sitemaps automatically with proper lastmod tracking and split-by-content-type indexes.

Free Sitemap Status Checker

Check if your sitemap is accessible, valid, and indexed by Google. Validate XML, count URLs, audit ping. Free.

4.6on G2

4.8on Trustpilot

Used by 25,000+ marketers

What this tool does

Sitemap Status Checker delivers fast, reliable results for check if your sitemap is accessible, valid, and indexed by google. validate xml,.

Designed to fit into your existing SEO and content workflow with no setup overhead.

How to use it

Five steps.

Enter your sitemap URL

Paste your sitemap URL (typically yoursite.com/sitemap.xml or yoursite.com/sitemap_index.xml) into the input field.

Run the validation

Click Check. The tool fetches the sitemap, parses XML, validates structure, and recursively checks any sub-sitemaps in an index.

Review the report

See HTTP status, URL count, lastmod validation, schema compliance, and any errors flagged by severity.

Fix flagged errors

Address malformed XML, missing lastmod, HTTP/HTTPS mismatches, or sitemap index issues. Re-validate after fixes.

Submit to Google Search Console

Once validation passes, submit the sitemap URL in GSC > Sitemaps. Add Sitemap: directive to robots.txt for auto-discovery by other crawlers.

When teams use it

Six common workflows.

Validate sitemap before launch

Before submitting to Google Search Console, validate sitemap structure, XML syntax, URL count, and lastmod accuracy. Catches errors that would otherwise show as red status in GSC and delay indexing.

Diagnose indexing problems

When GSC shows "submitted but not indexed" for many URLs, validate sitemap structure first. Eliminates technical sitemap issues as the cause before investigating content quality.

Migration validation

After CMS migrations or domain changes, validate that the new sitemap exists, is valid XML, and contains canonical URLs in the new structure. Catches HTTP-to-HTTPS issues and URL pattern errors.

Sitemap index troubleshooting

For large sites with sitemap_index.xml referencing 10+ sub-sitemaps, verify each child sitemap is accessible and valid. Find broken sub-sitemaps that GSC reports as "couldn't fetch".

Competitor sitemap analysis

Check competitor sitemaps to understand their site structure, content categories, and publishing cadence. /robots.txt usually references the sitemap; check for SEO competitive intelligence.

Monthly sitemap hygiene checks

Run a quick validation monthly. Sitemaps drift — CMS updates break generation, plugins introduce malformed entries, lastmod becomes stale. Catch issues before they hurt indexing.

Platform guides

Integrate with major platforms.

WordPress

Install Yoast SEO or RankMath — both auto-generate sitemap.xml at root
Default URL: yoursite.com/sitemap_index.xml (Yoast) or yoursite.com/sitemap.xml (RankMath)
Validate with our checker
Submit in Google Search Console > Sitemaps after validation passes

Shopify

Shopify auto-generates sitemap at yoursite.com/sitemap.xml — no plugin needed
Sitemap index format with /sitemap_products_1.xml, /sitemap_collections_1.xml, /sitemap_pages_1.xml children
Validate with our checker — verify all sub-sitemaps return 200
Submit yoursite.com/sitemap.xml in GSC; sub-sitemaps auto-discovered

Webflow

Webflow auto-generates sitemap at yoursite.com/sitemap.xml when you publish
Toggle on/off in Project Settings > SEO > Sitemap
Validate after publish with our checker
Submit in GSC after validation; CMS Collections auto-included if marked indexable

Next.js

Use next-sitemap package or generate manually with getServerSideProps in pages/sitemap.xml.tsx
For large sites, generate sitemap_index.xml referencing dynamic children (sitemap-blog.xml, sitemap-products.xml)
Implement lastmod from CMS timestamps, not generation time
Validate with our checker on every deploy; submit to GSC

Custom / static sites

Generate sitemap.xml manually or with build scripts (Hugo, Jekyll, Eleventy auto-generate)
Validate sitemaps.org schema compliance with our checker
Add Sitemap: directive to robots.txt
Submit to GSC and Bing Webmaster Tools; re-submit only when structural changes occur

Grigora vs. alternatives

Side-by-side.

Capability	Grigora	Screaming Frog	GSC	Free Tools	Manual
XML validation against sitemaps.org schema	Yes	Yes	Yes	Yes	Manual
Sitemap index recursive check	Yes	Yes	Limited	No	Manual
lastmod format validation	Yes	Partial	Yes	Limited	Manual
URL count vs 50K limit warning	Yes	No	Yes	No	Manual
HTTPS canonical mismatch detection	Yes	Limited	Yes	No	Manual
Free with no signup	Yes	Yes	Trial only	Yes	N/A
Indexing status from GSC	No	Limited	Yes	No	Yes
Image and video sitemap validation	Yes	Yes	Yes	Limited	Manual

Common errors and fixes

Eight issues users hit.

Sitemap returns 404 or 5xx error

Cause: Sitemap URL doesn't exist at the expected path, or server is misconfigured to return errors for /sitemap.xml.

Fix: Generate a sitemap (Yoast, RankMath, your CMS plugin, or custom code), upload to root, and verify accessible at https://yoursite.com/sitemap.xml. Update robots.txt with Sitemap: directive.

Malformed XML — parsing error

Cause: Special characters not encoded (& → &), unclosed tags, missing namespace declarations, or invalid datetime formats in lastmod.

Fix: Validate sitemap with W3C XML validator or our checker. Most issues: encode ampersands, ensure all `<url>` tags close, use proper xmlns="http://www.sitemaps.org/schemas/sitemap/0.9".

Submitted but not indexed (high ratio)

Cause: Sitemap includes 10,000 URLs but only 2,000 are indexed — typically thin content, duplicates, or non-canonical URLs being submitted.

Fix: Audit URLs in sitemap. Remove noindex pages, parameter URLs, and thin content. Improve content depth on pages worth indexing. Aim for 80%+ submitted-to-indexed ratio.

Sitemap exceeds 50,000 URL limit

Cause: Single sitemap file contains too many URLs — Google rejects parsing and reports error in GSC.

Fix: Split into multiple sitemaps (sitemap-blog.xml, sitemap-products.xml, sitemap-categories.xml) and create sitemap_index.xml as root referencing all. Each sub-sitemap stays under 50,000 URLs.

lastmod always shows current date

Cause: CMS or sitemap generator sets lastmod to the date the sitemap was generated, not when content actually changed.

Fix: Configure sitemap to pull lastmod from content modification timestamps in your CMS database. Yoast/RankMath do this correctly by default. Custom sitemaps need explicit lastmod logic.

Sitemap not referenced in robots.txt

Cause: Robots.txt missing the Sitemap: directive — crawlers other than Google may not auto-discover the sitemap.

Fix: Add `Sitemap: https://yoursite.com/sitemap.xml` to robots.txt at the root. Reload sitemap discovery in GSC, Bing Webmaster Tools, and any other search engines you target.

HTTP URLs in HTTPS sitemap (or vice versa)

Cause: Site migrated to HTTPS but sitemap still references http:// URLs — creates canonical mismatch.

Fix: Regenerate sitemap with consistent HTTPS URLs throughout. Verify with our checker that all `<loc>` values use the canonical https:// scheme.

Sitemap index referencing non-existent sub-sitemaps

Cause: sitemap_index.xml references sitemap-products.xml that returns 404 — Google reports "Couldn't fetch" error in GSC for the sub-sitemap.

Fix: Verify each sub-sitemap URL is accessible (200 response). If a sub-sitemap is removed, update the index file. Re-submit sitemap_index.xml in GSC after fixes.

Original data

2026 study.

21%

Sites with sitemap errors detected by GSC

82%

Avg submitted-to-indexed ratio for healthy sites

34%

Sites with stale lastmod values across all URLs

47%

Sites with sitemap not referenced in robots.txt

Frequently asked questions

Twelve answers.

Related free tools

Other utilities.

Try Sitemap Status Checker now

Free, unlimited, no signup.

Try the Tool