Ten Questions to Answer Before You Redesign an Indian Business Website

Website redesigns are where organic traffic goes to die. Not because redesigns are bad, but because they are almost always run as a design and development project with SEO invited to review the staging site a week before launch, at which point every decision that mattered has already been made.

The traffic loss is rarely dramatic on day one. It shows up over six to ten weeks as rankings drift down, and by then the agency has been paid and nobody connects the two events. Here are the questions worth forcing answers to before a single design file is opened.

1. Which pages currently bring traffic, and are they all in the new sitemap?

Export twelve months of Search Console data, sort by clicks, and take every URL that earned more than a handful. That list is non-negotiable. Any page on it that has no equivalent in the new site needs either a home or a deliberate decision to lose it.

2. Is every changing URL mapped to a 301?

Not a redirect to the homepage. A one-to-one map from old URL to the closest equivalent new URL, written as a spreadsheet before launch and tested after. Bulk redirects to the homepage are treated as soft 404s and pass nothing.

3. Are we changing the URL structure at all, and why?

Sometimes the answer is good - a genuinely better architecture. Often it is that the new CMS defaults to a different pattern and nobody questioned it. Changing URLs costs you ranking stability; it should be a decision, not a side effect.

4. What happens to the content?

The most common way an Indian business site loses rankings in a redesign is that the new design has less room for text, so 900-word service pages become 250-word pages with a hero image. The design brief should specify minimum content volume per page template, or the design will quietly set it for you.

5. Who owns title tags and meta descriptions in the new build?

New CMS, new templates, and suddenly every page title is the page name plus the brand. Twelve months of title optimisation gone in one deploy. These need to migrate as data, not be regenerated.

6. Will the new site render its content server-side?

If the rebuild is moving to a JavaScript framework, this is the single highest-risk item on the list. Content that only appears after client-side rendering is a gamble. Ask for server-side rendering or static generation for anything you need to rank, and test with a rendering tool before launch rather than after.

7. Is the staging site blocked from indexing - and is the block removed at launch?

Both halves fail regularly. Staging sites get indexed and compete with the live site; and a noindex or robots disallow left on at go-live can take weeks to notice. Check the live robots.txt and a sample of page sources within an hour of launch.

8. What is the internal linking plan?

Most redesigns simplify navigation, which sounds good and usually means important pages lose the internal links that were supporting them. Compare internal link counts to your top pages before and after. A page that dropped from fifteen internal links to two will fall.

9. How will we know if something broke?

Record the numbers before launch: indexed page count, clicks for the target keyword set, positions for the top thirty terms, and Core Web Vitals. Without a recorded baseline, the post-launch argument about whether traffic fell is unwinnable.

10. Who is watching for the first six weeks?

Someone needs to check Search Console coverage errors, crawl stats and rankings weekly after launch, with authority to get fixes prioritised. Most problems are cheap to fix in week one and expensive in month three.

The uncomfortable summary

A redesign is the riskiest thing a business does to its website, and the risk is almost entirely avoidable. The teams that come through without losing traffic are not the ones with the best developers - they are the ones who wrote the redirect map before the design was approved and refused to launch without it.

If a redesign is on your roadmap this quarter, getting an SEO expert in India involved at the brief stage rather than the staging stage costs a fraction of what recovering lost rankings does afterwards.

Related reading on why thin templates cap rankings: Thin Service Pages.