An address does not die when the lease ends. It lives on in old pages, cached listings and guide mentions, and an answer engine will keep sending people to a locked door long after the keys have changed hands.
A composite bistro left a small room in the 5e and reopened, larger, in the 11e. The move was a good one. The problem arrived three months later, when guests kept turning up at the old door on rue Mouffetard, phones in hand, having asked an answer engine where the restaurant was. The machine was confident and wrong. It had read the old address in a dozen places that still said the bistro lived there, and it had no reason — no clear, recent, owned signal — to believe otherwise.
This is the address echo, and it is one of the most stubborn failures I audit, because it is not caused by anything the business is doing now. It is caused by the past being louder than the present. The new address exists; the old address simply has more mentions, more age, more inbound links, and no one ever told the machine the old one is dead. Confidence, to an answer engine, is a function of corroboration, and the dead address is still better corroborated than the live one.
Silence lets the old address win
The instinct after a move is to update the homepage and consider it done. But the homepage is one source among many, and it is competing against years of accumulated mentions of the old location: the old listing, old reviews that name the street, a guide write-up from two years ago, a delivery profile no one closed. If the only new signal is a quietly changed contact line, the machine weighs a single fresh fact against a mountain of stale ones and keeps the old answer.
The correction is to make the change explicit and findable, not silent. A relocation announcement should exist as a real, crawlable page — not a banner that vanishes, not a social post that scrolls away — stating plainly: “We have moved. As of [month], [name] is now at [new address] in the 11e. We are no longer at our former address on rue Mouffetard.” That last sentence is the one that matters most, because it does the thing no amount of updating the new address can do: it tells the machine the old address is no longer the answer.
Canonical address lines and a dead-address page
Two moves do most of the work. The first is a single canonical address line, written identically everywhere the business controls — homepage, contact page, footer, booking note, structured data, map listing. When the owned sources all say one address in one form, they outweigh the scattered old mentions far more effectively than a single updated line ever could. Inconsistency is what lets the old address survive; consistency is what buries it.
The second is keeping a page at, or pointing from, the old context that explicitly retires the dead address. If the old site or an old URL still resolves, it should not quietly redirect and say nothing — it should state the move in words a crawler reads, then point to the new home. For a closure rather than a move, the same applies in reverse: a plain “this location is permanently closed” sentence, stated rather than implied by silence, stops the machine from assuming the place is merely between updates. An empty, un-updated old page is read as a still-open business. A page that says “closed” or “moved” is read correctly.
You cannot edit the guides, but you can outweigh them
The hardest mentions are the ones you do not own: a guide article, a roundup, a directory that still lists the rue Mouffetard address. You cannot rewrite them, and chasing each one is rarely worth the time. What you can do is two things. Update the listings you can claim — the map profile above all, because its address field and “permanently closed at this location” status feed answer engines directly and carry real weight. And make the owned, canonical signal so consistent and so recent that the machine prefers it to the older fragments.
Where a specific old guide mention is doing real damage and you have a relationship with the publisher, a short note asking for a correction is worth one polite attempt. But the durable fix is not erasing the past. It is making the present unambiguous and well-corroborated enough that the answer engine stops treating the dead address as the safe bet. The old door will keep its ghost for a while. The job is to make sure the live door is the louder, clearer, more consistent fact — so the next person asking is sent to the room that is actually open.
The Paris Trace
On rue Mouffetard, a moved bistro keeps drawing guests to a locked door not because the new address is wrong, but because the old one is still better corroborated and never declared dead. The trace to leave is a crawlable relocation page, one canonical address line repeated identically across every owned surface, and an updated map status. The exact wording move: state “we are no longer at our former address on rue Mouffetard” alongside the new one. So the answer engine remembers the room that is open, not the room that closed.