Search Console Property Showing No Data? 7 Causes to Check.

When a Search Console property shows no data, the cause is almost always one of seven things: the site was verified but the property was never added to your account, the URL-prefix property uses the wrong protocol or host (http instead of https, www instead of non-www), Google assigns the data to a canonical URL that lives in a different property, the property is new and data has not arrived yet, the site has no impressions in Google Search yet, you are signed in to a different Google account than the one that holds the property, or your permission level hides what you expect to see. Fix it in that order: confirm the property is in your account with the property selector or the Search Console API sites.list method, add a Domain property (sc-domain:) so every protocol and subdomain is covered, then give it a few days before you read the Performance report.

A Search Console property is the unit Search Console reports on. A Domain property, written sc-domain:example.com in the API, covers every subdomain and every protocol of a domain and can only be verified with a DNS record. A URL-prefix property, such as https://www.example.com/, covers only URLs that start with that exact string, protocol included. Verifying and adding are two separate steps. Verification proves you own the site. Adding the property puts it in your Search Console account so reports exist. The Site Verification API handles the first step (webResource.insert). The Search Console API handles the second (sites.add), and sites.list tells you which properties your account actually has.

Why does a verified site not show up in Search Console?

Verifying ownership of a site does not add it to your Search Console account; the property appears only after someone adds it, with Add property in the UI or the Search Console API sites.add method. We ran into this on one of our own sites. Ownership was verified through the Site Verification API and the call returned success, but the property never appeared in the Search Console property selector and the Search Console API returned no data for it. The fix was to add the property explicitly with sites.add, and to add the Domain property (sc-domain:) at the same time so no protocol or subdomain variant was left out.

Google's help is clear on why this matters: data collection for a property starts as soon as anyone adds the property to their Search Console account, even before verification, and continues as long as any user has it in their account. Verification on its own does not start it. If you script site setup, the sequence is three calls, not one: get a token and place it, call webResource.insert to verify, then call sites.add with the same Google identity. We now run that sequence on every new site, alongside the checks for new site pages not indexed.

The seven causes we find most often.

We see the same short list on our own sites and on sites we take over.

• Verified but never added: the Site Verification API or another Google product confirmed ownership, but no one called sites.add or clicked Add property, so the property is not in your Search Console account
• Wrong protocol or host on a URL-prefix property: the property is http://example.com/ while the site serves https://www.example.com/, so every real URL falls outside the prefix
• Data assigned to a canonical in another property: Google credits clicks and impressions to the canonical URL it selects, so if canonicals point to a different host, the data lands in that host's property
• New property: Google says data should begin to appear in a few days, and Performance data arrives about 48 hours after Search Console collects it
• No impressions yet: the site is not appearing in Google Search results, so there is nothing to report even when the property is set up correctly
• Wrong Google account: the property was added under a different login, a service account, or a colleague's account, so the account you are looking at does not list it
• Permission level: a restricted user has view rights on most data but not all of it, and cannot use every tool, which can look like missing data

How do you check that a property is actually in your account?

The Search Console API sites.list method returns every property the signed-in account has, each with a permission level of siteOwner, siteFullUser, siteRestrictedUser or siteUnverifiedUser. Run three checks, in this order.

The property selector. In Search Console, open the property selector dropdown at the top left. Look for the Domain property (shown as the bare domain) and any URL-prefix properties (shown with https:// or http://). If the site is not listed, it is not in this account, whatever a verification screen said earlier.

The API list. Call sites.list with the same credentials your scripts and dashboards use. If the site appears as siteUnverifiedUser, the property was added but this account never proved ownership. If it is missing entirely, it was never added for that identity. A service account has its own list, separate from your personal login, so check both.

URL Inspection. Once the property exists, inspect the home page URL inside it. If Search Console says the URL is not in the current property, your prefix does not match the live URL. If it shows a Google-selected canonical on a different host, that host's property is where the clicks and impressions go.

Diagnose top to bottom.

Each step isolates one layer. Stop at the first one that fails.

Should you use a Domain property or a URL-prefix property?

A Domain property covers every subdomain and both http and https, but it can only be verified with a DNS record. A URL-prefix property includes only URLs that start with the exact prefix, protocol included, and supports several verification methods. Google's own example: a URL-prefix property for http://example.com/ does not include https://example.com/ pages or any subdomain.

Our default is a Domain property for every site we run, plus a URL-prefix property for the main host when someone cannot edit DNS. The Domain property removes the most common setup mistake on this list in one step. It is the same habit we use in our conversion tracking audit checklist: check the identifier that reports are keyed on, not the settings screen.

How long does a new Search Console property take to show data?

Google says data should begin to appear in a new property in a few days, and collection starts when the property is added, even before verification. Search Console data is available about 48 hours after it is collected, so the most recent two days are always thin or missing. As of October 2026, Search Console keeps the last 16 months of data. An account can hold up to 1,000 properties, so adding both a Domain property and URL-prefix properties costs nothing that matters.

What is normal and what is a red flag?

An empty property is normal for a few days after it is added; a correctly set up property that is still empty after a week means the site is not being shown in Google Search. Use these markers.

• Normal: the latest two days of Performance data are missing, because data arrives about 48 hours after collection
• Normal: a property added this week has little or no history yet
• Normal: a URL-prefix property shows lower totals than the Domain property, because the prefix covers fewer URLs
• Normal: a restricted user sees fewer tools and settings than an owner
• Red flag: the site is missing from sites.list for the account your reports and dashboards use
• Red flag: URL Inspection says your home page is not in the property you are reading
• Red flag: Google-selected canonicals point at a host you have no property for
• Red flag: a correct Domain property older than a week still shows zero impressions

If the property has data but a page you care about is missing from it, the next stops are Search Console 404 validation failed and our notes on the Google Indexing API limits.