WordPress XML Sitemap Not Working: 7 Proven Fixes (2026)

You have been publishing content consistently for months. Blog posts, landing pages, product pages — all live on your WordPress site. Then you open Google Search Console and see something that stops you cold:

“Couldn’t fetch.” “0 URLs submitted.” “Has errors.”

Your WordPress XML sitemap is not working — and until it is, Google is crawling your site without a roadmap. New content goes unnoticed. Rankings stall. Indexing delays stretch from days to weeks.

The worst part about a WordPress XML sitemap not working is that the problem is completely invisible from the frontend. Your site looks normal. Visitors browse normally. But Googlebot cannot find your pages efficiently — and you have no idea how long this has been going on.

This guide covers every reason a WordPress XML sitemap stops working, the exact diagnostic steps to find the cause, and the proven fixes — in the right order.

Google Search Console → Sitemaps — “Couldn’t fetch” or “0 URLs submitted” are the two most common signs that your WordPress XML sitemap is not working correctly

What Is a WordPress XML Sitemap and Why Does It Matter?

A WordPress XML sitemap is a structured file — located at yourdomain.com/sitemap.xml or yourdomain.com/sitemap_index.xml — that lists every important URL on your site. It tells Google which pages exist, when they were last updated, and how often they change.

WordPress does not generate a sitemap on its own. The sitemap is created and maintained by your SEO plugin — RankMath, Yoast SEO, or All in One SEO. When the sitemap works correctly, you submit its URL to Google Search Console and Google uses it to crawl and index your content efficiently.

When your WordPress XML sitemap is not working, Google still crawls your site — but it relies entirely on finding links between pages. New posts, freshly updated pages, and deep content that lacks internal links are consistently the last to get indexed. For a site publishing content regularly, a broken WordPress XML sitemap directly delays rankings.

Why Is Your WordPress XML Sitemap Not Working?

Quick Diagnosis — Which Type Do You Have?

Fix 1: Verify the Sitemap Feature Is Enabled in Your SEO Plugin

This is the most common reason a WordPress XML sitemap is not working — and the easiest to miss. After plugin updates, fresh installs, or site migrations, the sitemap generation toggle in your SEO plugin can get reset to OFF. No toggle = no sitemap file generated at all.

For RankMath Users

1. Go to WordPress Dashboard → RankMath → General Settings
2. Click the Sitemap tab in the left sidebar
3. Verify the main Sitemap toggle at the top is turned ON (blue)
4. Save changes → visit yourdomain.com/sitemap_index.xml to confirm it loads

RankMath → General Settings → Sitemap — the main toggle must be ON (blue) for your WordPress XML sitemap to generate. This is reset to OFF after some plugin updates and migrations.

For Yoast SEO Users

1. Go to SEO → Features in your WordPress dashboard
2. Find XML Sitemaps in the features list
3. Verify the toggle is turned ON
4. Save changes → visit yourdomain.com/sitemap_index.xml to confirm

Yoast SEO → Features → XML Sitemaps toggle — must be ON for your sitemap to generate. Your sitemap URL will be yourdomain.com/sitemap_index.xml

For All in One SEO Users

1. Go to All in One SEO → Sitemaps → XML Sitemap
2. Verify Enable Sitemap is toggled ON
3. Save → check yourdomain.com/sitemap.xml

Fix 2: Resolve the SEO Plugin Conflict

If you have both RankMath and Yoast SEO installed — even if one appears deactivated — your WordPress XML sitemap will not work correctly. Both plugins register their own sitemap generation routines with WordPress. When both are present, these routines conflict. The output is either a blank sitemap, a partial XML file, or an XML parsing error.

1. Go to WordPress Dashboard → Plugins → Installed Plugins
2. Check if both RankMath and Yoast SEO (or All in One SEO) appear in the list
3. Decide which SEO plugin you want to keep — the one you actively configure and use
4. For the plugin you are removing: click Deactivate → then click Delete
5. After deleting — visit your sitemap URL again: yourdomain.com/sitemap_index.xml
6. If the sitemap now loads cleanly — the conflict was the cause

Fix 3: Flush Permalink Rules and Purge Sitemap Cache

Two separate but related issues can cause a WordPress XML sitemap to stop working or show outdated URLs: stale WordPress permalink rewrite rules, and a caching plugin serving an old cached version of your sitemap.

