WordPress Sitemaps in Core: Do You Still Need a Plugin?

Quick answer: Since WordPress 5.5 (August 2020), core can generate XML sitemaps at /wp-sitemap.xml without an SEO plugin. Many sites can rely on that baseline. You may still want a plugin if you need fine control over which URLs appear, image or news sitemap features, or tighter integration with a full SEO toolkit.

What changed in WordPress 5.5

For years, most site owners got XML sitemaps from plugins. WordPress 5.5 moved a basic sitemap provider into core. On a typical install with pretty permalinks enabled, you can open:

https://www.example.com/wp-sitemap.xml

That index file points to sub-sitemaps for content types core knows about, such as posts, pages, and taxonomies (when they are public). The feature aims to help search engines discover URLs even on sites that never installed an SEO plugin.

If you are planning or maintaining a business site, this sits beside other fundamentals in a solid WordPress development process: permalinks, HTTPS, crawlable navigation and clean templates.

What core sitemaps include (and skip)

Core sitemaps are intentionally simple. In broad terms they cover publicly queryable built-in and custom content that WordPress exposes.

They are not a full replacement for every plugin feature you might have used:

• No dedicated image sitemap UI like some SEO plugins offer
• No Google News sitemap workflow
• Limited per-URL metadata compared with mature SEO suites
• Less turnkey control in the admin for excluding singles without code or a helper plugin

For many brochure sites and blogs, the core list of posts, pages and public terms is enough. For large catalogs, membership content, or teams that exclude batches of URLs often, plugin control still matters.

Do you still need an SEO plugin for sitemaps?

You can often turn plugin sitemaps off if:

• You run a straightforward post and page site
• You do not rely on image or news sitemaps
• You are fine excluding URLs with a small bit of code or a lightweight utility
• You already manage titles, meta and canonicals another way (or with the same plugin’s other modules)

Keep or prefer plugin sitemaps if:

• You need a visual UI to exclude archives, authors or specific posts
• You want image sitemap output tied to media
• Your SEO plugin’s sitemap is already submitted and healthy, and you do not want two systems
• You use WooCommerce or complex custom types and the plugin’s filters match your catalog rules better

Popular suites such as Yoast SEO and Rank Math both ship sitemap modules. If you are choosing or revisiting a stack, our comparison of Yoast SEO vs Rank Math covers broader SEO features, not only sitemaps. Whichever path you pick, avoid enabling two sitemap systems that advertise different index URLs without a plan.

Avoid duplicate sitemap setups

A common post-5.5 mistake is leaving core sitemaps on while an SEO plugin also outputs sitemap_index.xml (or similar). Search engines can handle multiple sitemaps, but humans get confused, and conflicting exclusions create messy coverage.

Pick one primary sitemap index:

1. Decide: core or plugin (not an accidental mix).
2. Disable the other provider using the plugin’s setting or the core filter that turns core sitemaps off.
3. Update Search Console (and Bing Webmaster Tools if you use them) so the submitted sitemap URL matches reality.
4. Fetch the index in a browser and confirm the URL counts look sane.

If you recently migrated or changed plugins, watch for crawl errors in Search Console that point at old sitemap paths returning 404.

How to verify core sitemaps on your site

1. Confirm WordPress is 5.5 or newer.
2. Visit /wp-sitemap.xml while logged out (or in a private window).
3. Click through to a posts or pages sub-sitemap and spot-check a few URLs.
4. Make sure those URLs return 200 and are meant to be public (no thank-you pages, no account screens).
5. In Google Search Console, submit the sitemap index if it is not already there.
6. After a week or two, review coverage reports for spikes in excluded or errored URLs.

Core sitemaps respect public vs private content at a basic level, but custom code can still expose URLs you would rather keep out of indexes. Treat the sitemap as a discovery aid, not as a security boundary.

Developers: filters and exclusion basics

WordPress provides hooks so developers can disable core sitemaps entirely or adjust providers. Agencies often:

• Turn core sitemaps off when a client standardizes on an SEO plugin
• Remove a provider (for example, author archives) when those archives are thin
• Keep core on for minimal sites that refuse heavy plugins

If your team ships client sites, document which sitemap source is canonical in the handoff notes. Future plugin cleanups are easier when everyone knows whether /wp-sitemap.xml or a plugin index is authoritative.

Sitemaps vs on-page and internal linking

A sitemap does not make thin pages rank. It helps crawlers find URLs. You still need:

• Clear titles and content that match intent (on-page SEO checklist)
• Internal links so important URLs are not orphans
• Fast, usable templates so discovered pages deserve a good experience
• Logical publishing habits so new URLs appear in both navigation and the sitemap

Think of the sitemap as one pipe. Content quality and internal links are the water.

Special cases

Multisite: Each site in a network has its own sitemap surface. Check the site you care about, not only the root.

Noindex content: Pages marked noindex should not be treated as ranking targets. Keep sitemap policy aligned with robots meta so you do not advertise URLs you simultaneously ask Google not to index.

Large archives: Very large sites split across multiple sitemap files. Core handles pagination of sitemaps; still monitor performance on huge catalogs.

Non-WordPress URLs: If marketing landing pages live on another subdomain or stack, they need their own sitemap or a search console property that covers them. Core only knows what that WordPress install publishes.

Practical decision guide

Situation	Lean toward
Simple brochure + blog, few exclusions	Core sitemaps
Already happy with Yoast/Rank Math sitemap	Keep plugin; disable core
Need image/news sitemap features	Plugin (or specialized tool)
Custom exclusions without a full SEO suite	Core + small custom code, or a focused utility
Cleanup after plugin switch	One index only; resubmit in Search Console

FAQ

Where is the core sitemap URL?

Usually https://your-domain/wp-sitemap.xml when permalinks are enabled and core sitemaps are not disabled.

Will Google find my site without a sitemap?

Often yes, through links. Sitemaps still help with new URLs, large sites and pages that are weakly linked.

Should I delete my SEO plugin after 5.5?

No. Sitemaps are only one feature. Title templates, canonicals, schema and redirects are separate reasons teams keep a plugin.

Can I have both core and plugin sitemaps?

Technically yes; operationally it is messy. Choose one primary index and disable the other.

Do core sitemaps replace robots.txt rules?

No. robots.txt, meta robots and sitemaps solve different jobs. Use them together on purpose.

Pick one clear sitemap strategy

WordPress core sitemaps close a long-standing gap for sites that never installed an SEO plugin. They are a solid default for many business sites after 5.5. If you already depend on a plugin’s exclusions or image/news features, keep that plugin sitemap and turn core off so everyone (humans and bots) sees one story.

When you want help aligning WordPress technical SEO with pages that convert, see our Turn visitors into customers services.