Website Redesign SEO and Migration Checklist: Keep Your Rankings

This checklist is for business owners planning a new website and for the developers and agencies building it. It covers redesigns on the same domain, moves to a new domain, platform changes such as WordPress to Next.js, and protocol changes such as HTTP to HTTPS. By the end you will know what to prepare before launch, what to check on launch day, and what to monitor afterwards so that a better-looking site does not become a quieter one.

Website redesign SEO: why traffic loss after redesign happens

Google ranks URLs, not companies. When a redesign changes the address of a page, deletes the page, strips its text down to a hero image and three bullet points, or removes the links that pointed to it from the menu, Google sees a new page with no history and an old page that has vanished. Rankings earned over years go with the old URL. The design itself is rarely the cause; the plumbing underneath it is.

The second common cause is a content cut. Designers like clean pages, so a service page that ranked with 900 words is rebuilt with 150. The ranking signals attached to the detailed text disappear along with it. A redesign that keeps every URL but halves the content on every page will still lose traffic.

How to keep rankings after a redesign

Four things must survive: the URL (or a 301 redirect to its replacement), the title tag and main heading, the body content that answers the search, and the internal links pointing to the page. If the redesign keeps those four, you can change colours, layout, fonts, images and platform freely. Treat the four as a contract with the developer and put them in the project scope in writing.

Staging site noindex: keeping the build out of Google before launch

A new site is usually built on a staging address such as a subdomain or a temporary hosting URL. If Google finds it, it indexes a duplicate of your business with a strange address, and on launch day the new site competes with its own copy. Block staging with HTTP basic authentication, which stops crawlers at the door; add a noindex meta tag on every page as a second layer; and do not rely on robots.txt alone, because a disallowed URL can still be indexed from external links.

What to do if the dev site got indexed

Search the staging domain in Google with the site operator to see what is indexed. If pages appear, add the noindex tag, keep the pages crawlable so Google can read the tag, and request removal of the staging domain through the Removals tool in a Search Console property for that staging domain. Once the real site launches, 301 redirect every staging URL to the matching live URL. Do not simply delete the staging site, because the indexed copies then linger as errors for months.

Redirect map: how to make one that catches every URL

A redirect map is a two-column sheet: old URL, new URL. Build it before the new structure is final, because it shows which old pages have no new home and forces that decision early. Pull the old URL list from four sources: the XML sitemap, a full crawl of the live site, Search Console's performance report filtered to the last 16 months, and the analytics landing-page report. The sitemap alone misses old blog posts, PDF files and pages that were unlinked but still ranking.

URL change redirects: the rules that matter

• Use permanent 301 redirects, one hop, from each old URL straight to the final new URL. Chains through an intermediate address leak signal and slow the page.
• Redirect to the closest equivalent page, not to the home page. Bulk redirects to the home page are treated as soft 404s and pass nothing.
• Keep old URLs for pages you are deleting on purpose only if a sensible replacement exists; otherwise let them return a proper 404 or 410.
• Redirect images and PDF files too if they rank or are linked from outside.
• Keep the redirects live for at least a year, and in practice forever; they cost nothing.

Old URLs 404 after redesign: how to find and fix them

After launch, open the Pages report in Search Console and look at the Not found (404) group, then crawl the old URL list from your map and check every response code. Any old URL answering 404 that had traffic or backlinks needs a redirect added the same day. Also check the site's own internal links: menus, footers and in-content links often still point at old addresses, creating a redirect on every click and a slow, leaky site.

Domain change SEO, HTTP to HTTPS and www to non-www

Moving to a new domain is the riskiest form of migration because the brand signal attached to the old domain has to be re-learned. Keep the URL paths identical on the new domain so that the redirect map is a single pattern, redirect every page one to one, verify both domains in Search Console and use the Change of Address tool, update the Google Business Profile website field, and keep the old domain registered and redirecting for years. Expect a temporary ranking dip of two to eight weeks even when everything is done correctly.

HTTP to HTTPS migration

HTTPS is a protocol change, not a content change, so it is the gentlest migration if done completely. Install the certificate, redirect every HTTP URL to its HTTPS twin with a 301, update the canonical tags, sitemap, internal links and schema to the HTTPS versions, and fix mixed-content warnings where images or scripts still load over HTTP. Add the HTTPS property in Search Console; the old HTTP property keeps showing historical data.

www to non-www

