Changing page addresses can leave customers with broken bookmarks and links. Use website redirects to send each old address to its closest relevant new page, then test the paths before and after launch.
For a small business replacing an existing site, the safest approach is usually a page-by-page redirect plan, not a blanket redirect to the home page. You can prepare the page list and choose destinations yourself; a developer or hosting provider can implement the rules and help test them.
Choose website redirects page by page
A redirect tells a browser that a requested address has moved and sends the visitor to another address. A 301 redirect indicates a permanent move. It’s generally the appropriate choice when an old page is being replaced at a new address and you don’t intend to bring the old address back.
Match each old page to the new page that best answers the same need. An old service page should lead to the corresponding service page, for example, rather than to the home page. This helps people who arrive through bookmarks, search results, and links on other sites find what they expected.
If a service has been discontinued, don’t send visitors to an unrelated service just to avoid an error page. Send them to a genuinely useful replacement if one exists. Otherwise, let the old URL return a clear 404 page, or a 410 response if the removal is permanent and your platform supports it. A 404 or 410 means the page is unavailable; a helpful error page can offer a search box or links to relevant areas.
Temporary changes need different treatment. A 302 redirect signals a temporary move, such as a page being unavailable for a short period. Agree on an owner and a date to review temporary rules so they don’t become an accidental permanent arrangement.
Build a useful redirect map
Start with a list of existing URLs, not just the pages in your new site menu. Old campaign pages, downloadable files, and pages omitted from the redesign can still have visitors. Export a page list from your content management system if possible, then check your sitemap, analytics, and known inbound links for addresses the export missed.
Create a spreadsheet with one row per old URL and these fields:
- Old address: Record the full URL, including the path and any trailing slash.
- Destination: Enter the full new URL, or mark the page for a 404 or 410 response.
- Reason: Note the matching service, replacement content, or reason for removal.
- Status: Record whether the rule is planned, implemented, and tested.
- Owner: Name the person who can resolve questions about the content.
Include addresses that have changed only slightly. A move from /services/design to /web-design/ still needs a plan. Treat uppercase letters and trailing slashes as potentially different until your developer confirms how the server handles them.
Prioritize pages with bookings, purchases, contact details, or important outside links. Analytics can help identify visited pages, but it won’t reveal every bookmark or offline reference. Ask staff who handle customer inquiries about addresses printed on materials or shared regularly.
Match the implementation to your site
Website redirects can be set at the hosting or server level, through a content management system, or with a plugin. Choose one primary place to manage them and document any exceptions. Rules scattered across several systems are harder to debug, especially when one rule sends a visitor through another.
For WordPress, Redirection and Yoast SEO are common plugins to consider; check the provider’s current documentation for available redirect features. In the chosen tool, confirm the source address, destination address, and redirect type before saving. Avoid creating the same rule in a plugin and at the server level unless your developer has a specific reason.
The following is an illustrative Apache configuration for two permanent moves. A developer should confirm that the site uses Apache, that mod_alias is available, and that the host permits these rules in the selected configuration file. Replace the example addresses with the approved destinations.
# Permanent page moves
# Replace example.com with the live domain
Redirect 301 /old-design https://example.com/web-design/
Redirect 301 /old-contact https://example.com/contact/
# Keep rules with the site's server configuration
# Test each old address after deployment
These examples are not a complete site migration configuration. Server rules can interact with existing rules, and a different host or server may require a different format. If you can’t identify the server or rollback method, hand the map to a developer rather than editing configuration files yourself.
Test redirects before and after launch
Use a staging copy to catch mistakes before customers encounter them. The website staging process also gives you a place to check that destination pages exist and work before the new site replaces the old one. Confirm with your developer that the staging environment can reproduce the live redirect behavior; hosting and domain differences can affect the result.
For each priority URL, follow this test sequence:
- Open the old address and confirm it reaches the intended new page, not just any working page.
- Check the response with a browser’s developer tools or a redirect-checking tool. Confirm that a permanent move returns a 301 before the destination loads.
- Check that the destination returns a successful response and that its main action, such as a contact form, works.
- Check for chains, where one redirect leads to another, and loops, where rules send the browser back and forth. Update the first rule to point directly to the final page.
- Repeat the checks on the live domain after launch, including both mobile and desktop visits for key pages.
Browser caching can make a changed redirect appear unchanged. Use a fresh private browsing session or a response-checking tool, and ask the developer to inspect any server or caching layer if results differ. Record the actual result in the map rather than relying on a visual spot check.
Walk through a service page move
Suppose a business replaces /old-design with /web-design/. The owner checks that the new page describes the same service and includes the current contact route. The map records the old address, the new address, and a permanent move. The developer then adds one 301 rule in the agreed management system.
On staging, the owner opens the old address and checks the final page. The developer checks the response sequence and finds that an existing rule first sends the request to an intermediate address. The developer changes the rule so the old address points directly to /web-design/, then tests again.
After launch, they repeat the test on the live domain and check the contact form. If the old page had instead described a discontinued service with no suitable replacement, they would leave it unavailable with a useful error page rather than send people to an unrelated offer.
Keep old addresses under review
Redirects need an owner after launch. Check server logs or available site reports for requests to missing pages, then investigate addresses that customers or partners still use. A missing-page report is a prompt to inspect the request, not a reason to redirect every unfamiliar address.
Keep a copy of the map with the site’s launch records. Before removing a rule later, check whether the old address still receives legitimate traffic and whether outside references can be updated. There’s no single retention period that fits every site; the decision depends on how the address is used and what happens if it stops working.
Frequently Asked Questions
Treat them as potentially different URLs until your developer confirms how the server handles case and trailing slashes, then include the necessary variants in your redirect tests.
Ask your developer to check differences in hosting, domains, server rules, and caching layers, then test the redirect on the live domain after deployment.
Compare the export with your sitemap, analytics, known inbound links, and addresses staff know from customer inquiries or printed materials.
Check whether the old address still receives legitimate traffic and whether outside references can be updated; the article gives no single retention period for every site.
Do not use the Apache example as a complete configuration. Ask a developer to confirm the server, supported rule format, and rollback method before implementation.
Final Verdict
Businesses changing established page addresses should prepare a redirect map before launch and send each old page to its closest useful replacement. Skip the blanket home-page redirect, and leave truly obsolete pages unavailable when no relevant destination exists. Start today by listing your highest-value old URLs and assigning a proposed destination to each. Give the map to the person responsible for implementation, then test the live results together.
Ready to grow your online presence?
Let's build a smarter strategy for your website and business.
Let's talk about your project
