Redirect Mapping Template

SEO Migration Toolkit, template 2 of 6

Redirect Mapping Template

Map every old URL to its new home and verify each redirect: one permanent hop, a 200 page, no noindex, matching canonical.

Whether each planned redirect actually reaches the approved destination in one permanent hop, on an indexable page whose canonical agrees, with a human sign-off.

  • Excel workbook (.xlsx), opens in Google Sheets
  • PDF field guide, 9 to 11 pages
  • Blank and worked CSV templates
  • DataForSEO import script

Free, no email required. Version 3.0, updated November 2026.

Redirect Mapping Template.xlsx
M13fx=IF(K13="","",IF(K13<>"Ready","n.a.",IF(A13=B13,"Source equals target",IF(L13>1,"Duplicate source",IF(AND(OR(C13=301,C13=308),D13=1,E13=B13,F13=200,G13=0,H13=B13,I13=1),"Meets QA checks","Fix or review")))))

Start HereDashboardWorkspaceDelivery QAField Guide

The formula above is the real one from cell M13. Scroll it sideways to read the whole rule.

Connected to the DataForSEO API

This template is designed around one DataForSEO endpoint. Pull the data, convert it with one command, and the workbook does the rest.

Setup steps

DataForSEO On-Page APIA crawl of your site: URLs, status codes, canonicals, inlinks and sitemap membershipon_page/task_post

Save the JSON responseThe full API response, kept as your source of truth.response.json

Run the import scriptOffline. No API calls, no credentials.dataforseo_import.py import --template 08

Paste at A13Dashboard, checks and action list update instantly.Redirect Mapping Template.xlsx

Column map for this template:Filled by the APIAudit trail (automatic)You add

Old URLApproved targetSource HTTP statusRedirect hopsObserved final URLFinal HTTP statusFinal noindexFinal canonical URLDestination reviewedSource reference
4 of 10 input columns come straight from DataForSEO

What the redirect mapping template decides

A redirect map is only as good as its QA. Plenty of migrations had a perfect spreadsheet of old and new URLs and still lost traffic, because the server returned 302s, chained three hops, landed on a page with a stray noindex, or pointed at a canonical somewhere else entirely.

This redirect mapping template pairs every old URL with its approved target, then checks the observed result against seven conditions: a 301 or 308 source response, exactly one hop, the final URL equals the target, a 200 final status, no noindex, a canonical that matches, and a human review of the destination. Anything that fails is flagged Fix or review, duplicate source rows are caught, and the Dashboard shows what's broken.

Who it's for

  • SEOs and developers running a site migration or URL restructure
  • Teams cleaning up legacy redirect chains
  • QA leads who need pass/fail evidence for launch sign-off
  • Agencies handing redirect files to a client's dev team

Where it fits in your workflow

The redirect mapping template answers one question. These three templates answer the questions around it:

  • Site Migration URL Inventory Template: which legacy URLs carry real value, what happens to each one at launch, and which planned retirements would throw away clicks, revenue or backlinks.
  • SEO Migration Checklist: whether the migration is safe to launch: which critical controls are still open, who owns them, and what evidence closes them.
  • Post-Migration SEO Monitoring Template: whether each migrated section is performing above or below what you'd expect after adjusting for market-wide changes, measured against a control segment that didn't move.

What's inside the download

One ZIP with the workbook, a 10-column input template (blank and filled), the PDF field guide and an offline script that converts saved DataForSEO responses into the input CSV. The workbook has five tabs.

Workspace. The working table. 10 input columns, 3 calculated columns, room for 1,000 rows. Dropdowns, Yes/No fields and range checks catch bad inputs as you paste.
Start Here. What it decides, a four-step setup and the colour key.
Dashboard. KPI cards, charts, a ranked Top 10 and an automatic action list.
Delivery QA. Pass, fail or exclude each validation step with evidence, owner and date.
Field Guide. Every field explained, plus each formula in plain English.

