No, Submitting a Sitemap Does Not Get Your WordPress Pages Indexed

You submit your sitemap to Google Search Console. The job is done, you assume, and new pages will start showing up in search within days. That is the myth almost every website owner picks up somewhere along the way, usually from an SEO plugin that makes submission feel like the finish line. It is not. A sitemap tells Google what exists on your site. It does not tell Google to go and index it.

A business owner asked me a version of this exact question on a call this week. She had launched a new page, ticked the box marked "submit sitemap," and expected results. Three weeks later, nothing had changed. Understanding why takes about five minutes, and once you know it, you stop waiting on a mechanism that was never designed to guarantee what you think it guarantees.

A Sitemap Is a List, Not a Request

Google's own Search Central documentation is blunt about this: a sitemap helps search engines discover the pages on your site, but it does not guarantee that every listed page gets crawled or indexed ^[1]. Think of it less as a request form and more as an index card catalogue. You are handing Google a list of what is in the building. Nobody has booked an appointment for someone to come and read every book on the shelf.

Consider a fresh example. A canine hydrotherapy centre in Kildare opens a second treatment room and publishes a new service page two weeks before the autumn rush, when demand for winter conditioning sessions for working dogs typically climbs. The page goes live, and the sitemap updates itself moments later without anyone lifting a finger. Assuming the job is done, the owner moves on to the next task on the list. Weeks pass. The page never turns up for the exact search terms it was built for, and the phone does not ring for that service the way it should during the one season built to catch it.

That is not a hosting failure or a broken plugin. It is a business owner treating a discovery signal as a guarantee.

WordPress Already Builds One for You

Most business owners do not know this: since WordPress 5.5, released back in 2020, core WordPress generates a basic XML sitemap automatically at yoursite.com/wp-sitemap.xml, with no plugin required ^[2]. It splits large sites into multiple sitemap files once a section passes 2,000 URLs, and it adds a link to that sitemap at the bottom of your robots.txt file automatically.

So what does that mean for you? You are very unlikely to be missing a sitemap in the first place. WordPress ships one by default, and most SEO plugins simply replace it with a more configurable version. The mechanical part, the bit people worry about, is usually already handled before you have thought about it.

That default matters more than it sounds, because WordPress remains the internet's most used content management system by a wide margin, well ahead of the next competitor ^[3]. Platforms like Wix or Squarespace also generate a sitemap automatically, but they give you no visibility into what it actually contains or excludes. With WordPress, you or your hosting provider can see the file, filter it, and correct it. That visibility matters more than people realise once something needs fixing.

If you want the fuller picture of what makes a WordPress site fast and genuinely discoverable, our complete WordPress performance guide for business owners covers the rest of that stack.

Crawl Budget: The Part No One Explains to Business Owners

Google does not treat every page equally. It allocates what its own documentation calls a crawl budget, shaped by two things: how much your server can handle without strain, and how much Google actually wants to crawl based on the perceived value of your content ^[4]. A brand new page from a small, established site is not competing for attention the way a page from a major retailer is, but it is still competing for it.

Prioritisation is not personal. It is mechanical, and it favours pages that already carry some signal of value: internal links pointing to them, established traffic elsewhere on the domain, a track record of being crawled before. A brand new page with nothing linking to it and nothing distinguishing it from ten similar pages elsewhere on the same site can sit in a sitemap for weeks untouched, not because Google missed it, but because everything else in the queue looked more urgent.

I made this mistake myself early in my time at Web60, telling a prospective customer that submitting a sitemap was effectively the end of the SEO conversation. It was not, and I have not repeated that line since.

When a Sitemap Cannot Save You

The honest limitation, the one most guides skip entirely, is this: a sitemap has no power to override a noindex tag, a canonical pointing somewhere else, or a robots.txt rule blocking the page outright. If any of those are in place, Google will not index the page no matter how many times it appears in the sitemap file. The fix is never resubmitting the sitemap. It is checking the Page Indexing report in Search Console and using the URL Inspection tool to see exactly why a specific page was excluded ^[5].

