NAP still matters when the answer is generated

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 products need to identify the business being discussed. Depending on the product, signals may include the website, Google Business Profile, search indexes, maps data, and third-party listings. When those sources disagree, possible outcomes include:

• The answer hedges or 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. Conflicting or stale records are enough to create ambiguity, although they are not the only possible cause.

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 search can place a bad listing far below the visible results. A generated answer may instead summarize only a small set of sources or businesses. If a retrieved source still has the old town name, that error can surface directly in the response.

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. Start with the high-value sources customers and major search products use:

1. The website footer, contact page, and schema.
2. Google Business Profile — categories, hours, service area, and the address as Google stores it.
3. Apple, Bing, and the major directories you actually control.
4. 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 basic identity data. Google says complete and detailed Business Profile information helps it understand relevance, while local results are mainly based on relevance, distance, and prominence. Consistency does not guarantee a ranking or citation, but generated answers did not make accurate business records optional. (Google Business Profile guidance)