What does URL taxonomy authoring actually do?

It generates every location's URL from your canonical brand and territory data, enforces the hierarchy at publish time, and produces the redirect map for any migration automatically. The taxonomy spec and the live site stay in sync.

How is this different from Ahrefs Site Audit, Semrush, Moz Pro, Conductor, BrightEdge, seoClarity, or Botify?

Those audit the URL tree you already have. They flag the drift. They cannot author the tree you want or block bad URLs from being published in the first place.

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

Crawlers analyze your live site. Useful for post-publish triage. This works before publish — so the crawler has fewer issues to surface.

How is this different from Contentful, Sanity, Strapi, Storyblok, or Prismic?

Those are great content models and generic URL slugs. They do not know which of your 80 locations exists, what state each one is in, or what service mix each one offers. This works from the canonical location data.

What patterns can you enforce?

Hierarchy depth, slug character constraints (including PHI-safe constraints for healthcare), trailing-slash policy, lowercase normalization, no-parameter policy, sitemap-inclusion rules, and per-vertical patterns (dental, fitness, restaurant, retail, hospitality, automotive, financial, legal).

How does this work during a migration?

The pre/post URL diff and the redirect map are generated as a byproduct of authoring the new taxonomy. You no longer need a separate redirect-map sprint.

Does it work for multi-banner operators?

Yes. The same patterns apply across every brand, with per-banner overrides where the brand actually differs.

Skill catalog

Stop letting URL taxonomy drift during a multi-location site migration

Per-location URL hierarchies authored against your canonical brand and service data — and enforced at publish time, so the spec and the live site stay in sync.

The problem

You run 80 locations. You are migrating from /location-name URLs to a real hierarchy — /[state]/[city]/[location]/[service]. Your SEO engineer drew the taxonomy in a Miro board last quarter. Two months in, dev is publishing pages and the taxonomy is already drifting — some pages live at /[city]/[location], some at /[state]/[city]/[location], some at /locations/[city]/[location]. Sitebulb flags 1,400 inconsistent URL depths. Ahrefs Site Audit reports the problem but cannot enforce a canonical pattern. Contentful authors content models and URL slugs but does not understand your multi-location SEO model. Screaming Frog crawls the tree you already have; it does not author the tree you want. The default outcome is a post-migration cleanup project: thousands of redirects, hundreds of broken internal links, and six months of slow recovery while organic traffic dips. The taxonomy did not need to drift. It drifted because the spec lived in a slide deck and the publish pipeline had no way to enforce it.

What success looks like

Every location's URL is generated from your canonical brand and territory data. The hierarchy depth, slug constraints, trailing-slash policy, lowercase normalization, and parameter rules are enforced at publish time — pattern violations are blocked and the right fix is suggested back to the author. Per-vertical patterns apply automatically: dental uses /[state]/[city]/[clinic]/[service] with slug constraints that keep PHI out, fitness uses /[state]/[city]/[gym]/[class], restaurant uses /[city]/[location]/[menu], retail uses /[city]/[store]/[category]/[sku]. Multi-banner operators see one consolidated URL audit across every brand. Migrations generate the pre/post URL diff and the redirect map as a byproduct, not as a separate three-month project. Every URL change is preserved with a timestamp, the actor, the old URL, the new URL, and the redirect chain — so an SEO post-mortem or an auditor can ask how a URL got the shape it has and get a clean answer.

How most operators solve this today

Five categories of tools touch URL planning today. None of them author per-location hierarchies and enforce them at publish time:

