Question 1

What does the 4-stage multi-location citation pipeline actually deliver, and where does it sit in the local-SEO workflow?

Accepted Answer

An orchestration layer that sits above the operator listing-aggregator + per-directory + master-record + link-analysis + webmaster-tools + schema + policy-as-code + WORM-storage stack and runs a four-stage pipeline across 200+ citation directories. Stage 1 — citation governance: maintain the per-location master-NAP record (name, address, phone, categories, hours, amenities, services, attributes, service-area polygon, entrance coordinates) in the operator master record (Snowflake, Databricks, BigQuery, Redshift, Postgres — operator chooses) with per-location canonical resolution, per-location conflict resolution (when different sources disagree about the canonical NAP), per-location attribute versioning, and per-location change-event emission to the customer-change-event-emission sibling skill (so downstream systems stay in sync). Stage 2 — citation propagation: emit per-location per-directory updates across 200+ directories through the operator-chosen listing aggregator (Yext, Uberall, Synup, Birdeye, Reputation.com, Vendasta, Moz Local, BrightLocal, Whitespark) plus direct integrations (Google Business Profile API, Yelp Fusion API, Apple Maps Connect, Bing Places API, Facebook Pages API), with per-directory ingestion mechanism (API, webhook, SFTP, form submission), per-directory approval gating (some directories require human moderation), per-directory rejection handling, and per-directory re-submission protocol. Stage 3 — citation maintenance: per-directory drift detection (the operator master record says one thing, the directory says another), schema-change detection (the directory added a new field or deprecated an old one), deprecation detection (the directory itself is going away), orphan detection (a directory profile exists that the operator master record does not reference), suspension detection (a directory suspended the operator profile), per-directory health check, per-directory remediation. Stage 4 — citation link-building: per-directory inbound-link extraction, per-link domain-authority scoring (Ahrefs, Majestic, SEMrush, Moz, Cognitive SEO, Searchmetrics — operator chooses), per-link relevance scoring, per-link toxicity scoring, per-link disavow recommendation (fed into Google Search Console disavow + Bing Webmaster Tools disavow), per-location link-velocity tracking, anchor-text diversity tracking, referring-domain diversity tracking. Every stage decision routes through the 5-anchor compliance gate before commit and writes to the WORM audit trail with rule_id, policy_version, decision, evidence_pointer. The listing aggregator, per-directory, link-analysis, webmaster-tools, and schema vendors below ship strong primitives. The orchestration above them — governance, propagation, maintenance, link-building, compliance gate, audit trail — is operator-side architecture.

Question 2

Where does single-vendor listing management stop compounding for multi-location retail and multi-unit franchise operators?

Accepted Answer

Single-vendor listing management is solved. Yext ships strong enterprise-scale listing distribution. Uberall + Synup ship strong multi-location listing distribution. Birdeye + Reputation.com + Vendasta + Moz Local + BrightLocal + Whitespark ship strong local-listing primitives. The compound case the citation-link-build agent has to handle is the one where a multi-location operator runs 50-1,500 locations, the listing aggregator covers 70+ of the 200+ directories that matter for the operator’s vertical, but the long-tail 130+ niche-vertical directories (state-specific licensing-board directories for medical/dental/optometry/pharmacy/legal; vertical-specific directories for  or alcohol or pharma) need direct integration; the master NAP changes (a store moves, hours change for the holidays, a category gets added) need to propagate through the listing aggregator and through the direct integrations consistently; per-directory drift inevitably appears because directories normalize NAP fields differently (the address that the operator submitted as "123 Main St, Suite 400" gets stored as "123 Main Street, #400" at one directory and "123 MAIN STREET STE 400" at another); per-directory schema changes need to be detected before they break propagation; per-link toxicity needs to be tracked because spammy directories pick up the operator NAP and link to it whether the operator wants the link or not; per-vertical compliance overlays (HIPAA-vertical NAP cannot include PHI;  NAP must follow per--regulator content rules; alcohol NAP must follow DISCUS + state liquor-board rules) apply across the directories; FTC Fake Review Rule + Endorsement Guides 2024 amendments apply to review responses at any directory that supports reviews. Without an orchestration layer above the listing aggregator + per-directory + link-analysis + webmaster-tools vendors, the long-tail directories go unmaintained, the cross-directory drift accumulates, the per-link toxicity ratchets, and the cross-directory compliance gate cannot be enforced consistently. The 4-stage citation pipeline on the citation-link-build agent is the orchestration that holds the cross-directory + cross-vertical + cross-jurisdiction invariants.

Question 3

How does Stage 1 citation governance work, and how does it coordinate with the master-record-canonicalization sibling skill?

Accepted Answer