Fix 3a — Flush Permalink Rules (Fixes 404 and Blank Sitemap)

WordPress builds your sitemap URLs using the same rewrite rule system that creates your post and page URLs. After a migration, server move, or certain plugin installations, these rules become stale. The sitemap URL returns a 404 or a blank page until the rules are rebuilt.

1. Go to WordPress Dashboard → Settings → Permalinks
2. Do not change your permalink structure — just click Save Changes with the existing setting
3. This flushes and rebuilds all WordPress rewrite rules including sitemap URL routing
4. Visit your sitemap URL again to confirm it now loads

Fix 3b — Purge Sitemap Cache (Fixes Missing New Posts in Sitemap)

If your sitemap loads but newly published content is not appearing in it, your caching plugin has stored a snapshot of the old sitemap. New posts exist on your site but are invisible to Google until the cache is purged and regenerated.

• LiteSpeed Cache: Dashboard → LiteSpeed Cache → Purge → Purge Sitemap. Then in your SEO plugin — regenerate the sitemap manually.
• WP Rocket: WP Rocket → Tools → Clear Cache → Clear All. Then regenerate sitemap from your SEO plugin settings.
• W3 Total Cache: Performance → Purge All Caches. Then regenerate sitemap.

Fix 4: Check Your robots.txt for Sitemap Blocking

This is the most surprising cause of a WordPress XML sitemap not working in Google Search Console — and it costs sites weeks of SEO progress before the owner discovers it. A robots.txt file that contains a Disallow rule matching your sitemap URL tells Googlebot not to access your sitemap — even though the file itself exists perfectly on your server.

How to Check Your robots.txt

1. Open a new browser tab
2. Navigate to yourdomain.com/robots.txt
3. Read every line of the file carefully
4. Look for any Disallow line that includes /sitemap, /sitemap.xml, or /sitemap_index.xml
5. Also check for wildcard rules like Disallow: /*.xml — this blocks all XML files including your sitemap

Your robots.txt should contain a Sitemap: line pointing to your sitemap URL — not a Disallow rule blocking it. A misconfigured robots.txt is a common hidden cause of WordPress XML sitemap not working in GSC.

What a Correct robots.txt Should Look Like

The Sitemap: line at the bottom actively tells Googlebot where your sitemap is located. Most SEO plugins add this line automatically when the sitemap feature is enabled. Verify it is present — and that no Disallow rule above it contradicts it.

How to Fix a Blocked robots.txt

1. In RankMath: go to RankMath → General Settings → Edit robots.txt → remove any Disallow line blocking the sitemap URL
2. In Yoast SEO: go to SEO → Tools → File Editor → edit robots.txt → remove conflicting Disallow rules
3. Via cPanel File Manager: open public_html/robots.txt → edit directly → save

Fix 5: Increase PHP Memory Limit for Large Sites

On large WordPress sites — those with hundreds of posts, WooCommerce stores with many products, or sites with multiple custom post types — PHP can run out of allocated memory while generating the sitemap. When this happens, the XML output gets cut off mid-file. The sitemap URL loads, but the XML is incomplete and unparseable — causing an XML parsing error in Google Search Console.

How to Confirm This Is the Cause

1. Open your sitemap URL: yourdomain.com/sitemap_index.xml
2. View the page source (Ctrl + U in Chrome)
3. Scroll to the very end of the source — if the XML does not end with a proper closing tag like </sitemapindex> — the output was cut off
4. A missing closing tag confirms the PHP memory limit is the cause

How to Fix the PHP Memory Limit

1. Open cPanel File Manager → public_html → wp-config.php
2. Add this line before the /* That’s all, stop editing! */ comment:

1. For WooCommerce stores or very large sites — use 512M instead of 256M
2. Save wp-config.php
3. Go to your SEO plugin settings and manually trigger a sitemap regeneration
4. Visit the sitemap URL again and check the source for the proper closing tag

Fix 6: Check for Cloudflare or Firewall Blocking

If your sitemap loads fine in your browser but Google Search Console consistently shows “Couldn’t fetch” — the issue may not be your WordPress setup at all. A Cloudflare WAF rule or a WordPress security plugin can be blocking Googlebot’s IP range from accessing /sitemap.xml, treating it as automated bot traffic.

How to Diagnose a Firewall Block

