What a redesign actually is — same engine, new interface
New templates, navigation clarity, mobile behaviour, and performance on the same CMS and mostly the same URLs. Editors keep muscle memory. Content is curated, not retyped from PDFs.
It is the right move when WordPress (or Shopify) is healthy, backups exist, and the complaint is “it looks like 2018” or “the CTA is buried.”
Design systems beat homepage-only makeovers
If interior pages stay ugly, you did a hero. Redesign the components: header, cards, forms, footer. Homepages lie.
What a rebuild actually is — new engine or new IA
New stack, new hosting, new content types, or a URL scheme that matches how you sell now. You migrate meaning, not pixels. Old theme files are not an asset.
Rebuild when you cannot safely update, cannot add a service page without a developer, or the platform fights the job. That is a project, not a skin.
Rebuild is not a moral upgrade to React
Many rebuilds should stay WordPress or go static. Next.js is for ownership and product UX, not a trophy on the about page.
SEO and URL risk — the ranking you can donate in a weekend
Inventory every indexed URL worth keeping. Map 1:1 redirects. Keep titles that work. Launch with Search Console coverage checks.
Cosmetic slug changes (“/services/gst-return” → “/what-we-do/indirect-tax-poetry”) need a business case. Aesthetic URLs rarely outrank history.
Parallel run without two homepages
Staging on a protected host. Production cutover with DNS TTL planned. Do not leave the old site indexable on a second domain “just in case.”
When the CMS is the problem
Page-builder soup, 50 plugins, no updates, nulled theme — maintenance failed. Read WordPress maintenance. Sometimes you repair; sometimes you export content and install clean.
Wix or Squarespace lock-in with a growing blog or store is a platform problem. Use how to choose a platform as a second opinion, not a vibe.
Repair versus clean install on WordPress
Repair if the database and URLs are healthy. Clean install if malware or builder lock-in is the identity of the site. Do not “repair” malware with a new colour palette.
When the brand is the problem — and the CMS is fine
Logo, photography, tone, and offer changed; WordPress still edits well. That is redesign. Do not punish a working CMS for a stale brand.
If photography is WhatsApp screenshots of the factory floor, no theme will save you. Budget a shoot. It is cheaper than a stack change.
Rebrands that keep trust signals
GSTIN, address, and testimonials can survive a visual system. Stripping them because the new moodboard is “minimal” is how B2B bounce rates rise. See GST-ready trust.
Content inventory before anyone opens Figma
Keep, merge, kill, or rewrite — per URL. Founders skip this and then wonder why the rebuild took three extra weeks. Writers cannot design in a vacuum.
Salvage what ranks and what sales actually sends. Delete the 2016 “coming soon” blog. Quantity is not an asset if quality is spam.
PDF-only businesses still need HTML pages
If your “site” is a brochure PDF, you are not redesigning. You are finally building. Quote it as a new business website.
Cost comparison in India — polish vs migration labour
A redesign on a healthy install can sit near business-site bands if page count is stable. Rebuilds add content ops, redirects, and QA on two systems. Stores add catalogue remaps.
Compare three-year cost: fighting plugins monthly versus a clean ₹28,000–₹50,000 class project. Cheap paint on a hostage domain is not cheaper. Domain ownership: custom domain and email.
Do not buy custom from ₹50,000 to avoid writing copy
Engineering will not invent your services. Rebuilds fail for the same content reasons new sites fail.
Migration checklists that prevent silent 404s
URL map, analytics/ads pixels, forms to the current inbox, SSL, sitemap ping, WhatsApp widgets, and a post-launch crawl. Assign owners.
E-commerce: 301 product and collection URLs, or ads waste money on dead SKUs. Shopify migrations are data projects.
- Export content before touching DNS
- Redirect map reviewed by someone who sells
- Test forms on the new host with a real submission
- Keep old host billed until crawl is clean
Cutover night is not a design meeting
No colour debates at DNS time. Freeze 48 hours before. Keep a rollback: old host retained, TTL low.
When to stay and polish — the underrated option
If Core Web Vitals are fine, URLs rank, and editors cope, maybe you need better CTAs and mobile nav — not a rebuild. A focused UX pass plus SEO can beat a six-week spectacle.
Founder boredom is not a requirement. “I saw a Dribbble shot” is not a requirement. Conversion and maintainability are.
A two-week polish sprint we will actually sell
Header/footer, contact path, speed on a mid-range Android, and one lander for the live campaign. Then decide if a full redesign is still true.
How we decide on a Chennai discovery call
Admin quality, plugin/app list, backup restore, URL value, and whether the commercial job changed. We say polish, redesign, or rebuild — and which package floor it resembles.
Bring the brief using how to brief a website agency. Then Book a Consultation or Contact Us.
We will refuse a “refresh” that needs a rebuild
If malware or lock-in is the diagnosis, a colour swap is malpractice. We would rather lose a small invoice than inherit an incident.
Ready to automate one painful workflow?
Tell us your stack — n8n, Make, Zapier, WhatsApp, or Playwright. Chennai HQ · India delivery · reply within one business day.