BlogIndustry
NAP still matters when the answer is generated
Name, address, and phone consistency did not become obsolete when answers moved into chat. Models and maps still assemble an entity from messy listings.
Local SEO people have been arguing about NAP — name, address, phone — since before “AI visibility” was a slide title. The argument is usually that directories are dying, so matching suite numbers across the web is busywork.
Then a generated answer picks the old DBA, a truncated street line, and a phone that now belongs to a fax. The shopper calls the wrong number. That is still a NAP problem.
Models do not magically know the canonical record
Answer engines and map packs both need an entity. They build it from the website, Google Business Profile, and whatever other listings they can retrieve. If those sources disagree, you get one of three outcomes:
- The model hedges and names nobody useful.
- It names you with the wrong address or a closed location.
- It names the previous owner, a similarly spelled competitor, or a directory stub.
None of those require a conspiracy. They require two listings that do not match.
The boring mismatches still dominate:
- Name — legal name vs. the name on the door vs. “Smith Law, LLC” vs. “Smith Law Group”
- Address — “Ste 12” vs. “Suite 12” is usually fine; dropping the suite, the city, or using a PO box against a storefront is not
- Phone — tracking numbers that never made it onto GBP, old area codes, or a number that 301s to a national call center
Yelp and other directories often shorten the street line. That is not automatically a crisis. A leftover identity after a rebrand is.
Generated answers amplify the listing you did not clean up
Classic pack ranking could bury a bad citation below the fold. A chat answer has no fold. It will pick a single story. If the most confident source still has the old town name, that is the story.
This is why “we posted more Google reviews” does not fix a mention that uses last year’s address. Reviews do not reconcile NAP. Consistency does.
A practical pass, not a 400-citation spreadsheet
You do not need to hunt every aggregator. You need the sources a model or a map is likely to trust:
- The website footer, contact page, and schema.
- Google Business Profile — categories, hours, service area, and the address as Google stores it.
- Apple, Bing, and the major directories you actually control.
- One leftover: old domain, Facebook page, or Yelp listing under the previous name.
Fix the canonical record first (the name you want used everywhere), then make the site and GBP match it, then chase the stragglers that still rank for the brand query.
If you run an audit that flags mismatches, read the mismatch. “Shortened street line” is not the same finding as “different city.” Brief the second one first.
NAP is not a vibe and it is not nostalgia. It is the entity graph, written in the least glamorous format on the web. Generated answers did not replace it. They quote it.