For multi-location SEO + marketing leadership running a replatform

Your 200-store site is on its third replatform. Three agencies left three URL patterns. 40-80 collisions are about to surface as 404s. Author the taxonomy.

Per-location URL template library + per-vertical pattern catalog + pre-migration collision check + link-equity preservation playbook + per-location canary rollout. The authoring side underneath Screaming Frog, Sitebulb, OnCrawl, DeepCrawl, Lumar, Botify, ContentKing, JetOctopus, Audisto.

By Jay ChristopherMay 30, 20269 min read

Friday-night cutover. Monday Search Console floods with 404s on URLs the legacy patterns held.

The multi-location SEO lead inherits an agency-soup URL set on day one. Three previous agencies left three patterns: /locations/city/service, /city-service, /service-in-city. The first replatform tried to consolidate but only got 60% of the way. The current replatform team picked one new template and committed to ship in 6 weeks. The pre-migration collision check never ran. The canonical-tag coordination plan never got written. The link-equity preservation playbook lives in somebody’s head.

Friday night the cutover ships. Saturday the cache warms. Sunday Googlebot starts re-crawling. Monday Search Console fills with 404s on URLs the legacy patterns held. The long-tail per-location rankings on 80 store + service combinations slide inside 10 days. The CMO calls the SEO lead asking why organic-attributed walk-ins dropped 18% week over week. The recovery work runs 6-12 weeks per the published migration post-mortem timeline.

The pattern is not a discipline problem. At a 5-location site a senior SEO can hand-audit every URL before migration. At a 200-store site with 3-4 agencies in the rear-view mirror and 40-80 silent collisions, the audit-side tools (Screaming Frog + Sitebulb + OnCrawl + DeepCrawl + Lumar + Botify + ContentKing + JetOctopus + Audisto) tell you what is already broken. The team needs the authoring side — the per-location template library, the collision check that runs before migration ships, the link-equity preservation playbook, and the per-location canary that contains blast radius.

The audit-side stack is mature. The authoring side underneath is operator wiring.

Screaming Frog + Sitebulb + OnCrawl + DeepCrawl + Lumar + Botify + ContentKing + JetOctopus + Audisto each ship strong primitives at the diagnostic side — crawl, render, structural-issue surfacing, log-file analysis, change tracking. Each is excellent at its core surface. None ships with a per-location template library that survives the agency rotation, a pre-migration collision check that runs before the migration ships, a link-equity preservation playbook the migration team executes against, or a per-location canary rollout that contains blast radius.

The authoring side is five components. Per-location template library — named and versioned URL templates per page type per vertical. Location page template + service page template + service-in-location page template + blog template + category template. Each template renders against the canonical per-location master record. Per-vertical pattern catalog — multi-unit franchise patterns differ from specialty-retail patterns from multi-state service-brand patterns. The catalog encodes the per-vertical conventions instead of re-deriving them per engagement. Pre-migration collision check — the authoring layer runs before migration ships. Duplicate slugs across locations + corporate pages colliding with location pages + blog URLs matching category URLs all surface in the pre-migration report. Surfaced before migration, each is a 30-second fix. Surfaced after migration, each is a 404 burning equity. Link-equity preservation playbook — every inbound link from off-site + every internal link from on-site has to land on a one-hop redirect, not a chain. Equity preservation coordinates redirect-chain compression + canonical-tag management + the new URL authoring so the link graph stays consistent across the migration. Per-location canary rollout — migrate one or two locations first. Watch crawl + ranking + conversion + redirect health for 2-4 weeks. If the canary stays green, roll out the rest in cohorts. If anything degrades, you contained the blast radius to two stores instead of fifty.

Ranking trajectory stays uninterrupted instead of recovered six weeks later. The CMO question shifts from “why did organic-attributed walk-ins drop 18% week over week” to “the canary cohort is showing the new template ranks within the same band as the legacy URLs.”

Three engagement shapes

Each tier funnels into the next. None requires the next.

Tier 1 — AI Readiness Assessment (2-3 weeks)

Diagnostic on your current URL surface ahead of replatform. Inventory of legacy URL patterns + per-location collision surface + redirect-chain health + canonical-tag coverage + per-vertical template gap surface. Output is a written assessment with the per-location template library sketch + pre-migration collision report + link-equity preservation playbook outline + per-location canary rollout sequence. Process commitment: assessment delivered within the scoped window with named per-location collision count + per- vertical pattern recommendations.

Tier 2 — AI Swarm Setup Sprint (4-8 weeks)

Build the per-location URL template library + per-vertical pattern catalog + pre-migration collision check + link- equity preservation playbook + per-location canary rollout pipeline. Ships with documented per-vertical pattern maintenance runbook + collision-check operator playbook + canonical-tag coordination format + canary surveillance dashboard. 30-day operating tail to tune the canary threshold rules against real per-location ranking + conversion data. Process commitment: pipeline in production by week 6-8 with first canary cohort live and the collision-check report generated before any subsequent cohort ships.

Tier 3 — Fractional CMO with AI Swarm (6-month minimum · 1-2 days/week embedded)

