A website redesign can make your business clearer, easier to trust and simpler to contact. But if familiar page addresses disappear without a plan, visitors can land on errors instead of your new website. A WordPress redirect map helps prevent that: it records which URLs will stay, which will change and where each changed address should lead.
This matters even for a small website. Your existing URLs may appear in Google results, business listings, saved bookmarks, email campaigns and links from other websites. Changing the menu does not update those links.
The good news is that redirect planning does not need to be complicated. A spreadsheet, a reliable URL inventory and a careful launch check are enough to make a useful start.
What is a WordPress redirect map?
A redirect map is a list matching old website addresses to their intended destinations after a change. For permanent moves, those destinations will usually be reached through 301 redirects.
When someone requests an old URL, the server sends them to the replacement. Search engines also use that redirect as a signal that the content has moved. It helps them discover the replacement and consolidate signals, although rankings are never guaranteed to remain unchanged.
Not every page needs a redirect. If its address stays the same, it should normally continue loading directly.
A useful planning sheet therefore covers three decisions:
- Keep: the page remains at its existing URL.
- Redirect: the page moves or has a genuinely relevant replacement.
- Remove: the page is retired without an appropriate replacement.
Think of it as a content decision sheet first and a technical instruction sheet second.
1. Decide whether URLs need to change at all
A redesign does not automatically require new addresses. You can change layouts, typography, navigation and page content while keeping existing URLs.
Before renaming a page address, ask what the change achieves. A clearer structure may help a growing business organise its services. Removing an incorrect location from a URL may fix a real problem. Changing every address simply because the new design feels different usually creates unnecessary work.
For example, an established /kitchen-renovations/ page does not need to become /services/home/kitchens/ just to fit a new menu. Menu labels and URL paths do not have to match exactly.
Keep stable URLs where they still make sense. During a WordPress website redesign, this is one of the simplest ways to reduce avoidable migration risk.
2. Collect your existing URLs before replacing the site
Do this while the current website is still available. Once the old site has gone, finding every important address becomes harder.
Start with several sources rather than relying on a single export:
- The XML sitemap: WordPress or your SEO plugin may provide one.
- A website crawl: a crawler follows links and records the URLs it discovers.
- Google Search Console: the Performance report shows pages receiving search clicks and impressions within the selected reporting period.
- Analytics: landing-page reports can reveal addresses people still visit.
- WordPress content lists: check posts, pages, products and any custom content types.
- Campaign and business records: look for URLs used in ads, newsletters, directory listings and QR codes.
These sources answer different questions. A crawl may miss a page with no internal links. A sitemap may exclude an old landing page that still receives ad traffic. Neither source should be treated as a complete historical record.
Include important PDFs and other downloadable resources if people link to them. A pricing guide can attract useful visitors just as a service page can.
Save the inventory somewhere separate from the website, and keep an untouched copy for reference.
3. Build a spreadsheet that someone else could implement
Your redirect plan should be clear enough that the person configuring it does not need to guess your intentions.
Use columns for:
- Old URL
- Current page purpose
- Decision: keep, redirect or remove
- New destination URL
- Intended response, such as 200, 301 or 404
- Priority and notes
- Test result
Here is a simplified example for a hypothetical heating business:
| Old path | Decision | Destination | Intended response |
|---|---|---|---|
/contact/ |
Keep | Same URL | 200 |
/services/boiler-repair/ |
Redirect | /boiler-repair/ |
301 |
/heating-faqs/ |
Redirect | /heating-advice/ |
301 |
/winter-offer-2021/ |
Remove | No replacement | 404 |
A 200 response means the page loads successfully. A 301 signals a permanent move. A 404 means the requested resource was not found. A 410 can also be appropriate when you intentionally remove content permanently.
Use full URLs in the working spreadsheet when domains, subdomains or HTTP/HTTPS versions are changing. For a same-domain project, paths may be sufficient, but the implementation tool may have its own format requirements.
Never create a redirect from an address back to itself. A page marked “keep” is a reminder to preserve it, not an instruction to add a redirect rule.
4. Match destinations by visitor intent
The most important decision is not which plugin to use. It is where each old page should lead.
Ask: Would someone following the old link feel that they reached the right place?
An old emergency plumbing page should lead to the new emergency plumbing page, not a general homepage. A discontinued service may reasonably redirect to a replacement service if it solves substantially the same problem.
When several pages become one
Consolidation can be sensible when multiple thin or overlapping pages serve the same purpose. Redirect them to a stronger combined resource, but make sure the replacement actually covers their useful content.
For example, three short maintenance guides could become one complete guide. Redirecting them to a generic services page would be a weaker match.
When there is no replacement
Do not redirect every removed URL to the homepage. It frustrates visitors, and search engines may treat irrelevant redirects as soft 404s rather than useful replacements.
For a genuinely obsolete page with no equivalent, a proper 404 or 410 can be the right result. Your error page can still offer navigation, search and a contact option without pretending the missing content exists.
If a valuable page has no suitable destination, reconsider deleting it. Improving or retaining it may be better than forcing an unrelated redirect.
5. Set up redirects in one manageable place
On WordPress, redirects are commonly implemented through a redirect plugin, hosting controls or server configuration.
A plugin can be practical for a small business managing individual page moves. Hosting or server-level rules may be better for site-wide changes or large sets of redirects. The right choice depends on your hosting environment and who maintains the website.
Before changing anything:
- Back up the website and any configuration you will edit.
- Export existing redirect rules where possible.
- Identify which system already controls redirects.
- Test the new rules in a suitable environment.
- Keep a documented way to undo the changes.
Avoid scattering overlapping rules across several plugins and hosting tools. That makes conflicts harder to diagnose.
Use exact URL matches when possible. Broad pattern rules can be efficient, but one incorrect pattern can redirect a whole section of the site unintentionally.
Also decide how query parameters should behave. Tracking parameters such as utm_source may need to be preserved for campaign reporting. Parameters controlling filters or content need more careful handling; do not assume every parameter can be discarded safely.
For a domain migration, redirects must be served from the old domain. Keep control of that domain and maintain the hosting or forwarding infrastructure and valid HTTPS certificate needed to handle its requests.
6. Test destinations and remove redirect chains
A redirect existing is not the same as a redirect working correctly.
For every mapped address, check that:
- The old URL returns the intended redirect status.
- The destination is the correct page.
- The destination loads successfully rather than returning an error.
- There is no redirect loop.
- The redirect points to the final production domain, not staging.
Aim for a direct route from the old address to the final destination.
For example, avoid this sequence:
/old-service/ → /services/new-service/ → /new-service/
Instead, update the first rule so it points straight to /new-service/. If you control the intermediate address, it can also redirect directly to the final page.
Use an HTTP status checker or crawler alongside a browser check. Browsers follow redirects automatically, so the page appearing on screen does not tell you which status codes or intermediate steps were involved.
Prioritise testing service pages, high-traffic landing pages, pages with external links and URLs used in paid campaigns. Then check the rest of the map.
7. Update the website’s own links before launch
Redirects are a safety net for old references. Your new website should not depend on them for normal navigation.
Update internal links to point directly to the final URLs, including links in:
- Menus and footer sections
- Buttons and page copy
- Blog posts and related-content blocks
- Elementor or Divi templates
- Forms, confirmation pages and downloadable documents
Check canonical tags too. A canonical tag identifies a preferred URL for content; it is not a substitute for a redirect when a page has moved.
The production sitemap should list the final, indexable URLs rather than old redirecting addresses. Confirm that important replacement pages are not accidentally marked noindex and that a staging-site indexing block has not carried over to production.
This is where SEO web design goes beyond adding page titles. The site structure, internal links, redirects and indexing settings need to support the same final pages.
8. Monitor the launch and keep useful redirects
Deploy necessary redirects as the new URLs go live. Otherwise, visitors may encounter a gap between the old pages disappearing and their replacements becoming reachable.
After launch, crawl the live site and retest your priority URLs. Check Search Console for indexing issues and review relevant 404 logs if your tools provide them.
Not every logged 404 needs fixing. Bots request invented addresses, and old spam URLs may never have represented real content. Focus on missing pages that belonged to your website or are receiving legitimate visits and links.
When you discover an overlooked URL, add it to the spreadsheet before implementing the fix. That keeps the map useful as a maintenance record.
Keep permanent redirects for at least a year, and preferably longer where old links still matter. For established addresses, keeping them indefinitely is often the simplest choice. Avoid removing them just because the redesign is no longer new.
A smoother redesign starts before launch
A redirect map cannot guarantee unchanged rankings, but it removes a common and preventable source of disruption. Preserve sensible URLs, match moved pages to relevant replacements and test the actual responses—not just how the new site looks.
At Sophia & Saleem, we bring design and technical SEO together so a redesign works for both visitors and search engines. Planning a new website or worried about broken links after a recent launch? Request a free website audit, and we’ll help you identify the most useful next steps.