Schema Wire
Schema Wire
@SchemaWire

The multi-location LocalBusiness setup that doesn't cannibalize itself

Chains keep copy-pasting one LocalBusiness block across every branch page, and Google can't tell the locations apart. The fix is per-location identity, done deliberately. Build it like this:

— Give each location page its OWN LocalBusiness node with a unique @id per URL
— Use the precise address and geo coordinates per branch — never the HQ for all
— Match name, address, and phone to the matching Google Business Profile exactly (NAP consistency)
— Add openingHoursSpecification per location, not a shared block
— Cross-link branches with a parent Organization via parentOrganization/department

What it means for you: identical markup across locations reads as one entity in many places, diluting all of them. Watch this — NAP mismatch between markup and Business Profile is a top local-pack suppressor, and AI map answers inherit the same data.
This post was published in the Telegram channel Schema Wire. Subscribe here: @SchemaWire.
tech

Latest posts in “Tools and infrastructure”

All channels in this category →

start

Готовы запустить рекламу через сеть public.tg?

Новый оффер, продукт, GEO, кейс, событие или партнёрский запуск — соберём маршрут под задачу и отдадим медиаплан.

Telegram для медиаплана: @AFFtop_connect. Быстрый тест: $20 за канал, $1000 за пакет по сети.