A guide to changing an existing website

Tradie website redesign checklist: plan the change

By Asier Mugica ·

Keep the pages and contact routes that work. Use this tradie website redesign checklist to agree what changes, map moved URLs and check the live release. Consider a rebuild when a smaller change cannot meet the requirement within an agreed scope. A new design does not by itself require a new domain.

For a Australian trade business changing an existing website with a builder. The AskMagno example is a check on our own site, not evidence of a client SEO result.

Websites for Australian tradies

Choose the scope before the design

Write a requirement you can check: a customer can find the hot-water service and send an enquiry from their phone; the team can update opening hours without breaking the page. “Make it modern” leaves too much undecided.

A content correction, a clearer service page or a repaired form may be enough. A rebuild can make sense when the current system prevents essential changes, or when fixing several connected problems would be harder to maintain than replacing the affected parts. Ask the builder to show that limitation and compare the scope of both options.

If the only evidence is a quiet inbox, start with the website enquiry diagnosis. It separates search visibility, contact delivery and follow-up. No enquiries by itself does not establish that the website needs rebuilding.

Save the pages and evidence you already have

Before the old site disappears, list its page addresses and the job each page does. Include service pages, project pages and useful downloads. Save the approved words and photos you intend to keep. A screenshot helps with appearance; it does not preserve the content or the settings behind a form.

Where you have access, export search queries and landing pages from Search Console with the reporting dates and country filters. Record genuine received enquiries separately from phone-button taps or form confirmations. Ask the person who answers them which became suitable jobs. Keep identifiable customer details out of analytics events.

Use the same definitions after launch. If there is no reliable history, record that gap and begin measuring now. A missing report is not a zero, and a new design cannot create a trustworthy before-and-after comparison retrospectively.

Confirm who controls the domain and contact systems

Before choosing a launch date, identify the owner of the domain account, the website hosting and the business email service. Include the people responsible for enquiry notifications, bookings and measurement. Confirm that each can carry out their part of the change; do not leave access recovery until launch day.

Ask for a record of the current setup and a way to restore the working site if the release fails. Give the email provider a chance to check any proposed domain or DNS changes. Share account access through the provider’s authorised process rather than sending passwords around in a project email.

A new design can keep the same domain and page addresses. A change of hosting also has its own checks: Google’s hosting-move guidance covers testing the new infrastructure and monitoring the change. The builder should tell you which kind of move is actually required.

Decide what happens to each existing URL

For every existing page, record its purpose, the evidence you have, the decision and the final destination. Keep a useful address when its purpose stays the same. If content is combined, check that the replacement really covers what the old pages offered. Record who approved each decision.

For a permanent move, ask for a direct server redirect to the relevant replacement. Google recommends permanent redirects such as 301 or 308 where possible. Its site-move guide warns against sending many old pages to an irrelevant homepage. If a page is removed with no suitable replacement, a genuine 404 or 410 response can be the right outcome.

Here is a small check from our own site, made on 10 November 2026. We requested the old address, recorded its redirect and then requested the destination separately. Both destinations returned 200, a successful HTTP response. This checks those routes; it does not prove retained rankings or enquiry delivery, and it does not validate every legacy redirect on our site.

Two AskMagno routes checked on 10 November 2026
Old address on askmagno.comDestinationObserved result
/contact/au/contact301 redirect; destination 200
/about/au/about301 redirect; destination 200

Review the preview before switching traffic

Review the actual release you intend to publish. Check service wording, genuine coverage, approved photos and the destination of each main action on a phone. A placeholder licence number or a stock review is not ready for launch. Ask what remains incomplete and who will resolve it.

Keep confidential previews access controlled. For a preview that is publicly reachable, agree how it will stay out of search. Google explains that a noindex rule must be accessible to its crawler to be read; blocking the page in robots.txt alone does not guarantee exclusion from search. Noindex is not a privacy control.

At launch, remove temporary indexing blocks from the pages meant to be public. Keep the intended restrictions on private pages. Check the published domain as well as the preview: the configuration can differ.

Make the launch checks part of the handover

Agree who can publish, who can restore the previous version and how the owner will be told the checks are complete. Where practical, separate a redesign from an unnecessary domain change or platform move. Google recommends changing one thing at a time in its site-move guidance.

Ask for the results below on the live domain. A menu click tests one path; it leaves bookmarked or externally linked old addresses untested.

  1. Open the agreed public pages and a sample of important old addresses. Check the final content and record the HTTP result, including redirects and genuine missing pages.
  2. Confirm that public pages can be crawled and are eligible for indexing, their canonical addresses point to the intended version, and the sitemap and internal links use the final URLs.
  3. Test the contact route with the person who receives enquiries. Coordinate and label any message as a test, verify receipt, and exclude it from genuine enquiry totals. Check phone and booking links too; do not create an unannounced customer booking.
  4. Check the agreed measurement on the live site, subject to consent. Keep customer names and message contents out of analytics. Record the release date and any changes to how an event is counted.

Follow the live site after the redesign

Keep the old-URL map available after launch. Google recommends retaining redirects for as long as possible, generally at least a year. Ask who maintains them when hosting or support changes again. A redirect that disappears with the old hosting no longer helps someone using that old link.

Monitor the intended pages in Search Console, investigate unexpected errors and compare periods with the same filters. A successful HTTP response means the server returned a page; Google explains that it does not guarantee indexing. A sitemap submission is not proof that all its pages are indexed.

Search visibility can fluctuate while Google processes significant changes. There is no fixed recovery date in this checklist and no promise of unchanged positions. Keep received enquiries, suitable enquiries and booked work separate, so an increase in a website event is not reported as an increase in customers.

Ask for a release record you can use

Keep the approval short enough to use. For each item, record the requirement, who owns it, the page or account involved, the test date and the observed result. Mark anything untested as unknown, with a named person to resolve it. A green tick without the result behind it is difficult to challenge later.

Put the approved page list and URL map beside the quote. Compare the work after launch as well as the build itself; Magno’s pricing and ownership details show how our own service is set out.

Start with the website you have

If you want to discuss the change, send me your current website and the problem you need to solve. Include any pages or enquiry routes that must keep working. We can then discuss the scope using the existing site as the starting point.

Method: prepared with AI assistance from Google documentation, Asier’s stated approach and a limited check of two AskMagno routes. Published 10 November 2026. No client migration outcome has been measured here, and rankings are not guaranteed.