A website relaunch without unnecessary SEO risk: URL planning, redirects and acceptance testing

First preserve what already serves a purpose

Begin the relaunch with an inventory, not colour selection. List existing service pages, guides, downloads and contact routes. Ask sales about frequently shared links and documents. A page can matter even if it receives little organic traffic: it may be used regularly in quotations or personal emails.

For each important page, record its purpose, owner and planned treatment. Good content can be revised but should not disappear accidentally. Also preserve baseline search-traffic figures and enquiries actually received. Document current campaigns, seasonality and changes to the offer so later comparisons are not based on false assumptions.

Change addresses for a clear reason

A new design does not automatically require new URLs. If an address remains understandable and leads to the same content, it can remain. A new structure may be useful but should deliver a recognisable improvement for people. Decide deliberately which content will be combined, split or genuinely discontinued.

When making changes, create a table containing the old address, new destination and substantive reason. When pages are combined, the destination must still answer the original question meaningfully. Redirecting a former assembly guide to the general homepage is of little help to people who need that guide. Discontinued content needs a considered solution rather than a blanket redirect.

Test redirects against a clear list of expected outcomes

For permanently changed addresses, the technical implementation sets up suitable server-side redirects. Check every important old address and the destination actually reached. Prefer the direct route to the final content and update internal links to the new address. Visitors and systems then avoid unnecessary journeys through old intermediate destinations.

Content review matters as much as technical testing. Open the destination as someone who saved an old link would: is the service still recognisable? Do images, documents and contact options work? Keep the checklist for later changes. It is a useful operational document, not a file that should disappear after launch.

Approval needs technical and substantive criteria

Choose a time when the responsible people are actually available. Keep the previous state and an agreed rollback route ready in case central functions fail. Define which faults prevent launch: an inaccessible contact form, incorrect order prices or a public website accidentally blocked, for example. Small design details have a different priority.

1. Public pages are accessible; protections from the test environment have been specifically checked.
2. Page titles, canonical addresses, sitemap and internal links match the approved structure.
3. Images, downloads and important old URLs have been checked.
4. Forms work on smartphones and desktops, including receipt.
5. Measurement and consent have been tested in the intended states.
6. Responsibilities, launch time and rollback route are documented.

Have someone test who has not seen the design every day. That person often finds unclear terms or missing orientation that seem familiar to the project team. Do not confuse publication with acceptance: the agreed criteria must also be satisfied at the actual public address.

After launch, examine errors first and trends afterwards

Immediately after publication, check availability, important old links and receipt of genuine enquiries. Technical failures do not need weeks of observation. For search trends, however, compare suitable periods and page groups. Distinguish a general decline in demand from problems with particular migrated content.

Search Console's performance report lets you examine affected pages and queries separately. Add qualified enquiries from your business to this perspective. A decline in irrelevant visits may be less problematic than one main service that no longer works. New search positions immediately after launch are also not a reliable verdict on the entire project.

Combine a clear website scope with sensible ongoing development

Bissolux offers business websites with up to five content pages and SEO basics. For ongoing development, an SEO package covers one website, one language and one target market with a limited scope for analysis, content and implementation. This lets you deliberately plan design and continuing improvements.

View the appropriate services and discuss your existing site before commissioning work. Extensive migration, additional programming or a large redirect plan is not automatically included in the starter scope. Hosting, the domain, licences and work outside the agreed allowance are handled separately. Neither a relaunch nor an SEO package guarantees particular rankings. View Bissolux web design with a clearly defined scope ↗

Your decision in practical steps

1. Recorded important URLs, content and baseline figures
2. Made substantive decisions on retaining, combining and removing content
3. Mapped old and new addresses traceably
4. Checked redirects, forms and approval for public access
5. Assigned responsibilities and an observation plan after launch

Frequently asked questions