Question 1

What does done-for-you multi-location AI Overview presence tracking actually deliver?

Accepted Answer

Completions builds and operates a multi-location AI Overview presence tracker on the local-pack-tracking agent for multi-location retailers, multi-unit operators, and franchise systems running 50-1,500 locations across multiple DMAs and verticals. AI-surface scraping: the tracker collects responses from the AI-answer surfaces operator counsel approves — Google AI Overviews, Google SGE, ChatGPT browsing, Perplexity, Claude browsing, Gemini, Brave Leo, You.com — at the operator-approved cadence (typically daily, sometimes more frequent for crisis-response queries) through the operator residential-proxy and SERP-API layer (Bright Data, Oxylabs, Smartproxy, Zyte, ScraperAPI, SerpApi, Bright Data SERP API, DataForSEO, Apify, ScrapingBee) with per-location geo-targeting across zip, county, CBSA, DMA, Nielsen DMA, state, radius-circle, polygon, drive-time, walk-time, and transit-time dimensions. Citation extraction: each AI response passes through a multi-model LLM-as-judge ensemble (OpenAI GPT-5, Anthropic Claude Opus 4.7, Google Gemini Ultra, Mistral Large, Cohere Command R+, Meta Llama-3.1-405B) that identifies cited domains, cited pages, and cited entity references, with confidence-tier annotation and explainability trace per citation. Share-of-voice attribution: cited domains and entities resolve against the operator brand-entity registry (Wikidata IDs, Google Knowledge Graph IDs, sameAs-graph, per-entity-domain-mapping) and against the operator competitor watch list so share-of-voice rolls up per DMA, per vertical, per query, per surface, and per franchisee where applicable. Competitor diff: day-over-day deltas across the competitor watch list emit change events to the operator downstream marketing agents (local-content-generation, paid-search-bid-orchestration, brand-spec-authoring) when material movements occur. Below-floor alerting: per-location, per-franchisee, and per-cohort benchmarking (region, vertical, store-size, tenure, ownership-model corporate vs single-unit vs multi-unit vs area-developer) trigger alerts to the operator marketing team and franchisee council when AI-citation rate drops below operator-counsel-approved thresholds. Compliance overlay: where the operator is a franchisor, FDD Item 19 financial-performance-representation rules apply to any competitive-visibility data shared with prospective franchisees; FTC, state-AG UDAP, per-state franchise-relationship statutes, and per-jurisdiction AI-search vendor terms-of-service constraints (Google, OpenAI, Anthropic, Perplexity, Microsoft) on scraping cadence and data redistribution apply where relevant. Operator owns the brand-entity registry, query universe, competitor watch list, residential-proxy and SERP-API credentials under operator billing, scraping orchestration code in the operator repo, LLM-as-judge prompt library in the operator repo, compliance overlay rule library with attorney-approved updates, and the audit trail in operator-controlled storage. Completions owns the orchestration knowledge.

Question 2

Why is multi-location AI Overview presence tracking typically operator-side rather than proxy-vendor- or AI-visibility-tracker-shipped?

Accepted Answer

