How Routinely Should the Data Be Checked?
| Field | What to check |
|---|---|
| One rule | Prefer removing a wrong listing to leaving it half-corrected, which is why it keeps being rediscovered. |
| After you refresh | More usefully, correct the list of services before touching anything decorative. |
| Reading company profiles | Keep the description factual; the categories carry the relevance work. |
| Common traps | Do not submit to a new directory until the existing ones agree. |
Keeping the Record Straight
Still open
Anything unverifiable should be removed rather than corrected.
The website field
Record the canonical version of the primary category somewhere the agency of record can find it.
The location pages confirm
What follows from this is that confirm by phone or postcode lookup, not by memory.
Worth checking
Put plainly, set aside time to rebuild each quarter rather than treating it as a one-off project.
Worth checking
The practical upshot is that keep a change log; six months on, no one remembers which field was edited or why.
Measuring What Changed
| Field | What to check |
|---|---|
| Common traps | Confirm what a competitor in a competitive suburb has claimed before deciding where to submit. |
| Before you prune | If a listing cannot be claimed, document it and move on rather than duplicating it. |
| Review profiles for trade contractors | Photograph or screenshot each profile before editing -- reversions do happen, and the same holds at scale. |
| Fixing a broken website field | In practice, treat the name, address and phone number as a single source of truth, not as a field to be improvised per site. |
Outbound notes
A Closer Look at Local Citations
51% Rebuilding without drift 57% Rebuilding review profiles 51% Out of date 31% The accurate record 37% Notes on online mentions
More usefully, this is maintenance work, and maintenance work only fails when it stops. The pattern repeats: the businesses that audit at least annually are the ones that stop worrying about it.
Four Habits That Keep a Profile Clean
- Ongoing Claim what exists before creating anything new -- duplicates are harder to remove than to avoid.
- Week 2 Handle the high-authority sources by hand and batch the long tail afterwards.
- Quarter 1 Give one person the logins and one document the truth; ambiguity is what causes drift.
- Month 2 The order matters: update first, then reconcile, and only then submit anywhere new.
Audit At Least Annually, Not Once
None of this replaces a decent website; it makes the one you have easier to find. By contrast, get the facts to agree, and map providers will do the rest without being asked.
Work from the aggregators outward, because fixing a source fixes everything downstream. Keep the record unambiguous, revisit it on a fixed schedule, and most local problems solve themselves. More usefully, across a large sufficient sample, the correlation between canonical data and direction requests is hard to dismiss. The landscape shifts, but the underlying requirement -- checkable, accurate data -- has not. The finish line is not perfection; it is a profile that no one has to argue with.