Stage 1 lives at the boundary between the operator master record and the citation pipeline. The operator master record (maintained by the master-record-canonicalization sibling skill on the master-record agent) is the canonical source for per-location NAP. Stage 1 subscribes to the master-record change-event stream and turns every NAP-relevant change into a citation-propagation work item. The governance step also runs the inverse — when a directory propagation surfaces a per-location attribute the master record did not have (a new category the directory supports, a new hours-of-operation field, a new service-area attribute), governance escalates the gap back to the master-record-canonicalization sibling skill so operator-counsel-and-data-team can decide whether the new attribute belongs in the canonical record. Per-location conflict resolution handles the harder case: when two directories disagree about the canonical NAP (Yelp normalized the address one way, Google Business Profile normalized it another way, the operator POS system has yet a third version), governance applies the operator-counsel-and-ops-team-set canonical-resolution policy (typically: operator POS as ground truth + USPS verification + per-jurisdiction-municipal-address-database verification + operator-data-team-attested resolution rule) and emits the canonical form back to every divergent directory through Stage 2 propagation. Per-location attribute versioning preserves every change with attestor + timestamp + rule for SOC 2 + counsel-driven audit. Per-location change-event emission flows into the customer-change-event-emission sibling skill on the customer-graph agent (which propagates to CRM + ESP + ad-platforms + loyalty + analytics + downstream agents across the swarm under the GDPR Article 19 recipient-notification obligation). The vendors below ship strong primitives. The cross-skill governance contract above them is operator-side architecture.

Question 4

How does Stage 4 citation link-building handle per-link toxicity scoring + disavow recommendation without over-disavowing?

Accepted Answer

Stage 4 reads the inbound-link graph from operator-chosen link-analysis vendors (Ahrefs, Majestic, SEMrush, Moz, Cognitive SEO, Searchmetrics) and assembles a per-location per-link cross-vendor canonical view. Each link carries a vendor-supplied domain authority score (Ahrefs Domain Rating, Majestic Trust Flow, Moz Domain Authority, SEMrush Authority Score) and a vendor-supplied spam/toxicity score (Moz Spam Score, Ahrefs DR drop signal, SEMrush Toxicity Score). The orchestration layer computes a cross-vendor consensus per link with operator-counsel-and-SEO-team-set weighting per vendor (typically Ahrefs and Majestic weighted higher for backlink toxicity assessment; Moz weighted for spam score). Per-link relevance scoring runs against the operator vertical taxonomy and per-link anchor-text alignment — a low-relevance link is not necessarily toxic, but is treated as low-value. Per-link disavow recommendation applies the operator-counsel-and-SEO-team-set rule (typically: cross-vendor consensus toxicity above the disavow floor AND no remediation pathway to the referring domain AND no historical organic-traffic contribution from the referring domain) and surfaces the link for review before it enters the disavow file. Disavow files go into Google Search Console disavow tool + Bing Webmaster Tools disavow + are versioned in operator code repo with attestor + timestamp + cross-vendor evidence pointer. Per-location link-velocity tracking flags abnormal velocity (sudden inbound-link spike that could indicate a negative-SEO attack or a viral organic event); the cross-stream correlation sibling skill on the anomaly-detection agent ingests link-velocity anomalies into the broader anomaly-correlation surface. Anchor-text diversity tracking prevents over-optimization patterns. Referring-domain diversity tracking prevents over-reliance on a single referring domain. Operator counsel + SEO-team review the disavow file before submission to prevent over-disavowing (which can suppress legitimate links + drop rankings).

Question 5

What compliance does the per-event gate enforce, and how does it map to FTC Section 5 + Lanham + Made-in-USA, state licensing-board + per-state UDAP, FTC Fake Review Rule + Endorsement Guides, per-vertical claims allowlist, and per-platform editorial policy?

Accepted Answer

