“Richard and the crew from Pinecone Agency were incredibly accommodating in our very particular needsIncredibly accommodating”
Tim Zafir

How to redesign a website without losing SEO

A website redesign SEO checklist: what puts rankings at risk, what to decide first, what to keep, how to map 301 redirects, and what to check at launch and after.

Want help with your project? Book a discovery call
On this page
  1. What goes on a website redesign SEO checklist?
  2. What puts rankings at risk in a redesign?
  3. What should you decide before the design starts?
  4. How do you record a baseline?
  5. Which pages and content should you keep?
  6. How should old URLs be redirected?
  7. What should you check on launch day?
  8. What should you watch in the first weeks?
  9. Frequently asked questions
  10. Sources
  11. Redesigning with Pinecone Agency

The short answer: A redesign doesn't have to cost you your Google rankings. List every live URL, map each change to a 301 redirect, and keep the titles, descriptions and content that already earn traffic, unless you choose to change them. Test redirects on staging, remove noindex before launch, then watch Search Console.

Website redesign SEO is about the parts of a site search engines already know: its URLs, the content on them and how pages link to each other. Google says to expect some movement while it recrawls a changed site, so plan for it rather than hope it won't happen.

After our rebuild for Southside Engineering, organic search visits rose 146% in the 90 days after launch compared with the 90 days before. Over the same dates a year earlier they fell 11%, which rules out seasonal demand.

When Pinecone Agency moved pinecone.agency from Webflow to Astro on Cloudflare in late July 2026, we followed the same method. We kept the domain, with www as the canonical host and the apex redirecting to it. The platform changed, and so did some URL paths: /our-work became /work, /contact-us became /contact, and several service slugs were renamed. Those addresses were kept by 301 redirects, not by leaving the old paths in place.

Pinecone Agency is a Melbourne design and development agency. We build custom websites, web apps and AI systems on the stack that fits each project, build on Webflow or Framer when your team wants to edit pages visually, and build online stores on Shopify. This guide covers any redesign, including one that stays on the same platform.

What goes on a website redesign SEO checklist?

Eight checks, in the order you'll need them. Each one is covered in more detail below.

  1. URL inventory. Crawl the live site and record every URL, with a Search Console and analytics baseline for the pages that earn traffic.
  2. Redirect map. Keep URLs that still fit. Map every URL that must change to its closest new page with a 301.
  3. Ranking pages. Keep their titles, descriptions and content unless you choose to rewrite them.
  4. Internal links. Carry the important links across and point them at the new URLs.
  5. Structured data. Keep or update schema so it still matches what's visible on each page.
  6. Staging blocks. Keep the test site out of search while you build, then remove noindex and robots.txt blocks at launch.
  7. Search Console and analytics. Confirm verification, the new sitemap, forms and tracking on the live site.
  8. Monitoring. Watch errors, pages and queries for the following weeks, and fix what slips. In the first week, start with the not-found report.

What puts rankings at risk in a redesign?

The new look rarely does. When we moved our own site, the risk sat underneath: the platform change, the URL paths that didn't stay the same, the sitemap address search engines already knew, and staging settings that had to stay off the live domain.

The damage usually comes from:

  • URLs that change without a redirect. Search engines and other sites still send people to the old address, and they land on a 404.
  • Content that gets cut. A cleaner page with half the words can stop answering the question it used to rank for.
  • Pages that disappear. A service page or old blog post that quietly brought in visitors gets dropped because nobody checked its numbers.
  • Titles, headings and descriptions rewritten from scratch. The words search engines knew you by change all at once.
  • Internal links that change. A new menu can bury pages that used to be one click from the homepage.
  • Structured data dropped. A new template can leave out the schema the old pages had.
  • Staging settings left on. A noindex tag or a robots.txt block that kept the test site out of Google goes live with the new one.

Every item on that list is a decision someone makes, which means every one can be planned for.

What should you decide before the design starts?

Write down what's changing, in one line each:

  • Will any URLs change, and which?
  • Is the platform or CMS changing?
  • Is the domain changing?
  • Which pages are being merged, rewritten or removed?

On our own move we kept the domain and the www canonical. We changed the platform, and we changed some paths. That combination is enough to need a full redirect map, even though the site still lived at pinecone.agency.

