URL Structure Change: A Technical SEO Checklist for Site Migration
When you alter your site's URL structure—whether through a domain change, protocol switch, or site relaunch—you are fundamentally reshaping how search engines discover, crawl, and index your content. A poorly executed URL change can cascade into traffic loss, ranking drops, and indexation gaps that take months to recover. This checklist guides you through the critical steps, from pre-migration planning to post-launch monitoring, with a focus on preserving your site's search equity.
Understanding the Risks of URL Structure Changes
Every URL change introduces risk. Search engines rely on URLs as unique identifiers for content; when you change them, you sever the direct link between existing rankings and your pages. The most common failure points include:
- Broken redirect chains: Multiple redirects between old and new URLs dilute link equity and slow crawl efficiency.
- Orphaned pages: New URLs that no internal links point to, making them invisible to crawlers.
- Indexation loss: Google may drop pages from its index if redirects are not properly implemented or if the new structure introduces duplicate content.
- Crawl budget waste: Search engine bots spend limited crawl allocation on redirect chains instead of discovering new content.
Pre-Migration Audit: Baseline Your Current State
Before touching a single URL, you need a complete inventory of your existing site structure. This audit serves as your baseline and reveals issues that could compound during migration.
Step 1: Crawl Your Current Site
Use a technical SEO tool to crawl your entire site. Record:
- Total number of indexed URLs
- Internal linking structure (depth, orphan pages)
- Current redirect chains (if any exist)
- Response codes (200, 301, 404, 5xx)
- Canonical tag implementation
- XML sitemap contents
Step 2: Map Old URLs to New URLs
Create a one-to-one mapping spreadsheet. Every old URL that has traffic, backlinks, or rankings must have a corresponding new URL. Do not redirect multiple old URLs to a single new URL unless you accept the equity loss.
| Old URL | New URL | Redirect Type | Priority |
|---|---|---|---|
| /product/old-category/item-123 | /products/item-123 | 301 | High |
| /blog/2023/seo-tips | /blog/seo-tips | 301 | High |
| /about-us | /about | 301 | Medium |
Step 3: Document Your Backlink Profile
Export your backlink profile from tools like Ahrefs, Majestic, or SEMrush. Identify which old URLs have external links pointing to them. These are your highest-priority redirect targets. A single broken backlink can mean lost referral traffic and diminished authority flow.
Implementing the URL Change
With your mapping complete, execute the change in a controlled sequence. Do not change URLs and redirects simultaneously on a live site without staging.

Step 4: Configure Server-Side Redirects
Implement 301 (permanent) redirects from old URLs to new URLs at the server level. Avoid:
- 302 redirects: These are temporary and do not pass full link equity.
- Meta refresh redirects: These are slow and often ignored by crawlers.
- JavaScript redirects: Search engines may not execute JavaScript, leaving old URLs stranded.
Step 5: Update Internal Links
Change all internal links pointing to old URLs to point to new URLs. This includes:
- Navigation menus
- Footer links
- Content body links (including images and CTAs)
- Breadcrumb trails
- Pagination links
Step 6: Update Canonical Tags
If you have canonical tags pointing to old URLs, update them to reference the new URLs. Incorrect canonicalization can signal to search engines that the old URL is the preferred version, undermining your redirects. See our guide on canonical URLs for best practices.
Step 7: Update XML Sitemaps and robots.txt
- Replace all old URLs in your XML sitemaps with new URLs.
- Ensure your robots.txt file does not block new URLs.
- Submit the updated sitemaps via Google Search Console and Bing Webmaster Tools.
Step 8: Implement 404 Handling
Some old URLs may not have a direct new equivalent. For these, create a custom 404 page that helps users find relevant content, or redirect them to a category page. Never leave them as soft 404s (pages that return 200 but show "not found" content).
Post-Migration Monitoring
The work does not end when redirects are live. Monitor for at least 30–60 days to catch issues early.
Step 9: Verify Redirect Implementation
Use a redirect checker tool to test a sample of old URLs. Confirm:
- Each returns a 301 status code
- The redirect chain is no longer than one hop
- The final destination URL loads correctly
- No redirect loops exist
Step 10: Monitor Indexation in Search Console

In Google Search Console:
- Check the "Pages" report for new URLs being indexed
- Look for "Excluded" reasons: "Crawled – currently not indexed" or "Not found (404)"
- Monitor the "Index coverage" graph for spikes in errors
Step 11: Track Traffic and Rankings
Compare organic traffic for old vs. new URLs in your analytics platform. A temporary dip is normal (2–4 weeks), but a sustained drop of more than 20% signals a redirect or indexation problem. Use rank tracking tools to monitor keyword positions for pages that moved.
Step 12: Audit Core Web Vitals on New URLs
URL structure changes can impact page load times, especially if you changed directory depth or introduced new parameters. Run Core Web Vitals tests (LCP, CLS, INP) on a representative sample of new URLs. Poor performance can negate the benefits of a well-executed migration.
Common Pitfalls and How to Avoid Them
| Pitfall | Consequence | Prevention |
|---|---|---|
| Redirecting all old URLs to homepage | Massive loss of link equity and user experience | Map every significant URL individually |
| Using relative paths in sitemaps | Crawlers may misinterpret URLs | Use absolute URLs in sitemaps |
| Forgetting to update hreflang tags | International traffic confusion | Update all language/region annotations |
| Changing URLs during a crawl spike | Inconsistent indexation | Schedule migration during low-traffic periods |
| Not testing on mobile | Mobile-first index issues | Test redirects and page rendering on mobile devices |
When to Consider a Full Site Relaunch
A URL structure change is often part of a larger site relaunch. If you are also redesigning templates, updating CMS, or changing hosting, the complexity multiplies. For comprehensive guidance, see our site relaunch SEO checklist.
Final Verification Checklist
Before marking the migration complete, confirm:
- All old URLs return 301 redirects to new URLs
- No redirect chains longer than one hop
- XML sitemaps contain only new URLs
- robots.txt does not block new URLs or sitemaps
- Internal links point to new URLs
- Canonical tags reference new URLs
- Google Search Console shows new URLs as "Valid"
- Organic traffic has stabilized (within 20% of baseline)
- Core Web Vitals pass on new URLs
- Backlink profile shows new URLs accumulating links

Reader Comments (0)