The best website redesigns give a business a better-looking future while taking care of the pages, links and customer journeys that already work.

A fresh design can make your business feel more confident overnight. A relaunch can also remove a useful service page, break an old link or leave a search-engine setting switched off. Those details deserve a place in the brief before the new homepage is approved.

If you are researching how to redesign a website without losing SEO, start with a realistic goal: reduce avoidable risk and make problems easier to detect. No agency can promise that rankings or traffic will remain unchanged. Search visibility can fluctuate during a move, even when the work is carefully planned.

This checklist is designed for Australian business owners planning a redesign, a platform change or a move to a new domain. It explains what to preserve, what to ask your team for and what to verify after launch.

In this guide

• Define what is changing

• Save the baseline

• Protect useful content

• Map the URLs

• Test the new site

• Launch with a plan

• Monitor and investigate

1. Be precise about what is changing

“New website” can describe several different projects. Replacing colours and page layouts is different from moving platforms. Moving to a new domain adds another layer. Combining all three can make a later problem harder to diagnose.

Write down whether the project changes your domain, hosting, CMS, URL structure, page content, navigation or measurement setup. Then ask which changes are necessary for the business goal and which can wait.

Google’s site-move guidance recommends changing one thing at a time where possible. Its hosting-move guidance covers the separate case where public URLs stay the same.

Different kinds of relaunch need different checks. A platform change does not automatically require new public URLs.

Ask for: a one-page scope listing the changes, the person responsible for each and the evidence needed before launch. This is easier to approve than a vague promise that “SEO is included”.

2. Save a baseline before the old site disappears

Before you judge the new design, record what the current site does. Start with the pages that bring relevant visitors and enquiries, then look at the questions and searches that lead people there.

Google Search Console provides search-performance and indexing information. Combine it with your analytics and enquiry records. Search clicks, website sessions and qualified leads are different measures; keeping them separate makes later changes easier to interpret.

• Page inventory: all indexable pages, campaign landing pages, important PDFs and image URLs.

• Search baseline: clicks and impressions by page and query, with a comparable historical period.

• Business baseline: enquiries, bookings or purchases, including the forms and phone links that record them.

• Technical baseline: titles, main headings, canonicals, redirects, indexability and response codes.

• Recovery materials: a usable backup or export and a record of the current hosting and domain setup.

Choose a comparison period that reflects your business. A seasonal tourism operator needs a different reference from a firm with a steady weekly enquiry pattern. Record major campaign changes so they do not get mistaken for a redesign effect.

Ask for: an exported baseline you can retain. A dashboard that vanishes when the old agency account closes is a poor handover.

3. Keep the content that earns its place

A redesign is a good opportunity to remove repetition and improve the story. It is also easy to delete useful detail because a shorter page looks cleaner in a mock-up.

Review important pages by customer intent. What does the visitor need to know? Which examples establish credibility? Which questions prevent a qualified person from enquiring? Keep those answers in the new experience, even if the layout changes completely.

A building company might replace an overcrowded services menu with clearer categories. It should still explain the work it actually offers. A professional-services firm might combine overlapping pages, but the consolidated page needs to cover the relevant subject properly.

Navigation deserves the same attention. Google’s link guidance explains that crawlable links and descriptive link text help it discover pages and understand their context. Make sure important services remain linked from relevant pages, rather than becoming beautiful pages with no route to them.

Ask for: a keep, improve, merge or retire decision for each meaningful page. Base the decision on usefulness and evidence, rather than traffic alone. Some low-traffic pages answer an important buying question.

4. Give every changed URL an intentional destination

If a useful URL can stay the same, keeping it avoids an unnecessary move. Where the address must change, decide the destination before launch.

A redirect map is a simple working document: old URL, intended new URL, action, reason, owner and test result. It should cover more than the pages listed in your main navigation. Include URLs found through analytics, links, sitemaps and your CMS.

Illustrative URL decisions. These are hypothetical paths, not changes proposed for the live Creato website.

Google recommends permanent server-side redirects for permanent moves where possible. A 301 or 308 is a signal that an address has moved; it is not a promise that an unrelated replacement will inherit the old page’s performance.

Send a moved page to its closest relevant replacement in one step. Do not route every old page to the homepage. If there is no suitable replacement, a genuine 404 or 410 can be appropriate. Google’s HTTP status-code documentation explains how these responses are handled.

Two current platform examples

Framer’s redirect documentation shows how old paths can be routed to new destinations. Webflow’s redirect documentation covers 301 rules and CSV import and export. These are implementation tools. Your team still has to choose the right destinations and test the published result.

If the old domain is being retired, confirm who will keep it registered and maintain its redirects. Google generally recommends retaining redirects for at least a year; useful old links may justify keeping them longer. Update your own internal links to the final addresses so visitors do not need the extra hop.

Ask for: the full redirect map and a test report. Check high-value pages individually as well as testing the complete list.

5. Test the staging site as a working website

A visual review catches awkward spacing and broken images. It will not necessarily catch the settings that stop a page appearing in search, or a form that appears successful but never reaches the team.

Protect the staging environment appropriately. A development site may use authentication, indexing controls or both. Know which protections must remain on staging and which must be removed from the public site at launch.

There is an important distinction here: Google must be able to crawl a page to see a noindex instruction. Blocking crawling in robots.txt is not the same as keeping a URL out of search, and neither is a substitute for access control over private material.

Check the parts that templates can quietly change

• Indexability: key public pages must not inherit a staging-only noindex instruction or inappropriate crawl block.

