Local AEO Visibility (retired — see AI Visibility)
Updated · Aug 19, 2026Retired. Everything it measured now lives inside AI Visibility, behind a per-project local mode.
What changed
Retired. This add-on was built but never reachable by a customer: a stacked-PR accident merged its backend to staging while every UI branch merged into an orphaned parent, so the tables, models and services shipped with no way to open them. Rather than finish a second product that answers the same question as AI Visibility, the parts that were genuinely unique — locations, opportunities, crawler activity, reports — were ported into AI Visibility behind a local mode. This page is kept as a pointer so an old link does not 404, and because the honest record of why it went is more useful than a guide to a page that does not open.
User goal
Find where the local measurement features went.
- Tier
- Retired — no longer sold
- Nav label
- AI Visibility
- Route
- /projects/{project}/llm-listening/overview
- Gates
- —
Prerequisites
- llm-listening-addon active (AI Visibility)
QA focus
- No customer-facing route resolves to the retired add-on
Overview
This add-on is retired. Everything it set out to measure now lives inside AI Visibility, switched on per project with a local mode.
Where each part went
| Local AEO | Now in AI Visibility |
|---|---|
| Campaigns with locations | A project in local mode, with a Locations tab |
| Per-location visibility runs | The existing runs, expanded across your locations |
| Opportunities board | Recommendations in Intelligence, alongside search and analytics |
| Bot activity | The Bot activity tab, read from your own Cloudflare zone |
| Reports | The Report tab, on screen and as a co-branded PDF |
Why it was retired rather than finished
It answered the same question as AI Visibility, and AI Visibility was already the product customers used. Two features measuring one thing means two sets of numbers that can disagree — so the parts that were genuinely different were moved across and the duplicate was dropped.
Common issues & false alarms
- An old link to a Local AEO page → open AI Visibility for the project instead
Interactive guide
Step of
All steps (reference)
-
Step 1. Open AI Visibility instead
The local measurement features are on the project's AI Visibility screens. Turn on local mode in Project Settings → Local SEO, then add the cities you serve under AI Visibility → Locations.
What to do: Open AI Visibility for the project
Where: llm-listening.overview
Expected (pass)
- Local mode reveals the Locations tab
- Overview and Citations split by place once a run completes
Related guides
AI Visibility (LLM Listening)
See how the answer engines describe your brand — overall, per engine, and per place you serve — with the evidence behind every number.
Intelligence Hub
Cross-source insights combining GSC, GA4, scans, and audits.
Billing & Subscriptions
Manage subscription tier, purchase credits, add-ons, and view billing history.
Content Strategy
Find what competitors publish, which buyer questions nobody owns, and what to change when an AI answer cites someone else.