Blog

A redesigned website can look better and still lose valuable search traffic if its old URLs lead nowhere. When you change a page address, you need to give visitors and search engines a clear route from the old page to its replacement.

For permanent changes, that usually means a 301 redirect. Done carefully, redirects help search engines consolidate signals at the new URLs and keep existing links useful, but they cannot guarantee unchanged rankings after a redesign.

The safest approach is straightforward: keep working URLs wherever possible, map every necessary change, and test the redirects before and after launch. Here is how to handle that without turning a small-business redesign into an avoidable SEO cleanup project.

Understand what a redirect actually does

A redirect tells a browser or search engine that a requested address should send it somewhere else. Someone opening an old service page should arrive at the matching new service page, not an error screen or an unrelated homepage.

• 301: A permanent redirect, commonly used when a page has moved permanently.
• 308: Another permanent redirect status that preserves the request method. It can be appropriate, although 301 is a familiar choice for ordinary website page moves.
• 302 or 307: Temporary redirects, suitable when the original address is expected to return.
• 404: The requested page was not found.
• 410: The requested resource has deliberately been removed.

For a typical WordPress redesign, use permanent redirects for permanent URL changes. Avoid relying on JavaScript or a timed page refresh when a proper HTTP redirect is available.

A redirect preserves a route to content. It does not make an unrelated replacement relevant, restore deleted information, or guarantee that a redesigned page will rank where the original did.

1. Keep existing URLs unless there is a good reason to change them

You do not need new URLs just because you have a new design. Changing colours, layouts, navigation labels, or the WordPress theme can often happen without changing page addresses.

If an established page already uses /furnace-repair/, keep that address when the redesigned page still covers furnace repair. A slightly tidier slug rarely justifies creating extra migration work on its own.

URL changes make more sense when you are merging duplicate pages, correcting a confusing structure, or replacing content with a genuinely different organization. Even then, change only what needs changing.

Be especially careful with WordPress permalink settings. A site-wide change can affect every blog post, and changes to category or product bases can affect entire sections of a WooCommerce store.

2. Build an inventory before the old site disappears

Start collecting old URLs while the existing website is still available. Your WordPress page list is useful, but it will not show every address that visitors or search engines might know about.

Combine information from several places:

• The existing XML sitemap, including separate post, page, and product sitemaps where applicable.
• A crawl of the public website using a tool such as Screaming Frog SEO Spider.
• Google Search Console performance data showing pages receiving search clicks and impressions.
• Analytics reports showing landing pages and useful conversions.
• Available backlink reports and server logs.
• Links in advertising, business directories, newsletters, downloadable documents, and Google Business Profile.

If you have not connected the site to Search Console, see How to Set Up Google Search Console for Your WordPress Website. It can help identify valuable pages before launch and indexing problems afterwards.

Include important PDFs and other downloads if their addresses are changing. A restaurant menu, product specification sheet, or service brochure may have links pointing directly to the file rather than to a WordPress page.

Prioritize, but do not stop at the popular pages

Review pages with search traffic, enquiries, sales, or strong external links first. They deserve careful destination choices and manual testing.

Then work through the rest of the inventory. A low-traffic page may still be linked from a customer’s saved email or an industry directory.

3. Create an old-to-new URL map

Use a spreadsheet with one row for each old address. Include the old URL, intended action, destination URL, reason for the decision, and test result.

For example, a hypothetical Canadian heating business might plan these changes:

• /services/furnace-fixing/ redirects to /furnace-repair/, because the same service has a clearer address.
• /heating-maintenance/ and /furnace-tune-ups/ redirect to /furnace-maintenance/, because their useful content has been combined.
• /contact/ stays at /contact/, so no redirect is needed.
• An expired event page without a useful replacement returns 404 or 410.

Match the visitor’s intent, not just a shared keyword. Someone looking for commercial boiler repair should not be sent to residential air conditioning simply because both pages belong to an HVAC business.

Do not redirect every deleted page to the homepage

A blanket homepage redirect is convenient, but usually unhelpful. Search engines may treat an irrelevant destination as a soft 404, meaning the redirect does not provide a meaningful replacement.

If there is no equivalent content, a genuine 404 or 410 is often the honest choice. Give visitors a useful error page with navigation and search, while keeping the correct error status.

For discontinued products, consider retaining a useful product page explaining availability and suggesting alternatives. Redirect to a replacement product only when it genuinely meets the same need, rather than automatically sending every discontinued item to a broad category.

Preserve language and location relevance

If your Canadian website has English and French pages, map each old page to the appropriate language version. Sending all French URLs to an English homepage creates a poor experience and weakens the match between old and new content.

The same principle applies to service areas. An old Fredericton service page should not redirect to a Moncton page unless the content and business circumstances genuinely justify that choice.

4. Choose one clear place to manage redirects

WordPress redirects can live in a plugin, hosting configuration, web server configuration, or a CDN. There is no single best location for every website, but overlapping rules are a common source of problems.

A redirect plugin

A plugin such as Redirection can be practical for a small or medium-sized site. Some SEO plugins also include redirect management, so check what is already installed before adding another tool.

The advantage is easier editing and visibility inside WordPress. The tradeoff is that application-level redirects depend on the plugin and WordPress running, and they may not handle requests already intercepted elsewhere.

Check the plugin’s official documentation for current setup instructions, matching behaviour, and any applicable pricing. Interface labels and available features can change.

Hosting, server, or CDN rules