How the redirect mapping template calculation works

Redirect QA returns Meets QA checks only when the source is a 301 or 308, hops = 1, final URL = target, final status = 200, noindex = 0, canonical = target and reviewed = 1. It returns Source equals target for self-redirects and Duplicate source when an old URL appears twice with potentially different targets.

The key formula, exactly as it appears in the workbook

=IF(K13="","",IF(K13<>"Ready","n.a.",IF(A13=B13,"Source equals target",IF(L13>1,"Duplicate source",IF(AND(OR(C13=301,C13=308),D13=1,E13=B13,F13=200,G13=0,H13=B13,I13=1),"Meets QA checks","Fix or review")))))
Result column Plain-English formula What it tells you
Duplicate source rows COUNTIFS(all Old URL,Old URL) Duplicate sources must be reconciled before implementation.
Redirect QA IF(Old URL=Approved target,"Source equals target",IF(Duplicate source rows>1,"Duplicate source",IF(AND(OR(Source HTTP status=301,Source HTTP status=308),Redirect hops=1,Observed final URL=Approved target,Final HTTP status=200,Final noindex=0,Final canonical URL=Approved target,Destination reviewed=1),"Meets QA checks","Fix or review"))) Checks source status, one hop, exact destination, final 200, index directive, canonical and human approval.

The results you will see

Source equals targetDuplicate sourceMeets QA checksFix or review

Green meets the checks, red needs fixing first, amber needs a human decision and blue marks an opportunity. Rows with missing or out-of-range inputs are held back in the Input check column until they're fixed, so a half-filled row never sneaks into a total.

How to use the redirect mapping template

  1. Start from the URL inventoryBring in every old URL with a Redirect or Merge disposition and its approved target.
  2. Run a redirect traceUse a crawler in list mode or a redirect checker to record the first status code, number of hops, final URL and final status for each old URL.
  3. Add destination checksRecord whether the final page has noindex (1/0), its canonical URL, and whether a human has reviewed the destination as equivalent (1/0).
  4. Fix, retest, sign offWork the Fix or review rows, retrace them after deployment, then record evidence in Delivery QA.

The worked example in the Workspace tab. Clear the lime input cells, paste your CSV at A13 (values only) and every result recalculates.

Fill the redirect mapping template with DataForSEO

Every template in this library is built to run on DataForSEO data. This one uses DataForSEO On-Page API: a crawl of your site: URLs, status codes, canonicals, inlinks and sitemap membership.

Most of the data columns fill automatically. Add the business inputs listed below, then paste.

  1. Request the dataSend this request with your DataForSEO API login (HTTP Basic auth).
    POST https://api.dataforseo.com/v3/on_page/task_post [ { "target": "yourdomain.com", "max_crawl_pages": 1000 } ]

    Post the crawl task, wait for it to finish, then request on_page/pages with {"id": "<task id>", "limit": 1000} and save that response.

  2. Save the full JSON responseSave the complete response, not just the task ID, next to the template folder.
  3. Convert it with the included scriptIt runs offline, makes no API calls and never sees your credentials.
    python3 Automation/dataforseo_import.py import --template 08 --input response.json --output my-inputs.csv
  4. Add what the API can't knowApproved target, Redirect hops, Observed final URL, Final HTTP status, Final noindex, Destination reviewed
  5. Paste at A13Clear the demo rows, paste the CSV values at Workspace cell A13 and the dashboard updates.
Fills automatically from DataForSEO You add
Old URL, Source HTTP status, Final canonical URL Approved target, Redirect hops, Observed final URL, Final HTTP status, Final noindex, Destination reviewed

Source reference fills automatically with the task ID, endpoint, location, language, device and snapshot time, so every row is traceable. Before a big pull, estimate the cost with the DataForSEO pricing calculator. The same steps, plus an example request file, are in the download's Automation folder.

Worked example: Northbeam Outdoor