Embedded executive owns the multi-location orchestration including URL hierarchy authoring. Process commitments include: per-location template library maintenance + per-vertical pattern catalog + pre-migration collision check before every per-location URL change reaches publish; link-equity preservation playbook execution on every migration cohort with documented redirect-chain compression + canonical-tag coordination; per-location canary rollout for every replatform with 2-4 week surveillance before broader rollout; per-jurisdiction overlay compliance check against URL templates that intersect state rules. Per- cohort canary precision is tuned per stack and recorded as engagement KPIs.

What the multi-location SEO lead stops worrying about

The agency-soup URL set inheritance stops being the day-one surprise on every new replatform. The per-vertical template catalog survives the agency rotation; the next agency inherits the library instead of authoring a fifth parallel pattern.

The Friday-cutover Monday-404-flood pattern stops being the recurring migration anti-climax. The pre-migration collision report surfaces the 40-80 conflicts in the planning window; each is a 30-second fix in staging instead of a 404 burning equity in production.

The 6-12 week post-migration ranking-trajectory dip stops being the assumed-cost-of-migration. The link-equity preservation playbook coordinates the redirect-chain compression + canonical-tag management + new URL authoring so the new structure inherits the inbound equity instead of asking the search index to re-discover and re-rank a fresh URL set six weeks later.

The CMO conversation about organic-attributed walk-ins stops being a defensive explanation. The canary cohort shows the new template ranking within the same band as the legacy URLs before the broader cohort ships; the migration becomes a planned rollout, not a Friday-night bet.

Frequently asked

Why does URL taxonomy drift this far at 200-store + three-agency-history scale?

Each agency that has touched the site over the years shipped its own URL pattern — /locations/city/service, /city-service, /service-in-city, /our-locations/city, /find-us/state/city/store. Each pattern made sense in the agency engagement that produced it. By the time the third or fourth replatform begins, the production URL set is agency-soup with multiple parallel patterns referencing the same per-location entity. The drift is not a discipline problem; it is what happens when 4-5 agencies each ship their own taxonomy over 6-10 years without an authoring-side library that survives the agency rotation.

How is this different from Screaming Frog, Sitebulb, OnCrawl, DeepCrawl, Lumar, Botify, ContentKing, JetOctopus, or Audisto?

Those tools audit URLs that already exist. They are excellent on the diagnostic side — crawl, render, structural-issue surfacing, log-file analysis, change tracking. URL hierarchy authoring is the authoring side — the per-location template library, the per-vertical pattern catalog, the pre-migration collision check that runs before the migration ships, the canonical-tag coordination, the link-equity preservation playbook, and the per-location canary rollout. The diagnostic-side tools tell you what is broken; the authoring side is the wiring that prevents the breakage at migration time.

What is link-equity preservation and what does it actually protect against?

When URLs change, every inbound link from off-site (and every internal link from on-site) has to land on a one-hop redirect, not a chain. Equity preservation coordinates redirect-chain compression, canonical-tag management, and the new URL authoring so the link graph stays consistent across the migration. The protection is against ranking-trajectory interruption — the new structure inherits the inbound equity instead of asking the search index to re-discover and re-rank a fresh URL set six weeks later. Industry post-mortems on multi-location migrations regularly cite 15-30% inbound equity loss when this coordination is skipped.

What does Completions commit to on Tier 3 if we run URL hierarchy authoring for us?

Tier 3 process commitments include: per-location template library maintenance + per-vertical pattern catalog + pre-migration collision check before every per-location URL change reaches publish; link-equity preservation playbook execution on every migration cohort with documented redirect-chain compression + canonical-tag coordination; per-location canary rollout for every replatform with crawl + ranking + conversion + redirect-health surveillance against the canary cohort for 2-4 weeks before broader rollout; per-jurisdiction overlay compliance check against URL templates that intersect state rules. We commit to the operating discipline. Per-cohort canary precision is tuned per stack and recorded as engagement KPIs.

Who owns the URL template library, the canary rollout, and the redirect map post-engagement?

Your team owns the URL template library, the per-vertical pattern catalog, the redirect map, the migration go/no-go decision rights, and the engineering credentials. Completions owns the orchestration knowledge: the collision-detection runbook, the link-equity preservation playbook, the per-location canary rollout playbook, the per-vertical pattern maintenance history, the canonical-tag coordination format library. At engagement end we transition operational ownership back to your team over 30-60 days with documented handover.

How does URL hierarchy authoring compose with the rest of the multi-location stack?

URL hierarchy authoring sits inside the multi-location SEO architecture layer. The URL templates reference the canonical per-location master record (one canonical record + URL templates that render against it). Per-jurisdiction overlay composes at publish time when state-specific URL patterns intersect compliance rules. Multi-location reporting consumes per-location URL state to attribute ranking + traffic per store. Post-crisis SEO repair is the recovery path if a migration ships before the authoring layer is in place. Each capability page describes one layer; this URL-authoring page describes the per-location template + collision-check + canary capability the architecture includes.

Two ways into the work

Start with a pre-migration collision + template-gap diagnostic, or bring in the fractional CMO that runs the multi-location orchestration including URL hierarchy authoring.

Tier 1 — AI Readiness Assessment Tier 3 — Fractional CMO

Cal.com instant booking on either page. We scope on the call and send a private engagement link after.