Multi-Location Citation Cleanup: A Case Study

A regional service business with four locations came to us with a familiar problem: strong reviews and steady word-of-mouth referrals, but inconsistent visibility in local map pack results some locations ranking well, others barely appearing at all. The root cause wasn\'t content or reviews. It was scattered, inconsistent NAP data across more than 40 directories.Client SnapshotBusiness TypeRegional multi-location service businessLocations4 branches across neighboring citiesStarting ProblemDuplicate listings, outdated addresses, inconsistent phone formatting across directoriesDirectories Affected40+, including 2 major data aggregatorsEngagement Length6 weeks initial cleanup, ongoing monitoring afterThe Diagnostic PhaseThe engagement began with a full citation audit across all four locations, mapping every existing listing against the business\'s correct NAP data. The audit surfaced a pattern common to businesses that have moved offices, changed phone providers, or grown organically without a standardized listings process:Two branches had duplicate Google Business Profile listings one live, one abandoned from a previous addressA major data aggregator was still distributing an outdated suite number for the two-year-old head office locationPhone number formatting was inconsistent across roughly a third of all listings (mixing local format with full country code format)One branch had never been submitted to Bing Places or Apple Maps at allKey finding: The two duplicate listings were the single biggest issue duplicate profiles split review counts and ranking signals between two versions of the same branch, weakening both instead of strengthening either.Cleanup ExecutionWith the audit complete, cleanup followed the standard sequence: aggregators first, then major directories, then niche and local listings.Duplicate suppression: Formal merge/removal requests were filed for both duplicate Google Business Profile listings, consolidating reviews and ranking signals into a single verified profile per branch.Aggregator correction: Updated NAP data was pushed to the two major aggregators feeding the outdated suite number, correcting the source before it could keep re-propagating downstream.Standardization rollout: All 40+ listings were brought in line with a single NAP style sheet consistent phone formatting, consistent address structure, consistent business name across every directory.Gap-filling: The branch missing from Bing Places and Apple Maps was submitted and verified.Automation Layer: Preventing Drift After CleanupA one-time cleanup solves the immediate problem, but aggregators periodically re-pull data from stale sources  meaning uncorrected drift can silently creep back in within months. To prevent this, the business moved to a synced listings management platform after the initial cleanup, so future changes (a fifth location added six months later) propagated automatically instead of requiring a repeat manual audit.Results40+ Directories standardized to a single NAP sourceDuplicate listings merged and consolidatedBranches showing improved map pack appearance within 8 weeks100% Locations verified live on all Tier 1 & 2 directoriesTimeline BreakdownWeeks 1–2Audit: Full citation mapping across all four locations and 40+ directories; duplicate and inconsistency flagging.Weeks 3–4Cleanup: Aggregator corrections, duplicate suppression requests filed, standardization rollout across major and niche directories.Weeks 5–6Verification: Confirming listings live and matching the NAP style sheet; resolving any directory rejections.OngoingMonitoring: Monthly spot-checks on Tier 1/2 listings, quarterly full re-audit, automated sync for any future business changes.Client TakeawayThe biggest surprise wasn\'t how many directories had wrong information it was realizing two of our own branches had been quietly competing against each other in search results because of a duplicate listing nobody had noticed.Client feedback, For SEO consultants and marketing managers evaluating how to handle citation cleanup at scale, this engagement reflects a common pattern: the technical fix (standardizing NAP, suppressing duplicates) is usually less than half the work. The other half is building a monitoring system that keeps the fix from quietly unraveling months later.