Five anchors. Anchor 1: FTC Section 5 (15 USC 45) + Lanham Act false advertising (15 USC 1125) + FTC Made-in-USA Labeling Rule (16 CFR Part 323) + per-state UDAP cross-directory consistency. Listing-profile claims that appear across 200+ directories are claims; FTC substantiation applies. Comparative claims about competitor brands ("best dentist in Denver", "highest-rated dental office in the metro") are Lanham-exposed without substantiation. Made-in-USA claims in listing-profile categories or descriptions trigger the 2024 Made-in-USA Labeling Rule. Cross-directory consistency matters: a per-location profile that says "best in class" on Yelp but not on Google Business Profile creates inconsistent-claim exposure that state-AG UDAP enforcement can act on. The gate refuses to commit a comparative or superlative claim without operator-counsel-approved substantiation pointer attached. Anchor 2: State medical/dental/optometry/pharmacy/PT licensing-board advertising rules + per-state bar advertising for legal services + FINRA Rule 2210 + FDA OPDP for prescription + per--regulator + DISCUS Code of Responsible Practices + state liquor-board + FDA CTP per-vertical listing claims. For healthcare-vertical operators (dental, medical, optometry, pharmacy, physical therapy), state licensing-board rules govern claims language in directory profiles — most state boards prohibit superlative claims like "best dentist" without board-recognized specialty designation, and several state boards prohibit testimonial-style claims entirely. For legal-services operators, state bar advertising rules apply (each state bar has its own; some require pre-approval of directory listings). For financial-services operators, FINRA Rule 2210 requires principal approval of any communication that includes performance data or recommendations. For prescription-related operators, FDA OPDP rules govern claims. For  operators, per--regulator advertising rules apply — many states restrict directory listings entirely (only state-licensed-and-regulated directories permitted) or restrict the content of directory descriptions. For alcohol operators, DISCUS Code of Responsible Practices + state liquor-board rules apply. For tobacco operators, FDA CTP rules apply. The gate composes with the per-vertical compliance overlay sibling skill on the compliance-overlay-manager agent and refuses to commit a directory propagation whose content fails the per-vertical claims-allowlist check. Anchor 3: FTC Fake Review Rule (16 CFR Part 465 effective October 2024) + FTC Endorsement Guides (16 CFR Part 255 with 2024 AI-disclosure amendments). The Fake Review Rule prohibits buying fake reviews, soliciting incentivized reviews without disclosure, suppressing negative reviews, AI-generated reviews without disclosure, and review-response manipulation. For multi-location operators with thousands of directory profiles each accepting reviews, the operator is responsible for not engaging in any of these prohibited practices across every directory. The gate runs every review-response submission (when Stage 4 link-building or Stage 3 maintenance surfaces a review-response need) through a fake-review + endorsement-disclosure pre-check, and runs every AI-generated review response through the 2024 Endorsement Guides AI-disclosure check. Anchor 4: Per-vertical claims allowlist + ADA Title III (Robles v Dominos 9th Cir 2019) + WCAG 2.2 AA. The per-vertical claims allowlist composes with the per-vertical compliance overlay sibling skill (covered in Anchor 2 detail above). ADA Title III + WCAG 2.2 AA apply to operator-controlled listing-profile content (alt-text on profile photos, color-contrast for visual elements, reading-level for plain-language verticals, captions for video uploaded to listing profiles). The gate refuses to commit a propagation whose content fails the accessibility pre-check. Anchor 5: Per-platform editorial policy. Google Business Profile policy (the operator GBP guidelines + the Google Map Maker policies + the per-attribute community guidelines) governs what can and cannot appear in a GBP profile (no URLs in business names, no promotional content in names, no off-topic categories, no fake addresses, no virtual office addresses misrepresenting as physical locations). Yelp community guidelines + Apple Maps Connect content policy + Bing Places guidelines + Facebook Local + TripAdvisor + Foursquare community standards each layer additional restrictions. Per-platform fake-review prohibition (in addition to FTC Fake Review Rule) is enforced by each platform with profile-suspension consequences. Per-platform NAP canonicalization requirements (each platform has its own canonicalization rules — USPS-validated address only, E.164 phone only, etc) determine the form Stage 2 propagation must use per directory. Per-platform service-area policy (Google Map Maker service-area rules in particular) governs which locations can have what service-area definitions. The gate refuses to commit a propagation whose content fails the per-platform editorial policy pre-check. Broader gate also enforced: HIPAA when healthcare NAP touches PHI + NIST AI RMF + ISO 42001 + ISO 27001 + SOC 2 Type II via policy-as-code (OPA Rego + AWS Cedar + Casbin + Cerbos + Oso). WORM audit trail (AWS S3 Object Lock + GCS retention + Azure Blob immutable + Snowflake Time Travel) with per-statute retention (FTC 7yr + state-AG variable + per-platform retention variable + IRS 7yr + state variable) per operator counsel policy.

Question 6

What does the engagement look like across Tier 1 → Tier 2 → Tier 3, and what does the Tier 3 reporting cycle commit to?

Accepted Answer

