Read the AEO roll-up
How do I compare AI visibility across all my locations?
Choose a client, then leave the location picker on All locations. AEO turns into a portfolio view for that client. Use it to move from the brand picture to one location that needs a closer look:
- Check how many locations have a report.
- Find the location that is weak on the AI engine that matters to you.
- Open that location and read the evidence behind the gap.
- Return to the portfolio to see whether the problem repeats elsewhere.
Key facts
| Where it lives | Marketing → AEO, with a client chosen and the location picker on All locations |
| What it covers | Every location of that client. With no client chosen it covers every location you can access. Tags do not filter this report |
| First read | Coverage, then Avg AI visibility |
| Bands | Strong 60 or above, Fair 30 to 59, Weak below 30, No report |
| What it can't do | Start or refresh reports. Generating and scheduling happen one location at a time |
Steps
Open AEO from Marketing. In the scope bar choose the client, then All locations. If AEO opens on a single location instead, open the scope bar and choose All locations, or select Choose location and return.
Read Coverage before Avg AI visibility. In the example below, Coverage is
3/4with 1 awaiting first report, so the average of46/100describes the three locations that have reports, not all four.Find the weak location and engine in the location table (see the next section).
Open that location and stay on Overview to see the questions and engines behind the number.
Return to All locations and read Fix once, lift many to see whether the weak factor repeats.
Avg AI visibility and Needs attention (the cards with an arrow) open the Locations list filtered to the locations they count, and the small circled i beside a card names exactly which locations it includes.
Start with a trustworthy portfolio view
Coverage is the check on everything else. Here three of four locations have a report, so the average represents those three. A location marked Awaiting first report is unmeasured, not a zero, and it is left out of the average, Momentum and Needs attention.
To measure it, open that location from the table and generate its first report. The AEO roll-up has no refresh clock and no schedule of its own, because each location has its own: open a location and use Manage schedule, or go to Settings → Data updates. How AEO reports are made covers the first report, what the cost line means and the Weekly, Monthly, Quarterly and Never options. A location with no report is not run automatically until someone generates its first report or saves a schedule for it.
Find the location that is weak on your priority engine
The table at the bottom of the page lists each location with its Visibility, change, Trend, a column for each engine and its Top issue. Click a column heading to sort.
Top issue names each location's weakest factor, or Healthy when even the weakest is strong. Evanston leads overall, but the overall number is only an average of the engines. Lakeview is respectable on ChatGPT (61) and weak on Gemini (35), so for a Gemini investigation Lakeview and Oak Park come before Evanston. An engine your account does not have set up shows n/a in its column instead of a score.
Open the location and investigate the gap
Open Lakeview and stay on Overview. Its report turns the roll-up comparison into evidence:
- Prompt coverage shows the exact questions and engines where the location is strong, partial or absent. How do I read the prompt coverage grid? explains each cell.
- Visibility factors shows the supporting signals and a link to the area where each can be changed.
Lakeview's Reviews factor is 38 and Citations is 36. Those are leads to investigate, not proof that either one caused the weak Gemini score. Check the Gemini column in Prompt coverage first, then decide what to change.
Decide whether the issue is local or shared
Return to All locations and read Fix once, lift many. It groups weak factors that repeat across the reporting locations. Here two locations have a weak review signal, so Reviews is a shared job rather than a Lakeview-only one.
Each row has a link into the area that supports the fix:
- Fix in Reviews opens the Reviews roll-up for the client.
- Fix in Listings opens Listings for the client.
- Fix in Posts opens the Posts roll-up for the client, for stale content.
These links take you to the client, not to a particular location or directory. To go straight to the directories one location is missing, open that location's Citations tab and use its Fix in Listings button. A repeated factor tells you where to look together; it does not prove the cause, so compare the underlying location reports before changing a workflow for the whole brand.
Use health bands to narrow a larger portfolio
Portfolio health is a quick filter, not another score:
- Strong: 60 or above
- Fair: 30–59
- Weak: below 30
- No report: not measured yet
Select a band to filter the location table, then choose a location and engine to investigate. Select Clear filter to return to all of them. Needs attention counts only reporting locations below 30, so it excludes locations with no report.
Read movement with coverage
Momentum this month compares each location's latest report with its previous one, for the locations that have both. Hover the circled i for the exact rule: it is the latest report against the previous report, not calendar months, and a location whose score did not change counts in neither the up nor the down number. The change beside the average is the average of those locations' changes, not the difference between two portfolio averages.
The trend chart averages only the locations that produced a report in each month, and hovering a point shows how many that was. In the example, September has one reporting location, October two and November three, so part of the climb comes from more locations joining the average, not from any one location improving. A location that updates weekly or on demand still has one report per calendar month, so its movement is measured month to month.
A location on a Never schedule keeps its last report until someone refreshes it, so one stale score can sit beside fresh ones. Open the location and check Last check in its refresh clock before comparing.
What you'll see when it's done
- The average, momentum, coverage and attention cards for the client, with the locations behind the average and attention cards a click away
- A short list of locations to open first, chosen by engine, band or shared issue
- A decision on whether the issue is local to one location or shared by several
Watch out for
- Incomplete coverage changes what the average means. Read Coverage first.
- A different number of reporting locations changes the trend. Hover each point to see how many locations it averages.
- Fix once links are not location-specific. They open the client's roll-up pages.
- The roll-up cannot refresh anything. Updates are run one location at a time.
Questions people ask
Why does AEO open on one location instead of the roll-up?
The page can remember the last location you used. Open the scope bar and choose All locations.
Can I run reports for every location from here?
No. Reports are started and scheduled one location at a time, and Sydekick can read the roll-up but cannot start reports either.
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