Six engineering surfaces sit between operator data infrastructure and a working multi-location AI Overview tracker, and they sit outside the design center of the proxy, SERP-API, LLM, single-brand visibility-tracker, and warehouse ecosystems that own the upstream primitives. Surface 1 — AI-surface scraping at multi-location scale: Bright Data, Oxylabs, Smartproxy, Zyte, ScraperAPI, and SerpApi ship strong geo-targeted residential-proxy primitives but per-AI-surface response shapes (Google AI Overviews, Google SGE, ChatGPT, Perplexity, Claude, Gemini, Brave Leo, You.com) differ surface by surface and ship updates without notice; DataForSEO, Apify, and ScrapingBee ship strong SERP primitives but AI-Overview parsing is operator-side modeling. Surface 2 — Citation extraction calibrated to the operator brand and competitor watch list: OpenAI GPT-5, Anthropic Claude Opus 4.7, Google Gemini Ultra, Mistral Large, Cohere Command R+, and Meta Llama-3.1-405B ship strong inference primitives but the prompt library, confidence-tier calibration, and explainability trace are operator-side. Surface 3 — Share-of-voice attribution: Ahrefs Brand Radar, Semrush AI Overview Insights, BrightEdge AI Optimization, Profound, Otterly.AI, AthenaHQ, scrunch, and AI Profiler ship strong single-brand visibility primitives but multi-location per-DMA per-vertical per-query per-franchisee roll-up with entity-resolution against Wikidata, Google Knowledge Graph, and sameAs-graph rarely runs as one coordinated bundle. Surface 4 — Competitor diff with day-over-day delta change-events emitted to downstream marketing agents requires event-driven architecture that traditional BI dashboards do not support. Surface 5 — Below-floor alerting per-location per-franchisee with per-cohort benchmarking and FDD Item 19 overlay requires operator-side per-portfolio per-banner per-franchisee data modeling. Surface 6 — Compliance and ToS overlay: AI-search vendor terms-of-service constraints on scraping cadence and redistribution are operator-counsel-side; FTC, state-AG UDAP, FDD Item 19 financial-performance-representation rules, and per-state franchise-relationship statutes are operator-counsel-side. Completions runs orchestration across all six surfaces under one Tier 3 Fractional CMO with AI Swarm engagement; operator owns the artifacts and can in-house at any time.

Question 3

What does the engagement look like across Tier 1, Tier 2, and Tier 3?

Accepted Answer

Tier 1 AI Readiness Assessment ($10k, 2-3 weeks, diagnostic): audits the six surfaces above against the operator stack — what residential-proxy and SERP-API vendors are wired today, what LLM-as-judge models are accessible, what entity-resolution layer exists, what visibility tracker (Ahrefs Brand Radar, Semrush AI Overview Insights, BrightEdge AI Optimization, Profound, Otterly.AI, AthenaHQ, scrunch, or AI Profiler) is in place, where the per-DMA per-vertical per-query coverage lands, and where the AI-search vendor terms-of-service and FDD Item 19 overlay need counsel review. Tier 2 AI Swarm Setup Sprint ($25-50k, 4-8 weeks): builds the tracker on the local-pack-tracking agent, with the LLM-as-judge prompt library reviewed by the operator data-science team and the AI-search vendor ToS plus FDD Item 19 overlay reviewed by operator counsel. Tier 3 Fractional CMO with AI Swarm ($15-25k/month, 6-month minimum, 1-2 days/wk embedded): continues operating the tracker end-to-end and coordinating with the adjacent location-benchmarking, master-record-canonicalization, brand-spec-authoring, compliance-overlay-manager, and anomaly-detection skills.

Question 4

Who owns the brand-entity registry, query universe, competitor watch list, residential-proxy infrastructure, and audit trail?

Accepted Answer

Operator owns 100% of every artifact. The brand-entity registry (Wikidata IDs, Google Knowledge Graph IDs, sameAs-graph, per-entity-domain-mapping) is versioned in the operator repo. The query universe (per-location buyer queries) is versioned in the operator repo with monthly refresh cadence. The competitor watch list is versioned in the operator repo with quarterly counsel-reviewed updates. Residential-proxy and SERP-API credentials (Bright Data, Oxylabs, Smartproxy, Zyte, ScraperAPI, SerpApi, Bright Data SERP API, DataForSEO, Apify, ScrapingBee) sit under operator billing; Completions configures and tunes but does not hold these credentials. The scraping orchestration code lives in the operator repo with operator-controlled deploy pipeline. The LLM-as-judge prompt library lives in the operator repo with confidence-tier and explainability tuning knobs. LLM API credentials (OpenAI, Anthropic, Google, Mistral, Cohere, Meta) sit under operator billing. The data warehouse (Snowflake, BigQuery, Databricks, or Redshift) sits under operator credentials. The compliance overlay rule library lives in the operator repo with attorney-approved updates and tracks FTC, state-AG UDAP, FDD Item 19 financial-performance-representation rules, per-state franchise-relationship statutes, and per-jurisdiction AI-search vendor terms-of-service constraints. The audit trail persists to operator-controlled storage with WORM retention where SEC, FINRA, SOX, or state franchise-registrar rules apply. Completions owns the orchestration knowledge — how to design the query universe, how to tune the LLM-as-judge ensemble, how to debug residential-proxy degradation when AI-surface response shapes shift, and how to coordinate with the location-benchmarking, master-record-canonicalization, brand-spec-authoring, compliance-overlay-manager, and anomaly-detection siblings. The operator can in-house at any time; Completions credentials revoke immediately on engagement-end.

