If you are seeing “Couldn't fetch,” “Couldn't read,” or other sitemap errors in Google Search Console after installing or configuring Yoast SEO, there is usually no need to panic. In many cases, the problem is related to an outdated sitemap, caching, incorrect WordPress settings, server configuration, or unnecessary sitemap URLs.
Yoast SEO automatically creates an XML sitemap for your WordPress website. It helps search engines discover important pages, posts, categories, and other indexable content. However, if unnecessary content types or archives are enabled, your sitemap structure may become difficult to manage.
In this guide, you will learn how to fix Yoast SEO sitemap errors step by step, clean up unnecessary sitemap entries, refresh the sitemap, clear cache, and resubmit the correct sitemap in Google Search Console.
What Is a Yoast SEO Sitemap?
A sitemap is an XML file that tells search engines about the URLs that are available for crawling and indexing.
When Yoast SEO is active, it normally generates a sitemap index such as:
https://example.com/sitemap_index.xml
This sitemap index can contain separate sitemaps for different content types, such as:
Posts
Pages
Categories
Tags
Authors
Other custom post types
For example, a website may have URLs such as:
post-sitemap.xml
page-sitemap.xml
category-sitemap.xml
The exact sitemap files depend on the content and configuration of your WordPress website.
Google Search Console doesn't require you to submit every individual sitemap manually when Yoast's sitemap index is working correctly. In most situations, submitting the main sitemap_index.xml is sufficient.
Common Yoast SEO Sitemap Errors
Before fixing the problem, it is useful to understand what Google Search Console is reporting.
Some common sitemap-related messages include:
Couldn't fetch
Couldn't read sitemap
Sitemap could not be read
Sitemap has errors
Sitemap is HTML
Submitted URL blocked by robots.txt
Server error
Redirect error
Invalid XML
Sitemap could not be accessed
The cause can be different for every website. Therefore, don't immediately delete all sitemap files or change multiple SEO settings at once.
Why Do Yoast Sitemap Errors Occur?
There are several possible reasons for Google Search Console sitemap errors.
1. Cached Sitemap
Your website may still be serving an older cached version of the sitemap after changing Yoast settings.
This can happen when you use:
WordPress caching plugins
Server-side caching
CDN caching
Cloudflare caching
Hosting-level caching
This is commonly referred to as a Yoast sitemap cache issue.
2. Unnecessary Content Types
WordPress websites often contain content types that you don't want indexed in Google.
For example:
Elementor templates
Custom post types
Internal utility pages
Unused tags
Low-value archives
If these content types are configured to appear in search results, Yoast may include them in the sitemap.
3. Date or Author Archives
Date and author archive pages can sometimes create unnecessary URLs, particularly on small websites or single-author blogs.
For example:
/2026/08/
or:
/author/admin/
If these pages don't provide unique value, you may prefer to disable them.
4. Attachment Pages
WordPress can create attachment-related URLs for uploaded images and other media. These pages often don't provide meaningful standalone content.
This is why website owners sometimes search for solutions to remove attachment sitemap Yoast.
5. Server or WordPress Configuration
A sitemap problem isn't always caused by Yoast.
It can also result from:
Incorrect redirects
Firewall rules
Security plugins
Robots.txt restrictions
Server errors
Incorrect HTTPS configuration
XML being returned as HTML
Temporary hosting problems
So, if changing Yoast settings doesn't solve the issue, check the sitemap URL directly in your browser.
How to Fix Yoast SEO Sitemap Errors Step by Step?
Step 1: Check Your Yoast Sitemap URL
Before changing anything, verify whether Yoast is generating a sitemap correctly.
Open your browser and visit:
https://yourdomain.com/sitemap_index.xml
Replace yourdomain.com with your actual domain.
If the sitemap opens and displays an XML sitemap index, Yoast is probably generating the sitemap correctly.
If you receive:
404 error
403 Forbidden
500 server error
Redirect loop
Blank page
HTML page instead of XML
then the problem may require additional troubleshooting.
Don't submit a broken sitemap to Google Search Console until the URL works correctly.
Step 2: Review Yoast SEO Content Types
Log in to your WordPress dashboard.
Go to:
Yoast SEO → Settings
Review the available content types and determine which ones should appear in Google search results.
Your important content should normally remain available for search engines.
For example:
Blog Posts
Important Pages
Relevant custom post types
However, unnecessary or internal content should generally not be exposed as indexable search content.
If you find a custom post type that shouldn't appear in Google, review its Show in search results setting.
Important
Don't disable a content type simply because it appears in the sitemap.
First determine whether those URLs are genuinely useful for search users.
How to Submit Wordpress site to Google Search Console
Step 3: Disable Date Archives in WordPress
If your website doesn't need date-based archive pages, you can disable them through Yoast SEO.
Go to:
Yoast SEO → Settings → Advanced → Date archives
Look for the option related to enabling date archives.
If your website doesn't benefit from date archive pages, disable the feature and save the settings.
This is one of the common solutions searched for as disable date archives WordPress.
Should You Always Disable Date Archives?
No.
Date archives aren't automatically bad for SEO.
If your website genuinely uses chronological archives—for example, a news website or publication—they may have a legitimate purpose.
For a small blog where date archive pages provide little additional value, disabling them can simplify the site's indexable URL structure.
Step 4: Review Author Archives
Author archives can also create additional URLs.
For example:
https://example.com/author/admin/
If your website has multiple active authors and the author pages provide useful information, you may want to keep them.
However, if you're running a simple single-author blog and the author archive doesn't provide unique value, disabling it can reduce unnecessary archive URLs.
Go to the relevant Author Archives settings in Yoast SEO and configure them according to your website structure.
Again, the goal isn't to remove URLs just because they exist. The goal is to keep useful, indexable content and avoid unnecessary pages.
Step 5: Review WordPress Attachment Pages
WordPress media files can sometimes create attachment-related URLs.
For many websites, these pages don't provide enough standalone content to deserve separate search visibility.
Yoast SEO provides settings for handling attachment URLs.
If your website doesn't use standalone attachment pages, make sure media URLs are configured appropriately rather than allowing unnecessary attachment pages to become part of your site's indexable structure.
This is particularly relevant if you're troubleshooting remove attachment sitemap Yoast issues.
Don't Delete Your Images
Disabling or redirecting attachment pages does not mean deleting your images from the Media Library.
Your original image files can continue to be used inside your posts and pages.
Step 6: Refresh the Yoast Sitemap
After changing SEO settings, your website may continue serving cached sitemap information.
This is where a Yoast sitemap cache issue can sometimes occur.
First, save your Yoast settings.
Then open your sitemap again:
https://yourdomain.com/sitemap_index.xml
Check whether the sitemap reflects your latest changes.
If your website still appears to be serving an outdated sitemap, continue with the cache-clearing steps below.
Step 7: Clear WordPress and Server Cache
If you're using a caching plugin, clear its cache.
Popular caching solutions include:
LiteSpeed Cache
WP Rocket
W3 Total Cache
WP Super Cache
Hosting-level cache
If your website uses Cloudflare or another CDN, purge the relevant cache as well.
After clearing the cache, open the sitemap in an incognito/private browser window.
You should see the current sitemap rather than an older cached version.
Don't Clear Everything Without Reason
If your caching system provides a specific purge option for the affected URL, you can use that instead of unnecessarily clearing every cached resource.
Step 8: Refresh WordPress Permalinks
Another simple troubleshooting step is to refresh WordPress permalinks.
Go to:
WordPress Dashboard → Settings → Permalinks
You don't necessarily need to change your permalink structure.
Simply click:
Save Changes
This forces WordPress to refresh its rewrite rules.
Now open your sitemap again:
https://yourdomain.com/sitemap_index.xml
Check whether it loads correctly.
Step 9: Check Robots.txt
A sitemap may be generated correctly but still have crawling problems if your robots.txt file blocks important URLs.
Open:
https://yourdomain.com/robots.txt
Look for rules that could block access to your sitemap or important website sections.
Your sitemap location can also be declared in robots.txt, for example:
Sitemap: https://example.com/sitemap_index.xmlMake sure your sitemap URL uses the correct HTTPS domain and matches your preferred website version.
Step 10: Test the Sitemap in Google Search Console
Once your sitemap works correctly in the browser, open Google Search Console.
Select your website property and go to:
Indexing → Sitemaps
In the Add a new sitemap field, enter:
sitemap_index.xml
Then click Submit.
You generally don't need to submit every individual Yoast sitemap if the sitemap index contains them.
For example, submitting:
https://example.com/sitemap_index.xml
is usually preferable to manually submitting:
post-sitemap.xml
page-sitemap.xml
category-sitemap.xml
and other child sitemaps separately.
What About Old Sitemap Errors in Google Search Console?
This is an important point.
You may fix the website today but continue to see an older sitemap entry or error in Search Console for some time.
Don't assume that an old historical error means your current sitemap is still broken.
First check the current sitemap directly in your browser.
Then check its latest status in Google Search Console.
Google needs time to recrawl and process the updated sitemap.
Should You Remove Old Sitemaps From Google Search Console?
If you previously submitted unnecessary sitemap URLs manually, you can review them under:
Google Search Console → Indexing → Sitemaps
If an old or unnecessary sitemap is no longer relevant, you can remove the submitted sitemap entry.
However, don't remove a sitemap merely because it contains a child sitemap generated by Yoast.
If your current sitemap_index.xml is working correctly, Google can discover the child sitemaps through the index.
How to Fix “Couldn't Fetch” Yoast Sitemap Error
If Google Search Console reports Couldn't fetch, follow this quick checklist:
- Open
sitemap_index.xmlin your browser. - Check whether it returns valid XML.
- Confirm that the URL doesn't redirect incorrectly.
- Check your robots.txt file.
- Clear WordPress cache.
- Clear CDN/server cache.
- Check firewall and security plugins.
- Refresh WordPress permalinks.
- Verify that your website is accessible over HTTPS.
- Resubmit the sitemap index in Google Search Console.
If the sitemap doesn't open in a normal browser, fixing the Search Console submission alone won't solve the underlying problem.
Yoast Sitemap SEO Best Practices
A clean sitemap should focus on URLs that you actually want search engines to discover and potentially index.
Follow these best practices:
| Best Practice | What to Do |
|---|---|
| Use one main sitemap index | Submit sitemap_index.xml |
| Keep valuable content | Include important posts and pages |
| Review custom post types | Disable unnecessary indexable content |
| Review date archives | Disable them if they provide no value |
| Review author archives | Keep only when useful |
| Handle attachment pages | Avoid unnecessary attachment URLs |
| Clear cache | Refresh WordPress, CDN and server cache |
| Check robots.txt | Don't block important sitemap URLs |
| Use HTTPS | Make sure the sitemap uses the correct HTTPS URL |
| Monitor Search Console | Check sitemap status after changes |
Frequently Asked Questions
Q 1. Why is Yoast sitemap not showing in Google Search Console?
If your Yoast sitemap isn't showing correctly, first open sitemap_index.xml directly in your browser. If it works, check caching, robots.txt, server accessibility, and the sitemap submission in Google Search Console.
Q 2. How do I fix Yoast SEO sitemap errors?
To fix Yoast SEO sitemap errors, verify the sitemap URL, review Yoast content settings, disable unnecessary archives, clear WordPress and server cache, refresh permalinks, check robots.txt, and resubmit the sitemap index in Google Search Console.
Q 3. Should I disable date archives in WordPress?
If date archives don't provide unique value to your visitors, disabling them can reduce unnecessary archive URLs. However, date archives can be useful for news and publication websites, so the correct setting depends on your site's structure.
Q 4. How do I remove an attachment sitemap in Yoast?
Review your Yoast SEO media and attachment settings and configure attachment URLs so they don't create unnecessary indexable pages. Don't delete the original images from your WordPress Media Library.
Q 5. Should I submit post-sitemap.xml separately?
Usually, no. If Yoast's sitemap_index.xml is working correctly, submitting the main sitemap index allows Google to discover the child sitemaps automatically.
Q 6. Does a sitemap error directly lower rankings?
A sitemap error does not automatically mean your rankings will drop. The important question is whether Google can discover and crawl your important URLs through other means. However, a broken or incomplete sitemap can make URL discovery less efficient, so it should still be fixed.
Final Thoughts
Fixing Yoast SEO sitemap errors is usually a combination of checking your sitemap, cleaning unnecessary indexable content, refreshing WordPress settings, clearing caches, and verifying the result in Google Search Console.
Start by opening:
https://yourdomain.com/sitemap_index.xml
If it loads correctly, review your Yoast SEO settings and remove unnecessary archive or content types only when they don't provide value to your visitors.
Next, clear your WordPress, CDN, and server cache, refresh your permalinks, check robots.txt, and finally submit the sitemap index again in Google Search Console.
Most importantly, don't try to fix every sitemap warning by blindly disabling content types. A good SEO sitemap should contain the important URLs you want search engines to discover, while unnecessary or low-value pages should be handled through the appropriate WordPress and Yoast settings.
With a clean sitemap structure and correctly configured WordPress SEO settings, you make it easier for search engines to discover and understand the important content on your website.