Pick one hostname and redirect the other to it with a 301 on every URL. Which one you choose does not affect ranking; having both live without a redirect does, because it splits every page into two indexed copies. Make sure the canonical tag, sitemap and schema all use the chosen version, and verify both versions in Search Console so you can see any traffic still landing on the wrong one.

WordPress to Next.js migration SEO

Moving from WordPress to Next.js is a platform change that usually brings speed gains, but it rewrites every URL pattern unless you plan otherwise. WordPress URLs often carry category paths, date paths, trailing slashes, tag archives and query-string search pages. Decide for each pattern whether the new site will keep it or redirect it, and configure the redirects in the Next.js config or at the hosting edge, not in a plugin that no longer exists.

Three WordPress habits need a deliberate replacement. Author, tag and date archives usually have no equivalent, so redirect the useful ones to a category hub and let the rest return 410. Image attachment pages should never have been indexed; redirect them to the post. And the meta titles, descriptions and schema that a plugin generated must be rebuilt in code, page by page, or the new site launches with default titles and loses the snippets that earned clicks. Our comparison of Next.js and WordPress for SEO covers what to expect after the move.

Migration schema markup and internal links

Schema markup during a migration

Structured data is the first thing lost in a rebuild because it is invisible on the page. Before launch, export the schema from the old site with the Rich Results Test on each template: Organization or LocalBusiness on the home and contact pages, Service on service pages, Product on product pages, Article and FAQ on blog posts, BreadcrumbList sitewide. Rebuild each one on the new templates with the new URLs, then test the staging version before go-live. Rich results in Search Console should show the same counts within a few weeks of launch.

Internal links during a migration

Internal links tell Google which pages matter. A redesign that moves the main services from the top menu into a mega menu that renders only on hover, or into a footer, drops their link weight overnight. Keep money pages one click from the home page, keep in-content links between related pages, and run a crawl of the staging site to confirm that no page is orphaned and no link points to a redirect or a 404.

New site launch checklist for SEO

The item most often skipped is removing the noindex tag on launch day. It is copied from staging along with everything else, and the new site goes live invisible. Check the page source of the home page and two inner pages within an hour of launch.

Post-migration monitoring for the first 90 days

Export the Search Console performance report by page for the 90 days before launch and keep it as the baseline. For the first two weeks after launch, check the Pages report, the 404 list and the sitemap status every day. From week three, compare clicks and impressions per page against the baseline each week. A sitewide dip of 5 to 15% in the first month is normal while Google re-crawls and consolidates signals; a dip that grows after week four, or a single page down more than 30%, points to a missing redirect, a content cut or a lost internal link, and is worth tracing to the exact URL. Rankings usually settle by week eight to twelve, and that is the point at which to judge the migration.

What we have seen on Rajkot and Gujarat redesigns

Most of the recovery work we do in Rajkot starts the same way: a business launched a new site in March, noticed the phone had gone quiet by May, and only then looked at Search Console. A pump manufacturer in Rajkot moved from a 2016 site with 140 product pages to a modern site with 40, with no redirects for the hundred that were dropped; organic traffic fell by about 55% and took four months to rebuild after we restored the pages that had been ranking and redirected the rest. A real estate developer in Ahmedabad changed domain to match a new brand and left the old domain to expire; the backlinks from property portals and news coverage pointed at a dead address, and we had to renew the domain and set up redirects before anything else could recover.

On the positive side, a kitchenware exporter in Rajkot moved from WordPress to Next.js with a 300-row redirect map, every product description carried over and schema rebuilt before launch. Organic clicks dipped about 8% in the first three weeks and were above the old baseline by week seven, with a page load that was three times faster. The difference between the two outcomes was the preparation, not the budget.

What this means for your business

Ask whoever is building your new site three questions before signing: where is the redirect map, which pages will keep their content, and who checks Search Console after launch. If the answers are vague, add an SEO migration scope to the project. On a typical business site of 50 to 300 pages that work is two to five days, which is cheap next to a quarter of lost enquiries.

Related reading and next step

• SEO audit checklist for a website in 2026
• Next.js vs WordPress for SEO
• Schema markup for a local business in India
• Website development in Rajkot
• SEO services in Rajkot

If you are planning a redesign or already seeing traffic fall after one, share the old and new URLs through the contact page or on WhatsApp and we will send a fixed quote for the redirect map, migration checks and 90-day monitoring.