Ecommerce SEO
A store with physical locations runs two search businesses at once: the ecommerce catalogue competing nationally per this silo's playbook, and each shopfront competing in its neighbourhood's map pack for "near me" demand — plus the connective tissue between them (local inventory visibility, click-and-collect intent) that pure-play stores and pure-local businesses each get to ignore. Here's the hybrid architecture.
The local layer, store edition
Each location runs the full local stack: its own Business Profile (correct categories per what that shop actually sells, photos of the actual shop, hours honest, per the checklist), the review engine firing per location (in-store prompts — receipt QR codes, staff asks — plus the post-purchase flows, with reviews accruing to the right location's profile), NAP consistency per location, and the community link portfolio where each shop actually lives. The web-side anchor: one location page per shop — real content (that location's services, team, parking, local brands stocked), LocalBusiness markup with geo, embedded map, and the profile linking to it (not the homepage) — the honest version, distinct from the doorway-page mad-libs the case study warned about.
The connective tissue (where hybrids win or leak)
- Local inventory visibility: Google's local-inventory feeds (via Merchant Center, the feed discipline's local extension) surface "in stock near you" in Shopping and Maps — the highest-intent retail query family there is, served by data plumbing most multi-location retailers never connect.
- Click-and-collect as a landing experience: pickup availability on product pages, location-aware messaging — the conversion layer for the searcher who wants it today.
- The catalogue ↔ location page routing: location pages link their departments' categories; category pages surface "available at [locations]" — internal routing stitching the two businesses so equity and shoppers both flow across.
- Attribution honesty: local search drives in-store revenue analytics can't see — profile insights (calls, directions) and pickup orders are the proxies; report them per the chain or the local layer gets defunded for the crime of being unmeasurable.
Scaling across many locations
The multi-location disciplines: location data managed centrally (a listings platform earns its keep at this scale, per the tooling guide), location pages templated-but-individuated (the template carries structure; each page carries genuinely local content — the data-density rule applied to shops), review velocity monitored per location (laggard shops are operational findings, not SEO ones), and grid tracking per market for the pack-dependent categories. Franchise wrinkle: corporate-vs-franchisee profile ownership settled contractually before it becomes a support ticket — the commonest multi-location governance failure.
Frequently asked questions
Should location pages target "[category] in [city]" queries?
Where the shop genuinely serves that demand, yes — the location page (or a location-category hybrid for big shops) is the honest landing for it, competing in localized organic alongside the pack. The line remains inventory-and-presence truth: pages for what you actually sell where you actually are, per the doorway distinction.
Do the shops' local signals help the national catalogue rank?
Indirectly and genuinely: the brand-signal layer (branded searches, reviews, local press) accrues to the domain, and community links are real links. The two businesses share one authority pool — which is the argument for running them on one domain, per the structure rules, not a locations microsite.
We're one shop with a big online catalogue. Priorities?
The local stack is hours-per-month for the revenue share your neighbourhood provides (run it, per the single-location minimum), while the catalogue's national programme carries the growth ambitions — the standard split. Both engines run on the same fuels this silo keeps naming: pages built right, content that earns, and authority accumulating (our fuel depot).