That same tool lets you request indexing for one URL directly, rather than waiting for Google to get around to the whole sitemap on its own schedule. Google does not publish an official cap, but in practice, site owners report being limited to somewhere around ten to twelve individual URL submissions a day per property. Save that allowance for the pages that genuinely cannot wait.

We have covered the wider indexing puzzle before, including why a page can sit unindexed for weeks even when nothing is technically broken, so if the Page Indexing report leaves you stuck, that is the next place to look.

The Practical Steps to Get a New Page Indexed

Verify. Check the page for a stray noindex tag or a robots.txt rule that is quietly blocking it before doing anything else.

Link. Add at least one link to the new page from a page Google already crawls regularly. A sitemap helps discovery, but a real internal link is a stronger signal that the page matters.

Request. Use the URL Inspection tool in Search Console to request indexing for that specific URL, rather than waiting for the whole sitemap to be recrawled.

Recheck. Return to the Page Indexing report after a few days instead of assuming silence means success. If the page is still not indexed, the cause is usually content quality or a technical block, not bad luck.

What a Properly Handled WordPress Setup Should Give You

A website platform that takes technical SEO seriously does not leave a business owner guessing whether a sitemap is even working. It generates one automatically, keeps it aligned with what is actually published, and gives the owner enough visibility to spot and fix a conflict without waiting on someone else's schedule.

That is the standard Web60 is built to. Every Web60 site runs full WordPress, so core sitemap functionality is there from the first page you publish, included as part of Web60's all-inclusive €60/year hosting rather than bolted on as an extra you have to configure yourself. You are not locked into a platform's private version of a sitemap you cannot inspect. If something needs fixing, you can see it and fix it, or ask an Irish-based support team to look at it with you.

None of that changes the fundamental rule. No hosting platform, Web60 included, can force Google to index a page it has decided is not worth showing. What a decent setup can do is remove every avoidable obstacle, so the only thing standing between your page and the search results is Google's own judgement, not a technical fault nobody told you about.

If you are running a genuinely large site, thousands of product pages updated daily, a dedicated enterprise SEO platform with its own crawl monitoring earns its cost. For most local firms publishing a handful of new pages a month, that level of infrastructure is solving a problem you do not have.

Conclusion

A sitemap is a map, not a delivery guarantee. It tells Google what exists. Whether Google decides to index it depends on internal links, content quality, and a dozen signals no single file controls. Once you understand that distinction, the waiting stops feeling like a mystery. Check the Page Indexing report, fix what is actually blocking the page, and use the URL Inspection tool for anything that genuinely cannot wait until Google gets there on its own.

Frequently Asked Questions

Do I need to install a plugin to create a sitemap for my WordPress site?

No. WordPress has generated a basic XML sitemap automatically since version 5.5. Most SEO plugins replace this default with a more configurable version, but the underlying functionality already exists without one.

Where do I find my WordPress sitemap?

Add /wp-sitemap.xml to your site's homepage address. If you use an SEO plugin such as Yoast or RankMath, check that plugin's settings, since it may generate the file at a different address instead.

How long does it normally take Google to index a new page?

There is no fixed timeline. Established sites with strong internal linking sometimes see new pages indexed within days. Newer sites or thin pages can wait weeks. If a page has not appeared after several weeks, check Search Console rather than continuing to wait.

Why is my page in the sitemap but still not showing up in Google?

Usually one of three reasons: a noindex tag is present, a canonical tag points elsewhere, or Google has judged the page too similar to existing content to prioritise. The URL Inspection tool in Search Console will tell you which.

Can I make Google index a page immediately?

You can request indexing for a specific URL through the URL Inspection tool, which speeds things up in many cases but is not instant and is not guaranteed. There is a daily limit on how many individual requests you can make, so save it for the pages that matter most.

Does having a sitemap improve my Google rankings?

No. A sitemap affects discovery and crawling, not ranking. Once a page is indexed, its position in search results depends on content quality, relevance, and the usual ranking factors, not on the fact that it once appeared in a sitemap file.

Sources