WEBSITE REDESIGN / PROTECT EXISTING SEARCH VALUE
How to Redesign a Website Without Losing Google Rankings
A redesign can improve the brand, conversion path and WordPress experience without treating the existing website as disposable. The safest projects identify which URLs, content, links and search signals already carry value, then deliberately decide what stays, what changes and where every retired URL should go.
THE SHORT ANSWER
You cannot promise zero ranking movement during a redesign, but you can remove most avoidable causes of search loss.
The biggest risks usually come from deleting useful pages, changing URLs without relevant permanent redirects, weakening content, breaking internal links, leaving staging noindex rules on the live site, changing canonicals incorrectly or launching without monitoring. Google advises mapping old URLs to their new equivalents, using server-side permanent redirects where URLs change, updating internal links and sitemaps, and watching Search Console while the move is processed.
The redesign should improve what customers see without making search engines relearn everything your existing website already proved.
A common redesign mistake is to begin with a blank canvas. The team creates a new sitemap, rewrites every page, changes URL slugs and removes old sections because they no longer fit the visual concept. Only near launch does someone ask whether the old URLs had rankings, backlinks or enquiries attached to them.
By then the new architecture may already depend on decisions that are expensive to reverse. SEO preservation therefore belongs at the start of the redesign. The old website is evidence: it shows which pages attract demand, which topics Google already associates with the business and which external links have accumulated over time.
That does not mean freezing an outdated site forever. Weak pages can be consolidated, obsolete content can disappear and URLs can change when there is a real reason. The important part is making those changes with a map of what exists and a clear destination for anything that already has value.
01 / AUDIT BEFORE YOU REDESIGN
Find out which parts of the current website are already doing useful work
The old site may be visually dated and still contain pages you should not casually throw away.
Organic landing pages
Use Search Console and analytics to identify URLs that already receive search impressions, clicks or meaningful visits. A redesign should know why those pages work before replacing them.
Protect proven entry pointsPages that earn enquiries or sales
A modest traffic page can still be commercially important if the visitors arrive with strong intent. Conversion value should be considered alongside raw traffic.
Protect commercial valueURLs with external links
Pages referenced by partners, directories, publications or other websites carry relationship and discovery value. Preserve them or redirect them to the most relevant replacement.
Protect earned referencesContent that answers real questions
A page can deserve preservation because customers use it, sales teams share it or it removes an objection — even when it is not a top search landing page.
Protect customer utility02 / BUILD THE OLD-TO-NEW URL MAP
Every meaningful current URL should have a deliberate outcome before launch
Do not wait until launch night to decide what happens to the old sitemap.
Keep strong URLs stable where practical
If the page purpose is still the same and the current URL is clean, retaining it removes migration complexity and preserves continuity.
Map genuine replacements one-to-one
When a URL changes, redirect the old page to the closest relevant new page that serves the same customer need.
Consolidate overlapping pages carefully
If several weak pages are being merged into one stronger page, make sure the destination genuinely covers the old intent before redirecting them there.
Let obsolete content return the right outcome
Not every deleted page needs a redirect. If there is no useful replacement, an honest 404 or 410 can be better than sending unrelated URLs to the homepage.
Include media and important assets where needed
If externally linked documents, images or downloads are moving, include them in the migration inventory instead of auditing only HTML pages.
Save the mapping for post-launch checks
The redirect map becomes a launch test list and a reference when Search Console reports old URLs after the new site is live.
03 / REDESIGN THE CONTENT WITH INTENT
A new visual system should not accidentally make the useful content thinner
Search visibility can drop when a redesign keeps the URL but removes the substance that made the page relevant.
Identify the page’s real job
Understand the query, service, customer decision and next action the current page serves before deciding what the redesigned version needs to retain.
Keep distinctive proof
Case studies, project examples, service detail, team expertise, FAQs and local evidence are often more valuable than decorative copy. Carry forward what helps a customer choose you.
Improve hierarchy instead of deleting depth
Good design can make a detailed page easier to scan through headings, cards, accordions and visual grouping without reducing the answer to a few marketing sentences.
Consolidate only when the customer journey improves
Merge pages when they genuinely overlap. Do not collapse several distinct services into one page just because the new navigation has fewer menu items.
Write new content where the old site has a gap
A redesign is a good time to add missing service, pricing, process or proof content when that information helps both customers and search engines understand the offer.
04 / REDIRECTS NEED RELEVANCE
A permanent redirect should take the visitor to the page they would reasonably expect to see
Google recommends server-side permanent redirects for moved URLs and warns against sending many unrelated old pages to one irrelevant destination.
Use 301 or 308 for permanent moves
When a page has permanently moved to a relevant replacement, a server-side permanent redirect tells browsers and search engines that the new URL should take over.
Permanent moveAvoid redirect chains
Old URL → previous redesign URL → current URL adds delay and makes migrations harder to reason about. Point old addresses directly to the final destination wherever possible.
Old → finalDo not redirect everything to home
The homepage is rarely a relevant replacement for a detailed service, guide or location page. Irrelevant bulk redirects can confuse users and may be treated like soft 404s.
Match the old intentKeep redirects long enough
Google recommends keeping redirects in place for at least a year, and from a user perspective useful legacy redirects can remain longer when old links still exist in the world.
Preserve old links05 / UPDATE THE SIGNALS THAT POINT TO THE NEW SITE
Redirects are only one part of the migration — the new website should reference its own final URLs everywhere
A clean launch gives search engines consistent signals instead of asking them to reconcile old links, staging settings and conflicting canonicals.
Update internal links so menus, buttons, breadcrumbs, related-content modules and body copy point directly to the final URLs rather than depending on redirects. This improves both the customer journey and the clarity of the new site architecture.
Check canonical tags, XML sitemaps and any hreflang annotations where relevant. Each live indexable page should use the intended canonical URL, and the sitemap should list the new canonical addresses you actually want discovered.
Staging environments are commonly protected with noindex or access controls. Before launch, verify that those staging protections have not followed the new website onto the live domain. Also confirm that robots.txt is not blocking sections that should be crawled.
06 / TEST THE REDESIGN BEFORE SEARCH ENGINES HAVE TO
Crawl the staging build, test the redirects and complete the customer journeys before the domain switches over
A migration checklist should find broken relationships while the old site is still available as a reference.
Crawl the staging site
Look for broken internal links, missing titles, duplicate metadata, incorrect canonicals, orphaned pages and unexpected status codes before launch.
Test the redirect map
Run the known old URLs against the planned rules and verify they land on the correct final destination without loops or unnecessary chains.
Compare high-value pages
Check the old and new versions of important organic and conversion pages side by side so useful sections, proof and calls to action have not vanished accidentally.
Test forms, checkout and tracking
A redesign is not successful if the search traffic arrives but the new enquiry, booking or ecommerce journey fails after the click.
Check responsive behaviour
Test the redesigned templates on phones and tablets, especially menus, sticky elements, forms and interactive components that can change the layout.
Record the pre-launch baseline
Save key traffic, landing-page, ranking and conversion data so post-launch changes can be compared against a real baseline instead of memory.
07 / PERTH BUSINESS CONTEXT
A redesign should preserve the markets and services your current site already connects with — then improve how those customers move through the new one
Local visibility is part of the migration when existing Perth service and location pages already attract useful search demand.
A Joondalup service page, Fremantle hospitality guide or Osborne Park B2B landing page may each have accumulated different search history, links and customer behaviour. Renaming or removing those URLs because the new navigation looks cleaner can discard useful local context unless the replacement architecture has been planned properly.
We treat service intent as the primary structure and keep location content where it has a real purpose. If a location page remains useful, its local proof and internal links should migrate with it. If several thin suburb pages are being consolidated, the redirect destination should genuinely answer the old need rather than simply being the nearest geographic page.
Perth CBDSubiacoFremantleJoondalupOsborne ParkWannerooMidlandCanningtonRockingham
08 / DO NOT COMBINE EVERY HIGH-RISK CHANGE IF YOU DO NOT HAVE TO
A redesign is already a major change — changing the domain, CMS, URLs and content strategy at the same moment makes problems harder to diagnose
When the project allows it, separate major changes so the business can understand what caused an unexpected movement.
REDUCE MIGRATION VARIABLESIf the domain does not need to change, keep it. If a strong URL does not need to change, keep it. Spend the redesign budget on changes that improve the customer experience or business result.
Google’s site-move guidance recommends changing one major thing at a time where practical. The goal is not to avoid improvement; it is to stop the project creating technical migration risk without a corresponding customer or commercial benefit.
09 / LAUNCH DAY SHOULD BE A CONTROLLED CHANGE
The launch sequence should make the new site reachable, indexable and measurable in the same window
A visually successful deployment can still create search problems if the migration signals are switched on in the wrong order.
Deploy the final tested build
Move the approved website to production and confirm the live domain resolves correctly over HTTPS.
Activate and test redirects
Check a sample from every important URL group, including top organic pages, old campaigns, service pages and any URLs with external links.
Verify indexation signals
Confirm robots, noindex, canonicals and the XML sitemap match the production plan rather than the staging environment.
Submit the new sitemap
Use Search Console to help Google discover the new canonical URLs and monitor how the migration is processed.
Test analytics and conversion actions
Complete real form, phone, booking or ecommerce journeys and confirm the measurement setup is receiving data from the live site.
10 / THE REDESIGN IS NOT FINISHED WHEN DNS CHANGES
Watch the new site closely while customers and search engines move from the old URLs to the new ones
Some fluctuation can happen while Google recrawls and reindexes a significant move. Monitoring helps separate normal transition from a real migration fault.
Search Console coverage and indexing
Watch for spikes in not-found URLs, unexpected noindex pages, canonical differences and important pages that are not being indexed as expected.
Find crawl/index issuesOrganic landing-page traffic
Compare important page groups against the pre-launch baseline. A drop concentrated in one section often points to a migration issue that a site-wide total can hide.
Find affected templatesRedirect logs and 404s
Review old URLs customers or crawlers still request. Missing redirects can often be repaired quickly when you know which paths are actually being hit.
Repair missed pathsEnquiries and ecommerce actions
Ranking preservation has little value if the redesigned form, booking or checkout performs worse. Monitor conversion quality alongside search visibility.
Protect the business resultWEBSITE REDESIGN + SEO FAQS
Questions businesses usually ask before replacing a website that already has search visibility
A redesign can be ambitious without being careless. These answers focus on what deserves protection and what can safely change.
06 QUESTIONS
Clear answers to the decisions that usually affect cost, scope and ownership.
ANSWER
A redesign can cause temporary movement while Google recrawls and processes changed pages, and there is no honest guarantee that rankings will remain identical. The avoidable risk comes from losing useful content, changing URLs without relevant redirects, breaking internal links or launching with incorrect technical signals. A migration plan reduces those risks substantially.
ANSWER
Keep strong, clean URLs when the page purpose is still the same and there is no business reason to change them. Fewer unnecessary URL changes mean fewer redirects and less migration complexity. Change a URL when the new architecture genuinely improves the site, then map the old address to the correct replacement.
ANSWER
Google states that 301 and other permanent redirects do not cause a loss of PageRank. The bigger practical risks are irrelevant destinations, redirect chains, missing mappings and weakened replacement content. Use permanent server-side redirects to the closest relevant final URL and update your own internal links directly.
ANSWER
Yes, when the content is obsolete, duplicated or no longer serves the business. First check whether the page has traffic, links, rankings or a useful customer role. If there is a genuine replacement, redirect it there. If there is no relevant destination, returning a proper not-found response can be more honest than redirecting it to an unrelated page.
ANSWER
Google recommends keeping redirects for as long as possible and generally at least one year so signals can transfer as old URLs are recrawled. From a customer perspective, useful redirects can remain longer because old bookmarks and external links may continue sending people to those addresses.
ANSWER
Watch Search Console indexing and crawl reports, organic landing-page traffic, important queries, 404s, redirect behaviour, conversion tracking and real customer actions such as enquiries or checkout. Compare those against a pre-launch baseline so you can tell a normal transition from a specific migration problem.
PLANNING A REDESIGN ON A WEBSITE THAT ALREADY HAS HISTORY?
Show us the current site before anything is removed — we will map the URLs, content, search signals and customer journeys that deserve protection, then rebuild around a stronger WordPress experience.
Share your existing website, the pages or services that matter most, any known rankings and what you want the redesign to improve. We can scope the redesign and migration together so visual improvement does not come at the expense of search visibility or enquiry flow.