Most migration checklists map old URLs to new ones and call it done. That’s necessary but not sufficient — in the AI-search era, Google reads entities, not just URL strings.
Map Entities, Not Just URLs
If you have a deep resource page about “Federal Student Aid Eligibility” and redirect it to a generic “Financial Aid” homepage, you’ve broken the entity relationship — you’ve told the search engine that specific, high-value information no longer exists. Use a redirect hierarchy instead:
- Exact match: old URL → identical content on the new URL.
- Close match: old URL → the most relevant updated version of that specific topic.
- Category match: only if the page is genuinely retired — redirect to the immediate parent category, never the homepage.
Consider Subdomain-to-Subfolder Consolidation
If your organization has splintered into subdomains over the years — admissions.university.edu, alumni.university.edu, and so on — a migration is your chance to consolidate into a subfolder structure (university.edu/admissions/). This pools authority that’s currently scattered across separate domains into one, and it’s one of the fastest ways to see a post-migration ranking increase.
Don’t Underestimate the Politics
In large organizations, managing stakeholders can be harder than the technical execution. A department head will be unhappy that “their” URL changed. Bring data, not opinions — show how the new structure improves user flow and conversion rates, and most internal friction resolves itself.
For the full 10-point failure checklist and phased rollout plan, see 10 Reasons Your Site Migration SEO Isn’t Working.
