A redesign loses rankings when URLs, content or indexing settings change without a plan. To protect traffic, record your current rankings and pages first, map every old URL to its closest new URL with a 301 redirect, make sure no staging noindex or robots.txt block reaches the live site, carry over titles, headings and structured data, test speed on real devices, and watch Search Console closely for several weeks after launch. Expect some temporary movement while Google reprocesses the site.
A redesign is only risky when something search engines rely on changes
A purely visual refresh, with the same URLs, the same content and the same indexability, carries little search risk. Trouble starts when paths and slugs change, pages are merged or deleted, navigation is rebuilt, content is rewritten, or the site moves to a new platform that renders pages differently. Google's own guidance on site moves also warns that combining a move with a redesign of content and URL structure will probably cause some traffic loss, because Google has to reassess the pages.
The practical rule from that guidance is to change as few things at once as you can. If you must change platform, design and URLs together, plan for it explicitly and monitor harder.
A step-by-step checklist for founders and marketing leads who are rebuilding or replatforming a website and want to keep the search traffic it already earns.
Before you build: take a baseline
Export the list of pages that currently get organic traffic and impressions from Google Search Console and your analytics, along with the queries they rank for. Run a crawler over the existing site to get every live URL, its title, headings, canonical tag and status code. Save this as a spreadsheet. It becomes your redirect map, your content checklist and the before-picture you compare against after launch.
Mark the pages that earn leads, not only traffic: service pages, location pages and the articles that bring enquiries. These get the most careful treatment. Pages with no traffic, no links and no purpose can be retired, but decide that on purpose.
Map every old URL to a new one
For each old URL decide one of three things: it stays at the same address, it moves to a new address that covers the same topic, or it is retired. Moved pages need a permanent 301 redirect from the old address to the closest equivalent new page. Retired pages should point to the nearest relevant page, not by default to the homepage, which search engines can treat as a poor match.
Point redirects straight at the final address. If A redirects to B and B redirects to C, update the rule so A goes directly to C. Check trailing slash and www variants, and remember images and downloadable files that other sites may link to. Google's help pages suggest keeping redirects in place for a long time, at least 180 days for a domain move and longer if you still see visits through them, so do not remove them after a few weeks.
Launch-day technical checks
Staging sites are usually set to noindex or blocked in robots.txt so that they do not appear in search. Vendors report that this setting is regularly carried onto the live site by mistake, and it can remove a site from search results within days. Open the live robots.txt, view the page source of several key pages for a noindex tag, and use the URL inspection tool in Search Console to confirm that Google can fetch them.
Then confirm the basics survived: each page has one clear title and meta description, a single H1, a self-referencing canonical tag, an updated XML sitemap submitted in Search Console, and analytics tags that fire. If the old site had FAQ, organisation or local business structured data, carry it over, and make sure it still matches what is visibly on the page. If your new site is a React single-page app, check what a crawler sees in the raw HTML, because pages that render only after scripts run can be indexed late or incompletely.
Speed, mobile and content: do not trade them away
New designs often add large images, sliders, animation libraries and tracking scripts. Google's Core Web Vitals measure real visits: a good result is largest content paint within 2.5 seconds, interaction to next paint within 200 milliseconds and layout shift of 0.1 or less, assessed at the 75th percentile of visits. Test on a mid-range phone over a normal mobile connection, because that is what many Indian visitors use, and not only on a fast office laptop.
Keep the content that earned the rankings. Shortening service pages to make them look cleaner, or hiding detail behind tabs and carousels, can remove the very words that matched buyer queries. If you are rewriting, keep the answers, FAQs and headings that people were already finding.
After launch: monitor for six to eight weeks
Check Search Console daily in the first week, then weekly. Watch the page indexing report for new errors, the crawl stats for spikes in 404 responses, and the performance report for your key pages against the baseline. Crawl the live site again and fix redirect chains, broken internal links and missing pages as they appear.
Small movement in rankings in the first weeks is normal while Google recrawls. A sharp drop that starts on launch day and affects organic search but not other channels usually points to a redirect, noindex or crawl problem that you can fix. Agree before the project starts who is responsible for this monitoring, and ask for it in writing, so a launch does not end the agency's involvement the day the site goes live. GreenMindAI builds websites with this launch checklist in scope, and makes no promise about specific rankings.
Common questions
Not necessarily. If URLs, content and indexability stay the same, the risk is low. Rankings drop mainly when URLs change without 301 redirects, content is thinned out, or a noindex or robots block reaches the live site. Some temporary movement is normal while Google reprocesses the pages.
A 301 is a permanent redirect from an old URL to a new one. It sends visitors and search engines to the replacement page and helps Google understand that the page has moved. Without it, old addresses return errors and the page's search history is lost.
Google's help pages say to keep redirects for at least 180 days after a domain move, and longer if you still see traffic coming through them. For most business sites it is simplest to keep them permanently.
It is safer to separate them. Google advises changing as little as possible at once, and warns that combining a move with a content and URL redesign will likely cost some traffic. If you must do both, test carefully and monitor closely.