Why WordPress Site Owners need this
You launched the site, published a few dozen posts, and weeks later a search for your own post titles still returns nothing. Before blaming your theme, check the basics. The Search engine visibility box under Settings > Reading, labelled "Discourage search engines from indexing this site", is often left ticked after launch, and while it stays on, nothing else you fix will help. A second quiet problem is archive clutter: tag, date and author pages that get indexed by default and crowd out the posts you actually care about. A third is the slow, plugin-heavy setup that makes every fix feel risky.
A sitemap will not cure any of these, but it shows what you are offering crawlers. WordPress core generates one, and Yoast or Rank Math may generate another, so you can easily submit the wrong address. Enter your domain and the Sitemap Finder & Validator probes the usual paths, reads robots.txt, and lists each sitemap it finds with its type and entry count, so you see which one is really answering.
WordPress Site Owners specific guidance
Check the Reading setting first
Open Settings > Reading in the dashboard and look at Search engine visibility. If "Discourage search engines from indexing this site" is ticked, untick it and save; no sitemap work matters until that is off. Then run your domain through the tool and note the In robots.txt card. WordPress core adds a Sitemap line to its virtual robots.txt when the site is public, and SEO plugins usually add their own, so a Yes there is normal. A No means crawlers get no hint, which is worth fixing but not fatal. Passing this check proves only that an address is declared and fetchable. It does not show whether Google has indexed anything, and it does not test whether robots.txt rules block Googlebot.
Work out which sitemap is live
Read the table. A Sitemap Index at /sitemap_index.xml usually means an SEO plugin such as Yoast or Rank Math is serving it, while /wp-sitemap.xml means the core sitemap is live. Both usually redirect /sitemap.xml to their index, and the tool follows that redirect and lists the index once under its final address, so you see which one really answers. Two different indexes listed at once, say /wp-sitemap.xml next to /sitemap_index.xml, is the warning sign, so submit only one in Search Console. The tool does not open ordinary children, so the first 20 URLs shown are child addresses such as post, page and category sitemaps. Open one in your browser to see its posts. None of this proves the pages inside are indexable.
Fix in this order
Order matters. First, untick the visibility box if needed. Second, pick one sitemap source: in Yoast SEO the XML sitemaps switch sits under Yoast SEO > Settings > Site features, and Rank Math keeps its options under Rank Math > Sitemap Settings. Third, look at which child files exist; a long list of tag or author sitemaps hints at archives you may want to noindex in the plugin, which also drops them from the sitemap. Rerun the tool afterwards, and clear any caching plugin first so you see the new file. Last, submit the one address under Indexing > Sitemaps in Search Console, where processing errors appear; the tool checks presence and counts but is not a schema validator and cannot see what Google decided.
Example scenarios
1. Plugin index after switching SEO plugins
- Situation
- Illustrative example: A blogger moves from one SEO plugin to Rank Math and wants to confirm the sitemap is still healthy before resubmitting it.
- Input
- example-blog.com
- Reading the result
- The table would typically show one Sitemap Index at /sitemap_index.xml with about 5 loc entries, In robots.txt Yes, and child addresses for posts, pages, categories, tags and authors. The 5 is the number of child files, not posts. Open the post child and check it lists roughly the 140 posts you expect. If /wp-sitemap.xml also appears as a second index, the old setup is still answering.
2. Sitemap line lost on a core-only site
- Situation
- Illustrative example: A small studio site runs no SEO plugin, but someone uploaded a physical robots.txt file that replaced WordPress's virtual one and dropped the Sitemap line.
- Input
- example-studio.com
- Reading the result
- The cards would likely read Sitemaps 1 and In robots.txt No. The tool still finds the sitemap because core redirects /sitemap.xml to /wp-sitemap.xml, and the row shows that final address as a Sitemap Index with about 4 child files for posts, pages, categories and users. Add a Sitemap: line with the full /wp-sitemap.xml address to the physical robots.txt and rerun; expect In robots.txt Yes.
3. Tag sprawl inside the sitemap
- Situation
- Illustrative example: A recipe blogger with 90 posts has created about 400 single-use tags over two years, and wants to know why Search Console shows many tag URLs.
- Input
- example-recipes.com
- Reading the result
- The index would typically list six child sitemaps, one of them the post tag file. Opening that child in a browser shows roughly 400 URLs against 90 posts, which points to thin archives competing with real content. Set Tags to noindex in the plugin, clear the cache and rerun; the tag child should vanish from the listed addresses. The tool shows what is offered to crawlers, not whether Google has dropped those pages.
Common mistakes
- Leaving the visibility box ticked. A flawless sitemap does nothing while Settings > Reading still asks search engines to stay away from the site. Check that box before anything else.
- Submitting two sitemaps. Sending both /wp-sitemap.xml and /sitemap_index.xml to Search Console makes it harder to read the processing report. Keep the one your plugin or core declares in robots.txt.
- Reading Total loc as the post count. On a Sitemap Index the figure counts child sitemap entries, not the pages inside them. Open each child file to see real page counts.
- Believing zero results means no sitemap. The tool checks standard paths and the robots.txt declaration, so a sitemap at a custom address nobody declares can go unseen. Add a Sitemap: line and rerun.
- Keeping thin archives in the sitemap. Tag, date and author archives that add no value dilute what you offer crawlers. Set them to noindex in your SEO plugin and recheck the child sitemap list.
Frequently asked questions
Why is my WordPress site not indexed by Google even though I have a sitemap?
A sitemap only tells Google which URLs exist; it does not override a block. Start with Settings > Reading and confirm "Discourage search engines from indexing this site" is unticked, then check that individual pages carry no noindex setting in your SEO plugin. Run the Sitemap Finder to confirm the file returns and is declared in robots.txt. Even with all of that correct, Google decides what to index, so the result can show readiness but never a guarantee, and Search Console's page indexing report is where you see Google's verdict.
Is the WordPress core sitemap or my Yoast sitemap the one that is live?
Check robots.txt and the tool's table. WordPress core publishes /wp-sitemap.xml, while Yoast and Rank Math publish /sitemap_index.xml, and an active SEO plugin normally replaces the core one. Run your domain: a Sitemap Index at /sitemap_index.xml points to the plugin, and a listed /wp-sitemap.xml points to core. Whichever address robots.txt declares and Search Console holds should be the single one you keep. The tool reports what answers right now, not which plugin setting produced it.
How do I stop WordPress tag and author archives showing up in my sitemap?
Set them to noindex in your SEO plugin, which normally removes them from the sitemap too. In Yoast SEO, Settings has Categories & tags and Advanced > Author archives; in Rank Math, Titles & Meta has Tags and Authors tabs. Afterwards clear your cache and rerun the tool; the tag or author child sitemap should disappear from the list of child addresses. This tidies what you offer crawlers, but pages already indexed can linger until Google recrawls them.
Why does the tool show only a handful of URLs when my WordPress site has hundreds of posts?
If your sitemap is an index, the count reflects the child sitemap entries, not the posts inside them, because ordinary child files are not opened. A handful of entries is typical for a plugin index with post, page and category files. To see real page counts, open each child address in your browser or check the Sitemaps report in Search Console. A genuinely tiny count on a plain URL set is different and worth a look at your plugin's included post types.
Do I need a sitemap plugin or is the WordPress default enough?
Core's /wp-sitemap.xml covers posts, pages, taxonomies and users out of the box, which is enough for many small sites. A plugin like Yoast or Rank Math adds control, for example noindex settings that also prune the sitemap, plus its own address at /sitemap_index.xml. Pick one and avoid running two. After any switch, run the Sitemap Finder on your domain to confirm exactly one sitemap answers and robots.txt declares it, then update the address in Search Console.
Reference: Yoast's guide, WordPress SEO: the definitive guide, explains why date, author and tag archives can get indexed without adding any value.