Website Redesign Checklist: 15 Things Mumbai Businesses Must Audit Before a Rebuild
You've already decided to redesign. That's the easy part. The hard part is not losing everything your current website earns you — rankings, leads, indexed pages — in the process. Most Mumbai businesses that lose traffic after a website redesign don't lose it because the new design is worse. They lose it because nobody ran an audit before the developers started building.
This is that audit. Fifteen things to check, document, and preserve before a single new page goes live — from content inventory to legal pages. Run through it before you brief your web design company, not after you've already signed off on wireframes.
Why a Pre-Redesign Audit Comes Before Design Work
A website redesign without a pre-build audit is a guess dressed up as a project plan. Every page, URL, and ranking on your current site represents work Google has already rewarded — and every one of those can break silently during a rebuild if nobody tracked it first.
Google's own migration guidance is explicit on this: when you move or restructure a site, a permanent 301 redirect is the mechanism it uses to carry ranking signals from an old URL to a new one — without a redirect map, that signal has nowhere to go. If you're already comparing the signs that say it's time to redesign against a full rebuild versus a lighter refresh, this checklist is the next step once that decision is made.
1. Build a Complete Content Inventory
Before anyone redesigns a single page, list every URL your current site has — every service page, blog post, category archive, and even orphaned landing pages from old campaigns. A spreadsheet with URL, page title, traffic (last 12 months), and top keyword per page is the minimum viable inventory.
Businesses around Dadar and Matunga running multi-location or multi-category sites (a chain of shops, a coaching institute with multiple course pages) tend to have the messiest inventories — pages added ad hoc over years, several near-duplicates targeting the same keyword. Catching that overlap now means your redesign can consolidate instead of multiplying it.
2. Pull Your Analytics and Search Console Baseline
Export 12 months of Google Analytics 4 and Google Search Console data before redesign work starts: sessions per page, conversions per page, top 50 landing pages by clicks, and current keyword rankings. This baseline is your proof of what "success" looked like before, so you can measure the redesign against a real number instead of a vague "it feels faster now."
Without this baseline, a traffic dip after launch is undiagnosable — you won't know if it's seasonal, algorithmic, or a redesign mistake. With it, you can pinpoint the exact page or keyword that dropped within days.
A pre-redesign audit starts with inventory and analytics, not design mockups.3. Map Every Old URL to Its New URL
This is the single most common cause of post-redesign traffic loss. If your new site changes URL patterns — folder structure, trailing slashes, or renamed slugs — every old URL needs a documented 301 redirect to its new equivalent before launch, not after someone notices rankings have vanished.
Build a two-column mapping sheet: old URL, new URL. Every single indexed page from your content inventory in step 1 needs a row. A Sion-based clinic or service business with location-specific pages is especially exposed here — losing even one indexed local page to a broken redirect can mean losing that page's specific ranking for months while Google re-crawls and re-indexes the replacement.
4. Preserve SEO Equity: Redirects, Canonicals, and Internal Links
Beyond the URL map itself, three things need explicit sign-off before launch: every redirect returns a real 301 (not a 302, not a JavaScript redirect, not a meta refresh), every page's canonical tag points to itself correctly on the new site, and internal links across the new site point to the final URLs — not to old URLs that then redirect, which wastes crawl budget and dilutes link equity.
Google's migration documentation states plainly that a 301 or 308 status code is how "Googlebot follows the redirect, and the indexing pipeline uses the redirect as a signal that the redirect target should be canonical" — get this wrong and your new pages start from zero instead of inheriting the old page's authority.
| Redirect Type | Passes SEO Equity? | When to Use It |
|---|---|---|
| 301 (permanent server-side) | Yes — Google's preferred signal | Every URL that changes permanently in the redesign |
| 302 (temporary) | No — treated as short-term, not canonical | Only for genuinely temporary redirects (rare in a redesign) |
| Meta refresh / JavaScript redirect | Weak — unreliable signal for Google | Avoid; use only if server-side redirects are impossible |
5. Audit Current Keyword Rankings Page by Page
Pull your top 20-30 ranking keywords from Search Console and note which page ranks for each. During redesign, every one of those pages needs either the same content depth and keyword targeting carried forward, or a documented reason it's being merged or removed. Don't let a copywriter rewrite a page that ranks #4 for a valuable keyword without knowing that keyword exists.
6. Audit Your Current Design System and Brand Assets
List every brand asset your current site uses that needs to survive the redesign: logo files (vector and raster), brand colours with hex codes, font licences, photography you own the rights to, and any custom icon sets. A redesign is also the moment to decide what's staying and what's being replaced — document that decision instead of leaving it to whoever builds the new templates.
7. Decide the Tech Stack Before Design Begins
WordPress, Shopify, a custom Next.js and Laravel build, or a headless CMS — the tech stack decision changes what's technically possible in the design, so it has to happen before, not during, the design phase. A business planning heavy content publishing needs different CMS capabilities than an ecommerce store needing fast checkout and inventory sync.
If you're still weighing options, our guide on WordPress vs. Next.js for a business website is a useful starting point, and our Next.js development and Laravel development pages cover what a custom-built stack actually involves.
8. Check Hosting, Domain, and DNS Readiness
Confirm domain ownership access (registrar login), current DNS records, SSL certificate status, and hosting renewal dates before redesign work starts. A redesign launch day is the worst possible time to discover nobody has the domain registrar password, or that an SSL certificate expires mid-project.
- Confirm who has registrar access and admin rights to DNS
- Document current DNS records (A, CNAME, MX, TXT) before any changes
- Check SSL certificate expiry and auto-renewal status
- Confirm hosting plan capacity matches the new site's expected traffic and media weight
9. Audit Legal and Compliance Pages
Privacy policy, terms of service, refund policy (for ecommerce), and cookie consent banners often get forgotten in a redesign because they're low-traffic pages nobody thinks about — until a customer or a payment gateway partner asks for them. Carry these forward exactly, updating only the company details and any genuinely outdated clauses, and get sign-off before launch rather than treating them as an afterthought.
10. Audit Every Form and Third-Party Integration
List every form on your current site — contact, enquiry, newsletter signup, quote request — and what happens after submission: which email it sends to, which CRM it feeds, which WhatsApp number gets notified. Every one of those integrations needs to be rebuilt and tested on the new site before launch, not discovered broken after the first missed lead.
URL redirects and form integrations are the two most common points of silent failure after a redesign.11. Record a Page Speed and Core Web Vitals Baseline
Run your current top 10 pages through PageSpeed Insights and record their Core Web Vitals scores — Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift — before redesign work starts. Google's own documentation confirms these metrics are part of what "our core ranking systems seek to reward," which makes this baseline a real business number, not a vanity metric.
Set a rule with your developer that the new site must not regress below the old site's Core Web Vitals scores on any of these three metrics. Our Core Web Vitals guide for Mumbai business owners breaks down what each metric measures if your team needs the fuller explanation.
12. Audit Mobile Experience and Accessibility
Load your current site on an actual phone and check tap-target sizes, form usability, and whether WhatsApp/call buttons are reachable with a thumb. Note anything genuinely working well on mobile today so the redesign doesn't accidentally regress it while chasing a new look. A quick accessibility pass — alt text on images, colour contrast, keyboard navigation — costs little to check now and far more to retrofit after launch.
13. Map Every Conversion Path
Document how a visitor currently becomes a lead or a sale on your site — the exact click path from homepage to enquiry form, or product page to checkout. A redesign that changes navigation without preserving what's already converting is a common way businesses accidentally reduce enquiries even while traffic holds steady.
14. Benchmark Against Two or Three Direct Competitors
Pull up two or three competitor sites in your category and note what they do that yours doesn't — faster load time, clearer pricing, a better booking flow. This isn't about copying; it's about making sure your redesign brief includes fixing gaps you can actually see, not just a fresh coat of paint on the same weaknesses.
15. Plan Analytics and Tracking Continuity
Confirm your GA4 property, Search Console verification, and any ad-platform pixels (Meta, Google Ads) will carry over to the new site with zero gap in data collection. Set up GA4 events on the new site before launch, test them in a staging environment, and verify Search Console still recognises the domain the day the new site goes live — a tracking gap during launch week is data you can never recover.
Not sure where your current site stands before you brief a redesign? Get a full technical and SEO audit first.
Request a free website auditPutting This Checklist to Work Before You Brief Your Designer
Run through all fifteen items and hand the resulting documents — content inventory, URL map, analytics baseline, integrations list — to your web design company as part of the brief, not as an afterthought once wireframes exist. A website development company that receives this upfront can plan the build around preserving what already works, instead of reverse-engineering it after launch when something breaks.
If you've already launched a site recently and want the equivalent list for go-live day itself, our website launch checklist for Mumbai businesses covers the final pre-launch and go-live steps that follow after a redesign is built.
Ready to start your redesign the right way, with nothing lost in the move?
Talk to our team about your projectFrequently Asked Questions
What is the most important thing to check before a website redesign?
The most important pre-redesign check is your URL structure and redirect map. If your new site changes any URLs without a documented 301 redirect from every old URL to its new equivalent, you risk losing indexed rankings that took months or years to build. Content inventory and analytics baseline come immediately after, since you need both to know what's actually worth preserving.
Will I lose my Google rankings if I redesign my website?
Not if you preserve SEO equity correctly. Google's own guidance confirms that a permanent 301 redirect passes ranking signals from an old URL to its new equivalent, so a redesign with a complete, tested redirect map and unchanged core content typically keeps rankings intact or sees a temporary dip that recovers within weeks. Rankings are lost when redirects are missing, broken, or use a temporary 302 instead of a permanent 301.
How long should a pre-redesign audit take for a small business site?
For a typical small business site with 20-50 pages, a thorough audit covering all fifteen items in this checklist usually takes 3-5 business days when done properly, including pulling analytics exports and building the URL map. Larger sites with hundreds of pages, or ecommerce sites with many product URLs, can take one to two weeks.
Should I redesign on the same domain or migrate to a new one?
Stay on the same domain whenever possible. A domain migration adds an entirely separate layer of SEO risk on top of a redesign, and Google treats domain changes as a much bigger signal disruption than a URL structure change on the same domain. Only migrate domains for a genuine legal, business-name, or brand reason — never purely for a redesign.
What happens to my Google Analytics data if I redesign my website?
Your historical GA4 data stays tied to your existing property regardless of a redesign, as long as you keep using the same GA4 property ID and don't create a new one. The risk is a tracking gap: if new tracking code isn't correctly installed and tested before the new site launches, you can lose days or weeks of data during the transition. Test every GA4 event on staging before go-live to avoid this.