Enterprise SEO suites with site-architecture audit (Ahrefs Site Audit, Semrush, Moz Pro, Conductor, BrightEdge, seoClarity, Botify)
$99 to $499+ per user per month, plus enterprise tiers
Excellent at auditing the URL tree you already have. None of them author the tree you want or block bad URLs at publish time.
Technical-SEO crawlers (Screaming Frog, Sitebulb, DeepCrawl/Lumar, JetOctopus, OnCrawl, Audisto)
$35 to $259+ per month or annual
Analyze URL trees after publish. They do not author taxonomy.
Headless CMS and IA platforms (Contentful, Sanity, Strapi, Storyblok, Prismic)
$7 to $10,000+ per month
Author generic content models and URL slugs. They do not know which of your locations exists, what state it is in, or what services it offers.
In-house information architecture and manual URL planning
$130,000 to $210,000 per year per engineer, plus four to twelve weeks per migration
Miro board, Lucidchart, and a spreadsheet. Falls behind the first time a new location or vertical gets added.
Build it in-house
Custom validation rules wired into your CMS, plus ongoing maintenance
Possible, but the rule set and the per-vertical exceptions decay quickly as the brand expands or schema.org changes.

What changes when this is an agent skill

Every location's URL is generated from your canonical brand and territory data. The hierarchy is enforced at publish time — pattern violations are blocked, and the right fix is suggested back to the author with a one-click change. Per-vertical patterns apply automatically: dental gets /[state]/[city]/[clinic]/[service] with slug constraints that keep PHI out, fitness gets /[state]/[city]/[gym]/[class], restaurant gets /[city]/[location]/[menu], retail gets /[city]/[store]/[category]/[sku]. Migrations produce the pre/post URL diff and the redirect map as a byproduct — not a separate three-month project. The hierarchy stays consistent across canonical tags, internal linking, link-equity distribution, orphan-page detection, and redirect collapsing — all the moving parts of your link graph stay in sync because they share the same source data. Multi-banner operators see a consolidated URL audit across every brand with the same patterns applied. Every URL change is preserved with a timestamp, the actor, the old URL, the new URL, and the redirect chain — so an SEO post-mortem or an auditor can trace how every URL got the shape it has.

Agents that include this skill

Skills live inside agent rentals. To get this skill in production, hire any of the agents below — context-tuning at onboarding is included in the first month.

Internal Link Orchestration Agent
Owns the internal link graph across the entire site — URL hierarchy, canonicals, redirects, anchor optimization, orphan detection, link-equity flow.
Book a consultation →

FAQ

What does URL taxonomy authoring actually do?: It generates every location's URL from your canonical brand and territory data, enforces the hierarchy at publish time, and produces the redirect map for any migration automatically. The taxonomy spec and the live site stay in sync.
How is this different from Ahrefs Site Audit, Semrush, Moz Pro, Conductor, BrightEdge, seoClarity, or Botify?: Those audit the URL tree you already have. They flag the drift. They cannot author the tree you want or block bad URLs from being published in the first place.
How is this different from Screaming Frog, Sitebulb, DeepCrawl/Lumar, JetOctopus, OnCrawl, or Audisto?: Crawlers analyze your live site. Useful for post-publish triage. This works before publish — so the crawler has fewer issues to surface.
How is this different from Contentful, Sanity, Strapi, Storyblok, or Prismic?: Those are great content models and generic URL slugs. They do not know which of your 80 locations exists, what state each one is in, or what service mix each one offers. This works from the canonical location data.
What patterns can you enforce?: Hierarchy depth, slug character constraints (including PHI-safe constraints for healthcare), trailing-slash policy, lowercase normalization, no-parameter policy, sitemap-inclusion rules, and per-vertical patterns (dental, fitness, restaurant, retail, hospitality, automotive, financial, legal).
How does this work during a migration?: The pre/post URL diff and the redirect map are generated as a byproduct of authoring the new taxonomy. You no longer need a separate redirect-map sprint.
Does it work for multi-banner operators?: Yes. The same patterns apply across every brand, with per-banner overrides where the brand actually differs.
Can an SEO post-mortem or an auditor trace why a URL has the shape it has?: Yes. Every change is preserved with a timestamp, the actor, the old URL, the new URL, and the redirect chain.

Hire one of the agents that includes this skill

See all agents →Take the routing quiz