October 08, 2026
Redesign your small business website when it stops doing its job, not when it starts looking old. The three signs that matter: enquiries have fallen while search traffic has not, you cannot change the site without paying a developer for every line, or it fails on a phone. Looks come fourth.
And a redesign only costs you rankings when addresses change without redirects, pages that ranked are dropped, or the new site is slower than the old one. Keep a redirect map, keep the content that earns traffic, and keep Search Console open for a month after launch, and the risk is a manageable one.
This article covers the signs that separate a rebuild from a refresh, how often a site should change, the effect on SEO, what a redesign costs in India, what to settle before design starts, and the step by step redirect work that carries your existing positions across.
A refresh and a rebuild are different jobs. A refresh keeps the structure and changes what sits inside it: new photos, rewritten copy, current prices, a colour or type change, a new team page. It is cheap and quick and it is the right answer more often than people expect.
A rebuild is needed when the structure is wrong. The signs are practical. You cannot add a page or a product without a developer. The site was built on a page builder that loads slowly and breaks when a plugin updates. There is no proper mobile layout, or the mobile layout hides half the content. There is no https. The CMS version is no longer supported and cannot be updated. The business has changed: you now export, you have a second product line, you serve a new city, and the site still describes the company from five years ago.
One more sign that decides it for most owners: the phone rings less. If your search traffic in Search Console is flat or growing but enquiries are falling, the site is losing people after they arrive, and that is a design and content problem a refresh may not reach.
Content: the moment a fact changes. A price, an address, a person, a product that is no longer made. Review every page once a quarter for anything that is no longer true. A site with a wrong phone number is worse than no site.
Software: monthly. Updates to the framework, plugins and PHP version are maintenance, not redesign, and they should happen whether or not the design changes.
Structure and design: most small business sites end up being rebuilt every three to five years, but the trigger should be the business, not the calendar. If the site is fast, honest and still brings enquiries at year six, leave it alone and spend the money on content.
Yes, in both directions, and the direction is up to you.
Rankings are attached to three things: the URL of each page, the content on it, and the links pointing at it from other sites. A redesign that changes URLs without redirects throws away all three at once. Google sees a new page with no history at the new address and a missing page at the old one, and the links from other sites now point at an error.
The other common damage is quieter. Pages that ranked get merged or dropped because they looked untidy. Titles get rewritten to sound better and lose the words people search for. Content gets shortened to fit a cleaner design. The staging site gets indexed, or the noindex tag that protected it is left on at launch. The new site loads slower than the old one because of a bigger theme.
Done well, a redesign improves SEO. A faster site, one page per keyword instead of one page for everything, proper headings, a sitemap that lists the images, and content written for the questions people type. Article 20 is the audit checklist to run on the old site before you start, so you know what you are protecting.
A rebuild costs about the same as a new site, because it is one. For a 5 to 10 page business website in India: a freelancer roughly 10,000 to 40,000 rupees, a small studio roughly 40,000 to 1,50,000, and an agency with strategy and content roughly 1,50,000 to 5,00,000 and above.
The range inside each band is wide for reasons you control. The number of unique page layouts matters more than the number of pages. Custom design costs more than a theme, and a theme is often why you are redesigning. Writing and photography add cost when the old site has none worth keeping. Migrating a large catalogue or years of blog posts is real work. Integrations such as a payment gateway, WhatsApp or an accounting system each add days. A redirect map for a large old site is its own task.
A refresh costs less because the structure stays, and it is usually quoted per page or per day. Article 01 goes through what moves a website quote from the bottom of a band to the top; the same list applies here.
Get these answered in writing before anyone opens a design tool. Most redesign problems begin as a question nobody asked.
What is the one thing a visitor must be able to do on a phone within a minute of arriving? Which pages earn search traffic today, from a Search Console export, and which pages actually produce enquiries? Which URLs, titles and content are staying exactly as they are? Who writes the copy, and by when? What integrations must keep working on day one: forms, payments, WhatsApp, a CRM? Which photos are worth keeping and which need reshooting? Is there a date the launch is tied to, such as an exhibition or a season?
The answer to the first question shapes everything else. A tile exporter's site exists to get a specification and packing detail in front of an importer. A clinic's site exists to get an appointment booked. Design for that, and the rest of the pages fall into order.
This is the redirect map, and it is the part of the job that has nothing to do with how the site looks.
1. List every URL on the old site. Crawl it, export the pages report from Search Console, and export landing pages from your analytics. Three lists, because each misses things the others catch.
2. Mark each URL as keep, merge or drop. Keep means the same page exists on the new site. Merge means its content moves into another page. Drop means it is going and nothing replaces it.
3. Map every old URL to a new one. One to one wherever possible. A merged page redirects to the page that absorbed it. A dropped page redirects to the closest relevant page, not the home page.
4. Use permanent (301) redirects, set up before launch and tested against the whole list, not a sample.
5. Keep the titles and H1s of pages that rank. Improve them later, one at a time, once the new site has settled.
6. Carry the content across whole. Cut it later if you must, after you can see what each paragraph was earning.
7. Protect the staging site with a password rather than a robots rule, and on launch day check that no noindex tag came along with it.
8. After launch, submit the new sitemap, check the 404 report daily for the first two weeks, and use URL inspection on your top pages to ask for a recrawl.
Our own relaunch is a useful warning. The day after it went live, 17 of our 28 pages sat at "Discovered, currently not indexed" in Search Console. The fix was a resubmitted sitemap, footer links to the new pages so the crawler had a path to them, and IndexNow to announce them. We also found that the case study pages copied whatever URL was requested into their canonical tag, so any link with a ?utm parameter created a duplicate, and that 17 page titles ran over 60 characters. All three were found because someone was looking that week.
Ask the studio or freelancer seven things, and treat a vague answer as a no.
Will I own the design files, the source code and the hosting, in my own name? Will you give me a redirect map, and will you test it? Do the same people who design the site build it, or is the design handed to someone else? Who writes the copy? Will you test on a phone over a throttled connection before launch? Is the quote fixed, with a timeline, before work starts? What happens in the month after launch?
At Asket Studio a redesign starts with a conversation, then a short written brief we prepare, then a fixed quote with a timeline, and nothing starts until the client has both. There are no templates; every site gets its own structure and visual system built from reusable components, designed and built by the same people. A focused 5 to 10 page site is usually 2 to 4 weeks of design and a similar stretch of development. At handover the client owns the Figma files, design system, prototype, source code, hosting and every credential, and can take it anywhere. The design service page describes the process and the portfolio has the redesigns we have done, each with the three phone responsive build image.
Not if every old URL redirects to its new home, the content that ranks is carried across, and the new site is at least as fast. Expect some movement for a few weeks while Google recrawls; that is normal and it settles.
Yes, almost always. The domain carries the history and the links. Change the domain only for a rename or a merger, and then treat it as a second redirect project on top of the redesign.
For a focused 5 to 10 page site, usually 2 to 4 weeks of design and a similar stretch of development, plus the time it takes you to supply content. Content arriving late is the most common reason a redesign overruns.
Yes. A common order is to rebuild the pages that earn traffic and enquiries first, on the same URLs, and follow with the rest. It costs a little more in total but the risk at any one moment is smaller.
Sign in with Google to join the conversation. We use it for your display name and nothing else, and your email address is never shown.
No comments yet. Sign in above to write the first one.