Why is my page missing from Search Console reports?

Your data is filed under the address Google picked

Search Console does not report per URL. It reports per page, and it chooses which URL stands for that page.

Google describes the consolidation: "Search Console simplifies analyzing your performance data by choosing one canonical URL that represents all variations of a page. These variants include variations by device (desktop or mobile), variant URLs that point to the same page, and possibly even alternate language versions of a page."

The effect is spelled out too: "This means that even if you have separate URLs for the mobile and desktop version of a page, all click data will be assigned to the same URL in the Performance report."

So consolidation is a feature, and it is doing you a favour. You do not have to add up mobile and desktop by hand. The cost is that four addresses report as one. The three you did not search for look empty.

Google adds a caveat worth keeping, because it prevents a wrong conclusion. Data goes to the canonical "although in some cases data might be assigned to the actual URL, rather than the canonical URL". So the rule has exceptions, and a page that seems to break the pattern is not proof that something is broken.

Whether two addresses are the same page is a judgement

This is the part that surprises people, and the internet standard for addresses says it outright.

RFC 3986 defines how URIs are compared, and it is candid about the limit: "Even though it is possible to determine that two URIs are equivalent, URI comparison is not sufficient to determine whether two URIs identify different resources. For example, an owner of two different domain names could decide to serve the same resource from both, resulting in two different URIs."

In other words, no amount of looking at two addresses can tell you whether they are the same page. That is a fact about addresses. It is not a shortcoming of Google.

The standard even names who has to solve this in practice: "Extensive normalization prior to comparison of URIs is often used by spiders and indexing engines to prune a search space or to reduce duplication of request actions and response storage."

It is also honest that the problem has no clean answer. Comparison methods "are designed to minimize false negatives while strictly avoiding false positives", and, flatly, "false negatives cannot be eliminated."

So a search engine grouping your addresses is making a judgement under a documented impossibility. It will usually agree with you. It is not obliged to.

That matters for how you read a surprise. An address filed under another address is the system working as specified, and it is worth separating from the case where a page is genuinely not indexed at all. Those look identical in a report and have completely different fixes. One is a lookup problem and the other is a crawling problem.

You can suggest a canonical, not choose one

Google is direct that your declaration is an input rather than an instruction.

On declaring a preference: "There is no guarantee that Google will choose your preferred canonical, but we will take this into consideration."

And on what it may do instead: "Google might select the user-declared canonical, but sometimes Google might choose another URL that it considers a better canonical example."

That reframes a common complaint. A canonical tag that was not honoured is not a broken tag. It is a suggestion that lost. The remedy is to make the preferred version the obviously better example, rather than to repeat the instruction louder.

There is a timing detail that catches people testing their work: "You can determine the canonical version only in the indexed data; the live test cannot predict whether or not the tested version will be considered canonical." A live test tells you the page works. It cannot tell you which address Google will file it under.

The tool has a second limit, and this one can send you in the wrong direction entirely. When crawling is blocked, the indexing field always reads Yes, and Google explains why in a single clause: "because Google can't see and respect any noindex directives".

Read that carefully. A Yes there does not mean indexing is allowed. It means Google never got close enough to find out. Google spells out the consequence: "your page might appear in Search results even if indexing is blocked by your site."

So the single most reassuring field in the report is the one that reads Yes for two opposite reasons. Check what the crawl is allowed to do before trusting what the indexing line says.

Some links are never counted at all

One more reason a number can be missing, and it has nothing to do with addresses.

Google excludes search refinements: "If a link is a query refinement link, clicks and impressions are not counted for that link." Its own explanation of why is unusually plain, because the destination of such a link is another Google search rather than your site.

A related detail prevents a different wrong conclusion. If your site redirects a visitor after they arrive from Google, "that has no effect on the URL assigned the impression". The landing address is what gets credited. Wherever the visitor ended up does not enter into it.

What to check, in order

Five checks, and all of them are free.

• Run the URL Inspection tool on the address you expected and read the Google-selected canonical field. That names the URL your data is under.
• Search the report for that canonical address rather than the one you typed. The numbers are usually sitting there.
• Check whether the page has variants at all. Separate mobile addresses, tracking parameters and language versions all consolidate.
• Compare the user-declared canonical with the Google-selected one. If they differ, your preference lost and the page is the thing to change.
• Only after all of that, treat the page as genuinely absent from search.

Work out the scale before concluding anything, because the arithmetic is what makes this look like a catastrophe when it is bookkeeping. Suppose a service page exists at four addresses: the plain one, a mobile version, a tracking-parameter version from a campaign, and a translated version. Google consolidates the data to one.

Check the other three and each shows nothing. Now scale that. On a site with twenty such pages you could inspect sixty empty addresses and conclude that three quarters of the site earns no traffic at all. Every one of those zeros would be correct and none of them would mean what it appears to mean. The figures are an illustration, and the lesson is that an empty row is a statement about an address rather than about a page.

Working out which address your numbers actually live under, before anybody rebuilds a page that was performing fine, is part of what we do on search.

Terms used on this page

• Canonical URL

Sources

• What are impressions, position, and clicks? (Google Search Console Help)
• URL Inspection tool (Google Search Console Help)
• RFC 3986, Uniform Resource Identifier (URI): Generic Syntax (RFC Editor, Standards Track)

Last reviewed 2026-09-12.