How to redesign a website without losing SEO
A redesign is one of the few moments when a business can lose, within weeks, search traffic it took years to earn. The loss rarely comes from the new design itself. It comes from addresses that change without redirects, content that is cut, and settings left over from the staging site.
Will a website redesign affect SEO?
It can, in either direction. A redesign that keeps the addresses, the content and the signals search engines rely on usually passes with a short period of movement and little else. A redesign that changes every URL, rewrites the text and launches with a forgotten noindex can lose much of its search traffic within weeks, and winning it back is slow.
Google's guidance on site moves says to expect temporary fluctuation in rankings while it recrawls a changed site. A drop that persists is different, and it usually traces back to a short list of causes: old URLs that return errors or redirect to the wrong place, pages that were removed or emptied, internal links that still point at old addresses, and staging settings that block crawling or indexing.
None of these is a design problem. Each one can be prevented with an inventory, a map and a set of checks, set out below in the order the work happens.
Redesign or rebuild: what is actually changing?
Start by being precise about what the project changes. A visual redesign on the same platform can keep every URL and most of the markup, so the search risk is small. A rebuild on a new platform usually changes the URL structure and the way titles and descriptions are stored, even when the pages look similar. A new domain changes every address at once.
Choose between the two on what the business needs, not on search alone. Rebuild when the platform is in the way: the site is slow on a phone and cannot be made faster, nobody can edit a page without help, or ordering, bookings or a second language need a structure the old site cannot support. Redesign when the structure is sound and the problem is how the site looks or reads.
Either way, write down what will change: URLs, navigation, templates, languages, domain, hosting. Where a rebuild is the right answer, our website design and development work treats the transfer of search signals as part of the build, not as an afterthought.
Start with a URL inventory of the old site
The inventory is a spreadsheet with one row for every address the old site has, or has had recently. No single source holds all of them, so combine several: the XML sitemap, a crawl of the site with a crawler tool, the pages in Search Console's Performance report, the landing pages in your analytics, and Search Console's Links report, which shows the pages other sites link to most.
Include what visitors rarely notice: PDFs, images that appear in image search, old campaign pages still linked from elsewhere, and every language version. Google's site-move guidance names images, videos, scripts and stylesheets as URLs to move like any other.
For each row, record what the page earns (clicks, impressions, main queries, sites linking to it) and its current title, description, main heading, canonical tag and structured data. Export the Search Console data before launch: it is the baseline for every later comparison.
On a site with a large content library, the inventory is the biggest single task. leadinsure.gr, the website of an insurance agency, carries a library of insurance guides in Greek and an English section with guides of its own. An inventory for a site like that has to cover every guide in both languages, not only the pages in the menu.
How do you build a 301 redirect map?
The redirect map adds one column to the inventory: where each old URL goes, which should be its closest equivalent on the new site. A service page goes to the new page for the same service, an article to the same article at its new address, a product to the same product. Where several old pages have been combined into one, each of them can point to the combined page.
Three mistakes cause most of the damage. The first is sending everything to the home page. Google warns that redirecting many old URLs to one irrelevant destination confuses visitors and may be treated as a soft 404, that is, as a page that no longer exists rather than one that has moved.
The second is chains, where an address redirects to another that redirects again; Google advises pointing each old URL straight at its final destination. The third is temporary redirects used by default. With a 302, Google keeps showing the old address in its results; a 301 or 308 tells it that the new page takes the old one's place.
Pages with no equivalent should not be redirected for the sake of it; Google's guidance is that removed content should return a 404 or 410. Set the redirects up on the server, test every row on staging and again after launch, and keep them for as long as possible; Google's advice is generally at least a year.
Then update everything on your own site that still points at old addresses: menus, footers, body links, canonical tags, hreflang annotations and the sitemap. Redirects are for the links you cannot control. Our technical SEO checklist for a new website covers the rest of what has to be right on launch day.
Keeping the content that ranks
Redesigns often arrive with a new view of content: shorter pages, fewer words, more images. Before cutting, check the inventory. A page that appears for dozens of queries does so because its text answers them. Remove the paragraphs that do that work and the queries go with them, however well the redirect is set up.
Rewrite with the old page open beside the new one. Keep the headings that match what people search, the specific details a visitor came for and the internal links that connect the page to the rest of the site. Improve the writing by all means, but keep the substance.
Language versions need the same care. Kalimenu, our QR menu and table-ordering product, runs its English site on kalimenu.com and its Greek site on kalimenu.gr, and each declares the other with hreflang annotations. If a redesign changes the URL on one side and the annotation on the other is not updated, the two pages no longer point at each other, and Google's guidance is that hreflang annotations that are not reciprocal are ignored.
A shop that changes platform often changes every product and category URL at once, which makes the redirect map the largest part of the move. Our guide to building an online shop covers the choice of platform itself.
Metadata, structured data and the rest of the markup
Titles and meta descriptions are part of what the old site earned. Carry them across page by page from the inventory, and change them only where you can explain the improvement. New templates are a common source of loss: a theme that uses the business name as every page's title, or has no field for a description, can undo years of work on launch day.
Structured data deserves the same attention. If the old site described the organisation, its services, articles, products or frequently asked questions in structured data, the new templates must produce the equivalent, validated before launch. Google's structured data policies require markup to reflect content that is visible on the page, so markup describing questions or reviews that the redesign removed has to go as well.
Check the main heading, canonical tag and image alternative text in every template too; a designer rarely sees them, so they belong on a written list. Our technical SEO setup covers this work for redesigns as well as for new sites.
Keep the staging site out of Google, then open it at launch
The new site is built and reviewed on a staging copy, which must stay out of the index, or search engines may find two versions of the same content, one of them unfinished. Put it behind a password: a page that asks for a login cannot be crawled at all, and Google names password protection, alongside noindex, as a way to keep a page out of its results.
Many teams use a robots.txt rule or a noindex tag instead, and each has a catch. Google's documentation states that robots.txt is not a mechanism for keeping a page out of Google: a blocked URL can still be indexed if other sites link to it. A noindex tag does work, but only on pages crawlers are allowed to fetch, and it is easily carried over to the live site by mistake.
That is why launch day needs its own list. Google's site-move guidance advises preparing, in advance, the robots.txt file the live site will use and the list of URLs from which noindex rules will be removed. At launch, confirm that none of the staging protection has reached the live site: no password, no staging robots.txt, no leftover noindex, and canonical tags that point at the live domain rather than the staging address.
What to check in Search Console in launch week
The checks start in the first hour. Crawl the full list of old URLs and confirm that each one returns a single permanent redirect to the right page, or a 404 or 410 where that was the plan. Open the most valuable pages in Search Console's URL Inspection tool and run a live test, which shows whether Google can fetch each page as it now stands and whether it might be indexed.
Submit the new sitemap and, as Google suggests, a second sitemap listing the old URLs: over the following weeks the old one should show fewer indexed pages and the new one more, and warnings that the old URLs redirect are expected. If the domain itself has changed, use the Change of Address tool on the old property. It is meant only for moves between domains or subdomains, not for a switch to HTTPS or a change of paths on the same domain.
For the rest of the week, watch the Page indexing report for new entries under 'Not found (404)', for pages left out because of a noindex tag, and for unexpected changes in the number of indexed pages. Test the forms, analytics and cookie banner on the live domain too: a redesign that loses enquiries has failed whatever happens in search.
What should you monitor in the first 8 weeks after a redesign?
Google says that for a small to medium-sized site, most pages take a few weeks to move, and larger sites take longer. Judge the redesign on the trend, not on the first few days, and compare each week with the baseline exported before launch, page by page and query by query.
Weeks one and two: 404 errors, redirect faults and the indexing of the main pages. Weeks three to six: clicks and impressions for the pages that earned most before the move, and whether the old URLs are leaving the index as the new ones replace them. Weeks seven and eight: a full comparison with the baseline, and a list of pages that have not recovered.
A page that has lost its traffic usually shows why when you look closely: a redirect to the wrong place, text that was cut, a title that changed, a menu link that disappeared. Fix those first, and avoid further structural changes in this period, because each one resets the comparison.
Nobody can guarantee that a redesigned site keeps every position it held; a careful move removes the avoidable causes of loss. After the first two months the work becomes routine monitoring, which our Website Care plans include, or a monthly programme of ongoing SEO if the aim is to grow beyond where the old site stood.
Frequently asked.
How long does it take for search traffic to recover after a redesign?
There is no fixed period. Google's guidance says most pages of a small to medium-sized site take a few weeks to move, larger sites longer, with temporary fluctuation along the way. A drop that is still deepening after a month usually has a specific cause, such as missing redirects or removed content, and should be investigated rather than waited out.
How long should 301 redirects stay in place?
As long as possible. Google's site-move guidance says generally at least a year, which gives it time to transfer signals and recrawl links from other sites. There is rarely a reason to remove them, since old links elsewhere keep working while they exist.
Should I change my domain at the same time as the redesign?
Only if there is a reason to. A new domain changes every URL at once, so the redirect map covers the whole site and the Change of Address tool in Search Console is needed. If the change is necessary, consider making it separately from the redesign where you can: with one change at a time, any problem is easier to trace.
Will the new site keep my Google rankings?
Nobody can guarantee positions, before or after a redesign. A careful move keeps the addresses, content and signals that earned them, so search engines can treat the new site as a continuation of the old one. The outcome also depends on competition and time.
Our traffic dropped after a redesign someone else carried out. Can it be fixed?
Often, once the cause is found. The first checks are a leftover noindex or robots.txt block, old URLs that return errors instead of redirecting, and pages whose content was cut. An audit compares the old site, through Search Console data and archived copies, with what is live now.
Do you redesign websites you did not build?
Yes. The work starts with a conversation and an audit of the current site, its search traffic and what it needs to do, and the project is then quoted in writing. Whether the result is a redesign on the same platform or a rebuild depends on what that audit finds.