Why There Is No Data in 'Pulse'
'Pulse' shows dynamics for each link: positions, clicks, impressions, indexing. If there are dashes instead of numbers, the reason is almost always in the data sources, not a malfunction.
Where 'Pulse' Gets Its Numbers
| Metric | Source | Condition |
|---|---|---|
| Impressions, clicks, position | Google Search Console | A connected and verified resource is needed |
| Sessions and conversions | Google Analytics 4 | A connected GA4 property is needed |
| Publication indexing | Own checks | Works without connections |
| Referring domain metrics | External sources | Works without connections |
Hence the rule: part of 'Pulse' always works, while the search part only works after connecting Search Console.
Five Reasons for Empty Values
- Search Console is not connected. The most common case — see how to connect.
- The wrong resource is connected. The project domain must match the resource; for a subdomain, a parent domain resource is needed.
- Data has not yet accumulated. Search Console provides statistics with a delay of a couple of days, and history accumulates over weeks.
- No impressions for the page. No demand — no rows; this is data, not an error.
- The link is too fresh. The publication has not yet been indexed, so it cannot have an impact yet.
How to Check in a Minute
Open Search Console, select the project resource, and look at the performance report for the last 28 days. If it’s empty there, 'Pulse' has nowhere to take data from, and the fix needs to be on Google's side. If data exists but is not in 'Pulse', check the domain match and your account role, see Radar does not see the site.
What to Do If Search Console Is Unavailable
Part of the picture will remain: publication indexing, domain metrics, and the fact of a live link are counted without it. In this case, it is more convenient to track positions separately — through Rank Tracker, which does not require access to your analytics.
Delay Is Normal
Even with ideal settings, fresh days in search reports do not appear immediately: data is pulled with a delay of a couple of days, and sometimes longer. Therefore, "it was there yesterday, not today" for the last day is a common picture, not a loss of data.