Export every URL you have
From Search Console, analytics and a full crawl. Use all three, because each misses things the others catch. This single step prevents the most expensive redesign failure there is.
Delhi NCR
Website redesign checklist so you keep what you already have.
Redesigns fail in predictable ways and almost all of them are preventable in an afternoon of planning before anyone designs anything.
Overview
Before anyone designs anything
Before a redesign, export every indexed URL and every page's traffic, identify what is ranking and must be preserved, and build a redirect map. On launch day check redirects, robots directives, tracking and forms. Skipping the URL export is the single most common cause of a post-redesign traffic collapse.
Identify what is working
Which pages earn traffic, which earn enquiries, which have inbound links. Those must survive the redesign, even if they are untidy. Designers reasonably want to trim, and the untidy pages are often the earning ones.
Record your baseline
Traffic, rankings, conversion rate and page speed before you change anything. Without a baseline you cannot tell afterwards whether the redesign helped or hurt, and everyone will have an opinion.
Decide what problem you are solving
Conversion, speed, mobile, maintainability, or just that it looks dated. If the answer is only the last one, be careful, because redesigns chasing appearance sometimes reduce conversion.
Agree the redirect map early
Every existing URL mapped to a destination, built as a spreadsheet before development finishes rather than during launch week.
Keep the old site accessible
Full backup, and keep the old hosting live for at least a month. If something turns out to have been missed, having the original saves considerable time.
What to avoid
Launch day and after
| Check | Why |
|---|---|
| Every redirect tested individually | Syntax being valid is not the same as working |
| No noindex left from staging | The classic silent disaster |
| robots.txt allows crawling | Blanket disallow blocks everything |
| Canonicals point at live URLs | Not at staging |
| Forms submit and deliver | Test from a phone, check spam |
| Analytics and conversions fire | Otherwise you are blind |
| Sitemap updated and submitted | So the new structure is discovered |
| Coverage watched daily for two weeks | Catch problems while they are small |
Launch mid-week, never Friday, so the people who can fix problems are available for the next few days.
Detail
Ask these four before you commit
| Ask them | A good answer sounds like | Walk away if |
|---|---|---|
| How long until we can edit it ourselves? | From handover, with training included | Send us your changes |
| What does month two cost? | A number, before you sign | We can discuss that later |
| Can you show a Core Web Vitals score? | Real numbers on a live URL | Our sites are all fast |
| Can I open three live examples? | URLs you can check yourself | Screenshots and a PDF |
The month-two question separates firms that build assets from firms that build invoices.
FAQ
Common questions
What is the most common redesign mistake?
Not exporting existing URLs before starting. Pages that ranked return 404s on the new site and the traffic goes to a competitor. It is entirely preventable and it is the most expensive failure in this category.
Will a redesign hurt my rankings?
It can, and it does not have to. Damage comes from missing redirects, removed content and unnecessary URL changes rather than from new visuals. With a complete redirect map and preserved content, rankings usually hold or improve.
Should I keep content that looks untidy?
If it earns traffic or has inbound links, yes. The untidy pages are frequently the earning ones, and cutting them for design reasons is the second most common cause of post-redesign traffic loss.
How long does recovery take if something goes wrong?
With correct redirects, expect two to six weeks of fluctuation then a return to previous levels. If traffic has not recovered after two months, the usual causes are missed redirects or content that was removed.
When should we launch?
Mid-week, in the morning, when whoever can fix problems is available for the next few days. Friday launches mean any issue lives all weekend, and something always comes up.
What should we check in the first fortnight?
Search Console coverage daily, landing page traffic against the same period before launch, and any page that dropped to zero, which almost always means a missed redirect.
Next step
Every redirect tested individually?
Send us the brief and we will tell you which part is the real problem. No call required to get a number out of us.