There’s a scenario that plays out far too often for Brisbane businesses. The new website goes live — it looks great, the team is thrilled, and everyone’s waiting for enquiries to roll in. Instead, the phone goes quiet. Rankings that took years to build have vanished, and traffic has dropped off a cliff.
A website redesign doesn’t have to end that way. When website redesign is planned from the very beginning — not bolted on as an afterthought — you can redesign your website without losing SEO value, and often come out stronger. Losing traffic after a website redesign is almost always the result of skipped steps, not bad luck.
That said, there are no guarantees with Google. Some fluctuation during and after a launch is normal, and anyone who promises otherwise isn’t being straight with you. What you can control is how well you prepare. This guide walks through the process of redesigning sites with SEO in mind — from the pre-redesign audit and 301 redirect map through to launch day and beyond.
What Happens to Your Google Rankings When You Redesign a Website?
Why Website Redesigns Can Affect Search Rankings
Google ranks your pages using signals it has collected over time — URLs, content, internal and external links, and technical setup. A redesign can change any of them. When URLs are renamed without redirects, ranking pages are deleted, copy is trimmed, title tags are overwritten or a noindex tag is left behind from staging, Google has to re-evaluate your site with less to go on. That’s when rankings fall.
The more signals that change at once, the more disruptive the redesign. That’s not a reason to avoid redesigning — it’s a reason to manage the process with SEO services built into every stage.
Redesign vs Rebuild vs Website Migration — Understanding the Difference
A visual redesign changes how your site looks without altering URLs, content or platform. SEO risk is relatively low.
A rebuild keeps the same platform but changes the structure, page architecture and often the URLs. Risk is medium to high, depending on scope.
A website migration moves the site to a new platform, domain or server — or makes several major changes at once. It carries the highest risk, and it’s where website migration SEO becomes a discipline of its own.
How Google Recrawls and Reindexes a Redesigned Website
Google doesn’t discover your new site the moment you hit publish. Googlebot recrawls pages on its own schedule — more often for large, frequently updated sites, less often for smaller ones. After launch, it has to find your new pages, follow your redirects and work out how signals should flow through the new structure. Submitting an updated XML sitemap in Google Search Console helps, but Google still moves at its own pace.
Is Temporary Ranking Fluctuation Normal?
Yes — some movement is expected after launch while Google reassesses your site’s signals. How long that lasts depends on your site’s size, how often Google crawls it and how much has changed, so there’s no standard settling period. The key is telling temporary turbulence apart from a sustained drop caused by an SEO error — and that’s only possible if you benchmarked your rankings before launch.
Why Brisbane Businesses Can’t Afford to Lose Local Search Visibility
For service-area businesses across Brisbane, Logan, Ipswich, Moreton Bay and the Gold Coast, local search is often the main source of new enquiries. A drop in visibility for searches like “plumber Chermside” or “accountant Carindale” means lost leads for as long as it lasts. When it comes to a website redesign, Brisbane service businesses often have more to lose than they realise — local visibility is harder to rebuild than it looks, so it deserves as much protection as any technical consideration.
Signs Your Business Website Needs a Redesign
Before worrying about protecting your SEO, it’s worth confirming the redesign is warranted. The usual triggers are a dated design that no longer reflects your brand, a clunky mobile experience, slow load times, steady traffic that rarely turns into enquiries, a site that needs a developer for every small update, and services or content that no longer match what you actually offer. Outdated themes and unmaintained plugins are another — they’re a security liability as much as a design problem.
Accessibility belongs on that list too. Under the Disability Discrimination Act 1992, Australian businesses are expected not to exclude people with disability from their services — websites included — and the Web Content Accessibility Guidelines (WCAG) are the accepted benchmark.
If several of those sound familiar, a redesign is probably overdue. Many trace back to the same website design mistakes made when the original site was built, and fixing them is a chance to lift conversions, not just looks.
Types of Website Changes and Their SEO Risk
Not all redesign work carries the same risk. The table gives a realistic picture of where the danger sits and what each change needs.
| Type of Change | SEO Risk Level | Main Precautions Required |
| Visual design refresh (no URL or content changes) | Low | Crawl before and after; check Core Web Vitals and on-page elements |
| Content and page structure changes | Medium | Preserve heading structure, keyword targeting and topical coverage on key pages |
| URL structure changes | High | Build a complete 301 redirect map before launch |
| Changing your CMS or website platform | High | Migrate all metadata, test every redirect, verify tracking |
| Changing your domain name | High | Use GSC’s Change of Address tool, redirect the old domain, update key backlinks |
| Moving from HTTP to HTTPS | Low | Single sitewide HTTP-to-HTTPS 301 rule; fix mixed content; update canonicals and sitemap |
| Merging multiple websites into one | High | Redirect every legacy URL; consolidate overlapping content |
| Changing your web hosting provider | Low | Minimise downtime, confirm DNS propagation, compare speed after the move |
Platform and domain changes need the most care, so they get their own sections further down. HTTPS and hosting are covered under technical SEO.
Visual Design Refresh
A visual refresh changes colours, typography, imagery and layout while keeping your URLs, content and platform the same. It’s the lowest-risk type of redesign — but low risk isn’t no risk. New templates can quietly drop headings, tuck key content into accordions or tabs, slow pages down with heavier imagery, or stop outputting schema the old theme handled. Crawl before and after, compare the results, and test Core Web Vitals on your most important pages.
Content and Page Structure Changes
Rewriting copy, merging pages or reorganising sections changes what Google sees on each URL, even when the URLs stay put. Refreshing outdated details on a service page is low risk; rewriting your top-performing pages from scratch or folding three pages into one is not. Check which queries each page ranks for in Search Console before changing it, and make sure the new version still answers them.
URL Structure Changes
Changing URLs is where most redesign traffic losses begin. As far as Google is concerned, a changed URL is a new page that has to earn its place — unless a 301 redirect tells Google where the old one went. Small changes count too: removing a /services/ folder, switching from /blog/post-name/ to /post-name/, or dropping .html extensions all need redirects. Only change URLs when there’s a genuine structural benefit, and map every single one.
Merging Multiple Websites into One
Businesses that have accumulated separate sites — a second brand, a standalone site for one service, or a location-specific domain — often consolidate them during a redesign. Done well, merging concentrates authority on one domain. Done badly, it wipes out the rankings the smaller sites built. Every URL on every retired site needs a relevant redirect, and overlapping content should be combined into one stronger page rather than duplicated.
Setting Website Redesign Goals Without Sacrificing SEO
Defining Your Business Goals and KPIs
Every redesign should start with one question: what problem are we solving? More enquiries, a site that’s easier to manage, stronger brand positioning? Once the goal is clear, turn it into measurable KPIs — organic traffic, keyword rankings, conversion rates and Core Web Vitals — and record where each one sits today. Those baselines are how you’ll judge success, and spot problems, after launch.
Involving SEO from the Planning Stage
Good website redesign SEO can’t be retrofitted onto a completed design. By the time the new site is built, decisions about URLs, page hierarchy, content volume and technical setup have already been locked in. Designers want clean layouts, developers want efficient builds, and writers need room for the copy that earns rankings — a shared brief with SEO requirements written into it keeps everyone aligned. That’s why, at Content Authority, SEO is part of the brief from the very first planning conversation.
Deciding What Should Stay the Same
If you want to keep Google rankings after redesign work wraps up, one of the most underrated decisions is deciding what not to change. URLs that already rank, content that drives traffic, and local signals Google has already indexed should stay consistent. Change for the sake of change is expensive in SEO terms.
Planning Timelines, Budgets and Sign-Off
A rushed redesign is an SEO problem waiting to happen. Build in time for the redirect map, staging crawls, pre-launch testing and at least three months of post-launch monitoring. Then get the SEO requirements signed off as part of the project brief, so the redirect strategy and content requirements can’t be quietly dropped once the build is underway.
Conducting a Pre-Redesign SEO Audit
Benchmarking Your Traffic, Rankings and Conversions
Before anything changes, capture exactly where you stand. Google Search Console shows which pages earn impressions and clicks, the queries behind them, and any existing crawl errors. Google Analytics 4 adds sessions and conversions at page level. Export your keyword positions from Semrush, Ahrefs or Search Console’s Performance report as well. If your analytics isn’t tracking correctly, fix that first — otherwise your baseline is built on bad numbers.
Crawling Your Existing Website
A full crawl with Screaming Frog exports every URL, page title, meta description, heading, response code and internal link on your site. Archive it. It’s your complete record of the old site and the reference point for every comparison after launch.
Identifying Your Top Pages and Valuable Backlinks
A handful of pages usually drive most of your organic traffic, hold your strongest backlinks or convert best. Cross-reference GA4 and Search Console with a backlink export from Ahrefs or Semrush to find them. These URLs must be kept, or redirected to a closely matching page — losing one without a redirect throws away link equity that took years to earn.
Measuring Your Current Core Web Vitals
Record LCP, INP and CLS from PageSpeed Insights and the Core Web Vitals report in Search Console, particularly for your top pages, so you can confirm the new site matches or beats them.
Documenting Local SEO Signals
Record your NAP details (name, address and phone number) exactly as they appear on the site, along with your LocalBusiness schema, embedded maps and every suburb or location page. All of it needs to carry over precisely.
Building a Complete URL Inventory
Build your URL list from three sources — your XML sitemap, the Screaming Frog crawl and Search Console — because each catches pages the others miss. Then hunt down the URLs everyone forgets: orphan pages with no internal links, PDFs like brochures or price lists that other sites link to, images, old campaign landing pages, and parameter URLs that have ended up indexed.
Documenting Everything and Backing Up
Pull it all into a migration spreadsheet: every URL, its traffic and backlink data, its new counterpart, the redirect type and any notes. This becomes the central reference for the entire build. Then take a full backup of the existing site — files, database and configuration — so you can reference or restore it if anything goes wrong.
A thorough digital marketing audit at this stage gives you everything you need to make the redesign measurably safer.
Planning Your New Website Architecture
Keeping Existing URLs Where Possible
The simplest way to protect your rankings is to leave URLs alone. If /services/commercial-cleaning/ already ranks, renaming it /services/commercial-cleaning-brisbane/ adds risk without adding value.
Creating a Logical Hierarchy, Navigation and Breadcrumbs
Your structure should reflect how customers and Google navigate your content: top-level pages for major service categories, with supporting pages nested beneath. Your main navigation passes the most internal link equity, so priority pages belong there. Breadcrumbs reinforce the hierarchy for Google and can be marked up with schema.
Structuring Service and Location Pages
For businesses serving multiple suburbs, location pages are a cornerstone of local SEO. Keep them in a consistent hierarchy — for example, /locations/brisbane-cbd/, /locations/chermside/ and /locations/springfield/ — and link each one back to your core service pages.
Mapping Your Internal Linking Structure
Internal links spread authority across your site and tell Google which pages matter most. Redesigns break them easily: key pages lose the links that used to point to them, or anchor text stops matching the destination once pages are renamed. Map your existing internal links before the build, replicate them on the new site, and check the anchor text still describes each linked page accurately.
Consolidating Thin Pages Without Losing Rankings
A redesign is a good time to merge thin or overlapping pages into stronger ones — but never at the expense of pages that already rank. Anything on your top-performer list should be kept, updated, or redirected to a closely matching alternative. Consolidated pages should redirect to their replacement, and that replacement should cover the topic more thoroughly than the originals did.
Building a 301 Redirect Map
What a 301 Redirect Does
A 301 redirect tells Google and browsers that a URL has permanently moved. It tells Google to consolidate the old page’s ranking signals, including link equity, on the new URL, and ensures visitors who click old links — including those still in Google’s index — land on the right page rather than a 404 error.
Mapping Old URLs to the Most Relevant New URLs
Every old URL gets a single destination, and that destination should be the most topically relevant page on the new site. A page about timber flooring in Brisbane should redirect to your timber flooring page — not the homepage, the contact page or a generic services page. Include PDFs and images in the map too. If their file paths change, links pointing to them from other websites will break.
| Old URL | New URL | Redirect Type | Notes |
| /services/website-design/ | /services/web-design-brisbane/ | 301 | URL updated for local keyword alignment |
| /blog/seo-tips-2019/ | /blog/seo-tips/ | 301 | Year removed from updated post |
| /contact-us.html | /contact/ | 301 | Platform change removed .html extension |
| /old-service-page/ | /services/ | 301 | Service discontinued; redirect to category |
| /wp-content/uploads/brochure.pdf | /resources/company-brochure.pdf | 301 | File path changed in rebuild |
Why You Shouldn’t Redirect Everything to the Homepage
Redirecting all old URLs to the homepage is a shortcut Google can treat as a soft 404. When the destination isn’t a genuine replacement for the old page, Google may disregard the redirect, and the value that page built up is effectively lost. It’s also frustrating for visitors who clicked expecting a specific service or article.
Avoiding Redirect Chains and Loops
A redirect chain happens when URL A redirects to URL B, which then redirects to URL C. Each extra hop slows the page for visitors, wastes crawl resources and adds another point of failure — and Googlebot only follows a limited number of hops before giving up. Make sure every old URL resolves to its final destination in one hop. A loop, where A redirects to B and B redirects back to A, breaks the page entirely.
Handling Pages You’re Removing Permanently
If a page is genuinely being retired with no relevant replacement, it can return a 410 (Gone) status. Google treats 404 and 410 responses similarly, but a 410 is a slightly clearer signal that the removal was intentional.
Implementing Redirects in WordPress and on Your Server
In WordPress, redirects can be managed through the Redirection plugin, Rank Math or Yoast SEO Premium — and whichever of these WordPress plugins you choose, test it thoroughly before launch. For large or high-traffic sites, server-level redirects via .htaccess (Apache) or your Nginx configuration are faster and more reliable, because they execute before WordPress even loads.
How Long to Keep Your Redirects in Place
Google’s site move guidance recommends keeping redirects in place for as long as possible — generally at least a year. In practice, the safest approach is to keep them indefinitely. Other websites won’t update their links to your old URLs, so removing redirects too early means that traffic and link equity disappear.
Protecting Your Content and On-Page SEO Elements
Keeping the Content That Already Ranks
If a page ranks, its content is part of the reason why. Topic coverage, the entities and related terms it mentions, the questions it answers and the internal links within it all shape how Google understands it.
Word count itself isn’t a ranking factor — Google has said so repeatedly. The risk with trimming copy for a “cleaner” design is what gets cut along with the words. When an 800-word service page is pared back to 200 words, the specifics usually go first: the suburbs you service, related terms, answers to common customer questions, and internal links. Those are often the very things the page ranked for. Before cutting anything, check the page’s ranking queries in Search Console and make sure the content answering them survives.
Updating Content vs Rewriting It from Scratch
Updating means improving what’s already there — correcting outdated details, strengthening weak sections and expanding thin coverage. Rewriting from scratch risks removing keyword signals, shifting the page’s focus or losing depth. Update where you can; rewrite only where you must.
Preserving Trust Signals Such as Reviews, Case Studies and Author Information
Google’s quality guidelines put real weight on Experience, Expertise, Authoritativeness and Trustworthiness (E-E-A-T). Customer reviews, case studies, author bios and credentials all contribute — so carry them across rather than trimming them for a cleaner layout.
Title Tags, Meta Descriptions and Social Tags
Carry every title tag and meta description from the old site to the new one unless there’s a deliberate reason to change them. These fields are often wiped during CMS migrations, theme changes or SEO plugin switches. While you’re there, check the Open Graph tags that control how pages look when shared on Facebook or LinkedIn — they usually live in the same plugin settings.
H1 Tags and Heading Hierarchy
As best practice, each page should have one clear H1 that reflects its primary keyword target. This isn’t a Google requirement — Google handles multiple H1s without penalty, and they’re common in HTML5 themes — but a single H1 makes the main topic unambiguous for users and screen readers. Below it, H2s and H3s should keep the keyword-relevant structure your ranking pages already have. New templates often overwrite or drop headings, so crawl the new site to confirm.
Image Alt Text and File Names
Alt text serves both accessibility and SEO, and it’s frequently lost when images are re-uploaded to a new media library. Keep descriptive, keyword-relevant alt text and file names on every significant image.
Schema Markup and Structured Data
Schema markup — including LocalBusiness, Service, Article and Review schema — doesn’t always survive a redesign. If it’s generated by an SEO plugin that stays in place, it usually carries over. If it was hardcoded into the old theme or set up on a different platform, it needs to be rebuilt. Either way, run key pages through Google’s Rich Results Test after launch.
Canonical Tags and Duplicate Content
Canonical tags tell Google which version of a page is authoritative. Misconfigured canonicals — particularly ones pointing to the wrong URL — can lead Google to drop the page you want ranking in favour of a different URL. After launch, also make sure HTTP and HTTPS, and www and non-www versions, all resolve to a single version through redirects rather than serving duplicate copies.
Structuring Content for Google’s AI Overviews
Google’s AI Overviews tend to draw on pages that answer questions clearly and directly. Explicit question-and-answer formatting, clear definitions and concise summaries of key points make your content easier to surface there. A redesign is the perfect time to restructure with that in mind.
Technical SEO Considerations for a New Website
Protecting Your Staging Site from Being Indexed
The safest way to keep a staging site out of Google is to put it behind HTTP basic authentication (password protection) or restrict access to an allowlist of IP addresses. Googlebot can’t get past either, so nothing gets crawled or indexed — even if someone accidentally links to the staging URL.
A robots.txt disallow on its own isn’t reliable. It stops Google crawling the pages, but if the staging URL is linked from elsewhere, Google can still index the bare URL without a snippet. Combining a robots.txt disallow with a noindex tag doesn’t work either: if Googlebot can’t crawl the page, it never sees the noindex instruction.
Password protection has one more advantage — it sits outside the site’s code. A noindex tag, including the one WordPress adds when “Discourage search engines from indexing this site” is ticked, travels with the site when it’s pushed live. That’s exactly how so many new websites launch invisible to Google.
Reviewing Robots.txt and Your XML Sitemap
On the live site, check robots.txt isn’t blocking anything that should be indexed — one misplaced line can block an entire directory. Your XML sitemap should list every page you want indexed and nothing you don’t. Submit it in Google Search Console on launch day, then watch the Pages report for indexing errors.
Ensuring HTTPS and SSL Are Set Up Correctly
If your site is still on HTTP, moving to HTTPS is overdue — HTTPS is a lightweight ranking signal, and browsers flag sites without it as not secure. With modern hosting it’s low risk, since most Australian hosts provision free SSL certificates automatically. Redirect every HTTP URL to its HTTPS equivalent with a single server-level rule, make sure canonical tags and your sitemap reference HTTPS, and fix any mixed-content warnings from images or scripts still loading over HTTP. In Search Console, a Domain property covers both versions automatically.
Designing for Mobile-First Indexing
Google indexes your site primarily through its mobile crawler, so the new site must render completely on a phone. That means responsive layouts, tap-friendly buttons, legible font sizes, and no content that’s visible on desktop but hidden on mobile.
Checking JavaScript Rendering
Sites built on JavaScript-heavy frameworks such as React, Vue or Angular can be harder for Googlebot to process. Use the URL Inspection tool in Search Console to see how Google renders a page — if content you can see in a browser doesn’t appear in Google’s render, it isn’t being indexed.
Choosing Reliable Web Hosting
Hosting affects page speed and uptime, and both shape user experience. For Brisbane businesses, VPS hosting can offer a noticeable step up from shared hosting, particularly for sites with moderate to high traffic. If your redesign involves switching hosts, migrate during a quiet period, confirm DNS has propagated, compare speed before and after, and keep the old hosting active until everything is confirmed working on the new server.
Page Speed and Core Web Vitals in a Website Redesign
Understanding LCP, INP and CLS
Google’s Core Web Vitals measure real-world loading, responsiveness and visual stability:
- LCP (Largest Contentful Paint) measures how quickly the largest visible element, usually a hero image or heading, loads. Good: 2.5 seconds or less.
- INP (Interaction to Next Paint) measures how quickly the page responds to taps, clicks and key presses. Good: 200 milliseconds or less.
- CLS (Cumulative Layout Shift) measures how much the layout jumps around while loading. Good: 0.1 or less.
Google assesses these at the 75th percentile of real visits, and you can see them in Google Search Console and PageSpeed Insights.
Optimising Images with WebP and AVIF
Images are usually the heaviest part of a page. Serving them in WebP or AVIF — both much smaller than JPEG or PNG at the same visual quality — cuts load times substantially. Most modern WordPress setups and image optimisation plugins handle the conversion automatically, but confirm it’s actually working on the new site.
Loading Web Fonts Efficiently
Custom web fonts add personality to a design but slow things down when they’re implemented carelessly. Serving compressed WOFF2 files instead of older, heavier font file types, hosting them locally, using font-display: swap so text appears straight away, and limiting the number of weights you load all help LCP and CLS.
Reducing Page Builder and Plugin Bloat
Page builders like Elementor, Divi and WPBakery make polished designs quick to build, but they can weigh pages down with excess CSS and JavaScript — and every plugin adds more. After the redesign, remove plugins you don’t need, stop unused scripts and styles loading on pages that don’t use them, and switch on your page builder’s performance settings.
Using Caching and a Content Delivery Network
A caching plugin such as WP Rocket, LiteSpeed Cache or W3 Total Cache serves stored versions of your pages instead of rebuilding them on every request. A content delivery network (CDN) serves images, CSS and JavaScript from servers closer to your visitors. Both are standard for a well-performing WordPress site.
Testing Speed Before and After Launch
Run PageSpeed Insights and GTmetrix on staging and compare against your pre-redesign baseline — fix problems before launch, not after. Once you’re live, keep in mind that Search Console’s Core Web Vitals report is based on real-user data collected over a rolling 28-day window, so it takes several weeks to fully reflect the new site. PageSpeed Insights lab tests will catch issues sooner.
Protecting Local SEO During a Website Redesign
Keeping Your NAP Details Consistent
Your business name, address and phone number should appear identically on your website and every external listing. Redesigns often reformat, move or drop NAP details from templates, introducing inconsistencies that weaken local signals. NAP consistency is a foundational part of local SEO that’s easy to get right and costly to neglect.
Updating Your Google Business Profile Website Link
After launch, check your Google Business Profile points to the correct URL on the new site. If your domain or location page URLs changed, update the profile straight away so customers who find you on Maps don’t land on a 404.
Preserving Suburb and Location Pages
For service-area businesses across Brisbane, Logan, Ipswich, Moreton Bay and the Gold Coast, suburb pages are often the highest-performing pages in local search. Keep their URLs where possible, carry over their localised content, and preserve the internal and external links pointing to them.
Retaining LocalBusiness Schema, Maps and Reviews
LocalBusiness schema tells Google your business type, address, phone number, opening hours and service area in machine-readable form. It often lives in theme settings or a plugin, so it needs to be rebuilt deliberately on the new site. Check that embedded Google Maps still show the right location, and that review and testimonial widgets still work with the new theme — they’re trust signals customers look for before they pick up the phone.
Checking Local Citations That Link to Old URLs
Business directories, industry listings and local citation sites often link to specific pages, not just your homepage. Check whether any of them point to URLs that have changed, then update the citation or make sure a redirect is in place. If local SEO is a primary source of enquiries for your business, treat it as a first-class priority in the redesign — not an afterthought.
Redesigning an E-Commerce Website Without Losing Rankings
Preserving Product and Category URLs
On an e-commerce website, most of your ranking signals sit on product and category URLs. Every change needs a precise redirect — even moving /products/blue-widget/ to /shop/blue-widget/ creates a different page in Google’s eyes. Migrate product descriptions and customer reviews in full too. They’re the main content signals on product pages, and they’re easy to lose in a platform switch.
Handling Discontinued and Out-of-Stock Products
Permanently discontinued products should 301 redirect to the most relevant category or a comparable product. Temporarily out-of-stock products should stay live with clear availability information — deleting the page throws away rankings you’ll want back when stock returns.
Managing Filters and Faceted Navigation
Filter URLs like /products/?colour=red&size=large can generate thousands of near-duplicate pages. Use canonical tags, noindex directives or robots.txt rules to stop Google indexing filter combinations that have no search value.
Migrating Between Shopify and WooCommerce
Shopify uses fixed URL prefixes such as /products/ and /collections/, so URL changes are often unavoidable when migrating to Shopify — and the same applies in reverse when moving to WooCommerce. A comprehensive redirect map covering every product and collection URL is essential, and it’s usually one of the most time-consuming parts of the project.
Updating Google Merchant Center Product Feeds
If you run Google Shopping campaigns, your Merchant Center feed references specific product URLs. Any URL changes not reflected in the feed will trigger errors and disapproved products, so update the feed or its generation rules immediately after launch.
Changing Your CMS or Website Platform
Moving from Wix or Squarespace to WordPress
Wix and Squarespace generate their own URL structures, which rarely match a well-organised WordPress site. Moving platforms is effectively a full migration — audit, URL inventory, redirect map, metadata migration and thorough testing — and a chance to rethink your URL architecture, provided every old URL redirects to its WordPress equivalent.
Changing WordPress Themes Without Losing SEO
A theme change is lower risk than a platform move, but not risk-free. Themes affect page templates, heading structure, speed and sometimes schema output — especially themes that hardcode SEO elements. Crawl the site after the switch to confirm title tags, H1s and schema are intact.
Moving Away from Page Builder Lock-In
Switching page builders, or leaving them behind entirely, usually means rebuilding pages rather than simply reassigning templates. Content, headings and metadata are easily lost along the way, so manage the rebuild page by page against your original audit.
What Transfers Between Platforms and What Doesn’t
When you change platforms, expect to manually move or rebuild your SEO metadata (titles, descriptions and canonicals), schema markup, existing redirect rules, analytics and tracking code, and form configurations and integrations. Switching SEO plugins — from Yoast SEO to Rank Math, for example — is easier, since the major plugins include import tools, but crawl afterwards to confirm everything came across. Test platform-specific behaviour such as image handling, pagination and caching on staging before you launch.
Changing Your Domain Name During a Redesign
Why You Should Avoid Combining a Domain Change with a Redesign
Combining a domain change with a full redesign is one of the riskiest moves in SEO. If traffic drops, it’s almost impossible to tell whether the domain change, the redirects, the new architecture or the content changes caused it — because everything changed at once. Wherever possible, run the domain change as a separate project so issues are easier to diagnose.
Using the Change of Address Tool in Google Search Console
Google’s Change of Address tool formally notifies Google that you’ve moved domains and can help speed up reindexing. It only applies to domain-level moves, and it works alongside a full redirect strategy — not instead of one.
Redirecting Your Old Domain and Updating Backlinks
Every page on the old domain should redirect to its equivalent on the new one — not just the homepage. If the URL structure is also changing, your redirect map needs to account for both changes at once. Then contact the sites behind your most valuable backlinks and ask them to update their links. Redirects pass the signals, but a direct link doesn’t depend on redirects staying in place forever.
Keeping Your Old Domain Registered
Letting the old domain lapse is one of the most damaging migration mistakes. If someone else registers it, every redirect stops working — and your old links could end up pointing to a competitor or a spam site. Keep the old .com.au domain renewed so its redirects keep working for as long as practically possible.
Testing and Launching Your New Website
Crawling the Staging Site and Testing Every Redirect
Run a full Screaming Frog crawl of staging to surface broken internal links, missing metadata, incorrect H1s, missing canonicals and pages wrongly returning noindex. Since staging should be password-protected, set the crawler up with those credentials. Then test every redirect in your map — Screaming Frog in List mode, the Redirect Path browser extension or Ahrefs’ Site Audit will confirm each old URL lands on its intended destination in a single hop.
Testing Mobile, Browsers and Accessibility
Test on real iOS and Android devices, not just emulators, and in Chrome, Safari, Firefox and Edge. Run an accessibility check with WAVE, Lighthouse or Axe too. Missing form labels, poor colour contrast and broken keyboard navigation affect real visitors and can expose your business to complaints under the Disability Discrimination Act.
Testing Forms, Analytics and Conversion Tracking
Submit every contact form, quote request and booking system end to end, and confirm the notifications arrive where they should. Use GA4’s DebugView and Google Tag Manager’s Preview mode to confirm every conversion event fires. If tracking isn’t working from day one, you’ll be diagnosing the launch blind.
Choosing the Right Time to Launch
Good website relaunch SEO starts with timing. Avoid launching on a Friday afternoon, over a public holiday or just before your busiest trading period — if something goes wrong, you need the whole team on hand. A Tuesday or Wednesday morning in a quieter month is a sensible default.
Working Through Your Launch Day Steps
On launch day, work through these in order:
- Lift staging password protection or IP restrictions, and remove any noindex tags or robots.txt disallow rules left over from development.
- Confirm all 301 redirects are live, including server-level rules in .htaccess or Nginx.
- Submit the new XML sitemap in Google Search Console.
- Use URL Inspection to request indexing of your homepage, main service pages and key location pages. It doesn’t guarantee immediate indexing, but it prompts Google to recrawl them.
- Check GA4 is recording live sessions and conversion events.
- Confirm your Google Business Profile links to the correct URL.
- Watch your server logs and hosting dashboard for spikes in 404s, 500 errors or redirect loops.
Monitoring Rankings and Traffic After Launch
What to Check in the First 48 Hours
In the first two days, confirm Google is crawling the new site using the Crawl stats report and URL Inspection in Search Console. Check that major pages return 200 status codes, that 404 errors aren’t spiking, and that GA4 is recording sessions and conversions.
Comparing Keyword Rankings to Your Benchmark
Some ranking movement in the weeks after launch is normal. Check your keyword tracker — Semrush, Ahrefs or Search Console — weekly against your pre-launch benchmark. What warrants investigation is a decline that keeps going, or losses concentrated on specific pages that were previously stable. Those patterns usually point to a fixable cause.
Reviewing the Pages Report and Fixing 404 Errors
The Pages report in Search Console shows which URLs are indexed, which are excluded and why. Review it weekly after launch, and cross-reference any 404s against your redirect map. If a URL that should redirect is returning a 404, the redirect is either missing or broken.
Comparing GA4 Traffic and Conversions
Compare organic sessions and conversions in GA4 against the same period before launch, and year-on-year where seasonality matters. A properly configured Google Analytics setup lets you isolate organic traffic by landing page, so you can see exactly which pages have lost visitors rather than guessing from a sitewide total. A decline that keeps sliding rather than levelling out — especially one that lines up with lost ranking positions — is a problem to diagnose, not wait out.
Knowing When a Traffic Drop Needs Action
Broad, mild fluctuation across the site is usually Google re-evaluating and doesn’t necessarily need intervention. Sharp drops on specific pages, a rising 404 count, pages falling out of the index, or a decline that keeps sliding rather than levelling out are signals to investigate now — waiting rarely fixes a missing redirect or a stray noindex tag.
Recrawling and reindexing timelines vary significantly depending on your site’s size, how often Google crawls it and how much changed. There’s no universal recovery timetable, and anyone who gives you a specific number is guessing.
How to Recover Lost Rankings After a Website Redesign
Diagnosing the Cause of the Traffic Drop
Start with data, not guesses. Pull the Search Console Pages report, review your 404 errors, compare keyword rankings page by page against your benchmark, and audit your top-traffic pages for changes to content, metadata or status codes. Methodical diagnosis beats a scattergun of fixes every time.
Checking for Leftover Noindex Tags
One of the first things to check is whether any pages still carry a noindex tag from development. Crawl the live site and review the meta robots tag on every major page.
Fixing Redirects and Broken Internal Links
If 404s are appearing for URLs that should have been redirected, add the missing redirects immediately — every day without one is a day Google spends trying to index a page that doesn’t exist. Fix broken internal links at the same time, since they leave pages isolated and waste crawl resources.
Restoring Removed Content, Titles and Headings
If pages that used to rank were deleted without a replacement, restore them — at the original URL or at a new one with a 301 from the old address. If content was merged elsewhere, make sure the destination page covers the same ground in enough depth. Check whether title tags or H1s changed on pages that lost rankings too, because even small changes can shift how a page ranks for its target terms.
Checking Whether a Google Algorithm Update Coincided with Your Launch
Sometimes a post-launch drop has nothing to do with the redesign — it lines up with a Google algorithm update that would have affected your site anyway. The Google Search Status Dashboard lists confirmed updates, so you can check whether one landed around your launch date. If the Google traffic problems persist well beyond the redesign, it’s worth stepping back to look at broader SEO factors.
Common Website Redesign Mistakes That Hurt SEO
Most redesign traffic losses trace back to the same short list of common SEO problems, and every one of them is avoidable:
- Launching with noindex tags or staging protection still active
- Skipping the redirect map, or redirecting every old page to the homepage
- Deleting high-performing pages, or changing URLs without a good reason
- Cutting the copy that answered the queries a page ranked for
- Forgetting to reinstall analytics and conversion tracking
- Launching an image-heavy site that crawls on mobile
- Going live right before your busiest season
- Not monitoring the site after launch
Website Redesign SEO Checklist
Use these tables as your SEO website migration checklist — copy them into a shared doc and tick them off as a working document throughout the project.
Planning Stage Checklist
| Task | Completed |
| Define business goals and baseline KPIs (traffic, rankings, conversions, Core Web Vitals) | ☐ |
| Run a full pre-redesign SEO audit and crawl | ☐ |
| Build a complete URL inventory, including PDFs, images and campaign pages | ☐ |
| Identify top-performing and high-backlink pages | ☐ |
| Document NAP details and local SEO signals | ☐ |
| Back up the existing site | ☐ |
| Get SEO requirements signed off in the project brief | ☐ |
Design and Development Stage Checklist
| Task | Completed |
| Password-protect or IP-restrict the staging site | ☐ |
| Keep existing URLs wherever possible | ☐ |
| Build and review the complete 301 redirect map | ☐ |
| Migrate title tags, meta descriptions, canonicals and Open Graph tags | ☐ |
| Carry over ranking content, heading structure and image alt text | ☐ |
| Rebuild and validate schema markup | ☐ |
| Set up HTTPS, caching and a CDN | ☐ |
| Install GA4 and Google Tag Manager on staging | ☐ |
Pre-Launch Checklist
| Task | Tool | Completed |
| Crawl staging and resolve critical errors | Screaming Frog | ☐ |
| Test every redirect in the map | Screaming Frog / Redirect Path | ☐ |
| Fix broken internal links | Screaming Frog / Ahrefs | ☐ |
| Test on mobile devices and major browsers | Real devices / Chrome DevTools | ☐ |
| Test every form and conversion point | Manual | ☐ |
| Verify GA4 and conversion tracking | GA4 DebugView / GTM Preview | ☐ |
| Validate schema markup | Google Rich Results Test | ☐ |
| Run an accessibility audit | WAVE / Lighthouse | ☐ |
| Compare page speed to baseline | PageSpeed Insights / GTmetrix | ☐ |
Launch Day Checklist
| Task | Completed |
| Launch at a low-risk time (Tuesday or Wednesday morning) | ☐ |
| Lift staging protection and remove any noindex tags or robots.txt blocks | ☐ |
| Activate all 301 redirects | ☐ |
| Submit the new XML sitemap in Google Search Console | ☐ |
| Request indexing of key pages via URL Inspection | ☐ |
| Confirm GA4 is recording sessions and conversions | ☐ |
| Check the Google Business Profile website link | ☐ |
| Monitor server errors and 404s | ☐ |
Post-Launch Checklist (30, 60 and 90 Days)
| Task | Timeframe | Completed |
| Review the Pages report for crawl errors and 404s | 30 days | ☐ |
| Fix any missing or broken redirects | 30 days | ☐ |
| Compare rankings and GA4 organic traffic to baseline | 30 days | ☐ |
| Confirm conversion events are tracking correctly | 30 days | ☐ |
| Review Core Web Vitals in Google Search Console | 60 days | ☐ |
| Investigate any sustained ranking drops | 60 days | ☐ |
| Act on any unexpected indexing exclusions | 60 days | ☐ |
| Final ranking and traffic comparison to baseline | 90 days | ☐ |
| Decide whether further content or link-building work is needed | 90 days | ☐ |
Should You Work with an Agency on Your Website Redesign?
DIY Redesign vs Working with an Agency
A self-managed redesign can work for a small, simple site with a team that understands both WordPress and SEO. The risk climbs with complexity — the more pages, redirects, schema and local signals involved, the more there is to get wrong. For most Brisbane businesses with established organic traffic, the cost of an agency is far lower than the cost of a prolonged traffic loss.
Questions to Ask Your Web Designer About SEO
Before engaging a web design team, ask:
- Will you produce a redirect map before the build begins?
- How do you migrate title tags and metadata?
- Do you crawl the site before and after launch?
- Who sets up and verifies analytics and conversion tracking?
- How do you protect the staging site from being indexed?
- How long do you actively monitor the site after launch?
If the answers are vague, SEO isn’t part of their process.
Red Flags to Watch For
- Guaranteeing rankings — No agency controls Google’s algorithm, so no agency can guarantee rankings. Promises like “page one guaranteed” could be misleading under the Australian Consumer Law, which the ACCC enforces. Treat them as a reason to walk away, not a selling point.
- No pre-launch audit or redirect plan — A team that goes straight from design to launch is skipping the steps that protect your rankings.
- Suspiciously cheap fixed packages — Proper SEO protection takes time. Packages priced well below the market usually get there by leaving the SEO work out.
- No post-launch monitoring — A team that hands over the site and walks away isn’t taking responsibility for the results.
The Value of Having Design and SEO Under One Roof
When design, development and SEO are handled by separate providers, gaps appear. The designer doesn’t know about the redirect map, the developer picks a setup that can’t output the schema you need, and the SEO consultant sees the finished site a week before launch. That’s how we run redesigns differently at Content Authority — design, development and SEO work from the same plan, so the redirect map, content requirements and tracking are locked in before a single template is built. Being Brisbane-based also means we know which suburbs matter to your customers, how service-area businesses compete across South East Queensland, and we’re on hand during your business hours if something needs attention after launch.
Ongoing Website Support After Launch
The work doesn’t stop when the site goes live. Rankings need time to settle, new technical issues crop up, and content needs updating as your services evolve. Ongoing WordPress support — regular updates, security monitoring and performance checks — keeps your site stable and your rankings protected long after launch day.
Frequently Asked Questions About Website Redesigns and SEO
Will a Website Redesign Hurt My SEO?
A poorly managed redesign can hurt your SEO significantly. A well-managed one — with a pre-redesign audit, a complete redirect map and careful migration of on-page elements — can protect your rankings and, in many cases, improve them. The difference is preparation.
How Long Does It Take for Rankings to Recover After a Redesign?
It depends on your site’s size, how much changed, how well the migration was handled and how often Google crawls your domain. Small, sitewide fluctuations tend to settle once Google has recrawled the site, while drops caused by missing redirects or removed content usually won’t recover until the underlying problem is fixed. There’s no universal timeframe — which is why post-launch monitoring matters as much as the launch itself.
Can I Redesign My Website Without Changing URLs?
Yes, and it’s one of the best ways to reduce risk. A new look, better performance or even a new theme doesn’t require changing URLs. If your current structure is logical and performing well, keep it.
Will I Lose My Backlinks If I Redesign My Website?
The backlinks themselves stay on the sites that placed them. What you can lose is their value, if the URLs they point to start returning 404 errors. A complete redirect map passes that value through to the right new pages.
Do I Need to Tell Google About My New Website?
For a standard redesign, there’s nothing formal to do beyond submitting your updated XML sitemap in Google Search Console on launch day. For a domain change, use the Change of Address tool in Search Console as well.
Should I Get an SEO Audit Before Redesigning My Website?
Yes. A pre-redesign audit documents your current rankings, identifies your most valuable pages, flags technical issues to fix or leave behind, and gives you the benchmark you’ll need to measure success after launch.
Planning a Website Redesign in Brisbane?
A new website should win you more enquiries, not cost you the ones you already get. Content Authority plans every website redesign Brisbane businesses trust us with around SEO from day one — starting with a pre-redesign audit and a complete 301 redirect map, carrying through rigorous pre-launch testing, and continuing with active post-launch monitoring — so our WordPress website design work gives you a site built to convert without giving away the rankings you’ve spent years earning.
Ready to Redesign Your Website Without Losing Your Rankings?
Planning a new website for your Brisbane business? Contact Content Authority to discuss your redesign and how we can protect the search visibility you’ve already built.
Call: (+61) 0490 436 812
Email: [email protected]
