Why Search Console is missing a blog or subdomain
Find missing Search Console data by mapping protocols, hosts, paths, and canonical URLs to the property you actually verified and the report you opened.
By Crawlito · 5 min read
In short
- A Domain property covers protocols and subdomains under its verified domain.
- A URL-prefix property limits reporting to addresses that match the specified prefix.
- Property scope, canonical attribution, and date filters can each explain an empty report.
On this page
If Search Console shows impressions for your homepage but nothing for a new blog or help center, compare the exact published URLs with the property selected in the report. A URL-prefix property for https://www.example.com/ omits https://help.example.com/. A Domain property for example.com covers both, subject to the data the report actually has. Search Console’s property definitions
Build a map from real landing pages
Take three links from the public site. Choose the main homepage, a recent blog article, and a help article that customers already visit. Open each in a clean browser and record its final protocol, hostname, and path. The CMS's field label “Blog” tells you nothing about the production host. A button on the main site can point to a vendor's domain, a custom subdomain, or a folder reverse-proxied through the marketing host.
| Example landing URL | Property that includes it | Easy scope mistake |
|---|---|---|
| https://www.example.com/blog/setup | Domain example.com or the matching www URL prefix | Opening a prefix for the bare hostname |
| https://help.example.com/billing | Domain example.com or the matching help URL prefix | Opening the marketing site's URL prefix |
| https://manuals.example.net/start | A matching property under example.net | Expecting ownership of example.com to cover a different domain |
An internal redirect can change the row you need. A vanity link may begin on your main hostname but land at the provider's address. Note where the person lands and which address the page declares as canonical. If your team later changes the public hostname, keep this table dated. It gives you a way to explain why two reports that used to agree started diverging during one release.
Pick the property for the question you are asking
A Domain property is a convenient place to ask whether any section on a domain earned search visibility. Set it up with the verification method documented for your hosting arrangement, commonly a DNS record. Work with whoever controls DNS and preserve existing verification records. Your section owners can still use narrower URL-prefix properties to investigate paths or hosts. Multiple properties can cover the same pages, so adding their totals together can double count activity.
If you manage only a customer-facing help center, the owner may grant access just to its verified prefix. That can be sufficient. Copy the exact value from the property selector rather than reconstructing it from a browser bookmark. A prefix constrained to /blog/ covers a different set of pages from one rooted at /. An alternate locale on /fr/articles/ sits outside the former even if both sections belong to the same editorial team.
Choose the reporting boundary before sharing a screenshot. Label a report “HTTPS www host, blog folder” when that is what it covers. A statement that “the site got no impressions” can influence the next editorial budget; a statement that “this prefix has no impressions in this date range” directs the next person to a specific check.
Separate property scope from indexing and attribution
Open the appropriately scoped property, remove filters left over from an earlier analysis, and select the same search type and dates in each comparison. A branded query filter, a country selection, or an exact-page filter that still contains a redirecting URL can produce an empty table. Try an older article with known activity as a control. A result for that control tells you the report can return data for at least one page in your section.
Inspect the target URL in Search Console and compare the canonical you publish with Google's indexed selection when available. Performance is generally attributed to the canonical URL; Google's help documents exceptions and report-specific behavior. If an article syndicates to another canonical, the URL readers copy from the address bar may differ from the one that receives impressions in the report. See Google’s Performance report documentation and the guide to canonical URL conflicts.
A new section with no recorded impressions can still be public and technically readable. Test whether a person can follow an ordinary link to the article from the blog index. Look at its status, canonical, and index directive. Use URL Inspection to examine the specific page. Fix a content delivery error only when you actually observe one; changing a healthy template cannot correct a report opened under the wrong property.
Reconcile the result with app or referral analytics
Search impressions, visits, and completed actions describe different points in a customer's journey. Someone might search for a setup guide on the help subdomain and later open the application from a saved bookmark. That journey could produce an impression for the help article without a directly attributed signup. Conversely, a helpful shared link can drive app activity while contributing no Google Search impression for that visit.
For a before-and-after comparison, select a set of stable URLs, a date range that both reports cover, and the same property scope on both sides. Record major moves between hosts. If your blog moved from a separate domain into a folder, document the old and new properties and examine their date ranges separately. A single current-domain filter cannot recover the scope of the former domain. The site migration guide shows how to follow the URL changes themselves.
Give the owner a one-line diagnosis that another analyst can reproduce. For example, the help URL is accessible and self-canonical, the www-prefix report excludes it, and the domain-wide report contains the page after clearing the query filter. If the domain-wide report also has no data, record that as the observation and open the indexing investigation with the exact URL. Include the last date for which data was available so the next comparison uses a matching window.
Check a reporting chart against one exact URL
An agency dashboard may keep its old property selection even after an analyst has verified a broader property in Search Console. Open the source report and the shared chart side by side. Match the selected property, page filter, search type, date range, and country. Use a single article known to appear in the source report as the test case. A working example makes a disconnected chart easier to diagnose than two empty totals.
If the article appears under a precise page filter in the source report, remove chart transformations one at a time. A rule that groups URLs only when they begin with the old blog hostname can send every new URL into an unlabeled group. Repair the grouping rule and keep separate rows for hosts that need separate ownership. Save the working filter with the dashboard's existing documentation. This gives the next analyst an exact reference when the site adds a locale, moves its support center, or changes the reporting period.
Frequently asked questions
Do www and non-www have separate URL-prefix properties?
They can. The hostname is part of a URL prefix. A matching Domain property can give a broader view across those hosts.
Does verifying another property improve ranking?
Verification establishes access to Search Console data and tools for the property. It does not change the HTML, routing, or public content that a crawler visits.
Why does the live test succeed when the performance table is empty?
A live test investigates today's URL. The performance table requires reportable search activity inside the selected scope, filters, and time window.
Test an address from the missing section
Open the free page check with a public article from the host in question. Compare the returned page and canonical with the property map before changing your search reporting.
Filed under Strategy and audits. Topics: search-console, google, canonical, measurement