Loading tutorials…
Loading tutorials…
Submitting a sitemap is one click. Submitting the right sitemap, in the right format, with the right URLs is what separates indexed sites from invisible ones. Here's how to get this right and how to diagnose the most common errors.
Who this is forSite owners with 50+ pages who want to give Google a clear map to follow. Particularly important for ecommerce, blogs, and sites with frequent content updates — anything where waiting for Google to discover URLs organically is too slow.
What you'll need
Step 1
Most CMSs generate a sitemap at a predictable URL. Find yours before opening GSC.
WordPress + Yoast: yoursite.com/sitemap_index.xml (sitemap index that links to sub-sitemaps).
WordPress + Rank Math: yoursite.com/sitemap_index.xml (same convention).
Shopify: yoursite.com/sitemap.xml (auto-generated, can't customize).
Webflow: yoursite.com/sitemap.xml.
Wix: yoursite.com/sitemap.xml.
Squarespace: yoursite.com/sitemap.xml.
Custom Next.js / Nuxt: usually yoursite.com/sitemap.xml or /sitemap-0.xml depending on plugin.
Open your sitemap URL in a browser. It should return XML, not a 404 or a redirect to home page. If it returns HTML or 404, fix that first.
Step 2
GSC → Sitemaps → enter the sitemap path (relative to your domain) → Submit.
In GSC, navigate to Sitemaps (left sidebar).
In the "Add a new sitemap" field, enter only the path — e.g., "sitemap.xml" or "sitemap_index.xml". Do NOT enter the full URL.
Click Submit.
Status should change to "Success" within a few hours. "Couldn't fetch" means GSC couldn't load the file — see step 5.
Sitemaps panel will show: submission date, last-read date, status, discovered URLs.
Step 3
Add a Sitemap directive to robots.txt so other crawlers (Bing, Yandex) can find it too.
Open your robots.txt file at yoursite.com/robots.txt.
At the bottom, add: Sitemap: https://yoursite.com/sitemap.xml (use full URL, not relative).
If you have multiple sitemaps, list each one on its own line.
Save. This helps Bing, DuckDuckGo, and other crawlers find your sitemap without manual submission.
Verify by visiting yoursite.com/robots.txt in a browser.
Step 4
Sites with 10K+ URLs should split into multiple sitemaps by content type — products, blog posts, category pages, etc.
Google enforces a 50,000 URL / 50MB limit per sitemap file. Beyond that, you need a sitemap index.
Even below the limit, splitting by content type makes diagnosing indexing issues easier. If "product" sitemap has 80% indexing and "blog" sitemap has 40%, you know where the issue lives.
Common splits: sitemap-products.xml, sitemap-blog.xml, sitemap-categories.xml, sitemap-pages.xml.
All sub-sitemaps go inside sitemap_index.xml — submit only the index file to GSC, not each sub-sitemap.
Yoast and Rank Math handle this automatically — they generate per-post-type sub-sitemaps within a sitemap_index.xml.
Step 5
Most sitemap errors come from one of four causes: file 404, redirect, blocked by robots.txt, or malformed XML.
Open the sitemap URL in incognito. If you get a 404, the file path is wrong or the file doesn't exist. Fix the path.
If you get a 301/302 redirect (e.g., http → https), submit the FINAL URL after redirects, not the original.
Check robots.txt for Disallow rules that might block /sitemap.xml. Disallow: / blocks everything including the sitemap.
Validate XML by pasting your sitemap into an online XML validator. Common breakage: invalid characters in URLs (& should be &).
After fixing, in GSC → Sitemaps → click the sitemap → "Refresh status" or resubmit.
Step 6
GSC Indexing report shows submitted vs indexed. The gap tells you what to fix.
Go to GSC → Indexing → Pages.
Filter by "From submitted sitemaps" (top of report).
Compare "Indexed" count vs "Not indexed" count. Healthy ratio is 80%+ indexed.
Click "Not indexed" to see specific reasons — most common: Crawled-not-indexed, Discovered-not-indexed, Soft 404, Duplicate-no-canonical-selected.
Each reason has a different fix — see the fix-coverage-errors tutorial.
Step 7
Sitemaps drift. Set a calendar reminder to audit yours every 90 days.
Every 90 days, re-open GSC → Sitemaps. Confirm status is still "Success."
If discovered URL count dropped 20%+ vs prior reading, investigate — usually a category was unintentionally noindexed or a CMS change removed URLs.
If a new content type was added (e.g., a podcast section, a glossary), make sure it's included in the sitemap.
If you ran a site migration, resubmit the sitemap and request indexing on top URLs (see the request-indexing tutorial).
Common mistakes
Submitting the full URL instead of the path
What goes wrong: GSC field expects a path relative to the property root. Pasting "https://yoursite.com/sitemap.xml" can cause submission errors on Domain properties. Status shows "Couldn't fetch" with no useful detail.
How to avoid: Enter only "sitemap.xml" or "sitemap_index.xml" — no protocol, no domain.
Including noindexed pages in the sitemap
What goes wrong: Sitemap signals "these pages matter for indexing." Including noindex pages contradicts that. Google flags this in Coverage as "Submitted URL marked 'noindex'" and reduces trust in your sitemap.
How to avoid: Sitemap should only contain indexable pages. Exclude category pages, tag archives, paginated archives, and any URL you've intentionally noindexed.
Forgetting to update sitemap after site migration
What goes wrong: After migrating from /blog/ to /resources/, sitemap still lists old URLs. Google crawls all old URLs, finds 301 redirects, and loses crawl budget on redirects instead of new content. Indexing slows for weeks.
How to avoid: Regenerate sitemap immediately after migration. Submit the new sitemap. Old URLs will fade from the index over 30-60 days.
Not splitting large sitemaps
What goes wrong: One sitemap with 30,000 mixed URLs makes diagnosing indexing issues nearly impossible. You can't tell whether blog or product URLs are the problem.
How to avoid: Split by content type. Use sitemap_index.xml as the single submission, with sitemap-products.xml, sitemap-blog.xml, etc. inside.
Submitting the sitemap once and never re-checking
What goes wrong: Sitemap silently breaks during a CMS update (path changes, plugin update breaks generation). Google stops getting new URLs. New content takes months to be discovered.
How to avoid: Calendar reminder every 90 days — audit Sitemap status in GSC. If status changes from "Success" to anything else, fix within a week.
Including non-canonical URLs in the sitemap
What goes wrong: Sitemap lists /category?sort=newest while canonical is /category. Google sees the discrepancy and devalues the sitemap signal. Indexing slows.
How to avoid: Sitemap should only contain canonical URLs — the same URL you have in your <link rel="canonical"> tags. No tracking params, no sort parameters, no UTM codes.
Recap
Done — what's next
How to set up Google Search Console from scratch
Read the next tutorial
Hand it off
Submitting a sitemap is a one-time task. Maintaining sitemap health, fixing coverage errors as they appear, and catching CMS-related sitemap breakage during plugin updates is ongoing work. A technical SEO specialist on retainer runs $400-800/mo and prevents most sitemap-related indexing drops before you'd notice them.
See specialist rates
Initial read: a few hours for status to change to "Success." Actual URL discovery: 1-7 days for most URLs. Full indexing of new URLs: 14-60 days depending on site authority and content quality.
Not necessary. A sitemap index only matters when you have multiple sub-sitemaps. If you have one sitemap.xml under 50K URLs, submit it directly.
Three usual causes: (1) URLs are duplicates after canonicalization (Google de-duplicates); (2) some URLs are blocked by robots.txt; (3) GSC is still processing — wait 7-14 days. If still gapped, validate the sitemap with an XML validator.
No — Google re-reads your submitted sitemaps automatically every few days. You only resubmit if you change the sitemap's URL or structure (e.g., new sub-sitemaps in the index).
Yes — GSC accepts multiple separate sitemap submissions. Useful when different sections of your site are generated by different systems (e.g., main site + a separate blog platform). Submit each as a separate sitemap.
Google Search Console
Most owners pick the wrong property type on day one and spend the next year staring at split data. Here's the setup the way SEO specialists actually do it — including the domain-property workflow that captures every subdomain and protocol.
Google Search Console
URL Inspection is the most-misused tool in GSC. People use it on the wrong URLs, hit the daily quota, and wonder why nothing gets indexed. Here's the correct workflow — and when to use it vs trust the sitemap.
Google Search Console
GSC's Indexing report shows you what's broken — in language that often hides what to actually do about it. This is the field-tested decoder: every error type, what causes it, and the specific fix that works.
Google Search Console
DIY SEO works longer than DIY ads — you can run on momentum for 12+ months. But there's a point where you're losing more in opportunity than you'd pay a specialist. Here's how to tell which side you're on.