Redirect mapping
Redirect mapping defines where users and search engines should be sent when an old URL is no longer the preferred accessible location.
URL Migration · Redirect Mapping · Technical SEO · Website Migrations
SEO Redirection Mapping Services for Safe Website Changes
Protect organic visibility, backlinks, user journeys, and indexed URLs during website migrations, redesigns, domain changes, platform moves, and URL-structure updates.
I create page-by-page redirection maps, define redirect rules, identify equivalent destinations, prevent chains and loops, and validate implementation before and after launch.
- Page-by-page URL mapping
- Redirect chain prevention
- Post-launch validation
Service overview
What Is SEO Redirection Mapping?
Redirection mapping is the process of matching old website URLs with their most relevant new destinations before a website structure changes.
A redirect map documents what should happen when a URL is renamed, a page moves to another folder, two pages are consolidated, a website changes domain, a platform is rebuilt, categories are reorganized, products are removed, languages are restructured, HTTP changes to HTTPS, subdomains move into subdirectories, trailing-slash or case rules change, or a page is permanently retired.
The map normally includes the existing URL, new destination URL, recommended status code, page type, mapping reason, priority, traffic or backlink value, canonical destination, implementation status, and validation result.
A strong redirect map preserves user journeys and search signals while helping search engines understand the website’s new structure.
Related services
Continue the workflow
Natural next steps that connect this offering with related work on the same roadmap.
This service sits inside a wider SEO and digital growth system. Strong next steps usually include SEO Website Migration Services and Technical SEO Audit Services.
Depending on priorities, also consider On-Page SEO Optimization Services and Programmatic SEO Services.
Potential outcomes
What Redirection Mapping Can Improve
A structured redirect strategy can reduce the technical and organic risks associated with website changes. Typical outcomes include the following—actual outcomes depend on destination relevance, implementation quality, website authority, content continuity, crawl timing, and the wider migration process:
Preservation of access to important old URLs
Better transfer of relevance and external-link value to replacement pages
Fewer broken links and user-facing error pages
Reduced redirect chains, loops, and unnecessary hops
Clearer alignment between redirects, canonicals, internal links, and sitemaps
Better migration monitoring and faster issue detection
Cleaner retirement of obsolete, duplicate, or low-value URLs
A documented implementation plan for developers and stakeholders
Service components
What Is Included in the Redirection Mapping Service?
Existing URL Inventory
I build or review an inventory of URLs that may be affected by the migration—avoiding reliance only on current navigation or sitemap. Important old URLs may no longer be linked internally but can still receive organic traffic, backlinks, referrals, bookmarks, or campaign visits.
- Website crawls and XML sitemaps
- Google Search Console and analytics
- Server logs and backlink tools
- CMS exports and product databases
- Existing redirect files and campaign URLs
- Internal search and business-critical URLs
New URL Inventory and Architecture Review
I review the proposed destination structure before mapping begins. Redirect mapping should not be used to compensate for an unclear or unstable destination structure.
- New page inventory and naming conventions
- Folder, category, language, and location structure
- Product or service relationships
- Canonical, pagination, filter, and parameter rules
- Trailing-slash, case, protocol, and hostname consistency
One-to-One URL Mapping
Where possible, each important old URL is mapped directly to the closest equivalent new page. One-to-one mapping is preferred because it provides the clearest relationship between old and new pages.
- Page purpose, intent, topic, and audience
- Product, service, category, location, and language
- Content similarity and conversion action
- Current rankings, backlinks, and organic traffic
Many-to-One Consolidation Mapping
When several old pages are combined into one stronger destination, I document how those URLs should be consolidated. Consolidation should not simply reduce page count without preserving relevant content.
- Duplicate articles and similar services
- Product variations and thin location pages
- Outdated guides replaced by one resource
- Multiple category paths to one canonical category
Removed-Page Decision Framework
Not every page has a valid replacement. A clean removal can be more appropriate than an irrelevant redirect.
- Redirect to close replacement or parent category
- Return 404 Not Found or 410 Gone
- Remain temporarily available or archive
- Consolidate, remove from sitemap, or exclude from links
- Traffic, backlinks, demand, and business value
Redirect Status-Code Recommendations
I document the appropriate status code for each redirect type. For ordinary permanent webpage migrations, 301 redirects remain the most common recommendation.
- 301 Moved Permanently for permanent moves
- 302 Found for temporary redirects
- 307 Temporary Redirect preserving request method
- 308 Permanent Redirect preserving request method
Redirect Chain Prevention
I identify existing and planned chains and recommend updating redirects so old URLs point directly to the final destination. Existing rules are reviewed because a new migration can accidentally extend older chains.
- Prefer A → C over A → B → C
- Reduce crawl waste and debugging complexity
- Avoid inconsistent signals and broken paths
Redirect Loop Prevention
I review possible conflicts involving protocol, www, trailing slashes, case, language, geolocation, CMS, server, CDN, middleware, and plugins. Validation should be performed in the actual launch environment.
- A → B → A cycles
- HTTP ↔ HTTPS loops
- Hostname and trailing-slash conflicts
Domain Migration Mapping
For domain changes, I create a complete old-domain-to-new-domain redirect strategy. Broad rules may be possible when paths are preserved, but page-by-page validation is still required for exceptions.
- Protocol and hostname consistency
- Path preservation and page-by-page exceptions
- Subdomains, assets, canonicals, and hreflang
- Sitemaps, analytics, Search Console, and profiles
HTTP-to-HTTPS and Hostname Mapping
Every variation should resolve consistently to the preferred canonical version—avoiding chains such as HTTP non-www → HTTP www → HTTPS www.
- http, https, www, and non-www
- Alternate domains and staging hosts
- Legacy and mobile subdomains
- Direct redirect to the preferred version
Subdomain and Subdirectory Migration Mapping
I map URLs during structural moves such as blog.example.com/article to example.com/blog/article. Subdomain migrations can affect more than the URL path.
- URL equivalence and internal links
- Canonicals, hreflang, and sitemaps
- Navigation, analytics, and Search Console
- Cookies, application behaviour, and server rules
CMS and Platform Migration Redirects
Platform migrations can change URLs even when visible content remains similar. Platform defaults should not redefine important URLs without an SEO review.
- WordPress, Next.js, Shopify, Magento, and custom stacks
- Slugs, categories, product IDs, and pagination
- Tags, authors, media, search, and parameters
- Language paths, trailing slashes, and file extensions
Ecommerce Product and Category Redirects
I help define what should happen when products are discontinued, replaced, or moved, and when categories merge or filters change. Redirecting every discontinued product to the homepage is generally not useful.
- Keep live with availability information
- Redirect to direct replacement or closest category
- Display alternatives or return 404/410
- Preserve pages for historical demand where appropriate
Blog and Content Migration Mapping
I map high-traffic articles, backlinked resources, evergreen guides, research, case studies, categories, and author profiles. A redirect alone does not replace missing content relevance.
- Changed slugs and category structures
- Date-folder removal and tag/author changes
- Content consolidation and archive restructuring
- Preserve important information on destinations
Multilingual and Hreflang Redirect Mapping
An old French page should normally redirect to its relevant new French destination rather than defaulting to English. Redirects, canonicals, and hreflang must point to accessible and consistent destinations.
- Language and country folders or subdomains
- Hreflang, x-default, and canonical URLs
- Language-selector and automatic redirects
- Regional versions such as en-us, fr-ca, and ar-ae
Query-Parameter and Tracking-URL Handling
I review whether parameters should resolve, canonicalize, redirect, remain crawlable, or be excluded—coordinated with analytics, advertising, and application requirements.
- Filters, sorting, pagination, and tracking
- Campaigns, sessions, search, and variants
- Preserve attribution before analytics capture
Regex and Rule-Based Redirect Planning
For large URL groups, rule-based redirects can be efficient—but broad regex rules should be tested carefully because one incorrect pattern can affect thousands of URLs.
- Folder, protocol, domain, and extension changes
- Date-folder removal and trailing-slash consistency
- Case normalization and parameter cleanup
- Documented exceptions and testable patterns
Redirect Priority Scoring
I prioritize mapping and validation according to organic traffic, impressions, rankings, backlinks, conversions, revenue, campaign usage, and business importance.
- Critical, high, medium, and low groups
- Retire candidates
- Focus testing on highest-impact URLs
Internal-Link Update Plan
Redirects should not become a permanent substitute for clean internal links. After migration, internal links should point directly to final URLs.
- Navigation, footer, breadcrumbs, and contextual links
- Buttons, related modules, and XML sitemaps
- Canonicals, hreflang, structured data, and JS links
Canonical and Redirect Alignment
Redirects and canonical tags should communicate consistent signals. The destination should not require search engines to interpret several conflicting instructions.
- Redirect destinations are canonical
- Sitemaps and hreflang use final URLs
- Internal links point to final URLs
- No destination canonicalizing back to old URLs
XML Sitemap Migration
XML sitemaps should reflect the new indexable URL set. The long-term sitemap should not become an archive of redirected or non-indexable pages.
- Remove old URLs and add new canonical URLs
- Language, image, video, product, and news sitemaps
- Last-modified dates and Search Console submission
Staging Environment Validation
Where staging is available, I validate the redirect plan before launch—then recheck after launch because production infrastructure may behave differently.
- Status codes, destinations, chains, and loops
- Canonicals, hreflang, internal links, and sitemaps
- Robots, auth, server, CMS, and CDN behaviour
Pre-Launch Redirect Testing
Before launch, I prepare or perform checks for critical, high-traffic, high-backlink, rule-based, language, product, category, parameter, protocol, hostname, case, and trailing-slash variants.
- Correct status code and final destination
- No chain, loop, or unexpected homepage redirect
- No staging-domain, insecure, or broken destination
Launch-Day Monitoring
Immediately after launch, I review priority URLs and major redirect patterns. Critical issues such as loops, mass 404s, staging redirects, or homepage fallback rules should be identified quickly.
- Homepage variants and top organic landers
- Categories, services, products, and articles
- Sitemaps, robots, canonicals, hreflang, and analytics
Post-Launch Crawl and Error Analysis
A migration is not complete when the redirect file is uploaded—it is complete when the new system has been validated in production.
- Broken redirects, chains, loops, and wrong status codes
- Internal links to old URLs and old URLs in sitemaps
- Soft 404s, unexpected errors, and missing language destinations
- Orphan and duplicate URLs
Search Console and Indexation Monitoring
I monitor available search data for migration-related changes—distinguishing temporary processing from structural errors requiring correction.
- Indexed-page and not-found reports
- Redirected and crawled-but-not-indexed URLs
- Canonical selection and sitemap processing
- Impressions, clicks, rankings, and crawl activity
Backlink Destination Review
Important external links should continue to resolve to useful destinations. A redirect preserves access, but a direct external link to the final URL is still preferable where practical.
- Correct destination and relevance
- Chains, broken links, and lost content
- Partner, publisher, directory, and profile updates
Analytics and Conversion Continuity
URL migrations can disrupt measurement even when redirects work correctly. SEO success should not be judged using incomplete post-launch tracking.
- GA4, GTM, and conversion events
- Thank-you, booking, and ecommerce tracking
- Cross-domain, campaign parameters, and CRM
Redirect Documentation and Ownership
I prepare a clear document that can be used by developers, SEO specialists, content teams, analysts, and project managers—one source of truth for redirect decisions.
- Old/new URL, status code, mapping type, and priority
- Reason, traffic, backlinks, and owners
- Implementation, QA, launch status, and notes
Redirect Lifecycle and Maintenance
Redirects should not be removed simply because several weeks have passed. Important old URLs may continue to receive visits, backlinks, or crawler activity for a long period.
- New URL changes and consolidations
- Expired products and removed services
- Chain cleanup and legacy rule removal
- Monitoring frequency, ownership, and documentation
Search terminology
Redirect Mapping, URL Migration and Canonicalization: What Is the Difference?
URL migration
A URL migration is the wider process of changing website addresses because of a redesign, platform move, restructuring, rebrand, or domain change. It may include redirects, internal links, canonicals, sitemaps, analytics, content, and technical validation.
Canonicalization
Canonicalization indicates which accessible URL should be treated as the preferred version when duplicate or similar pages exist. A canonical tag does not normally replace a redirect when the old URL should no longer remain accessible.
URL rewriting changes how a URL is processed or displayed through server or application rules. It may occur with or without an external redirect. These systems may work together, but they solve different problems.
Ideal clients
Who This Redirection Mapping Service Is For
Businesses redesigning a website
Companies changing navigation, content, page names, templates, or URL structures during a redesign.
Websites changing domains
Businesses completing a rebrand, domain migration, merger, acquisition, or international domain change.
Companies moving to a new platform
Websites migrating between WordPress, Shopify, Magento, Next.js, custom systems, or other frameworks.
Ecommerce and marketplace websites
Platforms changing products, categories, filters, brands, sellers, collections, or marketplace structures.
Publishers and content websites
Websites consolidating articles, changing blog paths, removing date folders, or reorganizing categories.
Multilingual and international websites
Businesses restructuring language folders, country versions, hreflang clusters, subdomains, or country domains.
SaaS and technology companies
Companies changing documentation, integration pages, product routes, help centres, or application marketing pages.
Websites with redirect chains and legacy rules
Businesses with years of accumulated redirects, old platforms, several domain versions, or unclear server rules.
Businesses consolidating websites
Companies combining several domains, brands, branches, products, or content sections into one website.
Development teams preparing a migration
Teams that need SEO requirements documented before the new website launches.
What you receive
Redirection Mapping Deliverables
Concrete URL inventories, redirect decisions, implementation files, and validation support—scoped to your migration and technical environment.
- Existing URL inventory
- New URL inventory
- Organic landing-page data review
- Search Console URL review
- Backlink URL review
- Business-critical URL identification
- Page-by-page redirect map
- One-to-one mappings
- Consolidation mappings
- Removed-page recommendations
- Redirect status-code recommendations
- Regex and rule-based redirect logic
- Domain migration rules
- Protocol and hostname rules
- Subdomain migration mapping
- Multilingual redirect mapping
- Ecommerce product and category rules
- Query-parameter handling
- Redirect chain analysis
- Redirect loop analysis
- Canonical alignment review
- Internal-link update plan
- XML sitemap recommendations
- Hreflang update plan
- Staging validation
- Pre-launch QA checklist
- Launch-day testing
- Post-launch crawl
- 404 and soft-404 analysis
- Search Console monitoring
- Backlink destination review
- Analytics continuity review
- Developer-ready implementation documentation
- Prioritized issue report
- Post-launch monitoring report
Delivery process
How I Deliver Redirection Mapping
Discovery and Migration Scope
I review the reason for the migration, current website, new structure, target launch date, platform, languages, business priorities, and responsible teams.
Old and New URL Collection
I collect and combine URLs from crawls, sitemaps, analytics, Search Console, backlinks, CMS exports, databases, and stakeholder lists.
Page Classification and Priority Scoring
URLs are grouped by page type, purpose, traffic, backlinks, conversions, indexation, and business importance.
Destination Mapping
Each important old URL is assigned to the most relevant new destination or given an appropriate removal recommendation.
Redirect Rule Development
I define one-to-one redirects, group rules, regex logic, protocol rules, hostname rules, and documented exceptions.
Pre-Launch Validation
The implementation is tested for status codes, destinations, chains, loops, canonicals, internal links, hreflang, and sitemap consistency.
Launch Monitoring
Priority URLs and major rule groups are checked in the live production environment.
Post-Launch Quality Assurance
I crawl and monitor the migrated website, identify errors, document corrections, and track organic and indexation signals.
Specialist
Why Work With Me for SEO Redirection Mapping?
I combine redirect mapping with technical SEO, website development, content architecture, multilingual SEO, analytics, structured data, and migration quality assurance.
This allows me to evaluate more than whether an old URL technically redirects—whether the destination is genuinely relevant, whether important content has been preserved, whether the redirect is direct, whether canonical tags agree, whether internal links have been updated, whether sitemaps contain final URLs, whether hreflang points to valid pages, whether tracking continues to work, whether developers can implement the rules safely, and whether post-launch results can be measured.
I can support the complete process from migration planning and URL mapping through implementation review, launch-day validation, and post-launch monitoring.
- Rather than producing a simple two-column spreadsheet, I document:
- Which URLs carry the highest risk
- Which pages have direct replacements
- Which pages should be consolidated
- Which URLs should return 404 or 410
- Which redirect patterns can be automated
- Which exceptions require manual rules
- Where chains and loops may appear
- Who should implement each action
- How the migration will be validated
- What should be monitored after launch
Common questions
Frequently asked questions
A redirect map is a document that matches old URLs with their intended new destinations. It normally includes the old URL, new URL, redirect type, mapping reason, priority, and implementation status.
No. A redirect is appropriate when a relevant replacement exists. A URL with no suitable alternative may return 404 or 410 rather than redirecting users to an unrelated page.
Usually not. Redirecting many unrelated URLs to the homepage provides limited relevance and may create a poor user experience. A close replacement, relevant parent page, or proper removal status is normally more appropriate.
A 301 indicates a permanent move. A 302 indicates a temporary redirect where the original URL may return. The correct choice depends on whether the change is permanent and how the application handles requests.
A redirect chain occurs when an old URL passes through one or more intermediate redirects before reaching the final destination. Important URLs should normally redirect directly to the final page.
A redirect loop occurs when URLs continually redirect between one another or back to themselves. This makes the destination inaccessible and requires correction.
Relevant permanent redirects can help transfer signals and preserve access to old URLs. However, redirects cannot guarantee unchanged rankings, especially when content, architecture, internal links, or page purpose also change.
Important permanent redirects should generally remain available for a substantial period and often indefinitely when old URLs continue to receive links or visits. The decision depends on migration type, server requirements, traffic, backlinks, and long-term domain ownership.
No. A redirect sends users and crawlers to another URL. A canonical tag identifies the preferred version while both URLs may remain accessible.
Yes, when the destination genuinely consolidates and covers the purpose of those pages. Redirecting unrelated pages into one broad destination is not recommended.
A standard HTTP redirect sends the request to one destination. When an old page has been divided into several new pages, the primary intent and most appropriate replacement must be selected. The new destination can then link users to related pages.
No. After migration, internal links should normally point directly to final destination URLs rather than relying on redirects.
The long-term sitemap should contain final canonical and indexable URLs. Redirected URLs should normally be removed from the main sitemap.
Yes. I can create the mapping and rules for domain, protocol, hostname, folder, subdomain, language, content, and platform migrations.
Yes. Large migrations can combine page-by-page mapping, automated matching, rule-based redirects, regex logic, priority scoring, and manual review of critical URLs. Automation is used carefully and exceptions are documented.
I can implement redirects directly where server, CMS, hosting, and platform access allow. I can also provide implementation-ready files or specifications for developers. The exact format depends on the technology, such as Apache, Nginx, Next.js, WordPress, Shopify, Cloudflare, application middleware, or custom server environments.
I test priority URLs, crawl the website, review status codes, check final destinations, identify chains and loops, validate sitemaps and canonicals, and monitor Search Console and analytics.
The initial process normally requires the current website, staging or new website where available, planned domain and URL structure, target launch date, CMS or technical stack, current XML sitemaps, existing redirect rules, analytics and Search Console access where available, backlink data where available, CMS or database exports where relevant, and a list of critical pages, products, services, languages, and conversion paths.
Discuss Your Redirect Mapping Project
- 20 min intro
- No obligation
- You keep your data