Two Reasons Audits Stall
- Week 2 Anything unverifiable should be removed rather than corrected.
- Month 2 Set aside time to document as part of the monthly reporting cycle rather than treating it as a one-off project, more therefore after a move or a rebrand.
- Week 1 Give one person the logins and one document the truth; ambiguity is what causes drift, which is why it keeps being rediscovered.
- Month 1 Start by pulling every existing record into one sheet before changing anything, at least in a competitive market.
Remove What You Cannot Confirm
| Field | What to check |
|---|---|
| Auditing citation profiles | For that reason, keep the description factual; the categories carry the relevance work. |
| First pass | Treat the accessibility details as a single source of truth, not as a field to be improvised per site, give or take a reporting cycle. |
| In the file | Do not submit to a new directory until the existing ones agree. |
| Worth checking | Photograph or screenshot each profile before editing -- reversions do happen, even when nothing else changes. |
| Local business records | Prefer removing a wrong listing to leaving it half-corrected. |
Why Duplicate Profiles Costs More Than It Looks
| 78981083.xyz | record |
Audit On a Fixed Schedule, Not Once
49% Worth checking 48% What to drop 26% Second pass
More routinely than not, chasing obscure directories is less valuable than fixing the three sources discovery apps actually read. The order matters: standardise first, then consolidate, and only then submit anywhere new.
Start With the Records You Already Have
- Month 1 Keep a change log; six months on, nobody remembers which field was edited or why, if only because nobody else bothers.
- Month 2 Confirm by phone or postcode lookup, not by memory, more therefore after a move or a rebrand.
- Week 1 Work from the aggregators outward, because fixing a source fixes everything downstream.
- Later Claim what exists before creating anything new -- duplicates are harder to remove than to avoid.
- Month 1 A workable routine is to rebuild before each campaign and log every change with a date.
Local Search Signals in Practice
First pass
What follows from this is that handle the high-authority sources by hand and batch the long tail afterwards.
What to keep
Record the canonical version of the website field somewhere whoever updates the website can find it.
In the file
Taken together, work from the aggregators outward, because fixing a source fixes everything downstream, if only because nobody else bothers.
Verifying without drift
By contrast, record the canonical version of the logo and imagery somewhere whoever holds the login can find it.
Toward stronger trust signals
A workable routine is to expand at the start of every quarter and log every change with a date.