WordPress Sitemap Opens in a Browser but Google Can’t Fetch It: What to Check

Your XML sitemap loads perfectly when you open it in Chrome. You can see the page and post URLs. Yet Google Search Console still lists the sitemap as “Couldn’t fetch.” Does that mean Google cannot find your website?

Not necessarily. A sitemap opening in your browser proves that your browser can retrieve it at that moment. It does not prove that Google’s crawler received the same response during an earlier attempt. The difference matters, because changing plugins or submitting the same URL repeatedly may not fix the underlying problem.

This guide explains how to investigate the mismatch in a sensible order—starting with low-risk checks and saving server or security changes until there is evidence they are needed.

First, understand what the error actually means

A sitemap is an XML file that helps search engines discover URLs on your website. Some WordPress installations have a sitemap index pointing to separate page, post, and taxonomy sitemaps. One child sitemap can work while another encounters a problem.

Google’s Sitemaps report documentation says “Couldn’t fetch” can mean Google could not retrieve the sitemap. A wrong URL, crawl restriction, or server availability problem may be involved. The warning is not proof that every page has disappeared from Google’s index.

Check the exact sitemap address in Search Console

Open the Sitemaps report for the correct Search Console property. Copy the submitted URL and open that exact address in a private browser tab. Watch for details that can be easy to miss:

  • Does it load at the expected HTTPS address, or redirect through another domain?
  • Does it show XML rather than a styled error page or website homepage?
  • Is the spelling correct, including the filename and path?
  • Are you checking the sitemap index, a child sitemap, or another file?

Do not assume every WordPress site uses the same sitemap path. WordPress core, SEO plugins, and hosting configurations may expose different endpoints. Use the URL your own site actually provides.

Compare what your browser sees with what the server returns

An error page can look reassuring while returning an incorrect HTTP status. A server might return successful 200, a redirect like 301, missing-file 404, or temporary 503. The status and response body both matter.

If you’re comfortable with browser developer tools, inspect the sitemap request in the Network panel. Otherwise, ask your host or developer to check the HTTP response for the exact sitemap URL and its final destination.

A good sign: the final URL returns a successful response and valid sitemap XML without a login screen, challenge page, or unexpectedly long redirect chain. This still does not establish that Google saw the same response, but it narrows the possibilities.

Web developer working across two computer monitors

Keep the original error details

Before changing a plugin, save the exact failing sitemap address, its current status code and the time Search Console last attempted to retrieve it. Those details help identify whether the failure is limited to a single endpoint or occurs across the site.

If you contact your host, request the server response for that address—not simply confirmation that the homepage loads.

Look for security rules that treat Google differently

Security plugins, firewalls, bot protection, and hosting-level rules sometimes treat automated requests differently from ordinary browser visits. A sitemap can therefore look healthy to you while an automated fetch receives a block, challenge, or rate limit.

Check security and hosting logs around the failed fetch time. Look for requests to the sitemap path that were denied, challenged, or served a non-XML response. If you find evidence, review the specific rule and its purpose before changing anything.

Do not disable your entire firewall just to test a sitemap. An exception should be narrowly scoped and based on verified logs. User-agent text alone is not reliable proof that a request came from Google; use Google’s instructions for verifying Google crawlers.

Check robots.txt without making broad changes

Open your site’s /robots.txt file and read the rules carefully. A disallow rule that blocks the sitemap path can prevent Google from retrieving it. However, a rule aimed at unrelated areas—such as the WordPress administration screen—does not automatically cause sitemap failure.

Do not delete robots.txt rules wholesale. Compare the affected sitemap path with applicable crawler rules and correct only a verified conflict. When relevant, check whether the file contains a Sitemap: line pointing to the intended sitemap URL.

When one sitemap works but another fails

Suppose the page sitemap opens but the post sitemap sometimes fails. That pattern is more useful than a general statement that “the sitemap is broken.” It points your investigation toward the specific endpoint rather than the whole site.

Compare the URLs and their response codes. Check whether the failing endpoint has different caching behavior, an unexpected error, or a plugin operation that intermittently fails. If caching or optimization is involved, inspect its configuration before purging or disabling anything.

For broader maintenance questions, read our guide to keeping a small-business website updated. Regular maintenance makes it easier to notice when a change introduces a new problem.

Use Search Console as evidence, not just a status label

Click the affected sitemap entry to inspect available error details and last-read information. Then examine Google’s crawling and page indexing reports for related symptoms. If additional inspection diagnostics are available, use them rather than assuming a browser result settles the issue.

Google also provides crawling troubleshooting guidance. Keep three distinct questions in mind:

  • Sitemap retrieval: Can Google obtain and read the XML file?
  • URL discovery: Does Google know a page exists through links or other signals?
  • Indexing: Does Google decide to include the page in search results?

Successful sitemap submission does not guarantee indexing. Conversely, a sitemap error does not prove Google has lost all previously discovered pages.

Person using a laptop at a table

Compare results from more than one viewpoint

A browser visit is a useful first check. Follow it with the website’s HTTP response information, available Search Console diagnostics, and a review of firewall logs when the error persists.

When the evidence agrees, you can troubleshoot a specific issue rather than repeatedly changing unrelated settings.

A safe troubleshooting order for WordPress owners

  1. Record the error. Note the submitted URL, last-read date, and details shown in Search Console.
  2. Test the exact URL. Check XML and redirects.
  3. Inspect the server response. Verify its status and whether content is served consistently.
  4. Review robots.txt. Find any rule blocking the sitemap path.
  5. Inspect security and hosting logs. Identify blocks or intermittent errors.
  6. Compare child sitemaps. If one fails, examine that endpoint.
  7. Correct the verified cause. Make the smallest safe change and record it.
  8. Recheck Search Console. Allow time for another fetch rather than repeatedly resubmitting without a change.

What not to do when Search Console says “Couldn’t fetch”

Avoid installing several sitemap plugins at once. Multiple generators can create competing endpoints and complicate the diagnosis. Don’t assume an SEO plugin update caused the problem without comparing before-and-after behavior. Don’t change your permalink structure simply because a sitemap report looks wrong.

If you must update plugins during your investigation, use our WordPress plugin update checklist to reduce the risk of introducing another issue.

When to ask for technical help

Seek help if the sitemap repeatedly serves server errors, automated requests receive security challenges, or the problem appeared alongside other site failures. A host or developer can examine response headers, logs, crawler verification, and plugin behavior together. Provide the exact URL and error details so the issue can be reproduced.

If you’re planning wider site improvements, explore our Rochester website design services for a starting point.

The bottom line

When a WordPress sitemap opens in your browser but Google says “Couldn’t fetch,” investigate the mismatch rather than rebuilding the site. Verify the URL, returned XML, crawler access, and server logs. Make only the change the evidence supports. The goal is a sitemap that can be retrieved reliably—not simply a green status message on one particular day.