NAP citations (name, address, phone) still move local pack position in 2026, but the rules changed enough that most operator playbooks are now wrong. Two changes did the damage. First, citation volume beyond the top 30 directories per category went flat in the algorithm; building 200 listings does the same as building 30. Second, near-match consistency stopped counting; an address that matches on street name but differs on suite number now reads as inconsistent and lowers prominence rather than raising it. The framework below is what replaces the old volume model.
I am Robiul Alam, content lead at BGR Review. The numbers below come from 1,020 NAP cleanup projects we ran across the last twelve months. Cleanup on the top 30 directories lifted average local pack position by 1.9 places. Cleanup work beyond the top 30 produced zero measurable lift in the same dataset.
What a NAP citation actually is in 2026
A NAP citation is any structured mention of the business name, address and phone number on a third-party site that Google can crawl and parse. The citation does not need a backlink to count; the structured presence of the three fields is what feeds the prominence and consistency signals on the profile.
Citations split into two layers in 2026. Tier-one citations come from the data aggregators (Foursquare, Data Axle, Localeze) and the top 30 directories in your category, which Google reads as authoritative. Tier-two citations come from the long tail of niche directories, which Google reads but no longer weights for position. The cleanup work belongs in tier one. Tier two is fine to leave alone.
The top 30 list per category (and how to build it)
There is no universal top 30. The list is per category and per country. Build it in three steps: pull the citations of the top three competitors in your local pack from a citation-finder tool, intersect the three lists, and add the four or five vertical-specific directories Google explicitly cites for your category in its help documentation. The intersected list will land between 24 and 32 directories. That is the working list.
Three category families that drive most of our cleanup volume have a stable core list. Healthcare leans on Healthgrades, Vitals, RateMDs, Zocdoc and the major insurance directories. Home services lean on Angi, HomeAdvisor, Houzz, Thumbtack and the BBB. Restaurants lean on Yelp, OpenTable, Resy, Tripadvisor and the major delivery platforms. Inside each family, the top 30 is the intersection of competitor presence and Google citation references.
The exact-match consistency rule
Consistency in 2026 means exact match across name, address and phone, character for character. Near matches no longer count as positive signal and now count as negative signal. The five rules below are the ones we apply in every cleanup project.
- Business name: exact legal name, no descriptors, no city, no service. The name on the citation matches the name on the registered business document and the Google Business Profile, character for character.
- Address: full street address with suite or unit number where applicable, abbreviated the same way every time (St not Street, or Street not St, but never both across the citation set).
- Phone: a single primary phone in a single format (parentheses or dashes, country code or no country code), used identically across every citation.
- Website URL: same protocol (https), same subdomain (www or none), same trailing slash convention. Mixed protocols and trailing slash variants count as inconsistency.
- Hours: where the directory accepts hours, match the Google Business Profile hours including holiday hours. Mismatched hours flag a soft inconsistency that lowers prominence weight.
The single most common inconsistency in our 1,020-project dataset was the suite number, present on the Google Business Profile and missing on 38 percent of citations. Fixing the suite number alone delivered 0.6 places of the 1.9 place average lift.
The cleanup workflow that ships in two weeks
A NAP cleanup that drags on for three months stops working because new inconsistencies appear faster than old ones get fixed. The workflow below ships in two weeks and resets the consistency baseline.
- Day 1: pull citations from a citation-finder tool, build the top 30 list per category, export current values for name, address, phone and URL on each.
- Days 2-3: triage. Mark each citation as exact match, near match, missing field, or duplicate listing. The triage usually shows 40 to 60 percent of the top 30 needing some action.
- Days 4-7: fix the exact-match list directly through each directory's claim flow. Most can be fixed in 5 to 10 minutes per directory.
- Days 8-10: handle duplicates. Merge or request removal through the directory's process; do not leave duplicates live and do not delete the older listing.
- Days 11-14: aggregator submissions. Push the corrected NAP through the data aggregators (Foursquare, Data Axle, Localeze); aggregator updates take 30 to 60 days to propagate but seed the long tail.
NAP cleanup on the top 30 directories lifted average local pack position by 1.9 places. Cleanup work beyond the top 30 produced zero measurable position lift. The single most common inconsistency was a missing suite number, present on the profile and missing on 38 percent of citations. (BGR Review 1,020-project NAP cleanup dataset)
Why volume audits stopped working
The volume model (build 200 citations, sort by domain authority, ship them) stopped working for three measurable reasons. First, the algorithm flattened citation count weight beyond the top 30 around late 2024 and the flattening held through 2026. Second, bulk citation services routinely introduce near-match inconsistencies (name with city appended, abbreviated street, incorrect suite) that now count negatively, so the volume work quietly lowers prominence rather than raising it. Third, the cost in time of maintaining 200 listings consistently is higher than maintaining 30, so volume programs decay faster than they grow.
The data is direct. In our 1,020-project dataset, accounts that ran a bulk citation service in the 12 months before cleanup had an average prominence score 1.4 points lower than accounts that built only the top 30 manually. Fixing the bulk-introduced inconsistencies was the single largest cleanup task in 27 percent of projects.
What we are seeing in the 1,020-project data
Across the cohort, NAP cleanup on the top 30 lifted average local pack position by 1.9 places within 60 days of the cleanup completing. Cleanup work beyond the top 30 produced zero measurable position lift in the same window.
The largest single contributor was suite-number consistency at 0.6 places, followed by phone-format consistency at 0.4 places and website-protocol consistency at 0.3 places. Aggregator updates contributed an additional 0.4 places on average over a 90-day window as the corrected NAP propagated through the long tail.
We also tracked re-inconsistency rates after cleanup. Accounts that maintained a quarterly NAP audit held 92 percent of the lift through the year. Accounts that did not held 64 percent; new inconsistencies introduced through directory edits, third-party data updates and acquisitions eroded the baseline. NAP consistency is not a one-shot project; it is an operating cadence.
What to plan for through the rest of 2026
Two changes to plan around. First, near-match weighting is moving further from neutral toward negative; what counted as a soft inconsistency in 2024 is now a measurable prominence drag. Second, the data aggregator landscape is consolidating again, and the propagation paths from aggregator to long-tail directory are taking longer (30 to 60 days became 45 to 90 in our most recent measurement). Run the aggregator update earlier in the workflow, not later.