Every template ships filled with data from Northbeam Outdoor, a fictional outdoor-gear retailer that appears across all 40 workbooks, so you can see what useful output looks like before you add your own. This workbook has 18 example rows.

18Records
0Rows with input issues
9Mappings meeting QA checks
9Redirects to fix

Half of the 18 example redirects fail at least one check. The failures are the classic ones: a 302 on the sale page, a three-hop chain, a target that 404s, a destination carrying noindex, and a canonical pointing at a sort parameter.

Result breakdown

Result Rows Share
Source equals target 0 0%
Duplicate source 2 11%
Meets QA checks 9 50%
Fix or review 7 39%
Input issues 0 0%

Input fields

Keep the columns in this order when you prepare a CSV. A missing observation stays blank; use 0 only for a measured zero or a verified No. Fields marked DataForSEO can be filled automatically by the included script.

CSV field Column Meaning and rule Source
old_url Old URL Exact source URL being retired or moved. DataForSEO: url
target_url Approved target Reviewed equivalent destination. Your records
observed_status Source HTTP status HTTP response at the old URL before following redirects. DataForSEO: status_code
hops Redirect hops Measured number of redirects before the final response. Your records
final_url Observed final URL Exact final URL from an HTTP redirect trace. Your records
final_status Final HTTP status Status after following the full trace. Your records
noindex Final noindex 1 if the target has a blocking noindex directive, 0 if checked and absent. 1 = Yes, 0 = No. Your records
canonical_url Final canonical URL Canonical declared by the final page. DataForSEO: canonical_url
reviewed Destination reviewed 1 only after a human approves relevance and user equivalence. 1 = Yes, 0 = No. Your records
source_ref Source reference Task ID, export filename and observation scope. Retain the untouched source response separately. Optional. DataForSEO: source_ref

Reading the result honestly

Meets QA checks confirms only the listed observed conditions. It does not confirm indexing or relevance beyond the recorded review.

Limits. A crawl snapshot cannot substitute for a full redirect trace. Keep redirects and required old hosting operational according to the migration plan.

Redirect mapping template mistakes to avoid

Accepting 302sA temporary redirect tells Google the old URL may come back. Use 301 or 308 for permanent moves.
Leaving old redirects in placeNew redirects on top of existing ones create chains. Update legacy rules to point directly at the final destination.
Redirecting everything to the homepageMass homepage redirects are treated like soft 404s. Map to the closest equivalent page.
Testing only on stagingProduction server rules, CDNs and plugins behave differently. Retrace on production after launch.

Tips from practice

  • Trace the top 500 URLs by value on launch day, then the full list within 48 hours.
  • Keep redirects live for at least a year; longer for pages with strong backlinks.
  • Sort by Redirect QA, filter Fix or review, and hand that filtered list to dev as the ticket.

Frequently asked questions

What is a redirect map?

A spreadsheet that pairs every old URL with the new URL it should permanently redirect to during a migration or restructure.

Should I use a 301 or 308 redirect?

Both are permanent. 301 is universal and fine for almost every case; 308 also preserves the request method, which matters for forms and APIs. This template accepts either.

How many redirect hops are acceptable?

One. Google follows several, but each hop adds latency and risk. The template only passes single-hop redirects.

How do I check redirects in bulk?

Use a crawler in list mode (Screaming Frog, Sitebulb) or an HTTP checker to record the status chain, then paste the results into the Workspace.

Why does a correct redirect still fail QA?

Because the destination itself has a problem: a 404, a noindex tag, a canonical pointing elsewhere, or no human review yet.

Part of the SEO Migration Toolkit

Get all 6 SEO Migration templates in one ZIP, or the complete set of 40 SEO and GEO templates with the 401-page field handbook.

Download the SEO Migration Toolkit

See the complete SEO & GEO toolkit

Jourdan Rombough

Built by Jourdan Rombough, technical SEO and GEO consultant with 15+ years in search. About Jourdan or get an SEO plan.

More on digital marketing in our blog

See all posts