WordPress XML Sitemap Setup

WordPress sitemap setup is a five-minute job that mostly does itself — core ships a basic sitemap, and every SEO plugin replaces it with a better one automatically — which makes this guide short on setup and longer on the parts people skip: making the sitemap match your indexation strategy, submitting it properly, and reading the diagnostics it unlocks, per the general sitemap doctrine.

The setup (brief, as promised)

With Yoast or Rank Math active: the plugin's sitemap is on by default at /sitemap_index.xml (Yoast) or /sitemap_index.xml (Rank Math) — a sitemap-index splitting by type (posts, pages, categories...), which is exactly the per-section diagnostics structure the doctrine wants. Core's native /wp-sitemap.xml gets disabled automatically by the plugins (verify — two live sitemaps is the mini version of the double-emitter bug). Then: reference it in robots.txt (plugins handle this) and submit the index URL in Search Console — the active handshake that unlocks the reporting.

The alignment pass (the part that matters)

The golden rule — only canonical, indexable, live URLs — is enforced in WordPress by one principle: the sitemap must mirror the indexation map you set in the settings checklist. The plugins do this automatically when the map is set (noindexed types drop out of the sitemap) — so the alignment pass is a verification: open each child sitemap and check for the classics — tag archives present while noindexed by strategy (map not set in the sitemap section), attachment/media URLs (the redirect-to-file toggle unset), thin custom-post-types a plugin registered publicly (portfolio/testimonial types from themes — noindex and de-sitemap what shouldn't compete), and stray paginated or format archives. Fifteen minutes, once, then whenever a new plugin registers post types.

The diagnostics this buys

The per-type index files turn Search Console's sitemap report into the instrument panel: discovered-vs-indexed per content type — posts indexing at high rates while a custom type sits ignored is a quality or configuration finding localised for free; the drift alarm — indexed counts falling on a type that didn't shrink means investigation, per the audit's stage one; and lastmod honesty (the plugins set it from real modification dates — which stays honest as long as your refresh practice does, per the no-date-bumping rule).

Frequently asked questions

Do I need a separate sitemap plugin?

No — the SEO plugin's implementation is complete for almost every site; dedicated sitemap plugins predate that reality and now mostly add conflict risk. Exceptions are the specialist extensions (news sitemaps for publishers, video/image extensions for heavy media sites) where your SEO plugin lacks the module.

My sitemap shows fewer posts than I've published. Bug?

Usually design: noindexed content, non-public statuses and excluded types drop out correctly — diff the missing URLs against your indexation map first. Actual bugs to check second: caching serving a stale sitemap (purge, regenerate) and post-type registration arguments excluding content that should be public.

How often does the sitemap update, and should I resubmit?

The plugins regenerate dynamically — every publish/update reflects immediately, and Google refetches on its own rhythm (the ping mechanisms have been deprecated; the standing submission in Search Console is all the notification needed). Resubmission is only for structural changes (new index URL after a plugin switch). The sitemap then does its quiet job forever — discovery plumbing beneath the contest that stays content plus authority (our plumbing's upstairs).