Read the AEO roll-up
How do I compare AI visibility across all my locations?
Leave the location picker on All locations and the AEO page becomes a portfolio view instead of a report. It answers three questions: how many of your locations have been measured at all, which band each one sits in, and which single fix would lift the most of them.
Start with coverage. Everything else is unreliable until you know how much of the portfolio is actually in the data.
Coverage first, average second
The header tiles read Avg AI visibility, Momentum this month, Coverage and Needs attention. The one to read first is ② Coverage — it states how many locations have an AI-visibility report and counts the rest as awaiting first report.
On the portfolio above that reads 13/136. Coverage 13 / 136 means 13 of the 136 locations in this portfolio currently have an AEO report. It is not a performance score. The remaining 123 locations are awaiting their first measurement.
Read ① Avg AI visibility 11/100 in that light: it is the average of those thirteen measured locations, not of a hundred and thirty-six. An average across a tenth of your portfolio is not your portfolio average, and reporting it as one will mislead whoever you send it to.
Locations without a report are not scoring zero — they have never been asked. The table marks them Awaiting first report rather than 0, and the distinction matters: a zero is a finding, an unmeasured location is a gap in the data.
Opening one of those unmeasured locations starts a paid measurement immediately. Don't click through the roll-up location by location to "fill in" the blanks — see where reports come from.
The four bands
Portfolio health groups every location into four bands you can click to filter the table below.
| Band | Score | What it means |
|---|---|---|
| Strong | 60+ | Well cited by AI |
| Fair | 30–59 | Named sometimes, rarely first |
| Weak | under 30 | Nearly invisible to AI |
| No report | — | Never measured |
The table underneath carries Location, Visibility, Trend and Top issue — the last being that location's weakest visibility factor, or Healthy when none is weak. Sorting your attention by Top issue rather than by score is usually the faster route to a fix, because it groups locations that need the same work.
Fix once, lift many
This is the section that justifies the roll-up existing. It finds weaknesses shared across locations, counts how many are affected, and routes each to a single tool — "13 locations missing directory citations · AI cites directories like Bing Places & Apple Maps — get listed", with a Fix in Listings → button beside it.
Weak review signal routes to Reviews the same way, and stale content routes to Posts. When a weakness covers every reporting location, it is almost never that many separate problems. It is one workflow that was never set up, and fixing it once is worth more than any individual location's action list.
Movers, and why the biggest gains are usually not gains
Movers this month ranks by change against last month. Early in a portfolio's life that list is dominated by locations recording their first real measurement: a location that went from an empty first report to 81 shows as +81 and tops Biggest gains without anything having improved.
The same artefact shows up in ③ the portfolio trend line above. That line runs June 15 → July 2 → August 12, which looks like a collapse and a partial recovery. It is neither. July is the month the portfolio went from two measured locations to thirty, so the average fell as a crowd of first reports — most of them scoring zero — joined it.
Read the trend alongside the Coverage tile every time. A move in the average that coincides with a move in coverage is a measurement change, not a performance change.
When there isn't enough history to draw a line yet, the card shows your current average with "This is your first monthly data point" and a clearly-badged See example → illustration. That example is invented and always slopes upward; don't put it in front of a client.
Watch out for
Where to go next
- What does my AI Visibility score actually measure? — what each location's number is counting
- What should I fix first to improve AI visibility? — the single-location version of Fix once, lift many