• Canonicals: inspect the rendered page and source to confirm the preferred URL uses the public domain and intended path.

• Content: check page titles, headings, body copy, useful image descriptions and relevant structured data.

• Links: test navigation, contextual links, downloads and important campaign destinations.

• Conversions: complete a test enquiry or booking and confirm the receiving workflow with the team.

• Measurement: verify relevant events and consent behaviour, avoiding duplicate tags.

A canonical helps indicate the preferred version of duplicate content. It is not a redirect and it is not a guaranteed instruction: Google can choose a different canonical. Align the public URL, internal links, sitemap and canonical rather than asking one setting to compensate for contradictions elsewhere.

Test representative pages on a phone

Test a service page, an article, a case study, a contact page and any important ecommerce or booking flow. Include the longest heading, a dense comparison and a page with several images. The simplest page in the collection rarely exposes every template problem.

Measure loading, responsiveness and layout stability using the Core Web Vitals framework. A new site may not have enough real-user data immediately, so use lab tests to find issues and monitor field data as it becomes available. Google also makes clear that good page-experience scores do not guarantee top rankings.

Ask for: a signed-off test list with the actual page URLs, devices or viewport sizes, results and unresolved issues. Separate a launch blocker from an improvement that can safely follow.

6. Make launch a controlled handover

Pick a time when the people responsible for the website, domain and enquiries are available. Leave enough time to investigate a problem. A late Friday switch can be a poor choice if nobody can fix a broken form until Monday.

Agree on what would trigger a rollback or emergency fix: for example, widespread failed pages, unusable checkout or a missing enquiry workflow. Record who can make that decision and how the old version can be restored. Changing DNS is not a rollback plan on its own.

Once the new site is public, repeat the critical checks against the actual domain. Test the homepage, important service pages, old URLs, form delivery and analytics. A successful preview does not prove the production configuration is identical.

Submit an up-to-date sitemap containing the intended public URLs. A sitemap helps discovery; it does not guarantee that each page will be indexed. Use Search Console’s Change of Address tool for an eligible domain or subdomain move, not for a same-domain design refresh or ordinary path changes.

Ask for: a launch record with the time, the release version, the checks completed and the person watching for issues.

7. Monitor the pages, not just the headline traffic

After launch, look for patterns. A total traffic number can hide a broken service page if another page is gaining visitors. Compare the pages that mattered before the redesign and make sure the new equivalents are discoverable, usable and receiving the right enquiries.

Start with immediate technical checks, then review indexing and performance as enough data accumulates. The useful cadence depends on your site’s traffic, the scale of the move and the consequences of a fault. Agree on who owns this period rather than assuming the job ends when the new design appears.

Google’s published example of the 24-hour Search Console view, introduced in December 2024. Recent data can be preliminary; use it alongside longer comparisons. Source: Google Search Central, CC BY 4.0. Unmodified official example, not Creato or client performance.

A page-level comparison can help isolate where a change occurred. Source: Google Search Central’s traffic-drop guide, CC BY 4.0. Unmodified official example, not a result from a Creato project.

If traffic drops, investigate before making another big change

First separate a measurement problem from a search problem. If analytics falls while Search Console clicks remain similar, check the tracking setup and consent changes. If a specific page loses visibility, inspect its status, redirect destination, indexability, canonical, content and internal links.

Also consider demand and the wider search environment. Google’s troubleshooting guidance covers technical issues, seasonality, algorithmic changes and other possible causes. A decline after launch deserves investigation, but timing alone does not establish the cause.

Fix clear faults promptly. Avoid changing titles, URLs and page content repeatedly in response to a few hours of noisy data. Keep a change log so your team knows which intervention happened when.

The questions to put in your redesign brief

• Which current pages and customer journeys will we preserve?

• Which URLs will change, and who owns the redirect map?

• Who will test indexability, canonicals, forms and measurement?

• What are the launch blockers and the recovery plan?

• Who maintains the old domain or hosting while it is still needed?

• What monitoring and fixes are included after launch?

• Which exports, accounts and documentation will we receive at handover?

Use our website design brief template to turn those questions into a project scope. For a broader pre-launch review, see the web design checklist.

Frequently asked questions

Can I redesign my website without losing Google rankings?

You can reduce avoidable risk by preserving useful content, testing the new site and managing URL changes carefully. Rankings can still fluctuate. Treat a guarantee of zero loss with caution.

Do I need redirects if the URLs stay the same?

Not simply because the design changed. Check that the same public URLs still serve the intended pages. Existing redirects and domain variants still need testing, especially when the platform or hosting changes.

Should I change every URL to make it cleaner?

Only when there is a worthwhile reason. A cosmetic tidy-up creates extra work and risk if useful addresses already exist. Where a change is necessary, map it to a relevant destination and verify the result.

How long should post-launch monitoring last?

There is no reliable universal deadline. Continue until critical issues are resolved and you have enough indexing, traffic and enquiry evidence to assess the move. A large or low-traffic site can need a different review period from a small, busy site.

Will a relaunch also affect AI search visibility?

It can change the content and URLs available to search and retrieval systems. Preserve useful, accessible information and check the technical foundations. For more detail, see our technical AEO and GEO guide. That is a separate measurement question from guaranteeing a particular AI recommendation.

Plan the new design and the transition together

Your new website should feel like progress from the first visit. The work behind the launch should be just as deliberate: protect useful pages, make changes traceable and check that customers can still find their way to you.

Explore Creato’s web design services in Sydney and website design across Australia. If search visibility is part of the brief, our AEO and GEO services can be discussed alongside the redesign. Tell us what you are planning.