To submit a sitemap to Google, first find the XML sitemap your WordPress site actually generates. Then submit its URL in Search Console and check whether Google can read it. Submission helps discovery; it does not promise that every listed page will be indexed.
Back to the Google Search Console guide
Find the right WordPress sitemap
Check the sitemap settings in your active SEO plugin. Common paths include /sitemap_index.xml for SEO-plugin sitemap indexes and /wp-sitemap.xml for the WordPress core sitemap. These are examples, not a guarantee about your particular site. Open the actual URL before submitting it.
An XML sitemap is different from an HTML sitemap page for visitors. A human-readable list of links can be useful navigation, but the Search Console submission should point to the XML sitemap or sitemap index.
If several plugins claim to manage sitemaps, establish which one owns the site’s intended sitemap output. Installing another plugin just because Search Console shows a problem can make the configuration harder to understand.
Submit the sitemap
- Choose the Search Console property that covers the sitemap URL.
- Open Indexing → Sitemaps.
- Enter the sitemap address in the submission field, taking account of any prefix the interface already shows.
- Submit it, then inspect its status and any processing details.
- If it is a sitemap index, check its child sitemaps when troubleshooting a specific content section.
Keep the submitted address in your maintenance notes. If a future plugin change moves that address, you have a record of what Google was told to fetch.
What to do when the sitemap cannot be fetched
Open the submitted URL while signed out of WordPress. Confirm that it returns a sitemap rather than a login screen, a 404 page or ordinary website HTML. A browser displaying a pretty table does not make the file invalid; many XML sitemaps have a stylesheet.
- Wrong address: compare the submitted URL with the SEO plugin’s live sitemap link.
- Access restriction: check whether staging protection, a firewall or a security rule is blocking the request.
- Server failure: investigate hosting or application errors if the file is intermittently unavailable.
- Unexpected content: inspect plugin output and caching if the sitemap is replaced by an error message.
After correcting the cause, revisit the report and check its updated processing information. Avoid repeatedly submitting the same inaccessible file without changing anything.
Clean up the URLs inside it
Imagine you move a website to HTTPS, but the sitemap still lists old HTTP addresses. Even if Google can read the file, your sitemap is pointing at the wrong versions. Fix the underlying WordPress or plugin configuration and inspect the generated file again. Use the HTTP URLs in an HTTPS sitemap guide for that situation.
Review a small sample from each important post type. The intended URLs should be public, useful pages that you want indexed. Do not add private account pages simply to increase the number of submitted URLs.
Measure indexing separately
A successful sitemap status means Google processed the sitemap. Use Page indexing and URL Inspection to investigate what happened to the pages themselves.
For a new guide, also add a contextual link from an established page. A sitemap should support a navigable website, not be the only place a reader or crawler could discover your content.
Frequently asked questions
Should I submit the sitemap after every post?
Usually the existing sitemap updates automatically and remains at the same address. Verify your site’s behavior instead of creating a new submission for every article.
Why is a known sitemap missing from the report?
The report lists sitemaps submitted through supported submission methods, not every sitemap Google might have discovered elsewhere. An empty list alone does not prove Google has never found your sitemap.
Reference: Google’s Sitemaps report documentation.
