Website Redesign Services in Mumbai
A website redesign in Mumbai costs ₹35,000 – ₹1,20,000 and takes two to four weeks. The design is the easy part. The part that decides whether the redesign helps or hurts your business is the migration: if URLs change and nobody builds a one-to-one redirect map, you lose the rankings, the traffic and the leads the old site had already earned — and it can take months to recover.
So the centrepiece of this page is not a portfolio. It is the full SEO-safe migration checklist we work through on every redesign, published in the open so you can hold any agency to it, including us.
Key takeaways
- The number one cause of traffic loss after a redesign is unmapped URLs. Not design, not content — redirects that were never built.
- Crawl and archive the old site before you touch anything. Once the old site is gone, the URL list, the content and the internal link structure are gone with it.
- Redirect one-to-one, never everything to the homepage. Bulk redirects to the homepage are treated as soft 404s and pass almost nothing.
- Expect a short dip. A well-executed migration usually stabilises within two to six weeks. A dip that keeps deepening past a month means something is broken, not “settling”.
- Sometimes you should not redesign at all. If the site converts and only looks dated, content and speed work often returns more than a rebuild.
On this page
Should you redesign at all?
A redesign is a real risk to an asset that currently works. Before spending the money, be clear which problem you are solving, because several common complaints do not need a rebuild.
| Symptom | Real cause, usually | Cheaper fix first? |
|---|---|---|
| “It looks old” | Dated typography, stock imagery, cramped mobile layout | Sometimes — a design refresh on the same structure costs less and carries no SEO risk |
| “We get no enquiries” | No traffic at all, or traffic with no clear lead path | Check Search Console first. If you have 40 visits a month, a redesign will not fix that — content and visibility will |
| “It’s very slow” | Bloated theme, plugin excess, uncompressed images, weak hosting | Yes — optimisation often gains 30–40 mobile PageSpeed points at a fraction of a rebuild |
| “It’s broken on phones” | Non-responsive or half-responsive theme | Rarely — this usually does justify a rebuild |
| “We can’t edit anything” | Hard-coded HTML, or two page builders layered over each other | Rebuild is usually correct; untangling costs more than replacing |
| “Our business changed” | Structure no longer matches what you sell | Rebuild — the information architecture is the problem, and that is structural |
| “Traffic fell after our last redesign” | URLs changed with no redirect map | Fix the redirects. Do not redesign again on top of an unresolved migration |
| “Google penalised us” | Usually not a penalty — often a technical issue or an algorithm update | Diagnose before rebuilding. A new design does not clear a real manual action |
We will tell you not to redesign when that is the right answer. If your site converts, loads reasonably and simply looks a few years old, you will usually get more return from publishing service pages that can rank and fixing your mobile speed than from a rebuild. A redesign that loses 40% of your organic traffic for two months is a real cost, even if the new site is prettier.
Redesign costs
| Scope | What it covers | Price (ex-GST) | Timeline |
|---|---|---|---|
| Design refresh | New look on the same structure and URLs — typography, colour, imagery, layout polish. No migration risk. | ₹35,000 – ₹55,000 | 2 weeks |
| Standard redesign | New design and new build, structure largely retained, full redirect mapping, speed and SEO work | ₹55,000 – ₹85,000 | 2–3 weeks |
| Redesign and restructure | New information architecture, one page per service, content rewritten, full migration | ₹85,000 – ₹1,20,000 | 3–4 weeks |
| Platform migration | Wix, Squarespace, GoDaddy builder or hand-coded HTML moved to WordPress with full redirect map | ₹50,000 – ₹1,20,000 | 3–4 weeks |
| Store redesign | eCommerce redesign with catalogue, product-URL and category migration | ₹1,20,000+ | 5–8 weeks |
| Migration recovery | Diagnosing and repairing a botched previous migration — URL recovery and redirect rebuild | ₹18,000 – ₹45,000 | 1–2 weeks |
Excludes GST, hosting and domain. Content rewriting is included in the restructure tier and quoted separately otherwise. The wider price ladder is on the website design cost in Mumbai page.
What actually goes wrong
In order of how often we see it when a client comes to us after a bad redesign:
- URLs changed, no redirects. Every old page returns 404. Every backlink pointing at those pages now points at nothing. Rankings collapse within days.
- Everything redirected to the homepage. Technically not a 404, but Google treats mass homepage redirects as soft 404s, so the effect is nearly identical.
- Content cut in the rewrite. A 1,400-word service page becomes 200 words of design copy. The page no longer answers the queries it used to rank for.
- Staging left indexable. The staging site gets crawled and competes with production, or worse, the live site launches with
noindexstill switched on from staging. - Internal links not rebuilt. The new site has a pretty menu and almost no contextual internal linking, so authority stops flowing to service pages.
- Title tags and meta descriptions reset to theme defaults, wiping the mapping that made pages rank.
- Schema dropped. Organization, LocalBusiness, breadcrumbs and FAQ markup all lost, so rich results disappear.
- Images renamed and alt text lost, ending whatever image-search traffic existed.
- HTTPS or www inconsistency introduced, creating duplicate versions of every URL.
- Analytics and Search Console never reconnected, so the traffic loss is invisible for six weeks.
Every one of these is preventable with a checklist. None of them is a design problem.
The SEO-safe migration checklist
Before you touch anything
- Full crawl of the existing site, exporting every URL with its status code, title, meta description, H1 and word count. This is the master inventory and nothing else can be done without it.
- Export Search Console data — 16 months of queries and pages. This tells you which pages earn clicks and must not be damaged.
- Export the top landing pages from analytics, ranked by sessions and conversions, so priority is based on value rather than guesswork.
- Pull the backlink profile and note which specific URLs have links pointing at them. Those URLs must keep working or be redirected precisely.
- Save the XML sitemap as it stands today.
- Archive the old site — full file and database backup, plus a saved copy of the HTML of important pages. Content you cannot retrieve later is content you will have to rewrite.
- Record current rankings for your priority keywords, so post-launch you are comparing against a baseline rather than a feeling.
- Record baseline Core Web Vitals, so you can demonstrate the redesign improved them.
- Note existing schema types present on each template.
- List the existing redirects already in place. Old redirect chains must be carried forward or collapsed, not silently dropped.
While building
- Keep URLs identical wherever there is no strong reason to change them. The safest migration is the one with no URL changes at all.
- Where URLs must change, map them one-to-one in a spreadsheet: old URL, new URL, redirect type, and a note on why.
- Carry the content forward, then improve it. Do not let a designer’s word count decide what a ranking page says.
- Preserve title tags and meta descriptions that are already earning clicks; rewrite only where there is a reason.
- Rebuild internal links, using the old site’s link structure as the starting point rather than starting from an empty menu.
- Reimplement schema on every template that had it — and add it where it was missing.
- Keep image filenames and alt text where possible; if images move, redirect the old paths too.
- Block staging from indexing with HTTP authentication rather than only
robots.txt, so there is no chance of it being crawled. - Match or improve every Core Web Vital, tested on mobile with throttling, before launch is even discussed.
- Test every form and integration on staging — including that submissions actually arrive in the inbox.
The pre-launch gate
| Check | Pass condition |
|---|---|
| Redirect map complete | Every URL in the original crawl either exists at the same address or has a 301 to its closest equivalent |
| Redirects tested | Each mapped URL returns a single 301 to a live 200 page — no chains, no loops |
noindex removed |
No page carries a staging noindex; robots.txt does not block the site |
| Canonical tags | Self-referencing and pointing at the correct protocol and hostname |
| One H1 per page | Verified across every template, not assumed |
| Titles and descriptions | Unique on every page, none left as theme defaults |
| Sitemap | Regenerated, containing only canonical 200 URLs |
| Schema | Validates, no duplicate business entities, no fabricated ratings |
| Forms | Submitted end to end, email received, spam protection working |
| Analytics | GA4 firing, conversions defined, Search Console property ready |
| SSL | Valid, HTTPS forced, no mixed-content warnings |
| Mobile | Checked on real devices, not only in a desktop browser’s responsive mode |
| 404 page | Returns a genuine 404 status and offers useful navigation |
| Backup | Old site archived and restorable, so rollback is possible within an hour |
Planning a redesign? Get the migration plan first
Send your current URL and we will tell you what your migration risk actually is — how many URLs are involved, which pages carry your traffic, and what has to be redirected.
Redirect mapping in detail
This is the deliverable that separates a safe migration from an expensive one. The rules we work to:
301, not 302
A 301 is permanent and passes ranking signals. A 302 tells Google the old URL is coming back, so it holds the old address in the index and the move never fully consolidates.
Closest equivalent, always
An old page about industrial flooring redirects to the new industrial flooring page — not to the services index and certainly not to the homepage.
No chains
Old URL → new URL. Not old → interim → new. Chains dilute signals and slow every request. Collapse pre-existing chains during the migration.
Retired content still needs a decision
If a page genuinely has no successor, redirect to the nearest relevant parent. If it has links and traffic, consider keeping it instead of retiring it.
Include non-HTML assets
PDFs, brochures and spec sheets are frequently linked from elsewhere. They need mapping just like pages do.
Handle protocol and host once
HTTP to HTTPS and non-www to www resolved at server level in a single hop, not layered on top of page redirects.
The map is a spreadsheet you receive, not something that lives only in a config file. You should be able to audit it yourself, and you should be able to hand it to anyone who works on the site later.
Launch day sequence
- Final backup of the old site, verified restorable.
- Deploy the new site with redirects already loaded, not added afterwards.
- Remove staging protection and any
noindex, then confirm by fetching a page and reading the response headers and source. - Force HTTPS, confirm the SSL certificate covers the final hostname.
- Spot-check redirects live — the twenty highest-traffic old URLs, by hand.
- Submit the new sitemap in Search Console and request indexing on the priority pages.
- Confirm GA4 is receiving data in real time before anyone goes home.
- Test the forms on the live site, because staging email settings and production email settings are frequently different.
- Run a full crawl of the new site looking for 404s, redirect chains, missing titles and orphan pages.
- Watch Search Console coverage daily for the first week.
The first 30 days after launch
A migration is not finished at launch. It is finished when the numbers have stabilised.
| When | What we check | What normal looks like |
|---|---|---|
| Day 1–3 | Crawl errors, 404 log, indexing status, analytics flowing | A small crawl-error spike as Google discovers the changes. Zero 404s on mapped URLs |
| Week 1 | Search Console coverage, impressions, any manual actions | Impressions may dip. Pages should be moving into “Indexed”, not “Excluded” |
| Week 2 | Rankings for priority keywords against the pre-launch baseline | Some volatility, beginning to recover |
| Week 3–4 | Organic sessions, conversions, Core Web Vitals field data | Traffic returning to or above baseline; vitals improved on the old site |
| Anything worse at week 4 | Full re-audit — redirect gaps, thin content, indexing blocks | Not normal. A continuing decline past a month means something is broken |
We keep the 404 log under active review for the first month, because it surfaces URLs the original crawl missed — pages linked from an old brochure, an email campaign, or a directory listing nobody remembered.
Types of redesign
Design refresh
Same structure, same URLs, new visual language. The lowest-risk option and often the highest return for a site that already performs.
Mobile-first rebuild
For sites built before responsive design was standard, or ones where mobile was clearly an afterthought. Most Mumbai traffic is mobile.
Restructure for search
Splitting a single crowded services page into one page per service so each can rank on its own query. The most common cause of a step change in organic traffic.
Platform migration
Wix, Squarespace, GoDaddy builder or static HTML moved to WordPress, with the full redirect map as the primary deliverable.
Speed-led rebuild
When a bloated theme and thirty plugins cannot be salvaged, and Core Web Vitals are costing you both rankings and conversions.
Migration recovery
Repairing someone else’s botched move — recovering the old URL list from archives and logs, and rebuilding the redirects that were never written.
Process and timeline
| Stage | What happens | Time |
|---|---|---|
| 1. Audit and inventory | Crawl, Search Console and analytics export, backlink review, ranking baseline, archive of the old site | 2–3 days |
| 2. Structure decision | New sitemap, page-by-page mapping, and the redirect spreadsheet drafted before any design work | 2–3 days |
| 3. Design on staging | Key templates designed and reviewed on a live staging URL you can open on your own phone | 4–7 days |
| 4. Build and content migration | Pages built, content carried forward and improved, internal links and schema rebuilt | 5–10 days |
| 5. Pre-launch gate | Every item in the checklist above verified and signed off | 1–2 days |
| 6. Launch | Deploy with redirects live, sitemap submitted, monitoring on | 1 day |
| 7. Monitoring | Daily for week one, then weekly to day 30, with a written report at the end | 30 days |
Frequently asked questions
How much does a website redesign cost in Mumbai?
₹35,000 – ₹55,000 for a design refresh on the same structure and URLs, ₹55,000 – ₹85,000 for a standard redesign with full redirect mapping, and ₹85,000 – ₹1,20,000 for a redesign that also restructures the site and rewrites content. Platform migrations run ₹50,000 – ₹1,20,000 and store redesigns start at ₹1,20,000. All excluding GST.
Will a redesign hurt my Google rankings?
It can, and that is the whole risk. Rankings are lost when URLs change without one-to-one 301 redirects, when content is cut in the rewrite, when title tags reset to theme defaults, or when a staging noindex ships to production. Executed with a proper migration checklist, a redesign typically causes a short dip that stabilises within two to six weeks, then improves.
How long does a website redesign take?
Two weeks for a design refresh, two to three weeks for a standard redesign, three to four weeks for a redesign with restructuring, and five to eight weeks for an eCommerce redesign. Add 30 days of post-launch monitoring before the project is genuinely closed.
What is a redirect map and why does it matter so much?
It is a spreadsheet listing every URL on the old site against its closest equivalent on the new one, with the redirect type. It matters because a URL that changes without a 301 loses everything it earned — its ranking, and the value of every backlink pointing at it. Redirecting everything to the homepage instead is treated by Google as a soft 404 and passes almost nothing.
Should I keep my existing URLs?
Yes, wherever there is no strong reason to change them. The safest migration is one with no URL changes at all. Change them only when the structure itself is the problem — for example splitting one crowded services page into separate pages per service — and then map every change one-to-one.
My traffic dropped after a previous redesign. Can it be recovered?
Usually yes. We recover the old URL list from archives, server logs, Search Console history and any surviving sitemap, then rebuild the redirects that were never written. Recovery work is ₹18,000 – ₹45,000 over one to two weeks. The sooner it is done the better, but even months later it is worth doing.
How long before traffic recovers after a migration?
Two to six weeks for a well-executed migration, with the dip shallowest in the first week if redirects went live at the same moment as the new site. If traffic is still declining at week four, that is not settling — it indicates a redirect gap, an indexing block or content that was cut, and it needs a re-audit rather than patience.
Can you redesign without changing my content?
Yes — a design refresh keeps structure, URLs and content and changes only the visual layer. It carries essentially no SEO risk and is often the right call for a site that converts but looks dated. If content is genuinely underperforming we will say so, but design and content are separate decisions and you can take them separately.
Do you redesign sites you did not originally build?
Most of our redesign work is exactly that. We audit what exists first — platform, theme, plugin stack, hosting, whether a previous developer still holds credentials — and tell you honestly whether a rebuild or targeted repair is better economics over two years.
What if the previous developer holds my domain or hosting?
Recovering control is the first task, before any design work. A domain can be transferred with the registrant’s authorisation, and hosting can be migrated to an account in your name using a backup. We have done this many times. Never start a redesign while someone else controls the domain.
Can you migrate from Wix, Squarespace or GoDaddy builder to WordPress?
Yes, at ₹50,000 – ₹1,20,000 over three to four weeks. Content and structure are rebuilt in WordPress and the critical deliverable is the one-to-one redirect map, because these platforms use URL patterns that WordPress does not replicate by default.
Will my new site be faster?
That is one of the explicit pass conditions before launch — the new site has to match or beat the old one on every Core Web Vital, measured on mobile with throttling, not on desktop broadband. We record the baseline before starting so the comparison is evidence rather than assertion.
Do I need to take the site offline during the redesign?
No. The new site is built on a separate staging environment protected from search engines, and your existing site stays live and taking enquiries throughout. The switchover is a single deployment on launch day, with the old site backed up so rollback is possible within an hour.
What happens to my Google Business Profile and reviews?
Nothing, as long as the domain stays the same — your profile and reviews are attached to the business, not the website. Update the website link in your profile after launch if any landing URLs changed, and check that the NAP details on your new site match the profile exactly.
Is ongoing SEO included in a redesign?
The on-page foundation is included: titles, meta descriptions, one H1 per page, heading structure, internal links, schema, sitemap, Search Console and GA4. Ongoing SEO — content published month after month, link acquisition, technical work over time — is a separate retainer, and we will be clear about which one you actually need.
Are you based in Mumbai?
No. Amezing Tech is based in Satara with a presence in Pune, and we handle Mumbai and MMR redesigns remotely — fixed written scope, live staging link you test yourself, scheduled review calls, and the redirect map delivered to you as a spreadsheet you can audit.
Redesign without losing what you have built
Every redesign we do starts with a crawl and a redirect map, and ends with 30 days of monitoring. Send your URL for an honest read on the risk.
Related reading
- Website design services in Mumbai — packages, process and coverage.
- Website design cost in Mumbai — the full price ladder and first-year totals.
- WordPress website design in Mumbai — the platform most redesigns land on.
- eCommerce website development in Mumbai — including store migrations.
- SEO site migration checklist — the technical version of this process.
- All our Mumbai resources — every guide and service page in one place.