Infrastructure-level redirects can be useful for domain changes, protocol changes, large URL patterns, and requests that should redirect before WordPress loads. They also require care because a broad rule can affect the whole website.

Do not paste an Apache configuration example into an Nginx setup or assume every hosting panel processes rules the same way. Ask your hosting provider which method fits the environment, and keep a copy of the working configuration before changing anything.

Whichever approach you choose, document where the redirects live. Otherwise, a future plugin removal, hosting move, or CDN change can quietly erase part of the migration.

5. Keep rules narrow and avoid redirect chains

A redirect chain sends someone through multiple addresses before reaching the final page. For example, an old service URL might redirect to an intermediate slug, which redirects again to the current page.

Point old addresses directly to the final destination wherever practical. Extra hops add delay and make troubleshooting harder, particularly when HTTPS and www rules are also involved.

• Check HTTP and HTTPS versions of important old URLs.
• Check www and non-www variants if both have been used.
• Confirm trailing-slash rules do not create unnecessary extra redirects.
• Update older redirects when their destinations change again.
• Avoid sending a URL back to itself or creating a cycle between two pages.

Start with exact URL matches unless you understand the pattern you need. Regular expressions can handle many changes efficiently, but a loose pattern can accidentally capture product pages, account screens, or unrelated content.

If the browser reports a redirect loop, adding more rules usually makes diagnosis harder. Use How to Fix the Too Many Redirects Error in WordPress to work through likely conflicts.

Decide how query strings should behave

Some addresses contain parameters after a question mark. These may be advertising tags, search filters, language settings, or functional values used by a store or booking system.

Check whether your redirect tool preserves, drops, or matches those parameters. Preserve legitimate tracking where appropriate, but do not blindly forward obsolete functional parameters that break the destination or change its behaviour.

Keep migration rules away from checkout actions, payment callbacks, login requests, and other functional endpoints unless a developer has assessed them. Redirecting a public information page is not the same as redirecting a payment request.

6. Test before launch, then test the public website again

Take a recoverable backup before changing redirects or permalink settings. Use a staging copy to check destination pages and rule behaviour where your hosting setup allows it.

If staging is unfamiliar, WordPress Staging Environments Explained covers the basic idea. Staging checks are useful, but they cannot fully prove how production DNS, CDN rules, and cached redirects will behave.

For each mapped URL, verify:

1. The old address returns the intended permanent redirect status.
2. The redirect destination is the correct final public URL, not a staging address.
3. The destination returns 200 OK and contains the expected content.
4. The destination is accessible to search crawlers and does not have an unintended noindex directive.
5. The destination’s canonical tag points to the appropriate final URL.
6. The visitor is not sent through an avoidable chain or loop.

Use browser developer tools or a crawler that reports HTTP responses to inspect status codes. Simply seeing a page load does not tell you whether the redirect is permanent or whether several hidden hops occurred.

After launch, clear relevant website and CDN caches, then repeat the checks on the public domain. Test key enquiry forms, booking links, and shopping journeys as well, because a destination can load successfully while its main function is broken.

7. Update links and SEO signals to the new addresses

Redirects are a fallback for old links, not a reason to leave your own website pointing at outdated URLs. Update menus, buttons, body links, footer links, and links inside downloadable documents you control.

• Generate an XML sitemap containing the final indexable URLs, not redirecting addresses.
• Update canonical tags to match the intended final URLs.
• Update language-alternate references if your multilingual site uses them.
• Check structured data for old page addresses.
• Update advertising destinations, directory listings, and Google Business Profile links.
• Remove launch-time noindex settings and confirm production crawling is allowed.

Do not block old URLs in robots.txt just because they redirect. Search engines need to request those addresses to discover the move.

Also compare the content itself. If a detailed service page becomes a short paragraph with a new design, redirects cannot compensate for the information you removed.

8. Monitor the migration without expecting instant stability

Search engines need time to recrawl old addresses and process replacements. Some ranking movement can happen even when the technical migration is sound, especially if the redesign also changes content or navigation.

Check critical URLs immediately after launch, review errors frequently during the early period, and continue checking over the following months. Use Search Console, analytics, and available server logs together rather than relying on one traffic graph.

Look for new 404s with legitimate incoming links, unexpected destination pages, indexing exclusions, and drops concentrated on particular services. An old URL reported as redirected in Search Console is generally expected when that redirect was intentional.

Google generally recommends keeping migration redirects in place for at least a year. Keeping useful redirects longer is often sensible, since bookmarks, printed materials, and external links can outlast the migration period.

If you change domains, keep control of the old domain and maintain its HTTPS certificate so secure old links can still reach the redirects. A .ca domain does not automatically forward visitors simply because you have launched another website.

What to ask before approving a redesign

Before launch, ask whoever is building the site for the URL inventory, redirect map, test results, and a record of where the rules are managed. Agree on who will investigate missed redirects afterwards and what follow-up work is included in the project scope.

Ambrite builds custom WordPress websites, with direct access to the developer handling the project. If you are replacing an existing site, share the old sitemap, Search Console access, and business-critical URLs early so URL changes can be discussed before launch.

For an existing site with missing redirects, contact Ambrite by email with a few example old URLs and their intended destinations. That gives the developer something concrete to assess, rather than guessing from a general report that traffic has dropped.

The simplest migration is usually the safest: keep good URLs, redirect necessary changes to genuinely equivalent pages, and verify what the live website actually returns.

This article was written with the help of AI and reviewed by Ambrite. Pricing, features, and technical details may change, so always verify with official sources before making decisions.