Tier 1 AI Readiness Assessment (2-3 weeks, diagnostic): audits the operator current citation pipeline posture against the 4-stage architecture + 5-anchor compliance gate; deliverable is a gap-pack report identifying which of the 200+ directories are unmaintained, which directory-pairs have NAP drift, which per-vertical claims-allowlist gaps surface in the long-tail directories, which Fake Review Rule exposures exist across review-accepting directories, which per-platform editorial-policy violations need cleanup, and a recommended remediation sequence for Tier 2. Tier 2 AI Swarm Setup Sprint (4-8 weeks): builds the 4-stage pipeline on the citation-link-build agent, wires listing aggregator (operator-chosen Yext, Uberall, Synup, Birdeye, Reputation.com, Vendasta, Moz Local, BrightLocal, Whitespark), wires direct per-directory integrations for the long-tail vertical directories, wires link-analysis (operator-chosen Ahrefs, Majestic, SEMrush, Moz, Cognitive SEO, Searchmetrics), wires webmaster tools (Google Search Console, Bing Webmaster Tools, Yandex Webmaster), wires per-vertical compliance overlay composition, wires per-platform editorial policy pre-checks, configures policy-as-code + WORM-storage, runs 30-day shadow + canary period before flipping to enforce-mode. Tier 3 Fractional CMO with AI Swarm (6-month minimum, 1-2 days/wk embedded): continues operating with weekly Stage 1 governance review, monthly Stage 2 propagation refresh, quarterly Stage 3 maintenance audit, monthly Stage 4 link-building review with operator-counsel + SEO-team disavow approval, quarterly per-vertical claims-allowlist library refresh, quarterly per-platform editorial policy update sync, quarterly compliance evidence packages. Tier 3 reporting is a 6-workstream pre-engagement-baseline reporting cycle (per-directory coverage trend + per-location NAP-consistency trend + per-directory drift detection cadence + per-link toxicity trend + per-platform editorial-policy compliance + WORM audit-trail completeness) measured against the operator’s pre-engagement baseline. Each workstream surfaces trend direction and the gap to operator-defined targets. Reporting carries explicit caveats: listing aggregator SLA + per-directory API availability + per-platform policy updates (Google Business Profile + Yelp + Apple Maps + Bing Places + Facebook + TripAdvisor + Foursquare each update policies on their own cadence) + FTC Fake Review Rule implementing guidance updates + FTC Endorsement Guides updates + per-state licensing-board rule changes + per--regulator updates + DISCUS Code amendments + state-AG rulemaking sit outside Completions control. Attorney-client privilege preservation across per-vertical claims-allowlist library + per-platform editorial policy library + per-state licensing-board policy library + disavow-file decision records is maintained per operator counsel policy.

Question 7

Who owns the master-NAP record, the directory credentials, the disavow file, and the audit trail?

Accepted Answer

Operator owns every artifact. The per-location master-NAP record lives in operator data infrastructure (Snowflake, Databricks, BigQuery, Redshift, Postgres — operator chooses). The listing-aggregator subscription (Yext, Uberall, Synup, Birdeye, Reputation.com, Vendasta, Moz Local, BrightLocal, Whitespark — operator chooses) runs under operator billing. The per-directory credentials for direct integrations (Google Business Profile API + Yelp Fusion + Apple Maps Connect + Bing Places + Facebook Pages + TripAdvisor + Foursquare + 200+ directory accounts) all run under operator-controlled accounts. The link-analysis subscriptions (Ahrefs, Majestic, SEMrush, Moz, Cognitive SEO, Searchmetrics — operator chooses) run under operator billing. The webmaster-tools accounts (Google Search Console, Bing Webmaster Tools, Yandex Webmaster) run under operator authentication. The per-link disavow file lives in operator Google Search Console + Bing Webmaster Tools + a versioned operator code repo with attestor + timestamp. The citation pipeline code, per-directory connector code, per-link toxicity-scoring model code, and policy-as-code policies (OPA Rego, AWS Cedar, Casbin, Cerbos, Oso) all live in operator code repo. The per-vertical claims-allowlist library, per-platform editorial policy library, per-state licensing-board policy library, FTC Fake Review Rule compliance evidence, and FTC Endorsement Guides 2024 AI-disclosure compliance records are operator-counsel-maintained. The WORM audit trail lives on operator-controlled cloud storage (AWS S3 Object Lock, GCS retention, Azure Blob immutable, Snowflake Time Travel). Completions owns the orchestration knowledge — how to design the 4-stage pipeline for the operator’s actual directory mix, how to coordinate Stage 1 governance with the master-record-canonicalization sibling, how to tune Stage 2 per-directory propagation across listing-aggregator + direct integrations, how to design Stage 3 drift detection thresholds that survive per-directory canonicalization variance, how to tune Stage 4 per-link toxicity scoring against operator-counsel-and-SEO-team disavow tolerance, how to compose per-vertical claims-allowlist + FTC Fake Review Rule + per-platform editorial policy enforcement — and that knowledge transfers under the Tier 3 transition path (30-60 days at engagement end with full hand-off of the pipeline code, the per-directory connectors, the per-link toxicity model, the disavow methodology, and the compliance evidence-package generation playbook). Completions credentials revoke on engagement-end.

4-stage multi-location citation pipeline for multi-location retail and multi-unit franchise operators — Governance + Propagation + Maintenance + Link-Building across 200+ directories, under a 5-anchor compliance gate

The real ecosystem this sits above

Listing aggregators

Per-directory APIs

Master record + change-event emission

Link analysis + webmaster tools

Schema + structured data

Policy-as-code, WORM storage, compliance tooling

Frequently asked