How to document WordPress redirects for ongoing ownership
A redirect works today, but the person who set it up has left. The next owner can’t tell why it exists, where it should go or whether anyone still needs it. Fun.
Redirects are part of a site’s history, and undocumented rules turn into a tangle at the next redesign. A small register makes the intent visible, so WordPress owners can review redirects without relying on memory.
Record the reason and destination
For each rule, capture the source path, destination, redirect type, date, reason, owner and ticket or migration reference. Say whether the destination is a replacement page, a canonical URL or a temporary route. “SEO fix” is not a reason.
If a rule covers a pattern, write down a few examples and the intended match, so a later editor can test it. Keep private data out of any broadly shared redirect file.
Check for chains and conflicts
Crawl the important old URLs and inspect the response path. A chain adds hops. Conflicting rules can create loops or send visitors somewhere irrelevant. Make sure WordPress, plugins, server configuration and any CDN aren’t all managing the same redirects.
The interface differs by setup, so I verify the actual response rather than trusting one screen. Take a backup or export before bulk edits, and test a few representative rules afterwards.
Review the register as the site changes
When a page returns, moves again or is removed, update the record and test the old address. Retire obsolete rules only after checking links and migration requirements. Keep an eye on important destinations for errors.
The register is useful when it tells the next owner what to keep and why.
Keep the work reviewable
Start the next review with one question the current setup can answer, such as which rules have no owner. A small scope gets finished.
Note the date and source of every observation. A redirect that worked in March may be shadowed by a plugin update in June.
Compare one ordinary rule with one exception, such as a pattern rule or an old URL with a query string.
Know which layer is the source of truth and which only displays the result. A plugin screen can show a rule that the server never applies.
If two crawls disagree, don’t merge them. Check the timing and settings first and keep the difference on record until it is explained.
Follow the route a visitor really takes, from old link to final page, not only the row where you expect the rule to live.
Before you apply a pattern rule site-wide, test it on a representative URL and check the live response afterwards.
A good handover names the person who can answer questions about the domain, hosting or plugin. “The web team” is not a person.
When the evidence is incomplete, say what is missing and pick the next check. I’d rather leave a note saying “unknown” than guess a reason.
Record each change with a short reason and an owner, and keep the earlier export for rollback.
Separate a confirmed fact (this rule exists) from a likely explanation (it was added for the migration) and from a proposed action (retire it). The three can sit in one note, but they don’t carry the same weight.
Keep the note on each rule brief but specific: the owner, the source and the event that should trigger another review. A real change, such as a redesign or a hosting move, is a better prompt than a calendar reminder.
When you report a finding, put its limitation next to the recommendation. Whoever reads it should see what is known, what is uncertain and why the next step is proportionate.
Keep a short list of assumptions still to confirm, and say who can settle each. A convenient working note is not a verified source.
The scope of every rule should be visible to anyone acting on it, particularly where one section of the site or one language version behaves differently.
Review the register after a platform, plugin or hosting change that affects its scope. Redirect plugins get replaced, servers get migrated, and rules that lived in one place can quietly end up in two.
Add a column for “safe to remove?” and fill it only with evidence, such as no traffic to the old URL, no internal links and no external links worth keeping. A blank is better than an optimistic yes.
If you inherit a site, ask early for the old redirect export. It is the cheapest piece of history you can get.
Related reading
- What to document before a WordPress hosting move
- Maintaining useful search visibility on a WordPress resource library
- When a WordPress plugin needs a staging test first
Could someone new to your site explain the purpose of its oldest redirect?