Locations Dashboard

The Locations dashboard lets you track AI visibility separately for each geography you operate in — different cities, countries, or storefronts under one parent brand or product. Each location runs the same prompts as the parent with its own location injected, so you can compare share of voice across markets on an even footing.

Typical use cases include a multi-office practice (e.g. a dental group with offices in three cities), a regional or national chain, a brand expanding into a new market and wanting to baseline visibility before and after, or a single product rolling out country by country.

What You'll Learn

• How locations relate to a parent brand or product
• How to add a location and what data it requires
• How prompts and brand identity are inherited from the parent
• How metrics roll up to the parent and where to find them
• How to compare share of voice across locations

How Locations Work

A location is a sub-property of a parent brand or product. (Those are the only two subject types that can own locations — a product's markets work exactly like a brand's.) Locations:

• Inherit the parent's brand snapshot, company name, and aliases for brand-mention matching. The location's own label (e.g. "Downtown") is display only — it is never used to match brand mentions in AI responses.
• Inherit the parent's discovery prompts. When prompts run for a location, the location's city / region / country is injected into the LLM context (and substituted into any {location} placeholder in the prompt text).
• Manage their own competitors. Local competitor sets often differ market-by-market, so each location has its own list rather than inheriting from the parent.
• Accrue their own metrics — share of voice, mentions, citations — independent of the parent's brand-wide rollup.

You can drill into a location to see its own dashboard, run an AI Visibility Report against it, manage its competitors, and view its historical metrics, all scoped to that market.

Adding a Location

From the parent property's sidebar — a brand or a product — click Locations, then Add location. The dialog asks for two things:

1. Location (required). Search and pick a place. Toggle City ↔ Country to switch the granularity — use Country to track at the national level (good when local results vary little within the country) and City for finer-grained tracking.
2. Label (defaults to the city or country name). A short name that distinguishes this location in lists, e.g. "Downtown", "Airport", or just the city. Customize it if you want, or leave the auto-filled name.

Note: the label is a display field only. It does not affect brand-mention matching — the parent brand's company name and aliases are always used for that. A location labeled "Palm Beach Gardens" still has its mentions counted against "Anchor Bank" (the parent), not against "Palm Beach Gardens".

After creation, nightly prompts will start running for this location automatically. The first metric data points appear after the next nightly run completes (usually within 24 hours). You can also trigger an AI Visibility Report on the location at any time to populate data immediately.

The Locations Page

The Locations page lists every location under the parent and shows the latest SOV and mentions for each at a glance. The page exists for both management (add / open / delete) and quick scanning.

Locations with no data yet show — instead of 0 so you can tell "no measurements yet" apart from "measured zero."

Where Location Metrics Show Up

On the parent property's dashboard

When a brand or product has at least one location, the main property dashboard replaces the property-wide Share of Voice widget with a Share of Voice by Location widget. It shows three at-a-glance tiles plus a ranked list:

• Average SOV — equal-weighted across all locations with data, i.e. the "typical location" number
• Total Mentions — summed across locations
• Total Citations — summed across locations
• Ranked list — each location with its latest SOV, mentions, and citation count, sortable by Highest SOV / Lowest SOV / Most Mentions / Name

If the parent has no locations, the property-wide Share of Voice widget shows instead — the original behavior is preserved.

On a location's own dashboard

Each location has its own Share of Voice widget showing that location's metrics in isolation — SOV, mentions, and citation trends over time, plus competitors specific to that market.

On the locations drill-down

When a brand or product has locations, its dashboard gains a Locations card that opens a cross-market view: a share-of-voice trend line per market (with the location-neutral brand-wide run as a dashed reference line), and a table of each market's latest measurement. Opening a market from that table gives you its own funnel, its own prompts, and the full AI answers for any day — the same two-level drill-down the brand-wide funnel uses, scoped to that market.

How Brand Identity Is Inherited

When AI responses are analyzed for brand mentions on a location's runs, the matcher always uses the parent brand's company name and aliases — never the location's label. This is intentional:

• A response that says "Anchor Bank has branches in Palm Beach Gardens and Boca Raton" should count as one mention of the parent brand at both locations' runs, because we're testing whether AI assistants recognize the brand in each market — not whether they recognize the location.
• The location's label ("Downtown", "Palm Beach Gardens") is meaningful to you for navigation and reporting, but is not a brand the LLM is being asked about.

Under a product parent the rule is the same, with the product's name and aliases doing the matching instead of the brand's.

This applies to:

• AI Visibility Reports run on a location
• Nightly prompt runs for a location
• Brand-mention extraction in the citation intelligence pipeline
• Share of voice calculations and competitor SOV comparisons

If you edit the parent's aliases later, the historical metrics for every child location recompute automatically — typically within 10–30 seconds.

What Locations Do Not Have

A location is a geographic slice of the parent brand or product. It does not have:

• Its own domain — it inherits the parent's
• Its own brand snapshot — shown read-only on the location, sourced from the parent
• Its own AI readiness audit, robots.txt analysis, or sitemap import — these are domain-level concerns and only meaningful on a parent brand
• Its own prompts — the parent owns the canonical prompt set; locations run them with location context injected

If you need to track something independently of the parent (e.g. a sub-brand on a different domain), create a separate top-level property instead.

How Locations Are Billed

Each location runs its own real prompt against every tracked platform every night, so each location adds a daily prompt run. A tracked prompt on a brand or product with N locations consumes N + 1 of your plan's included prompt runs per day — one for the location-neutral parent-wide run, plus one per location. Runs beyond your plan's allocation are billed at 1 credit per 30 daily runs, prepaid per run. If your organization runs out of credits, runs pause individually — a paused location never stops the parent-wide run or your other locations, and everything resumes automatically the day after you add credits.

Best Practices

Add your primary market as its own location

The parent-wide run is deliberately location-neutral — no city or region is injected — so it measures your national/global baseline, not your home market. To measure your primary market on the same footing as the others, add it explicitly as a location alongside the rest. Many multi-location customers do exactly this: a Denver-headquartered brand tracking Denver, Boulder, and Colorado Springs adds all three as locations and treats the parent-wide run as the geography-free control.

Start with City-level for local businesses

Local businesses typically see meaningful differences between cities. Use City-level tracking and you'll get the most actionable insights.

Use Country-level for national chains

If your locations span entire countries and the prompts you care about are national rather than local, Country-level tracking is enough and produces less noisy results.

Manage competitors per location

Local competitors really do vary by market. Don't copy the parent's competitor list into every location — let each location track its actual local rivals. The same holds for a product's markets: the rival energy drink in Berlin is rarely the rival in Austin.

Use the same prompts for fair comparison

Resist the urge to write location-specific prompts. The point of the locations feature is that the same prompts run for each market, so SOV is comparable. If you need a one-off local prompt, add it to the parent and rely on the location injection — don't fragment your prompt set.

Related

• AI Visibility Reports — Run a report against a specific location
• Competitors — Each location manages its own competitor list
• Discovery Queries — Parent-owned prompts that all locations inherit
• Tracking Locations & Franchises — The feature guide: when to use locations and how prompts fan out
• Tracking Products — Products can own locations too