SEO Pipeline · Produce and measure
Did your clicks really drop, or is your Search Console just not seeing them? The difference between a Search Console Domain property and a “URL prefix” property sounds technical. Yet it can hide part of your clicks, without any error message. It’s the first thing to check to measure your content’s performance.
A Domain property covers every variant of your site: http and https, with or without www, and all subdomains. A URL-prefix property only covers addresses that start exactly with the chosen prefix, protocol included. To see everything, choose the Domain property.
I discovered it while preparing the monthly report for a multi-location network. The report read a URL-prefix property in https://www, the site’s official version. Everything seemed consistent. But when compared with a Domain property, a gap appeared.
In October 2026, a notable share of clicks to the branch pages was invisible in the https://www property. They did exist, but the property couldn’t see them. In the spring, the gap was small. It had widened considerably in a few months, without any indicator flagging it.
For a branch, the consequence was direct: its report showed fewer clicks than it really got. Someone reading those figures without knowing could have concluded performance was dropping, and gone looking for a culprit who didn’t exist.
The explanation lay outside the website. External links pointed to an old variant of the site’s address, in http://, without the “s.” The site correctly redirected visitors to the right address. But for Search Console, the click was recorded on the http:// address, which the https://www property doesn’t cover.
A telling detail: those http:// addresses weren’t even indexed. The clicks didn’t come from regular search results, but from those external links. That’s why nothing looked abnormal in the other reports: the problem sat in an area the property simply wasn’t looking at.
Links in http:// aren’t the only case. A URL-prefix property in https://www also doesn’t see:
http to https: if the migration happened a few years ago, the earlier history sits in another property, and the new one started from zero.In every case, the principle is the same: a prefix only sees what starts exactly like it. It doesn’t flag what it’s missing, because it doesn’t know it exists.
The check takes about fifteen minutes. It requires no special tool:
http:// pages. In the Domain property, add a page filter “URLs containing” http:// (https:// addresses don’t match this filter), then do the same for non-www variants or subdomains. What shows up there is invisible in an https://www property.https://.If you only have a URL-prefix property, the first step is to create a Domain property. Which leads straight to the next question.
To track a website’s performance, the Domain property is the right default choice. It sees everything, whatever address variant the visitor came through. It’s verified with a DNS record, added at your domain name provider: that’s often the step that makes people hesitate, but it only has to be done once.
One important limit: Search Console starts collecting data for a property when it’s added. A Domain property created today will therefore have no earlier history. That’s the best reason to create it right away, even if you still read your reports in the old property.
Can you keep both? Yes, and it’s often the best solution. Nothing forces you to delete the old URL-prefix property: it keeps its history, while the Domain property builds its own. During the transition, you read long-term trends in the old one and the full picture in the new one. What matters is knowing, every time, which one you’re looking at.
The URL-prefix property remains useful. It lets you isolate a specific section of the site, such as a blog or a language version. But it should never be the only source of a performance report.
Before concluding there’s a drop, ask yourself one question: which property am I reading? A report based on the wrong property can underestimate your clicks, and that gap can grow silently, as in the case I described.
The solution is simple and free: a Domain property created as early as possible, business profiles that point to the right address, and a periodic check of the gap between properties. It’s the foundation of a reliable monthly report.
Choosing the right property is part of a complete method, from listening to the market to monthly measurement. To see the whole picture, discover the AI SEO pipeline.