You submitted your sitemap to Google Search Console, but after days the number of indexed URLs hasn't moved. Or you see a “Couldn't fetch” error. It's a common issue, and the fix is often simpler than you think.
We at Meteora Web see dozens of sites with misconfigured sitemaps: wrong paths, invalid XML, robots.txt blocking Googlebot. This guide cuts straight to the point: how to submit a sitemap in GSC, verify it works, and solve the most frequent errors.
Why submit a sitemap in Google Search Console?
Google finds pages mainly through links and crawling. An XML sitemap is not mandatory, but it's a direct signal telling Google: “Here are my important pages, index them.” It's essential for sites with:
- Frequently updated content (blogs, e-commerce)
- Pages isolated from internal links (e.g., landing pages)
- Large volumes of URLs (over a few hundred)
A common mistake: submitting a sitemap but never updating it. Google doesn't re-read it magically every day — you must force a request via GSC or update the file. Without a sitemap, some pages stay invisible for weeks.
Sponsored Protocol
How to correctly submit a sitemap in GSC?
1. Create a valid XML sitemap
The standard format uses <urlset>, <url> and <loc>. Example:
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://www.yoursite.com/</loc>
<lastmod>2025-03-15</lastmod>
<priority>1.0</priority>
</url>
<url>
<loc>https://www.yoursite.com/about</loc>
<lastmod>2025-02-20</lastmod>
<priority>0.8</priority>
</url>
</urlset>2. Upload to your domain root
Place the file at the root of your domain, e.g., https://www.yoursite.com/sitemap.xml. WordPress users: SEO plugins like Yoast auto-generate a sitemap index.
Sponsored Protocol
3. Submit in Google Search Console
In GSC, go to “Sitemaps”, enter the relative URL (e.g. sitemap.xml) and click “Submit”.
Common sitemap errors in GSC and how to fix them
“Couldn't fetch”
Google cannot download the file. Causes: wrong path, blocked by .htaccess or firewall, server timeout. Use URL Inspection Tool to test.
“Redirect error”
The sitemap redirects. Ensure the URL is final with no 301/302.
“URL blocked by robots.txt”
Check robots.txt – it must allow access to the sitemap path. Example: Allow: /sitemap.xml.
“Invalid XML”
Syntax errors. Validate with an online validator. Common: missing encoding, & instead of &.
Sponsored Protocol
How to verify indexing status after submitting
GSC shows submitted vs indexed URLs. Click on “Indexed URLs” for details. Use the “Indexing” report to see specific errors. After 48 hours, check again. If zero indexed, test a single URL with URL Inspection.
What to do now
- 1. Check your current sitemap – open
https://yoursite.com/sitemap.xmlin browser. If missing, generate one. - 2. Submit it to GSC – if already there, review the status. If not, submit now.
- 3. Fix any errors – use the solutions above. Test a single URL with URL Inspection.
For a complete deep dive into GSC and indexing, check our Advanced Google Search Console Pillar Guide.
Need help with your sitemap or indexing? We at Meteora Web handle this every day. Contact us.
