Before replacing the old website, make sure you know its content, addresses and account access. Otherwise, you might only notice after launch that an often-linked service has disappeared or an enquiry no longer reaches you.
Clarify the reason for the relaunch, too. Has your offer grown? Is the content out of date? Is the site hard to use on a phone? A relaunch is easier to plan when you know which problem it should solve.
Take stock before anything disappears
List the existing pages and important content. Include PDFs, images, contact forms and embedded services. Note what to keep, revise or retire.
- Existing URLs and page titles.
- Important search queries and pages from Search Console, if available.
- Contact methods, form destinations and responsible inboxes.
- Domain, hosting and administration access.
- Content and images, including confirmed usage rights.
- Connections to booking, shop, newsletter or other software.
Make a backup of the old website within the agreed scope. A list of login details is not a backup of the content. Confirm with the responsible person what could actually be restored later.
Decide what happens to each important page
A page does not need to disappear solely because the new navigation should be shorter. Check what questions it answers and whether customers or other websites link to it. The new structure should continue to serve those needs.
| Existing content | Decision | New destination |
|---|---|---|
| Service page for an offer that is still available | Revise or keep | The relevant new service page. |
| Two pages with substantial overlap | Combine where it makes sense | One page that serves both purposes. |
| Product no longer offered | Clarify the content and what replaces it | An accurate alternative or an appropriate error page. |
| Contact page | Check the details and responsibility | The contact section people can actually use. |
This inventory also helps if you move to a one-page site. The content is brought together, not simply removed from the navigation. The new page still needs to answer the essential questions.
Give old addresses relevant destinations
For permanent URL changes, Google recommends server-side permanent redirects such as 301 or 308. Map important old addresses to the most relevant new content. Redirecting every page to an unrelated homepage is not a sound solution.
If content has genuinely been combined on a new page, that page can be the right destination. Record the mapping in writing. Then update internal links to point directly to the new addresses.
Approval should cover how the site works
Review the content in its intended order and follow typical journeys: from a service to an enquiry, from the navigation to the address, from an article to a relevant offer. Fix missing information in the journey, not only individual sentences.
- Confirm contact methods with the people responsible for them.
- Have someone check where forms actually send their submissions.
- Account for mobile layouts and long content.
- Approve opening hours, prices and service details.
- Clarify legal copy and any required settings.
- Name a person responsible for the changeover and follow-up.
Collect feedback in one place. If several people comment, reconcile conflicting notes before handover. This keeps the approved version clear.
Settle the essentials before launch day
Confirm the domain, hosting and responsibilities before the new website goes public. Check whether email services depend on the same settings. A website change is not a reason to alter those connections as an afterthought.
The published version needs its final URLs, suitable canonical tags and an up-to-date sitemap. Make sure preview restrictions do not accidentally block the public site. This belongs in the technical handover.
Agree how to report a problem and who will handle it. A planned changeover window helps bring feedback and approvals together.
Keep an eye on important journeys after launch
With the responsible provider, check key contact methods, important old URLs and the visibility of new pages. Search Console data helps identify unexpected errors. Compare relevant periods and account for other changes in the business.
Google notes that visibility can change temporarily during a site move. A guarantee that rankings will stay exactly the same would be misleading. A traceable changeover, clear responsibilities and follow-up monitoring matter more.