To keep your rankings through a website redesign, treat it as a site move. List every existing URL, map each one to its new address, use permanent 301 redirects, carry over canonical tags, structured data and content, submit a new sitemap, and watch Search Console for several weeks after launch.
Why do rankings drop after a redesign?
Google ranks pages at specific URLs. A redesign often changes those URLs, removes content, or changes how the site is crawled, even when the business and the domain stay the same.
Google’s guide on how to move a site with URL changes covers any move that changes URLs, including changes to URL paths. Its advice is reassuring on one point: permanent redirects do not cause a loss in PageRank. The risk comes from the steps that get missed.
Google also recommends changing one thing at a time. If you can, avoid launching a new domain, a new platform and a new design on the same day, and time the launch for a quieter period.
Before launch: prepare
1. Record what you have
- Export every current URL. Google suggests pulling them from your sitemaps, server logs, analytics, content management system and the Links report in Search Console. Include images, videos and downloads such as PDFs.
- Save your current rankings, top landing pages and traffic so you have a baseline.
- Save a list of external sites that link to you.
2. Build the URL map
Create a spreadsheet with each old URL next to its new one.
| Situation | What to do |
|---|---|
| Page keeps the same URL | Nothing. Keep it identical, including trailing slashes. |
| Page moves to a new URL | Permanent redirect to the matching new page |
| Two pages merge into one | Redirect both to the combined page |
| Page is removed with no replacement | Return a 404 or 410 response |
Google warns against irrelevant redirects, such as pointing many old URLs at the home page. Each redirect should lead to the closest matching content.
3. Prepare the new site
- Canonical tags. Give each new page a self-referencing canonical tag. Google’s canonical URL documentation recommends absolute URLs and consistent signals, so do not name different canonical URLs in different places.
- Internal links. Update menus, footers and in-page links to the new URLs so they do not rely on redirects.
- Content. Carry over the titles, headings and body copy of pages that perform well. A page that loses its content has less to rank for.
- Structured data. Rebuild your schema markup in the new templates. Google’s structured data introduction recommends JSON-LD where your setup allows it, and suggests validating with the Rich Results Test during development. See schema markup for local business for what to include.
- Robots.txt and noindex. If your development site blocks crawling, Google advises preparing the production robots.txt file in advance and keeping a list of any noindex rules to remove at launch.
- Search Console. Verify the site, and make sure the verification method (file, meta tag or analytics) survives the rebuild.
- Speed. Test the new templates against Core Web Vitals before launch. Google’s Core Web Vitals page defines good as a Largest Contentful Paint within 2.5 seconds, an Interaction to Next Paint under 200 milliseconds, and a Cumulative Layout Shift below 0.1. Core Web Vitals for business owners explains each one.
During launch: switch over
Work through these in order on launch day.
- Turn on the redirects. Use permanent server-side redirects. Google’s redirect documentation says 301 and 308 status codes signal that a page has permanently moved and that the new URL should be treated as canonical. Temporary codes such as 302 do not send that signal. JavaScript redirects are a last resort.
- Avoid chains. Redirect each old URL straight to its final destination. Google says Googlebot can follow up to 10 hops, but advises keeping chains short, ideally no more than 3.
- Remove staging blocks. Confirm the live robots.txt allows crawling and that no leftover noindex tags remain. Note that robots.txt is not a way to keep a page out of Google. It controls crawling, and a blocked URL can still be indexed if other sites link to it.
- Check canonicals. Confirm they point to the new live URLs, not to the staging address.
- Test. Check a sample of redirects from every section of the old site. Google suggests the URL Inspection tool in Search Console for individual pages.
- Submit the new sitemap. Submit a sitemap of the new URLs in Search Console and remove the old one. Google’s sitemap overview notes that a sitemap helps discovery but does not guarantee that every listed URL will be crawled and indexed.
- If the domain changed, submit a Change of Address in Search Console for the old site. Google says this tool is for domain or subdomain changes, not for path changes or a move from HTTP to HTTPS.
Make sure your hosting can handle extra crawling. Google notes that crawl activity rises after a move because requests to old URLs are redirected to the new site.
After launch: monitor
Google’s guidance is to expect temporary ranking fluctuation while it recrawls. For a small to medium-sized site, it says most pages may take a few weeks to move, and larger sites take longer.
What to check each week
- Page indexing report. The Page indexing report shows which pages Google has indexed and why others are not. Watch for spikes in “Not found (404)”, “URL blocked by robots.txt” and “URL marked ‘noindex’”. Google’s help page notes that a drop in indexed pages without a matching rise in errors can point to new robots.txt rules, noindex tags or login requirements.
- Sitemaps report. Indexed pages should build up under the new sitemap.
- Performance report. New URLs should begin receiving impressions and clicks.
- Rich results. Google notes that structured data can break after deployment because of templating or serving issues, so check the rich result status reports.
- Core Web Vitals report. Google recommends this Search Console report for seeing how your pages perform. Compare it with your pre-launch baseline.
- Server logs and analytics. Look for unexpected errors and confirm traffic is arriving on the new URLs.
What to keep doing
- Keep the redirects in place. Google advises keeping them for as long as possible, generally at least one year.
- Fix every 404 that should have been a redirect, then add it to the map.
- Ask the owners of important external links to update them, and update your own profiles, listings and ad campaigns.
A redesign is also a good moment to make your content easier for AI answer engines to quote. How to get cited in AI search covers that side.
The short version
A redesign keeps its rankings when every old URL either stays the same or redirects permanently to its closest match. Prepare the URL map, canonicals, structured data and robots.txt before launch, switch redirects on and submit the new sitemap at launch, then monitor Search Console for several weeks. Keep the redirects for at least a year.



