A redirect mapping template is a structured spreadsheet that inventories every old URL on your site, assigns each a matching new URL, and documents the redirect type and reasoning — essential for preserving search equity during migrations, redesigns, or domain changes.
Every redirect mapping template needs five fundamental columns. Old URL is the complete address you're retiring, including protocol and any parameters if they matter for indexing. New URL is the destination — the closest semantic match on the new site structure. Redirect Type is almost always 301 (permanent) for moved content or 410 (gone) for genuinely deleted pages with no replacement; avoid 302 (temporary) unless you truly intend to bring the old URL back. Match Quality is a manual tag you assign: Exact (same content, same intent), Close (related topic or category), Broad (homepage or top-level fallback), or None (for 410s). Notes capture your reasoning — why this pairing makes sense, any edge cases, or whether the old page had notable backlinks. These five columns turn a chaotic migration into a transparent, auditable process. Optional extras include traffic rank from Analytics, inbound link count from your backlink tool, and a status column to track implementation.
You cannot map what you do not know exists. Start with a complete crawl of your current site using Screaming Frog, Sitebullet, or DeepCrawl set to follow all internal links and capture parameters. Export that URL list as your baseline. Next, pull a full year of URLs from Google Search Console Performance report — filter by page, download all rows — because the crawl may miss pages that lost internal links but still receive search traffic. Add URLs from your Analytics property, filtered to pages with at least one session in the past twelve months. If you run server log analysis, merge in any URLs that received Googlebot requests recently. Deduplicate and sort alphabetically. For Canadian bilingual sites, ensure both English and French URL sets are captured if you use path or subdomain language targeting. The goal is zero surprises: every URL that ever earned a visit or a backlink gets accounted for, even if it ultimately maps to a 410.
When you are consolidating categories, renaming URL slugs site-wide, or moving from one CMS path convention to another, manually mapping hundreds of URLs is inefficient and error-prone. Instead, define pattern rules in a separate tab of your template. For example, if all old blog posts lived under example.ca/news/YYYY/MM/slug and the new structure is example.ca/blog/slug, document that pattern once with a formula: the Old URL Pattern, the New URL Pattern, and a note explaining the logic. Use spreadsheet functions or a script to apply the rule in bulk, then spot-check a sample. Common patterns include dropping date folders, changing category names, or stripping query parameters that no longer serve a purpose. Always manually review high-traffic outliers — a top-performing post may deserve a custom slug rather than a mechanical replacement. Pattern mapping saves hours but should not override editorial judgment for your most valuable pages.
Some pages require individual attention because their content does not fit a formula. A detailed service page about trademark law in Ottawa has no mechanical equivalent if you are pivoting service offerings; you decide whether to map it to a broader legal services page, a related practice area, or mark it 410 if that service is discontinued. Product pages with unique SKUs, case studies, resource downloads, and location-specific landing pages all demand manual review. Cross-reference each URL's backlink profile — use Ahrefs, Majestic, or your preferred tool — and its traffic history. A page with ten referring domains and steady monthly visits deserves an Exact or Close match, even if that means creating a new landing page on the new site to preserve the topic. A page with zero backlinks and zero traffic in two years can safely 410. The redirect mapping template becomes your decision log: future site managers will see why you chose each destination, and auditors can verify that you preserved equity intelligently.
Once your redirect map is complete, stage the new site with redirects implemented via server config, .htaccess, or your CDN redirect rules, depending on your stack. Run a full crawl of the staging environment, feeding it the old URL list. The crawler should follow each redirect and confirm the destination matches your map. Flag any redirect chains (old URL redirects to intermediate URL redirects to final URL — collapse these to a single hop), loops (A redirects to B redirects to A), or unmapped URLs that return 404 instead of an expected redirect. Fix those entries before go-live. Post-launch, monitor Google Search Console for 404 errors. Sort by click volume descending — if a 404 page was receiving search traffic, you missed it in your inventory and need to add a redirect immediately. Update your template with these additions so the map reflects reality. Treat the template as a living artifact: months after migration, you may discover old URLs in referral logs or broken backlinks and need to layer in new redirects.
Canadian agencies often handle bilingual sites or multi-brand portfolios where redirect mapping spans domains. If you are consolidating example.ca and example-fr.ca into a single domain with /en/ and /fr/ paths, your template needs a Domain column to track the source. Each row then specifies the old domain, old path, new domain, and new path. For Quebec-targeted content, ensure French URLs map to French equivalents and metadata reflects the correct hreflang annotations — the redirect alone does not solve language targeting. When merging multiple brands into one corporate site, add a Brand column so stakeholders can filter and review their subset. The template also serves as the handoff document between your migration team and the client's IT or dev team who will implement the rules in Nginx, Apache, or Cloudflare. Clear column headers and consistent formatting reduce implementation errors. Export a .htaccess snippet or JSON ruleset directly from the spreadsheet if your server stack allows automated ingestion.
A spreadsheet format like Excel (.xlsx) or Google Sheets works best because you can sort, filter, use formulas for pattern matching, and share with non-technical stakeholders. CSV is acceptable for final handoff to developers but lacks formula support. Avoid plain text files — the structure and validation features of a spreadsheet prevent errors.
Use 301 when the content has moved or merged into another page that serves the same user intent. Use 410 when the page is truly gone with no equivalent — discontinued products, outdated event pages, or retired services. A 410 tells search engines to drop the URL from the index faster than a soft 404 and prevents diluting equity by forcing unrelated redirects.
Yes, many-to-one redirects are common and acceptable when the old pages genuinely consolidated into one resource. For example, redirecting five outdated regional office pages to a single updated locations page is fine if that new page covers all the offices. Avoid redirecting dozens of unrelated topics to your homepage just to eliminate 404s — that looks manipulative and provides poor user experience.
Include every URL that Google or users might request — traffic and backlinks are priority filters, not exclusion criteria. A page with zero recent visits but inbound links from a .edu site still matters. A page that ranked years ago may have residual crawl budget allocation. Mapping everything prevents random 404 spikes and ensures completeness. You can mark low-priority URLs in a separate column to deprioritize implementation if needed.
Review it monthly for the first three months post-launch, checking Search Console for new 404s and adding redirects as needed. After that, revisit quarterly or whenever you make structural changes. The template is a living document — any time you retire a page, restructure a section, or discover broken backlinks, update the map and implement the new redirects. Keeping it current saves hours during the next migration or redesign.
Screaming Frog can crawl both old and new site structures and export URL lists. Google Sheets or Excel formulas handle pattern-based replacements using SUBSTITUTE or REGEX functions. For large sites, Python scripts with pandas can parse server logs and match old-to-new URLs by fuzzy logic or title similarity. Redirect management plugins for WordPress or apps like Redirectly for Shopify streamline implementation but you still need the mapping template as your source of truth before you load rules into any tool.