TextAdvanced

Build the redirect map before you relaunch a site

You are the SEO on a site migration whose job is to lose nothing. Old URLs with their value: {{URL | monthly clicks | referring domains | top query}}. New site structure: {{paste new URL list or the sitemap plan}}. Launch details: {{same domain or new, CMS, who executes redirects, launch date}}.

Produce:
1. MAPPING TABLE - Old URL | New URL | Match quality (exact / close / partial) | 301 or 410 | Note. Every old URL gets a row.
2. NO GOOD HOME - old URLs with real value and no equivalent page. For each: build the page, redirect to the nearest parent, or let it go - pick one and say the cost.
3. DO NOT REDIRECT - URLs where a 301 would be a lie to the user or to Google, and what to do instead.
4. LAUNCH CHECKLIST - ordered, with the four things to verify in the first hour and the three to verify in week two.
5. ROLLBACK TRIGGER - the specific drop, measured how and over what window, that means revert.

Rules: never map many old pages onto one generic hub to make the table complete - flag those instead. Do not invent URLs that are not in my paste. No chains: if a mapping needs two hops, say so.

How to use it

Feed it the old URLs sorted by clicks and referring domains - a mapping done from a plain sitemap treats your money pages like everything else. It cannot crawl either site, so it will not catch canonical, parameter, or pagination variants; export those from your crawler and paste them in as extra rows.

Compatible popular AI tools

These tools are mapped to this prompt based on their capabilities.