If the answer to the first three questions is no, you're mostly protecting content, titles and internal links. If any is yes, you also need that map. A domain change adds a Change of Address request in Search Console, which Google says you only need when moving to a different domain or subdomain.

Google's advice for site moves is to change one thing at a time where you can. Its example: if you want a new domain, a new CMS and a new layout, do them one after the other rather than together. Each change you stack on top makes problems harder to trace.

How do you record a baseline?

Before anything changes, capture how the current site performs so you have something to compare against:

  • Search Console. Export the Pages and Queries reports from the Performance report. Pick a window long enough to cover any seasonal swings in your business.
  • Analytics. Note traffic and key events (leads, bookings, sales) by landing page, and confirm the tag container will have a home on the new site.
  • A crawl of the live site. Record every URL with its title, description, H1, status code and internal links. Our redirect list started from the pre-launch sitemap and a migration crawl of what was already indexed.
  • Links from other sites. Search Console's Links report shows which pages other sites link to.

This becomes your list of pages that matter. A page with search clicks, links from other sites or leads attached to it needs a plan, even if it looks dated.

Which pages and content should you keep?

Keep anything that earns traffic, links or leads, unless you have a deliberate reason to change it. That doesn't mean keeping the old design. It means keeping the substance: the topic of the page, the content that answers the searcher's question, and a title and H1 that still match what people search for.

Where you can keep a URL, keep it. A page that stays at the same address with the same core content has the least to relearn. Where a path has to change, a 301 is what keeps the old address alive.

Sometimes a rewrite is worth the trade-off. On our own Astro rebuild we deliberately rewrote a lot of titles and copy, accepting that search engines would need to relearn those pages. If a page already ranks and brings in leads, keep its title and core copy unless you're willing to take that risk.

Where you merge pages, make sure the new page covers what the old ones did. Where you remove a page, decide if anything replaces it. If nothing does, Google says the old URL should return a 404 or 410 rather than redirect somewhere unrelated.

On one rebuild, a client's blog lived on a separate Wix site, which split the domain's authority. We moved every post into the Webflow CMS on the main domain, in under three weeks, and checked the export so nothing was lost in the move.

Carry the structured data across too. If the old pages had schema, such as organisation, service or FAQ markup, rebuild it on the new templates and check it still describes what's on the page. Google's guidelines say not to mark up content that isn't visible to readers. If you also want your pages to stay easy for AI assistants to quote, our answer engine optimisation work covers answer-first copy and markup generated from the visible page.

This is also where a redesign can improve things rather than just hold the line. Clearer service pages, better internal links and faster pages are all part of the same job. When Pinecone Agency rebuilt the Alum Works website from the ground up, search visibility was built into the structure from day one: a dedicated page for each service, and schema markup. The case study reports 151% more traffic in three months and 475% more leads year on year. Our Nealon Insulation case study reports going from 22 monthly Google clicks to over 5,500 a year after the rebuild, pairing a clean URL structure and local-business schema with dedicated service pages and educational articles.

How should old URLs be redirected?

Every URL that changes needs a permanent, server-side redirect to its closest new match. Google recommends HTTP permanent redirects such as 301 or 308, and says permanent redirects don't cause a loss in PageRank.

At cutover we had 16 redirect rules for pinecone.agency, written in the host's redirect file and again in the Worker that serves the site, and tested before the switch. The two copies have to stay in sync, because page requests are handled by the Worker. The map grew as old paths turned up. By 28 October 2026 it had 53 rules.

The first map is not the last one. In the first week we check Search Console's not-found report and add a 301 for any old URL that was missed.

The rules that matter:

  • One old URL, one closest new page. Don't send lots of old URLs to the homepage. Google says this can confuse users and be treated as a soft 404.
  • No chains. Redirect straight to the final page. If a chain can't be avoided, keep it short.
  • Include files. Images and PDFs that get traffic or links move too.
  • Keep them. Google recommends keeping redirects for as long as possible, generally at least a year.

Build the map in a spreadsheet: old URL, new URL, action (keep, redirect, merge or remove) and notes. If you're also leaving WordPress, our Moving off WordPress checklist goes through building that URL inventory, including the archive pages WordPress creates on its own.

On a redesign, that mapping and the pre-launch check are the same promise you'll find on our web design page.

