📘 This use case demonstrates generating an old-to-new URL mapping at scale, filtered by traffic and matched semantically rather than by pattern rule.
Best for: Teams planning a site migration · Uses: crawl and traffic data, via your AI assistant
Overview
Migrating a site to a new URL structure means mapping old URLs to new ones, including matches that are semantically close but not identical, the kind of mapping simple pattern rules cannot handle. Botify MCP can generate that mapping at scale, with guardrails.
Prerequisites
Botify MCP connected to your AI assistant, such as Claude or ChatGPT. See Connecting to the Botify MCP for setup steps.
Access to the Botify project for the site being migrated, and to the new site's URL structure.
Description of the problem
Mapping old URLs to new ones across several country sites during a migration means working through the catalog categories individually, which can take hours per category when done manually.
Application
Ask your AI tool to pull every URL with meaningful traffic in a category.
Set a traffic threshold to filter out low-value URLs and reduce noise.
Why this approach works:
Pulling URLs by traffic first, rather than mapping the entire catalog, is what keeps the guardrail doing its job of filtering out low-value URLs before they add noise to the match.
Matching semantically rather than by pattern rule is what handles the close-but-not-identical cases a simple regex would miss.
Have your AI tool match the old URL patterns to the new site structure and generate the redirect file.
Review the mapping before anything goes live.
Follow-up prompts
"Flag any old URL your AI tool couldn't confidently match." — surfaces the cases that need a person to decide, rather than letting a low-confidence guess into the redirect file.
"Run the same mapping for [next category or country site]." — repeats the approach across the rest of the migration instead of starting over.
Make it repeatable
Reuse the same traffic threshold and matching approach for each category or country site in the migration, so results across the whole migration are produced the same way and stay comparable.
After the migration, use Checking Whether a Ranking or Traffic Shift Lines Up With a Change to read performance either side of the cutover date.
Result
Thousands of URLs mapped, category by category, across several country sites, with hours of manual matching done in minutes.
Read next
Related topics