The Ember Repository

Local Citations: Field Notes

In the file · What discovery apps read · The local business records confirm

Comparison sites rarely announce a penalty here -- they simply rank a less certain record lower.

Keeping the Record Straight

FieldWhat to checkFrequency
Still openBroadly, fix the payment methods before touching anything decorative.after any move or rebrand
Second passIf a listing cannot be claimed, document it and move on rather than duplicating it.before each campaign
More direction requestsPrefer removing a wrong listing to leaving it half-corrected.at least annually

Understanding Local Search Signals

  1. Ground rules. Record the canonical version of the service area somewhere the owner can find it.
  2. Avoiding conflicting category choices. The order matters: audit first, then consolidate, and only then submit anywhere new, and the same holds at scale.
  3. Before you expand. Set aside time to cross-confirm as part of the monthly reporting cycle rather than treating it as a one-off project.
  4. The canonical record. For the most part, claim what exists before creating anything new -- duplicates are harder to remove than to avoid, more therefore after a move or a rebrand.

Related references


Why Consistency Beats Volume

FieldWhat to check
How discovery apps decideBroadly, confirm what a competitor in a tightly defined neighbourhood has claimed before deciding where to submit.
Local citationsResist the urge to vary the business name for keywords; consistency beats cleverness here, particularly for a newer business.
Aggregator feeds for law firmsTreat the primary category as a single source of truth, not as a field to be improvised per site.
In the fileKeep the description factual; the categories carry the relevance work.