Search Engines Find Your Pages Without an XML Sitemap

A sitemap is not a ranking device. It is a list you hand a crawler so it does not have to find your pages by following links from somewhere else.

Fifty-seven Enterramon reports across twenty-seven domains carry this finding. It sits at low severity, and on WordPress the fix is usually already done for you.

Discovery, not ranking

Google’s own guidance is careful here, and worth repeating plainly. Publishing a sitemap does not guarantee that the pages in it get crawled, and it does not lift any of them in the results. What it does is shorten the path between publishing a page and a crawler learning the page exists.

On a small site that path is already short. Your homepage links to everything, a crawler arrives within days, and a sitemap adds very little. That is worth saying out loud, because it means a small site carrying this finding can reasonably do nothing about it. On a large site the arithmetic changes. New pages sit several clicks from the homepage, some are reachable only through a search box or a filter, and the sitemap becomes the only reliable route in. The bigger the catalogue, the more the file earns its place.

There is one interaction worth knowing because it wastes a lot of effort. A page blocked in robots.txt will not be indexed even when it is listed in your sitemap. The file that grants access and the file that announces the URLs have to agree, and when they disagree the restriction wins.

How the check finds it

The check requests the usual locations at the domain root and looks at what comes back. The card is worded No sitemap.xml, with the note that a sitemap helps search engines discover and prioritise your pages, especially on larger sites.

A sitemap does not have to live at /sitemap.xml to count. It does have to be declared somewhere a crawler will look, and the two places that work are a Sitemap: line in robots.txt and a submission in Search Console.

Generating a sitemap

WordPress has built this in since version 5.5. A stock install serves an XML sitemap at wp-sitemap.xml, it updates itself as you publish, and it needs no configuration at all. If a WordPress site has no sitemap, something switched it off rather than never providing one.

Most WordPress sites already have one and do not know it.

SEO plugins usually replace it. When one does, it disables the core sitemap and serves its own, often at a different path. That is fine, and it is the usual reason the addresses you might guess do not match the address you actually have.

enterramon.com is a working example of that. The core path and both of the common plugin paths redirect to the one file the site really uses, so a crawler arriving at any of the three lands in the same place.

/sitemap.xml       301 -> /br-sitemap.xml
/sitemap_index.xml 301 -> /br-sitemap.xml
/wp-sitemap.xml    301 -> /br-sitemap.xml

Redirecting the guesses is optional. Declaring one good sitemap properly matters more than catching the paths somebody might try.

Pointing robots.txt at it

The declaration is a single line at the end of the file, and it needs the full address rather than a path.

WordPress adds this line for you when it is serving its own sitemap, which is easy to forget if you have written a robots.txt by hand. A hand-written file replaces the generated one completely, so the pointer disappears with it and nothing warns you.

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

Check the address resolves before you publish the line. A pointer at a 404 is worse than no pointer, because it sends a crawler somewhere that looks like it should have answers.

Submitting it

Search Console is the second declaration, and the one that tells you whether the file is being read. Submit the address once and the report there will show discovered URLs and any parsing errors.

Two limits are worth knowing before a large site surprises you. A single sitemap file covers up to fifty thousand URLs and fifty megabytes uncompressed. Past that you need a sitemap index, which is a file listing other sitemap files, and Search Console takes the index as the submission.

WordPress adds a tighter ceiling of its own on the way in. Core splits a large site across sub-sitemaps and caps each one at two thousand URLs, well under what the protocol permits, to avoid exhausting memory on modest hosting. Go past that and it builds the index for you, so the limit is not something you manage.

There is one habit worth dropping while you are here. Google retired the sitemap ping endpoint in 2023, so a plugin or a deploy script still calling it is now quietly doing nothing. The thing that replaced it is the lastmod value inside the file, which is what tells a crawler a page has changed and is worth fetching again. Google’s own advice is to keep that value accurate rather than to keep announcing the file.

Then leave it alone. The engine’s own warning is the one to remember here, that a stale sitemap pointing at dead URLs wastes crawl budget. An automatically generated sitemap cannot go stale, and one maintained by hand eventually will.

If the findings list is new to you, the walkthrough of an Enterramon report explains where this card sits and what the neighbouring checks measure.

Declare it once, point robots.txt at it, submit it, and let the software keep it current.