A redesign goes live. Two weeks later the phone stops ringing. The organic rankings look roughly intact, but the business has dropped out of the local pack for its main service terms in its own neighbourhood. This happens often enough in Mumbai that I now treat it as the default risk of any redesign for a local business.
The causes are boring and almost entirely preventable.
1. The NAP block moved into an image or a script
Designers love a clean footer. A clean footer often means the address is now rendered by JavaScript, or baked into a graphic, or collapsed into an accordion that never opens for a crawler.
Your name, address and phone number need to exist as plain, crawlable text on the page. Not in a widget. Not in an SVG. Plain text, in the same format as your Google Business Profile, character for character. "Andheri East" and "Andheri (E)" are two different strings to a matching algorithm.
2. Location pages got consolidated
The redesign brief said "reduce page bloat." Six location pages became one "Areas We Serve" page with a list. Every locality-level relevance signal the site had accumulated went with them.
If those pages were thin, the answer was to make them substantive, not to delete them. A Mumbai business serving Andheri, BKC, Lower Parel and Thane needs pages that say something specific about serving each of those areas — travel time, local case examples, the kind of buildings or businesses there. A list of pin codes is not a page.
3. The URLs changed and the redirects are partial
Nine times out of ten there are redirects. They just don't cover everything. The old blog paths redirect, the old service paths redirect, and the old location paths quietly 404 because nobody put them in the mapping spreadsheet.
Export every URL Google has indexed before the migration — Search Console's Pages report, plus a crawl of the live site, plus the sitemap — and reconcile that list against the new site one URL at a time. Anything without a 301 to a genuinely equivalent page is a signal you've thrown away.
4. Embedded map and review widgets were dropped
The old site had a Google Maps embed and pulled in review snippets. The new one has neither because they "slowed the page down." Those were corroborating signals tying the page to a physical place. Losing them won't tank you on its own, but combined with the three problems above it compounds.
If page speed was the concern, lazy-load the map on interaction rather than removing it.
5. The site got faster for desktop and slower for a Mumbai phone
Core Web Vitals field data is collected from real users. In Mumbai, a meaningful share of those users are on mid-range Android devices on congested networks. A redesign that ships a heavier JavaScript bundle can improve lab scores while making real-world LCP worse.
Check the field data in Search Console, not the lab score in Lighthouse. They disagree more often than people expect.
The pre-launch checklist that prevents all of this
Before any redesign goes live for a local business:
- Crawl the old site, export every indexed URL, build a complete redirect map, and test it against the staging environment.
- Confirm the NAP block renders as text with JavaScript disabled, and matches the Google Business Profile exactly.
- Confirm every location and service page that exists today still exists tomorrow, at the same URL or with a 301 to a true equivalent.
- Confirm LocalBusiness schema survived the template change and still validates.
- Take a ranking snapshot — local pack and organic — for your top twenty terms, by locality, the day before launch. Without a baseline you can't tell a drop from normal volatility.
- Keep the old sitemap accessible for a few weeks so Google can discover the redirects quickly.
After launch
Resubmit the sitemap. Request indexing for the priority pages. Then watch the local pack specifically, not just organic positions — they move independently and a local business usually feels the pack first.
Most redesign recoveries I've handled took four to eight weeks once the underlying cause was fixed. Nearly all of them would have taken zero weeks if someone had run the checklist above.
Deepak Bhardwaj — I work with businesses across Mumbai on exactly this kind of migration risk; you can find my approach at Deep Bhardwaj.
Related reading: Mumbai SEO by neighbourhood.