Radar does not see the site in Search Console
Radar builds calculations based on Search Console data, so the first thing it checks is whether the project's site is verified in the connected Google account. If the message 'project domain not found in your Search Console' appears, the reason is almost always one of the five things below.
What is suitable and what is not
| Resource in Search Console | Project | Suitable? |
|---|---|---|
Domain resource example.com | example.com | Yes |
Domain resource example.com | blog.example.com | Yes — the domain resource covers subdomains |
Prefix https://www.example.com/ | example.com | Yes, www is discarded |
Prefix https://example.com/ | blog.example.com | No — the prefix resource does not cover the subdomain |
| Google Analytics resource | any | No — Radar works with Search Console resources |
Five reasons by frequency
- A different Google account is connected. In the settings, you can see the linked email: the site must be verified in that account.
- The subdomain does not have a suitable resource. The parent domain resource will work, but the prefix will not: add a domain resource or a resource for the subdomain itself.
- You are an unverified user in the resource. Such resources are skipped by the platform — ask the owner to grant full access.
- The resource has been added, but verification is not complete. It must have a verified status in Search Console.
- The resource was just created. The list of sites is cached, but if the matching fails, the platform reads it again — if that doesn't help, re-enter the dashboard.
Domain resource vs prefix
The domain resource is verified by a DNS record and covers everything at once: http and https, with www and without, all subdomains. The prefix is verified by a file or meta tag and covers exactly one address variant — for Google, http://site.com and https://www.site.com are different resources. If you are starting from scratch, choose the domain: it does not break into variants and covers future subdomains.
Action steps
- Open Search Console and check if there is a verified resource for the project address or its parent domain.
- Make sure the same Google account is connected in PromoPilot.
- Reopen Radar for the project.
- If the resource was just created — re-enter the dashboard to ensure the site list cache is reset.
- Allow the new resource to accumulate data: Radar needs a history of about 28 days.
What Radar will show when data appears
Pages at the top threshold, queries with insufficient clicks, budget strategy, and comparison with competitors. Full description — how Radar works, and the connection instructions — here.