You’ve added your website to Google Search Console, submitted your sitemap — and then you see it. Could Not Fetch. Or maybe it’s ” No Referring Sitemap Detected ” on your crawled pages. Either way, your sitemap isn’t being read, your pages aren’t getting indexed, and your site is invisible on Google. This guide covers every known cause of the couldn’t fetch sitemap error and walks you through each fix, step by step — whether you’re on WordPress with Rank Math, WordPress with Yoast SEO, or Blogger.
Table of Contents
- What Does “Could Not Fetch” Mean in Google Search Console?
- Step 1: Verify Your Sitemap URL Is Correct
- Step 2: Make Sure Your Sitemap Is Enabled in Your SEO Plugin
- Step 3: Fix “No Referring Sitemap Detected” Errors
- Step 4: Regenerate Your Sitemap
- Step 5: Check Your robots.txt File
- Step 6: Resolve Plugin and Theme Conflicts
- Step 7: Clear Your Cache
- Step 8: Fix Your Permalink Structure
- Step 9: Check Firewall and Hosting Issues
- Step 10: Fixing the Could Not Fetch Error on Blogger
- Step 11: Resubmit Your Sitemap and Request Indexing
- Final Thoughts
What Does “Could Not Fetch” Mean in Google Search Console?
When Google Search Console displays a Could Not Fetch error next to your submitted sitemap, it means Google’s crawler tried to access your sitemap URL and failed. It couldn’t read the file. As a result, Google has no map of your site’s pages — so it either doesn’t know they exist, or it can’t confirm they should be indexed.
This is different from a page being crawled and not indexed. A Could Not Fetch error is earlier in the chain — your sitemap itself is the problem, not the individual pages. Until this error is resolved, your posts will not reliably show up on Google, regardless of how good your content is or how strong your SEO is otherwise.
The good news: this error is almost always fixable. There are a handful of root causes — a wrong URL, a disabled sitemap feature, a caching conflict, a firewall blocking Google’s crawler, or a misconfigured robots.txt file — and each one has a clear solution. Let’s go through them one by one.
➡️ How to Increase Domain Authority: Proven Step-by-Step Guide
Step 1: Verify Your Sitemap URL Is Correct
The first thing to check — before anything else — is whether the sitemap URL you submitted to Google Search Console is actually correct and accessible. This sounds obvious but is one of the most common causes of the Could Not Fetch error.
If you’re using Rank Math SEO, go to your WordPress dashboard, navigate to Rank Math → Sitemap Settings → General tab. Your sitemap index URL will be displayed there. Copy it exactly.
If you’re using Yoast SEO, your sitemap URL is typically yourdomain.com/sitemap_index.xml. You can find the direct link in Yoast SEO settings under the XML Sitemaps section.
Once you have the URL, paste it directly into your browser and press Enter. It should open and display a list of sitemaps being fetched — posts, pages, categories, and so on. If it loads correctly in the browser, the URL is valid. If you get a 404 Not Found error or a blank page, your sitemap needs to be regenerated. If nothing shows at all, there may be a plugin conflict or the sitemap feature is disabled — both covered below.
Step 2: Make Sure Your Sitemap Is Enabled in Your SEO Plugin
A very common reason for the Could Not Fetch error is simply that the sitemap feature was never turned on — or was accidentally disabled.
For Rank Math users: Go to Rank Math → Sitemap Settings. Make sure the sitemap toggle is active. Then check that Posts, Pages, and Categories all have Include in Sitemap enabled. If you run a WooCommerce store, ensure Products and Product Categories are also included. Without these being active, those content types won’t appear in your sitemap at all.
Also go to Rank Math → Titles & Metas and confirm that the Robots Meta is set to Index — not No Index. If your global setting is No Index, Google won’t index anything regardless of what your sitemap says.
For Yoast SEO users: Go to Yoast SEO → Settings and look for the XML sitemap toggle. Confirm it is turned on. Click the link provided in the settings to view your sitemap and check that it loads correctly and is properly formatted. If the toggle is on but the sitemap still shows an error or appears empty, move on to the steps below.
Step 3: Fix “No Referring Sitemap Detected” Errors
If you’re seeing No Referring Sitemap Detected when inspecting individual URLs in Search Console, it means those specific pages aren’t being picked up by your sitemap. This often happens alongside the Could Not Fetch error, or it can appear independently even after your sitemap is submitted.
The fix involves two things. First, go back into your SEO plugin settings and confirm that the content type for that page or post is included in the sitemap (as described in Step 2). Second, open the individual page or post in the WordPress editor, click on the Rank Math or Yoast SEO icon, go to Advanced settings, and confirm the Robots Meta is set to Index. Sometimes individual pages get accidentally set to No Index, which removes them from the sitemap and prevents indexing entirely. Save the change, then go to Search Console and request indexing for that URL.
Also remove and resubmit your sitemap in Search Console if it’s been sitting there for a month or two without updates. Go to Sitemaps, click the three dots next to your existing sitemap, remove it, then resubmit the correct URL fresh. Old, stale sitemap submissions can cause persistent fetch errors even if the sitemap itself is now working correctly.
➡️ Page Is Indexed but Not Showing in Google Search Results? (Fix Guide
Step 4: Regenerate Your Sitemap
If your sitemap URL returns a 404 error or loads as empty, the sitemap file needs to be regenerated. This is a straightforward process.
For Rank Math users: There’s a useful trick that forces Rank Math to regenerate the sitemap. Go to Rank Math → Sitemap Settings and change the posts per sitemap value from 200 to 199. Save the settings. Then open your sitemap URL in the browser to confirm it now loads. After that, go back and change the value from 199 back to 200 and save again. This toggle triggers Rank Math to rebuild the sitemap files from scratch, and it resolves a surprising number of Could Not Fetch errors.
For Yoast SEO users: Disable the XML sitemap feature in Yoast settings, clear all your caches, then re-enable the sitemap feature. This forces Yoast to regenerate the sitemap files. After re-enabling, verify the sitemap loads correctly in the browser before resubmitting to Search Console.
Step 5: Check Your robots.txt File
Your robots.txt file tells Google’s crawler what it can and cannot access on your site. If this file is misconfigured or missing a reference to your sitemap, it can cause fetch errors or incomplete crawling.
To check your robots.txt file, type yourdomain.com/robots.txt in your browser. It should load and display rules. A healthy robots.txt for most WordPress sites includes a line like Sitemap: https://yourdomain.com/sitemap_index.xml pointing to your sitemap. If this line is missing, you need to add it manually.
You can access and edit your robots.txt file through your hosting file manager — look inside the public_html folder. Alternatively, both Rank Math and Yoast SEO have built-in robots.txt editors in their settings. If you don’t have direct server access, a free WordPress File Manager plugin will give you access to the file through your dashboard. Always keep a backup before editing any server-level file.
For Blogger users: Go to Settings → scroll down to find Enable Custom Robots TXT. Enable it, then click on Custom Robots Text and add the correct robots.txt content including your sitemap URL in the format https://yourdomain.com/sitemaps.xml. Save it. This step is critical for Blogger sites — without proper robots.txt configuration, Google’s crawler can’t confirm it has permission to access your content, which leads directly to the Could Not Fetch error.
Step 6: Resolve Plugin and Theme Conflicts
Plugin conflicts are one of the most frustrating causes of the Could Not Fetch error because they’re not obvious. Two types of plugins commonly cause problems: security plugins and duplicate sitemap plugins.
Security plugins like Wordfence or Cloudflare’s WordPress plugin can block Google’s crawler from accessing your sitemap URL, treating it like a suspicious external request. If you have a security plugin installed, temporarily deactivate it, then go back to Search Console and try fetching the sitemap again. If it suddenly works, the security plugin was the culprit. You’ll need to whitelist Google’s crawler IP ranges in the plugin’s settings, or configure an exception for the sitemap URL, rather than keeping the plugin permanently disabled.
If you have any other plugins installed that generate their own sitemaps — older SEO plugins, standalone sitemap generators — deactivate and remove them. Two plugins generating competing sitemaps creates conflicts that can break both. Only one sitemap source should be active on your site at a time.
Themes can also occasionally interfere with sitemap generation. If you’ve tried everything else and the sitemap still won’t load, temporarily switch to a default WordPress theme like Twenty Twenty-Four and test whether the sitemap becomes accessible. If it does, your theme is causing the conflict and you’ll need to investigate its code or contact the theme developer.
➡️ My Website Is Indexed But Not Ranking : The 2026 Recovery Guide
Step 7: Clear Your Cache
Caching is another hidden culprit. If your site uses a caching plugin — W3 Total Cache, WP Super Cache, LiteSpeed Cache, or server-level caching through your host — it may be serving an outdated or empty version of your sitemap to Google’s crawler.
After making any changes to your sitemap settings, always clear all caches immediately. In LiteSpeed Cache, go to the LiteSpeed menu in your WordPress dashboard and click Purge All. In W3 Total Cache, go to Performance → Dashboard and click Empty All Caches. In WP Super Cache, go to Settings → Delete Cache.
It’s also worth going into your caching plugin settings and explicitly excluding your sitemap URL from being cached. The sitemap is a dynamic file that needs to update every time you publish new content — caching it defeats the purpose and can cause persistent Could Not Fetch errors even after other issues are resolved.
Step 8: Fix Your Permalink Structure
An incorrectly configured permalink structure in WordPress can break sitemap URLs and cause fetch errors in Search Console. This is a quick fix that’s easy to overlook.
Go to WordPress Dashboard → Settings → Permalinks. Make sure the permalink structure is set to Post Name — this is the recommended setting for both SEO and sitemap compatibility. Once you’ve confirmed this, click Save Changes even if you didn’t change anything. Simply saving the permalink settings flushes the rewrite rules in WordPress, which can resolve sitemap URL conflicts caused by outdated rewrite rules.
Step 9: Check Firewall and Hosting Issues
If you’ve worked through all the steps above and still see Could Not Fetch, the problem may be at the server level. Firewalls, slow server response times, and hosting restrictions can all prevent Google from successfully fetching your sitemap.
Contact your hosting provider’s support team and ask them to check whether any firewall rules are blocking Googlebot from accessing your sitemap URL. Some managed hosting providers apply aggressive firewall rules by default that can inadvertently block crawlers. Ask them specifically about firewall blocking and server response time for the sitemap URL.
Also make sure your SEO plugin is up to date. Go to WordPress Dashboard → Plugins and check whether Rank Math, Yoast, or any other SEO plugin has an available update. Outdated plugins can have bugs that affect sitemap generation. Always take a backup before updating plugins, then update and clear your cache afterward.
➡️ Crawled – Currently Not Indexed: What It Means & How to Fix
Step 10: Fixing the Could Not Fetch Error on Blogger
If your site runs on Blogger rather than WordPress, the process is a little different but the core principle is the same — your sitemap URL needs to be correct, accessible, and referenced properly in your robots.txt configuration.
Make sure your Blogger account and your Google Search Console account are both on the same Gmail address. If they’re on different accounts, you’ll need to manually verify ownership. Using the same Gmail enables automatic verification and avoids a layer of complexity.
In your Blogger dashboard, go to Settings → scroll down to Enable Custom Robots TXT and enable it. Then set up your Custom Robots Text with the correct user-agent rules and your sitemap URL. The sitemap URL for Blogger is typically yourdomain.com/sitemaps.xml. Save it.
In Google Search Console, submit sitemaps.xml as your sitemap. Note that when you first submit it, you will see the Could Not Fetch error immediately — this is normal for Blogger sites. It typically takes three to four days for the submission to become successful. Don’t resubmit repeatedly thinking something is wrong. Give it the time it needs.
If you want Google to index more than 500 posts, you can also submit an atom.xml?redirect=false&start-index=1&max-results=500 feed URL alongside your sitemap, adjusting the max-results number as your content grows past 500 or 1,000 posts.
Step 11: Resubmit Your Sitemap and Request Indexing
Once you’ve worked through the fixes above and confirmed your sitemap URL loads correctly in the browser, it’s time to resubmit it to Google Search Console and request indexing for affected pages.
In Search Console, go to Sitemaps. If your old sitemap submission is still showing an error, remove it using the three-dot menu. Then paste your correct sitemap URL and click Submit. For Rank Math users this is typically yourdomain.com/sitemap_index.xml. For Yoast it’s also sitemap_index.xml. For Blogger it’s sitemaps.xml.
For individual pages showing “No Referring Sitemap Detected,” use the URL Inspection tool in Search Console. Paste the page URL, click Test Live URL to confirm Google can now access it, and then click Request Indexing. Manual indexing requests process faster than waiting for Google’s regular crawl cycle — expect one to seven days for the page to be indexed after a successful request.
If the indexing request gets rejected, don’t panic. As long as your sitemap is now being fetched successfully and the page passes the live URL test, Google will index it in its next crawl. A rejection on the manual request doesn’t mean the page won’t be indexed — it often just means Google’s queue is full at that moment.
If after resubmission you still see Could Not Fetch, wait one to two days and resubmit again. Sometimes Google’s crawler is simply delayed, and a fresh submission after a short wait resolves the issue without any further changes needed on your end.
Final Thoughts
The Could Not Fetch sitemap error in Google Search Console looks alarming but is almost always fixable with a systematic approach. Start by verifying your sitemap URL is correct and loads in the browser. Check that your SEO plugin has sitemaps enabled and your content types are included. Clear your caches, check for plugin conflicts — especially security plugins — and make sure your robots.txt file references your sitemap correctly. If hosting-level issues are involved, your support team can help.
Work through each step methodically rather than trying random fixes and hoping one works. Most Could Not Fetch errors resolve within one to two days of the correct fix being applied. Once your sitemap is being fetched successfully, Google will begin indexing your pages — and your content will start appearing in search results where it belongs.