What should you check on launch day?

Test the new site before the switch, then run the same checks on the live domain straight after:

  • Remove staging blocks. While you build, keep the test site out of search with noindex or a robots.txt block, and list exactly where they are. At launch, take them all off the live domain. On our move, the staging host stayed noindexed. Google lists forgetting this as a common site-move mistake.
  • Test every redirect in the map, and confirm each old URL lands on the right page in one hop.
  • Confirm the sitemap address. If the old site had a sitemap at a known URL, keep or restore that address. In the two days after our cutover we restored /sitemap.xml, the address the old site had used, and published a single sitemap file. Then submit the sitemap in Search Console.
  • Test structured data on your main templates and confirm it matches the visible page.
  • Check canonicals. Each new page should point to itself on the live domain, not to staging. For us, www stayed the canonical host, with the apex redirecting to it, and without a trailing slash.
  • Update internal links. Point links in your content and menus straight at the new URLs rather than relying on redirects.
  • Check Search Console verification. If you verified with an HTML file or a meta tag, make sure it carried across to the new site.
  • Submit every form and confirm the lead, email and tracking event all arrive. A few days after our move we restored the same Google tag container the old site had used, so analytics and ads tags were not left behind.

If only your hosting is changing and the URLs stay the same, Google has a separate, shorter guide: copy and test the site, remove any crawl blocks, switch DNS, then watch crawling in Search Console.

What should you watch in the first weeks?

Some movement is normal. Google says rankings can fluctuate while it recrawls a changed site, and that for medium-sized sites it can take a few weeks or more for the new URLs to replace the old ones in results. Larger sites take longer.

What to watch:

  • Not found errors in Search Console's Page indexing report. Fix each with a redirect to the right page. This is the report we check in the first week.
  • Clicks and impressions for the site, and for the pages in your baseline, compared against the weeks before launch.
  • Average position is a misleading number to watch straight after a move. A rush of new impressions, often on pages that have just been indexed, can pull the average down even when clicks hold.
  • Key events by landing page in your analytics, against the weeks before launch.
  • Links you control, such as your Google Business Profile, social profiles and ad landing pages. Update them to the new URLs.

Treat a steady drop in clicks on one page as a signal to check that page: its redirect, its content against the old version, and its title. A dip across the whole site in the first days is usually Google catching up.

Frequently asked questions

Will a website redesign affect SEO?

It can, if URLs, titles, descriptions or ranking content change without a plan. Planned well, a redesign keeps the pages that already earn traffic and gives search engines a clear path to the new ones. Expect some short-term movement while Google recrawls. Nobody can promise rankings will stay exactly the same.

How long do rankings take to settle after a redesign?

Google says it can take a few weeks or more for a medium-sized site's new URLs to replace the old ones in results, and longer for larger sites. Keep comparing clicks and impressions against your baseline over that period, rather than judging the first few days or leaning on average position alone.

Do we need a 301 redirect for every page?

For every URL that changes, yes, mapped to its closest new page. URLs you keep don't need one. A removed page with no replacement should return a 404 or 410, and unused URLs shouldn't all be sent to the homepage in one blanket rule. The first map is rarely complete, so check the not-found report after launch and add what was missed.

Should we change URLs in a redesign?

Only when the current structure is wrong for the new site. If a URL already ranks and still describes its page, keep it. Every URL you change needs a 301 and a period of recrawling before Google shows the new one.

How do you migrate a website without losing SEO?

Website migration SEO uses the same checks, plus the platform or domain cutover. Google's advice is to change one thing at a time where you can, because stacked changes make problems harder to trace. A domain change also needs a Change of Address request in Search Console. If you're moving off WordPress, our Moving off WordPress checklist covers the export and access work. Our guide to what drives the cost of a website covers how a migration changes the scope.

Sources

Google sources checked 20 November 2026.

Redesigning with Pinecone Agency

Pinecone Agency redesigns and rebuilds websites on the platform that suits the team running them, with old URLs mapped, redirects checked before launch and Search Console watched after it. Our SEO work covers the same migration and redirect protection when a redesign is already under way. We reply within one business day.

Book a discovery call

Want help with your project?

Tell us what you're building and we'll talk through the right approach.

Book a discovery call

Related reading

See how we approach Web Design