What Yoast's XML Sitemaps Do and When Disabling Makes Sense

Yoast SEO generates a sitemap index at a standard path on your domain, with child sitemaps for posts, pages, custom post types, and taxonomies. Search engines use it to discover URLs, which is genuinely useful on large sites, on sites with weak internal linking, and on new sites with few external links.

So the first question is whether you should disable it at all. In most cases you should not. There are, however, four situations where switching it off is correct. The first and most common is a conflict: another SEO plugin, a caching or ecommerce plugin, or your hosting platform is also producing a sitemap, and two competing sitemaps at different URLs create confusion about which is authoritative. The second is that you have built a custom sitemap that includes logic Yoast cannot express. The third is that your site is genuinely tiny and fully internally linked, so the sitemap adds nothing. The fourth is a temporary staging or private environment where you do not want any discovery surface at all.

If your actual problem is that the sitemap contains URLs you do not want indexed, disabling it is the wrong fix. Exclude those content types instead, which is covered below.

Need a Second Opinion? AAMAX.CO Can Audit It First

We are AAMAX.CO, a full service digital marketing company offering web development, digital marketing, and SEO worldwide, and sitemap misconfiguration is one of the most frequent findings in our WordPress audits. Sometimes the right answer is to disable Yoast's sitemap because another system owns it; more often the sitemap is fine and the real problem is indexation rules, thin archive pages, or canonical conflicts. We diagnose before we change anything, then implement in a way that survives plugin and theme updates. If you would rather have that judgement call made by people who do it daily, hire us for SEO services and we will audit your setup before touching a switch.

Before You Change Anything: Back Up and Record the Current State

Take a database backup or a full site snapshot. Then note what exists today: load your sitemap index in a browser and record which child sitemaps it lists and roughly how many URLs each contains. Check Google Search Console and note which sitemaps are submitted and their last read date. If you disable the sitemap without recording this, you will not be able to tell later whether an indexing change was caused by your edit or by something else.

If you are on a live site with meaningful traffic, make the change during a quiet period and plan to monitor coverage reports for the following two weeks.

Method One: Disable From the Yoast Settings Screen

In recent versions of Yoast SEO the sitemap toggle lives under the plugin's general settings, on the site features or features tab, listed as XML sitemaps. Switch it off and save. In older versions the same control sits under the plugin's general settings on a features tab with an on and off toggle per feature.

Once saved, load your sitemap index URL again. You should now get a redirect or a not found response rather than the sitemap. If the sitemap still renders, your page cache or CDN is serving a stored copy: purge both and retest. On some hosts you also need to flush a server-level object cache.

This method is the right choice for most site owners because it is reversible in one click and it survives plugin updates.

Method Two: Disable With a Filter in Code

If you manage a site where plugin settings are locked down, or you want the state enforced in version control rather than in the database, use Yoast's filter for sitemap output. Add a small snippet to a child theme functions file or, better, a small must-use plugin, returning false for the sitemap enable filter. Keeping it in a must-use plugin or a code snippet plugin means a theme switch cannot silently re-enable the sitemap.

Do not edit the Yoast plugin files directly. The change will be wiped on the next update and you will spend an afternoon working out why the sitemap came back.

Method Three: Disable Only Part of the Sitemap

This is what most people actually need. Rather than removing the whole sitemap, exclude the parts that should not be indexed.

Inside Yoast, the content types and taxonomies settings control whether each post type and each taxonomy appears in search results, and anything set to not show in search results is automatically excluded from the sitemap. That single setting solves the majority of complaints about unwanted URLs, particularly for tag archives, date archives, author archives on single-author sites, and utility post types created by other plugins.

For finer control there are filters to exclude specific post types, specific taxonomies, or individual post IDs from the sitemap. Use these when a plugin registers a post type you cannot configure through the interface. The advantage of partial exclusion is that you keep the discovery benefit for real content while removing the noise.

What to Do Immediately After Disabling

If you disabled the Yoast sitemap because another plugin or platform provides one, submit that sitemap in Search Console and remove the old Yoast sitemap submission so you stop receiving errors for a URL that no longer exists.

Check your robots file. If it references the Yoast sitemap path, update the reference to the new sitemap or remove it. A robots file pointing at a dead sitemap is a small but avoidable error.

If you disabled the sitemap entirely with no replacement, make sure your internal linking can carry the load. Every page you care about should be reachable from your navigation or from body links within two or three clicks of the homepage, because that is now the only discovery route crawlers have.

Then watch Search Console coverage for two to four weeks. A slow decline in indexed pages on a large site is a sign the sitemap was doing more work than you thought, and re-enabling it is a one-click fix.

Troubleshooting Common Outcomes

If the sitemap URL still loads, it is almost always caching, but it can also be another plugin generating a sitemap at the same path. View the output and check whether the formatting matches Yoast's.

If you see a sudden drop in impressions rather than a gentle one, the cause is probably not the sitemap. Check for an accidental noindex, a robots disallow, or a canonical change made in the same session, because sitemap removal alone rarely produces an abrupt collapse.

If your host or a security plugin blocks sitemap access with a firewall rule, the sitemap may appear disabled when it is only inaccessible. Test from an incognito window and, ideally, with a crawler user agent.

The Short Answer

Disable Yoast's XML sitemaps through the plugin's own settings toggle when another system owns your sitemap, use a filter when you need the state enforced in code, and use per-content-type exclusion when the real goal is cleaner indexation rather than no sitemap at all. Always back up, always purge caches, and always verify in Search Console.

If sitemap questions are part of a larger cleanup, or you want this handled alongside your broader digital marketing programme, our team can audit the site, make the change safely, and monitor the effect for you.