1. Open your sitemap URL in an incognito browser window — if it loads normally, your browser is fine
2. Go to Google Search Console → URL Inspection Tool
3. Enter your sitemap URL → click Test Live URL
4. If GSC’s live test shows an error but your browser loads it fine — a firewall is blocking Google’s crawlers specifically

Cloudflare Fix

1. Log into your Cloudflare dashboard → select your domain
2. Go to Security → WAF → Custom Rules
3. Review any rules that match URL paths containing sitemap or .xml
4. Add an exception or bypass rule for /sitemap*.xml to allow Googlebot through
5. Also check Security → Bots → Bot Fight Mode — if enabled, it can challenge Googlebot. Add Google’s crawlers to the allowlist.

Security Plugin Fix

• Wordfence: Wordfence → Firewall → Web Application Firewall → check for any rules blocking the sitemap URL pattern. Add an exclusion if needed.
• iThemes Security: Security → Settings → 404 Detection — aggressive 404 blocking can flag sitemap URLs from new crawlers. Add sitemap paths to the whitelist.
• All In One WP Security: Firewall → Basic Firewall Rules — check for any XML file blocking rules and add an exception for your sitemap.

Fix 7: Resubmit Your Sitemap in Google Search Console

After fixing the underlying cause — do not wait for Google to discover the change on its own. Google Search Console caches sitemap error states, and a “Couldn’t fetch” or “Has errors” status can persist for days even after your sitemap is fully functional again. Resubmitting forces an immediate fresh crawl attempt.

1. Open Google Search Console → Sitemaps in the left sidebar
2. Find your existing sitemap submission — note the current error status
3. Click on the sitemap URL → click the three-dot menu → select Remove sitemap
4. After removing — click Add a new sitemap
5. Enter your sitemap URL: sitemap_index.xml (for RankMath and Yoast) or sitemap.xml
6. Click Submit
7. Monitor the Coverage report over the next 24–48 hours to confirm URLs are being queued for indexing

Google Search Console → Sitemaps → delete the old error submission → resubmit fresh. This forces an immediate crawl attempt and clears the cached error state — essential after fixing a WordPress XML sitemap issue.

How to Prevent WordPress XML Sitemap Issues

• Never run two SEO plugins simultaneously: RankMath, Yoast, and All in One SEO cannot coexist. Pick one and fully delete the others. Check your plugin list quarterly — developers sometimes install a second SEO plugin for testing and forget to remove it.
• Purge sitemap cache after every content publish: Configure your caching plugin to exclude sitemap URLs from caching — or build a habit of purging the sitemap cache every time you publish a batch of new content. LiteSpeed Cache has a dedicated Purge Sitemap button for this reason.
• Check robots.txt after every security plugin update: Security plugins can add or modify robots.txt rules during updates. Verify yourdomain.com/robots.txt still contains a proper Sitemap: line and no conflicting Disallow rules after any security plugin update.
• Monitor GSC Coverage report weekly: The Coverage report shows you the exact number of submitted vs indexed URLs. A sudden drop or a “Has errors” status is the earliest warning sign that your WordPress XML sitemap has stopped working. Catching it early minimizes indexing delays.
• Check INP and Core Web Vitals after fixing: A sitemap outage can temporarily suppress rankings. After fixing — monitor your performance signals and read Fix INP in WordPress and Fix LCP in WordPress to ensure your recovery is complete.
• Use a site monitoring tool: Tools that regularly fetch your sitemap URL and alert you if it returns an error give you instant notification when the sitemap breaks — before Google has been crawling blind for days.

The Bottom Line

A WordPress XML sitemap not working is almost always caused by one of seven issues: sitemap feature disabled in your SEO plugin, plugin conflict between two SEO tools, stale permalink rules, cached outdated sitemap, robots.txt blocking, PHP memory limits, or a Cloudflare/firewall rule intercepting Googlebot. Work through the fixes in order and you will identify the cause before you reach Fix 5 in most cases.

The most important step after any fix is to resubmit your sitemap in Google Search Console immediately — not passively wait for Google to rediscover the change. A fresh submission triggers an immediate crawl attempt and clears the cached error state from your GSC dashboard.

The broader lesson: your WordPress XML sitemap is one of the most important files on your site for SEO, yet most site owners never check it after the initial setup. A monthly 30-second check of your GSC Sitemaps panel is enough to catch any issue before it causes meaningful ranking damage.

Related Articles

Frequently Asked Questions