Question 5

What does Completions commit to on a Tier 3 engagement?

Accepted Answer

Completions commits to a 6-workstream pre-engagement-baseline reporting cycle on the local-pack-tracking agent: (1) AI-Surface-Scraping workstream — pre-engagement baseline of which AI-answer surfaces the operator scrapes today and at what cadence, then weekly reporting on per-surface scrape coverage, residential-proxy health, and surface-response-shape change events caught. (2) Citation-Extraction workstream — pre-engagement baseline of how citations are extracted today (manual review, regex, single-model LLM), then weekly reporting on LLM-as-judge ensemble coverage, confidence-tier distribution, explainability completeness, and operator-data-science-team-aligned holdout-sample agreement. (3) Share-of-Voice workstream — pre-engagement baseline of how operator brand vs competitor share-of-voice is measured today, then weekly reporting on entity-resolution coverage against Wikidata + Knowledge Graph + sameAs-graph + per-entity-domain-mapping. (4) Competitor-Diff workstream — pre-engagement baseline of which competitors are tracked today, then weekly reporting on day-over-day delta capture and change-event emission to downstream marketing agents. (5) Below-Floor-Alerting workstream — pre-engagement baseline of which per-location and per-franchisee thresholds are wired today, then weekly reporting on alert volume, per-cohort benchmarking output, and operator-marketing-team and franchisee-council response cadence. (6) Compliance + ToS workstream — pre-engagement baseline of AI-search vendor terms-of-service review status and FDD Item 19 overlay status today, then weekly reporting on overlay completeness, ToS-update detection, and counsel re-review state. Caveats: AI-search vendor response shapes (Google AI Overviews, Google SGE, ChatGPT, Perplexity, Claude, Gemini, Brave Leo, You.com) change without notice and require Completions to update scrapers and prompt libraries on detection; AI-search vendor terms-of-service updates are vendor decisions outside Completions control and require operator-counsel re-review of scraping cadence and data redistribution; residential-proxy vendor pricing, IP-pool health, and CAPTCHA rates are outside Completions control; LLM-vendor API rate limits, model deprecation, and pricing changes are outside Completions control; FDD Item 19 financial-performance-representation thresholds and per-state franchise-relationship statutes can change and require operator-counsel re-review; FTC and state-AG UDAP policy can change without notice; per-cohort benchmarking depends on operator data-warehouse maturity and the size of each cohort; the audit trail persists to operator-controlled storage on the operator cloud account; below-floor alert thresholds are operator-counsel-policy decisions; competitive-visibility data shared with franchisees is operator-counsel-policy.

Question 6

How does engagement end and what is the operator transition path?

Accepted Answer

Tier 3 engagements are 6-month minimum with 90-day notice. At engagement end, Completions transitions back to operator in-house in 30-60 days: operating-playbook hand-off + in-house staff training across 3-5 operator team members covering AI-surface scraping, citation extraction, share-of-voice attribution, competitor diff, below-floor alerting, and compliance and ToS overlay management + brand-entity registry hand-off + query universe hand-off + competitor watch list hand-off + residential-proxy and SERP-API credentials hand-off + LLM API credentials hand-off + scraping orchestration code hand-off + LLM-as-judge prompt library hand-off + compliance overlay rule library hand-off + audit-trail hand-off with operator-account-ownership confirmation; Completions credentials revoke immediately on engagement-end.

Frequently asked