"No referring sitemaps detected": what Discovery is telling you

Searching for the no referring sitemaps detected meaning usually starts with a URL Inspection report that looks half empty. The short answer: Google could not tie the inspected URL to any sitemap it knows about for your property. That is a statement about how Google found the page, not a verdict on whether the page is indexed.

Where the message appears

Open the URL Inspection tool in Search Console, inspect a URL and expand the Page indexing section. Under Discovery there are two fields:

When the Sitemaps field is empty, Search Console shows a message such as "No referring sitemaps detected". Google's help page describes the same state as "Google couldn't identify a sitemap that refers to this page."

What it does not mean

If both Discovery fields are empty, the report may add that the URL might be known from other sources that are currently not reported. In that case Google found the URL by some route other than a sitemap or a referring page.

When the message is worth acting on

Treat it as a signal only when it shows up on a page that you want indexed and the verdict is "URL is not on Google". Then discovery is one of the things to check, next to crawl and indexing blocks. For the full list of verdicts and what each one asks you to do, see the SpeedyIndex guide to URL Inspection verdicts.

Common causes

  1. No sitemap was submitted or referenced. Google's sitemap documentation describes two routes: submit the sitemap in the Sitemaps report, or add a Sitemap: line to robots.txt.
  2. The sitemap lists a different version of the URL. Google crawls URLs exactly as they appear in the sitemap. An http entry, a missing www, an extra trailing slash or a tracking parameter makes it a different address from the one you inspected.
  3. The sitemap only covers part of the site. Unless it is submitted through Search Console, a sitemap affects only the files in its own directory and below. A sitemap in /blog/ does not vouch for URLs in /shop/.
  4. Google could not read the sitemap. In the Sitemaps report, a status of "Has errors" or "Couldn't fetch" means some or all of its URLs may not have been picked up.
  5. The page was added after Google last read the sitemap. The Sitemaps report shows when Googlebot last accessed each file. If that date is older than the page, wait for the next read or resubmit the sitemap.

How to trace it in five steps

  1. Copy the exact inspected URL, including protocol, host and trailing slash.
  2. Open the Sitemaps report and confirm each sitemap shows "Success" and a recent read date.
  3. Confirm the URL is really listed. For large or nested sitemaps, it is quicker to pull every URL out of an XML sitemap and search the list for the exact address than to scroll through raw XML.
  4. If the URL is missing or listed in another form, fix the sitemap so it uses the canonical URL you want to appear in search results.
  5. Add at least one internal link from a page that is already indexed, then run a live test and request indexing once the page is ready.

FAQ

Is "No referring sitemaps detected" an error?

No. It describes discovery. It becomes relevant only when a page you want in search is not indexed.

Will submitting a sitemap get the page indexed?

Not by itself. Google calls a sitemap a hint: it does not guarantee that Google will download it or use it for crawling.

Why does a URL that is listed in the sitemap still show the message?

Usually because the sitemap entry and the inspected URL differ slightly, the sitemap sits in a directory that does not cover the URL, or Google has not read the latest version of the file yet.

Related: Is the site: operator reliable for checking indexing?

Sources