Visibility troubleshooting.
Partial crawls, missing Core Web Vitals, an AI score that says 'Not measured', and a Search Console connection that keeps dropping. Most of these are the product telling you the truth.
The six things people write in about, with what's actually happening in each case. Most of them are the product working correctly and telling you the truth — which is exactly why they're confusing.
“It only audited 63 of my 200 pages”
You're on Agency, you asked for 200 pages, and the report says it audited 63. Nothing is broken.
A crawl has two budgets: a page budget (your plan's ceiling) and a hard time budget. The audit runs inside a single request, so it has a wall-clock cap of well under a minute — and on a large or slow site it will hit the clock before it hits the page count. When it does, it stops, scores what it read, and reports honestly: audited 63 of 200 pages.
- You're only charged for the pages actually read. Not for the 200 you asked for. The bill follows the crawl, not the request.
- The 63 aren't a random 63. Pages are ranked for template diversity before the crawl starts, so you get a spread of page types — homepage, product, blog, about — rather than the first 63 URLs in your sitemap. The score is representative even when the crawl is partial.
- Pages we never reached aren't counted as failures. A page the clock never got to can't fabricate a broken link or a missing title. It's simply absent.
Speed up your server, and the crawl reaches further in the same time. That's not a cop-out answer — a slow time-to-first-byte is why the crawl fell short, and it's costing you rankings for exactly the same reason. See Core Web Vitals.
No Core Web Vitals
The Core Web Vitals section is empty, or it says it's measuring.
Real Core Web Vitals are field data — they come from actual Chrome users who visited your site. Google only publishes them once a page (or an origin) has enough traffic to be statistically meaningful and to stay anonymous. A quiet site simply has none. This isn't a fault, and there's nothing to configure — it's a consequence of not having many visitors yet.
When there's no field data we fall back to a lab estimate: a single simulated page load on a throttled mobile connection. The section labels it as a lab result so you're never comparing the two by accident. One difference to know about: the lab can't measure INP (it needs real people clicking things), so it reports TBT in its place as the closest stand-in.
Treat the lab number as directional. It's a good guide to whether your page is heavy; it's not a measurement of what your visitors experience. Field versus lab, in full →
AI Visibility says “Not measured”
A component bar on the AI Visibility tab shows Not measured yet instead of a score. There are three causes, in order of likelihood:
- You have no competitors. This is nearly always it. AI share-of-voice — 45% of the score — asks whether the assistant names you or them. With no rivals on the brand there is no “them”, so it can't run. Add at least one under Brand → Competitors and run the check again.
- You haven't run a check. AI Visibility doesn't compute itself in the background. If you've never pressed the button, there's nothing to show. The first check on each brand is free.
- Citability has no site to read. If your brand has no website URL, we have no content to score. Add it under Brand.
An unmeasured component isn't scored as zero — it's reweighted out, so your score is calculated from what we could measure. That's the honest treatment, but it means the first check that does include share-of-voice can move the number sharply. That's not a bug. How the composite works →
Search Console keeps asking me to reconnect
Traffic worked, then one day the tab is asking you to connect Search Console again.
We hold a refresh token from Google, and Google can revoke it. When it does, the next attempt to read your data fails, we mark the connection as errored, and the tab prompts you to reconnect. Common reasons:
- Someone removed ScoutRival's access in the Google account's third-party apps settings.
- The Google password was changed, or the account's sessions were revoked.
- The Google account lost access to that Search Console property.
The fix is the same in all three cases: reconnect. It's the same popup as the first time, it takes a few seconds, and your history isn't lost. If it drops again within days, check that the Google account you're authorising is the one that actually owns the property. Connecting Search Console →
My score jumped when I connected Search Console
Your SEO score moved several points the moment you connected Search Console, and you hadn't touched the site. Correct — and expected.
Without Search Console we have no search-visibility data, so that pillar can't be scored. Rather than give you a zero for something we couldn't measure, we remove it from the calculation and score you out of the remaining pillars. Connecting Search Console switches the pillar on: now it counts, and your score is recalculated with it included.
Which way it moves depends on how you're actually doing in search. Up if you're ranking well, down if you aren't. Either way the new number is the more truthful one. How the pillars are weighted →
Audits don't refresh on their own
They don't, and they aren't meant to. Audits and AI Visibility checks are manual, on demand. Nothing schedules them; nothing re-runs them overnight; a score you're looking at is from the last time you ran one.
That's deliberate — an audit costs credits and takes time, and we won't spend either without you asking. But it has a consequence people get caught by: fix something and your score won't move until you re-run the audit. Deploy your fixes, then run it again to see the change.
The date sits next to the score. If it's from six weeks ago, it's telling you about the site you had six weeks ago.
The smaller ones
- “Already refreshed today” — AI Visibility is limited to one check per brand per day. Share-of-voice doesn't move hour to hour; come back tomorrow.
- The device screenshots are blank. Google's PageSpeed service either rate-limited us or timed out on your homepage. Hit Try again. If it keeps timing out, that's a real finding about your homepage's weight. Device render →
- My AI mention rate dropped, but I changed nothing. Check the ± band before you react. AI answers vary between runs — if the move is smaller than the band, you haven't measured a change. Turn your runs up (they're free) for a tighter reading. Why →
- One engine shows 0% and the others don't. That usually isn't a content problem — it's an access problem. Check whether that engine's crawler is blocked in your
robots.txt. The six user-agents that matter → - My off-site footprint scores badly and I don't know why. Open the recommendations — the missing Wikidata entity is usually the one dragging it, and it's the most fixable item on that list.