Picture a Saturday evening in Indore. Someone in Vijay Nagar types "cake shop near me" into their phone. Three bakeries appear in a little box with a map, stars and opening hours. They tap the second one, call, and walk in twenty minutes later.

There might be a better bakery two streets closer. It never had a chance, because it wasn't in the box.

That box is called the local pack, and for a huge number of small businesses it is now the front door. Not the website, not the signboard: the three results Google shows before anyone scrolls. This guide is about how a business gets into it. The examples are from Indore because that is where we work, but nothing here is specific to one city. A dentist in Pune, a florist in Leeds and a gym in Toronto are playing exactly the same game.

What Google is actually looking at

Google is unusually open about this. Its own help page for business owners says local results are based mainly on relevance, distance and prominence. Those three words explain almost everything you see on the map.

Distance is the one people get stuck on. You can't move your shop closer to every customer, and you shouldn't try (more on fake addresses later). The good news is that the other two are where most businesses are leaving points on the table, and both are within reach.

Start with your Google Business Profile

If you only do one thing after reading this, do this. Your Google Business Profile is the listing that appears on Maps and in the local pack. It's free, and it is one of the most neglected free things a small business has.

Open yours and check, honestly:

1. Is the name your real name? Exactly what is on your signboard and your bills. Adding keywords, like "Sharma Sweets Best Mithai Shop Indore", is against Google's guidelines and can get the listing suspended. It's tempting. Don't.
2. Is the primary category right? This one choice does more for relevance than anything else on the profile. A "Wedding photographer" and a "Photographer" are not shown for the same searches. Pick the most specific category that is true, then add secondary ones for the other things you genuinely do.
3. Are the hours correct, including holidays? Few things lose a customer faster than driving to a shop Google said was open. Update them for Diwali, for Sundays, for the week you're away.
4. Is the phone number one somebody answers? A number that rings out tells Google nothing, but it tells the customer everything.
5. Have you listed your services or products? Each one is another chance to match a search.
6. Are there real photos? Your actual shopfront, your actual work, your actual team. A customer looking at the map is trying to picture walking in. Help them.

If you don't come to the customer's location (a plumber, a caterer, a videographer), you can set a service area and hide your address. That is allowed, and it's better than inventing a shopfront.

Reviews: the part you can't fake

Reviews feed prominence, and they also do something no ranking factor can: they convince the person reading them. A four-star average with a hundred honest reviews will usually beat a perfect five with six.

What works is boring and consistent. Ask every happy customer, at the moment they're happiest. Make it easy: a short link or a QR code at the counter, sent on WhatsApp after the job is done. Then reply to reviews, the good ones briefly and the bad ones carefully. A calm, specific reply to a one-star review is read by every future customer who scrolls past it, and it often does more for you than the five-star ones.

What doesn't work, and can get your profile penalised: buying reviews, writing them yourself, offering a discount in exchange for one, or asking only the customers you know are happy while quietly steering the unhappy ones away. Google's policies forbid all of these, and customers are better at spotting them than most owners think.

A review isn't a score. It's a stranger telling the next stranger what it was like to deal with you.

Say the same thing everywhere

Search engines cross-check. If your Google profile says "Shop 4, Palasia", your JustDial listing says "Near Palasia Square", your Facebook page has an old phone number and your website has none at all, Google has four slightly different stories about you and fewer reasons to trust any of them.

The fix is unglamorous: write down one exact version of your business name, address and phone number, and make every listing match it. Your website, Google, Bing Places, Apple Business Connect (iPhone users search through Apple Maps), and whichever directories matter in your trade, whether that's JustDial, IndiaMART, Sulekha or Practo. You don't need to be on fifty directories. You need to be accurate on the ones your customers actually use.

Where your website comes in

A lot of local businesses ask why they need a website when they have a Google profile and an Instagram page. Fair question. Here is the honest answer: the profile gets you onto the map, and the website is often what Google reads to decide what you're relevant for, and what the customer reads to decide whether to call.

A website that helps local search does a few specific things:

It has a page for each thing you sell

If you do bridal makeup, party makeup and makeup classes, that is three pages, not one page with a list. Each page can answer the real questions someone has about that service: what it includes, roughly what it costs, how long it takes, what to bring. A page that answers those questions properly is relevant in a way a bullet point never will be. Our piece on how search engines understand a website goes deeper into why.

It says where you are, in words

Your full address and phone number as real text, in the footer of every page, not inside an image. The areas you serve, named naturally ("we deliver across Vijay Nagar, Bhawarkuan and Rau") rather than as a block of place names stuffed at the bottom. An embedded map on the contact page.

It tells Google the facts in Google's own format

Structured data is a small block of code that states your business type, address, hours and phone number in a form search engines read directly. For a local business the relevant type is LocalBusiness. Visitors never see it. Search engines rely on it.

It loads fast on a phone, on mobile data

Most "near me" searches happen on a phone, often outside, often on a patchy connection. If your site takes eight seconds to appear, the customer is already looking at the next result. We wrote about why speed matters in more detail, but the short version is: test your site on your own phone, on mobile data, and be honest about what you see.

It sounds like you, in the words customers use

People search the way they talk. In Indore that often means a mix of Hindi and English, "AC repair near me", "mehendi artist Indore", "best poha near Rajwada". You don't need to stuff these in. You do need to describe what you do in the words a customer would use, not the words on your trade licence.

If you serve more than one city

This is where a lot of well-meaning businesses get into trouble. The temptation is to copy your services page twenty times and change the city name: "Web Design in Indore", "Web Design in Bhopal", "Web Design in Ujjain", each one identical apart from a single word.

Google calls these doorway pages and treats them as spam. A page for a city is worth having only if it has something genuinely different to say: a real branch with its own address, work you have actually done there, information that only applies to that place. If it doesn't, one strong page that mentions the areas you serve will do better than twenty thin copies.

The same applies if your customers are global. A studio in India can win clients in Dubai or London, and plenty do. You don't get there by pretending to have an office you don't. You get there with work that is good, a site that clearly explains what you do and who it's for, and proof from real projects.

Things that don't work (and a few that backfire)

• A fake address or a virtual office in a better area. Google verifies addresses and removes listings that fail. Customers who turn up to an empty office don't come back.
• Keywords in your business name. Covered above, but it bears repeating because it is so common.
• Buying reviews or links in bulk. Cheap at first, expensive later.
• Paying someone who promises "rank one in 7 days". Nobody can promise that, and the ones who do usually get there by breaking the rules on your behalf.
• Setting up the profile and forgetting it. Hours change, phone numbers change, photos go stale. A profile that was last touched three years ago looks like a business that was last open three years ago.

A one-week plan for any local business

You don't need an agency to do most of this. Here is a week of small tasks, roughly an hour each:

The website part (separate service pages, structured data, speed) is where most owners need help, and it's the part we do. But the first five days are free, and they are often where the biggest gains are hiding.

"How much for a website?" is a question with a real answer, just not a single one. It's a bit like asking what a house costs. The answer depends less on the number of rooms than on where it is, what it's built from, who designed it and how long you want it to last.

This guide explains where the money in a website goes, what the typical price bands look like in India right now, and, most usefully, how to compare proposals that look nothing alike.

A word on the numbers first. There's no reliable public survey of Indian website pricing, and we'd rather not invent one. The ranges below are indicative: the kind of figures commonly quoted for each type of provider at the time of writing. Treat them as a way to orient yourself, not as a market rate card. Your city, your deadline and your industry will all move them.

The short version: price bands by type of provider

Each band overlaps the next, and there are excellent freelancers charging studio prices and agencies charging freelancer prices. The type of provider tells you less than what the proposal actually includes.

Why two ten-page websites can cost ₹60,000 and ₹6 lakh

This is the part that confuses most people, so it's worth being concrete.

Imagine two proposals for the same brief: a ten-page site for a manufacturing business in Indore.

Proposal A takes a premium WordPress theme, sets your colours and logo, pastes in the text you supply, adds stock photography, installs a contact form plugin and an SEO plugin, and launches in three weeks. Around ₹60,000 is a fair price for that work.

Proposal B starts with two workshops about who buys from you and why. It rewrites your service descriptions from scratch, plans a product photoshoot at your plant, designs a type system and page layouts for your business specifically, builds the site to load quickly on a mid-range phone, sets up analytics that track real enquiries, and includes a round of testing with people who resemble your buyers. It takes three months. Around ₹6 lakh is a fair price for that work too.

Both are ten pages. They are not the same product. One is a website; the other is a website plus the strategy, content and craft that make a website work. Neither is a scam. The question is which one your business needs, and it isn't always B.

Where the money in a website actually goes

When a studio quotes ₹5 lakh, the page count is a small part of the calculation. The hours go roughly here:

Discovery and strategy

Understanding the business, the buyers, the competitors, and what the site has to achieve. On a premium project this can be 10–20% of the budget. On a cheap project it's zero, which is often the single biggest difference between the two.

Content

Writing, editing and structuring what the site says. This is the most underestimated line in almost every website budget. If you supply finished copy, the cost goes down. If you supply rough notes and expect them to become persuasive pages, someone has to do that work. Professional photography and video sit here too, and can easily be a third of a premium budget on their own.

Design

Typography, layout, visual direction, how each type of page is composed, how it adapts to a phone. A template-based site uses a design someone else made once for thousands of businesses. A custom design is made once for yours. Custom design also covers the small decisions that most separate a premium site from an average one: the type, the spacing, the photography, the way things move.

Development

Building it. A template install might be a few days. A custom build, with performance budgets, accessibility, animation and a content management setup tailored to your team, takes weeks. Integrations with CRMs, booking systems, ERPs or payment gateways add to it. Animation and interactive work add more, because they have to be built carefully to avoid making the site slow.

Testing and launch

Checking across devices and browsers, performance testing, accessibility checks, redirects from old URLs so you don't lose search traffic, analytics configuration. Easily skipped, expensive to skip.

Project management

Someone has to run the timeline, the feedback rounds and the decisions. On a larger project this is real time, and it's in the price whether or not it's a line item.

The costs that come after launch

A website's price isn't only its build cost. Budget for these as well:

GST applies on top of professional fees, at 18% for most design and development services at the time of writing. It is worth checking whether a quote includes it.

What pushes a quote up (and what doesn't)

Things that genuinely add cost:

• Custom design rather than an adapted template.
• Content creation: copywriting, photography, video.
• Animation and interaction built to perform well.
• Integrations with other systems: CRM, inventory, bookings, payments.
• Multiple languages, each needing its own content and testing.
• Ecommerce, especially with many products, variants or custom checkout rules.
• Tight deadlines, which mean people working in parallel or out of hours.
• Accessibility and performance targets written into the scope.

Things that add less than people assume:

• Extra pages that reuse an existing layout. The tenth case study page costs far less than the first.
• Blog functionality, if the CMS already supports it.
• Contact forms, unless they feed into another system.

How to compare proposals that don't look alike

This is where most businesses go wrong. Not by paying too much or too little, but by comparing a ₹60,000 proposal and a ₹6 lakh proposal as if they described the same thing.

A few questions that make proposals comparable:

1. Who writes the content? If it's you, how much time will that take, and is that time really free?
2. Is the design custom, or a template adapted to your brand? Both can be fine. They're not the same thing.
3. What happens on a phone? Ask to see previous work on your own phone, on mobile data.
4. How fast will it be? A serious provider will talk about performance targets. A vague "it'll be fast" is a flag. Our article on website speed explains what to ask.
5. What's the platform, and who can edit it? WordPress, a hosted builder, a custom build. Each has trade-offs covered in custom website vs WordPress.
6. What's included after launch? Bug fixes, training, a support period?
7. Who owns what? Make sure you own the domain, the hosting account and the code or content, not the agency.
8. What does basic SEO include? Titles and descriptions, redirects, sitemap, structured data, clean markup. See how search engines actually understand a website.
9. Can you speak to past clients? Not testimonials on their site, but actual people.

If a proposal can't answer these clearly, the price isn't really comparable to one that can.

So which should you choose?

It depends on what the website has to do. A few honest rules of thumb:

• If you're just starting out and need something credible online next month, a good freelancer or a well-used builder is often the right call. Spend the difference on your product.
• If your website is where buyers form their first impression, because you sell high-value services, compete on trust or pitch to larger clients, the strategy and content in a premium build usually pay for themselves.
• If you're somewhere in between, a small agency with a strong portfolio in your sector can be the best value.

What rarely works is paying a studio price for template work, or expecting studio outcomes from a template budget. The second trap is the more expensive one, because the cost shows up later: in a rebuild, in lost enquiries, or in a site nobody can maintain.

The right budget is the one that matches what the website has to do, not the one that matches the number of pages.

Most business owners' idea of SEO was formed around the time it was mostly about keywords. Put the phrase you want to rank for in the title, repeat it a few times on the page, get some links, and wait. That picture wasn't entirely wrong then. It's badly out of date now.

Modern search engines try to understand pages the way a knowledgeable person would: what is this about, who is it for, is it any good, and is it the best answer to this particular question? Everything that follows is an attempt to explain how they get there, without the jargon.

Step one: crawling, or can they find it?

Search engines discover pages with automated programs called crawlers, which follow links from pages they already know about to pages they don't. Google's own explanation of how search works is short and worth reading.

For a business site, crawling fails in a few predictable ways:

• Pages nobody links to. If a page only exists in your sitemap, or is only reachable through a search box or a form, crawlers may never find it or may treat it as unimportant.
• Links that aren't really links. A menu built from elements that respond to clicks with JavaScript, rather than proper <a href> links, can be invisible to crawlers. Google's guidance on crawlable links is explicit about this.
• Accidental blocks. A robots.txt rule or a "noindex" tag left over from a staging site. This is more common than it should be, and it can quietly remove a whole site from search.

A sitemap, a file listing your pages, helps search engines find everything, but it's a hint, not a substitute for good internal links.

Step two: indexing, or do they understand it?

Once a page is found, the search engine reads it and decides what it's about and whether to store it. This is where most of what used to be called "on-page SEO" lives, but it's broader than keywords.

Text that exists as text

Search engines read text far more reliably than they interpret images. A headline baked into a picture, or a services list that only exists inside a slideshow, is much harder to understand. Real text in real HTML is the foundation.

Structure: headings and semantic HTML

A page has an outline, like a document. One main heading (<h1>) saying what the page is, then section headings (<h2>, <h3>) in a sensible order. HTML also has elements that say what things are: navigation, main content, articles, lists, tables. When a site uses them properly, both search engines and assistive technology like screen readers can understand the page's shape. When everything is a generic box styled to look like a heading, that meaning is lost.

Titles and descriptions

Each page's title tag is still one of the strongest signals of what it's about, and it's usually the blue link people see in results. The meta description doesn't directly affect ranking, but it's often the snippet under the link, so it affects whether people click. Every page should have its own of both.

Entities, not just words

Search engines increasingly think in terms of entities, meaning specific things like a business, a place, a product or a person, and the relationships between them. They don't only notice that a page contains the words "web design Indore"; they try to work out that it's a page from a particular company, located in a particular city, offering a particular service.

You help by being consistent: the same business name, address and description everywhere, and pages that clearly describe one thing each.

Structured data

Structured data is a way of labelling information on your page in a standard vocabulary (schema.org) so search engines don't have to guess. You can state that this page is an article, published on this date, by this organisation; or that this business is located here and has these social profiles. Google explains it in its introduction to structured data.

Two cautions. Structured data doesn't guarantee any special appearance in results. And it must describe what's actually visible on the page. Marking up reviews you don't display or FAQs that aren't there is against Google's guidelines and can lead to penalties.

Step three: ranking, or is it the best answer?

When someone searches, the engine picks from everything it has indexed and orders the results. Nobody outside the search companies knows exactly how, but the broad principles are public.

Intent comes first

Every search has an intention behind it. "Website cost India" is someone researching budgets. "Web design agency Indore" is someone looking for a provider. "What is INP" is someone who wants a definition. A page that matches the words but not the intention won't rank well for long. A pricing guide won't rank for "web design agency", and a services page won't rank for "how much does a website cost". Nor should it.

This is why the most useful SEO question isn't "which keywords?" but "what is this person actually trying to find out, and is this page the best answer to it?"

Helpfulness and trust

Google publishes guidance on creating helpful, reliable, people-first content. The gist: content should be written for people, demonstrate real knowledge or experience, be accurate, and not exist mainly to attract search traffic. Useful self-assessment questions in that document include whether the content provides original information, and whether someone would bookmark it or recommend it.

Links from elsewhere

Links from other sites are still a significant signal, a kind of reference. But quality matters far more than quantity. A mention from a respected industry publication or a local business association is worth more than hundreds of links from directories nobody reads. Buying links or trading them in bulk breaks Google's spam policies and can backfire.

Page experience

Speed, mobile usability and a secure connection all play a part. They help at the margins, particularly when several pages are equally relevant; they won't lift an irrelevant page. We go into this in why website speed matters.

Internal linking and topical authority

This is the part of SEO most within a business's control, and the most often neglected.

Internal links, the links between your own pages, tell search engines which pages matter and how they relate. A service page linked from the homepage, the menu and several relevant articles is clearly important. A page linked from nowhere is not.

Topical authority is the idea that a site demonstrating depth on a subject is more credible on it. One article on website pricing is a page. A set of articles that covers pricing, platforms, performance, search and redesign, each linking to the others where it genuinely helps the reader, is a body of knowledge. That's the thinking behind how this blog is organised, and why the articles link to each other where it's relevant rather than at random.

What a business can actually control

You can't control Google's algorithm. You can control a surprising amount of what it sees:

1. Technical foundations: crawlable links, a correct robots.txt, a sitemap, fast pages, one clear URL for each page, proper redirects when URLs change.
2. Structure: sensible headings, semantic HTML, text as text.
3. Metadata: a unique, accurate title and description for every page.
4. Structured data: describing your business and content accurately.
5. Content that answers real questions: one clear purpose per page, written for the person searching.
6. Internal links: connecting related pages in ways that help readers.
7. Consistency: the same business name, address and description everywhere, including your Google Business Profile.
8. Patience: new sites and new pages take time to be trusted.

Notice how many of those are decided when a site is built. SEO added after launch is often retrofitting what should have been designed in, which is one reason the platform matters when you choose between a custom build and WordPress.

Common SEO myths worth dropping

• "Repeat the keyword a set number of times." There's no magic density. Write naturally about the topic.
• "More pages means more traffic." Many thin, similar pages can hurt more than they help.
• "Meta keywords matter." Google has ignored the meta keywords tag for many years.
• "SEO is a one-off project." It's closer to maintenance: content, links and technical health all need tending.
• "We guarantee first-page rankings." Nobody can honestly guarantee that. Google itself warns about SEOs who do.

And a newer one: AI-powered search features and answer engines haven't replaced these fundamentals. They still rely on pages that are crawlable, clearly structured, specific and trustworthy. If anything, they reward those fundamentals more, because an answer engine can only quote what it can read and trust.

Search engines are trying to read your site the way a careful customer would. Build for that reader and you've built for both.

This question comes up in almost every website conversation, usually phrased as a verdict waiting to be delivered. Is WordPress outdated? Is custom development worth it? The honest answer is that both are good tools for different jobs, and most of the regret we hear about comes from using one for the other's job.

We should declare an interest. Our own site, and most of the marketing sites we build, are custom and static. So we'll try to be especially fair to WordPress, which for a lot of businesses is the right answer.

First, what the options actually are

"Custom versus WordPress" is really four or five choices.

WordPress (traditional). The most widely used content management system on the web. You get an admin panel for editing pages and posts, a huge library of themes and plugins, and a large pool of people who know how to work with it. The site is assembled by the server on each request, usually from a theme, plugins and a database.

Hosted website builders. Wix, Squarespace, Webflow, Shopify for shops. You rent the platform; hosting, security and updates are handled for you. Easy to start, constrained by what the platform allows, and you don't fully own the underlying site.

Custom static sites. Built with a modern framework and published as ready-made files. There's no database or server-side code for each visit, which makes them very fast and removes a whole category of security risk. Content can live in code, in files, or in a CMS.

Headless CMS. A content management system (such as Sanity, Contentful, Strapi, or WordPress itself used "headlessly") that only stores and edits content. A separate custom front end displays it. You get friendly editing and custom design and speed, at the cost of more moving parts.

Custom applications. Portals, dashboards, booking systems, marketplaces: products rather than marketing websites. These are a different decision, and neither WordPress nor a static site is usually the answer.

The comparison, honestly

Where WordPress genuinely wins

When lots of people edit lots of content. A publisher, a school, a business with a busy news section or a large resource library: WordPress's editing experience is mature, familiar and hard to beat for the cost.

When budget is tight and speed to launch matters. A good theme, sensibly customised by a competent developer, can produce a perfectly respectable site quickly.

When you want to be able to change provider easily. Because WordPress is so widespread, it's easy to find someone to take over the site. That's a real form of security for a business.

When you need a plugin that already exists. Event listings, membership areas, multilingual content, simple shops. There's usually a mature plugin, and building the same from scratch would cost far more.

Where WordPress struggles

Speed, in practice. WordPress can be fast. Many WordPress sites aren't, because they're built with heavy page builders, bundled themes and a dozen plugins, each adding scripts and database queries. Keeping it fast takes discipline and good hosting. See why website speed matters for what that involves.

Maintenance. WordPress core, themes and plugins release updates regularly, many of them security fixes. A WordPress site that nobody updates becomes a liability. Outdated plugins are one of the most common ways sites get compromised. Budget for maintenance, or don't choose it.

Distinctive design with page builders. Drag-and-drop builders make editing easy and design sameness likely. A custom theme avoids this but costs more, which narrows the price gap with custom builds.

Where custom builds genuinely win

Performance. A static site serves ready-made files from a CDN. There's very little to slow it down, which makes good Core Web Vitals much easier to reach and keep.

Security and upkeep. With no database or admin panel exposed on the live site, there's far less to attack and far less to patch. A marketing site can sit for months without needing an update.

Design and interaction. Nothing is constrained by a theme's assumptions. If the site's job is to make a strong impression, as it usually is for studios, premium brands and high-value service businesses, that freedom matters.

Clean foundations for search. Full control over HTML, structured data, metadata and URLs, as covered in how search engines understand a website.

Where custom builds struggle

Editing, if it isn't planned for. A purely code-based site means every text change goes through a developer. That's fine for a site that changes a few times a year, and frustrating for one that changes weekly. The answer is either a headless CMS or an honest agreement about how updates will happen.

Dependence on a capable developer. Fewer people can work on a custom build than on WordPress. Make sure the code is clean, documented and yours, so another competent developer could pick it up.

Upfront cost. Custom design and development cost more at the start. Lower maintenance and hosting costs recover some of that over a few years, but not always all of it. Our guide to website costs in India breaks this down.

Ecommerce and complex applications

For shops, the choice is usually different again. Shopify handles payments, inventory, taxes and security for you and is a very sensible default for most small and mid-sized stores. WooCommerce (WordPress's ecommerce plugin) gives more control and needs more care. A fully custom store makes sense mainly for unusual catalogues or checkout rules, or for brands where the shopping experience itself is the differentiator.

For applications such as client portals, booking systems and internal tools, you're building a product, and should choose a stack for that product. Trying to stretch a marketing-site CMS into an application is a common and expensive mistake.

A decision framework

Instead of asking which is better, answer these five questions:

1. Who will edit the site, and how often? Several non-technical people, weekly: favour WordPress or a headless CMS. One person, a few times a year: custom static is fine.
2. What does the site have to do? Mainly impress and generate enquiries: custom is often worth it. Mainly publish lots of content: WordPress or headless. Sell products: usually Shopify or WooCommerce. Run a service: build an application.
3. How much does speed and distinctiveness matter to your market? If you compete on perceived quality, lean custom.
4. Who will maintain it, and is that budgeted? WordPress without maintenance is a risk. Custom without a reliable developer is a different risk.
5. What's the three-year cost, not the launch cost? Include hosting, licences, maintenance and likely changes.

A few typical outcomes:

• A consultancy with a handful of service pages and occasional case studies: custom static, possibly with a light CMS for case studies.
• A school or association publishing news weekly: WordPress with a well-built custom theme and a maintenance plan.
• A premium brand with a growing library of stories and products: headless CMS with a custom front end.
• A new small shop: Shopify, with a customised theme.

The right platform is the one that fits how your business will actually use the site in two years, not the one that won the argument.

Ask someone why their website needs redoing and the answer usually arrives as a feeling. It looks old. It doesn't feel like us any more. A competitor launched something and ours suddenly looks tired.

That feeling is worth taking seriously, because visitors have it too. But it is also a poor guide to what to change. When you pull it apart, the thing people are reacting to is almost never the one they name first.

"Outdated" is usually a symptom, not a style

Web design does have fashions. Heavy drop shadows, carousels on every homepage, stock photos of handshakes. You can date a site to within a few years by looking at them. So it is tempting to think the fix is to swap the old fashion for the current one.

The trouble is that fashions are the most visible layer and the least important one. A site built five years ago in a style that has since gone out of favour can still feel perfectly current if it is clear, fast and honest about what the business does. A site launched last month in this year's style can feel stale on arrival if it says nothing specific.

What visitors actually read as "old" is closer to neglect. The signs are small and they add up:

• A copyright line two years behind.
• A "latest news" section whose latest item is from before the pandemic.
• Services listed that the business no longer really offers, and the one it now makes most of its money from missing.
• Team photos of people who left.
• A contact form that sends somewhere nobody checks.

None of those is a design problem. All of them make a site feel abandoned, and abandoned reads as outdated.

The seven things that actually age a website

When a business site feels tired, the causes tend to be the same handful. Roughly in the order they matter:

1. The message is vague

"We deliver innovative solutions for your business needs" could be a bank, a plumbing contractor or a software firm. If the first screen doesn't say what you do, for whom, and why someone should pick you over the obvious alternative, the site feels generic, and generic is the fastest way to feel dated, because it was already vague when it was built.

A useful test: cover your logo and ask whether the headline could belong to a competitor. If it could, it isn't doing any work.

2. It is slow on a phone

Most sites are designed on a large monitor with a fast connection and reviewed the same way. Visitors, a lot of the time, are on a mid-range phone on mobile data. A homepage can look polished in a meeting room and feel sluggish in someone's hand because a large hero image, several font files and a pile of scripts all have to arrive before anything responds.

Slowness reads as age. We go into why, and what to do about it, in why website speed matters more than most businesses think.

3. The typography is doing nothing

Default system fonts at default sizes, body text in a light grey that is hard to read, headings barely larger than paragraphs. Type is most of what a visitor looks at on a website, and when it has no hierarchy the page reads as a wall. Good typography is the single cheapest way to make a site feel considered.

4. The photography is someone else's

Stock photography of smiling people in meeting rooms is instantly recognisable, and the recognition carries a message: this business did not have anything of its own to show. Real photographs of your people, your space, your product or your work, even modest ones, outperform glossy stock on credibility almost every time, because they are evidence.

5. The navigation mirrors the org chart

Menus that read "About / Divisions / Verticals / Resources / Media" are organised around how the company sees itself. Visitors arrive with a question: can you do this, have you done it before, what does it cost, how do I get in touch. Navigation built around those questions feels modern regardless of what it looks like.

6. It doesn't work the same everywhere

A layout that was made "responsive" by squeezing the desktop design until it fits is still a desktop design. Tiny tap targets, text that needs zooming, a menu that covers the page and can't be closed. These are what people mean when they say a site feels old on mobile.

7. It feels like a template

There is nothing wrong with templates as a starting point. The problem is the site that is visibly one: the same hero, the same three icon boxes, the same testimonial slider as thousands of others. It signals that nobody made decisions about this particular business, and visitors pick up on that even if they couldn't tell you why.

Why a new colour scheme rarely fixes it

Here's a pattern worth knowing about before you commission anything. A business decides the site looks dated. A redesign is scoped as a visual refresh: new palette, new fonts, a new hero image. The old pages are carried over, the old copy is pasted in, the old structure is kept because "the content is fine". Six months later the new site feels exactly as flat as the old one.

It happens because the visual layer was never the problem. The copy still doesn't say anything specific. The pages still answer questions nobody asked. The photography is still borrowed. The site is still slow, now with a heavier design on top.

A redesign that only changes how the site looks will be outdated by the time it launches, because it was never about how it looked.

A redesign that works starts somewhere less glamorous: with what the site is for, who it's for, and what a visitor needs to see before they'll trust you.

How to tell whether you need a redesign at all

Not every tired site needs rebuilding. Some need a weekend of editing. Before spending money, it helps to be honest about which kind you have.

If most of your symptoms sit in the first three rows, you probably don't need a new website. You need to update the one you have, rewrite what it says, and speed it up. That's cheaper and often more effective.

If your symptoms are in the last three rows, a repaint won't hold. The structure itself no longer fits the business.

What a redesign that works actually changes

When a site genuinely needs rebuilding, the order of work matters more than the look. The approach we'd recommend, whether or not you work with us:

1. Decide what the site is for. Generating enquiries, supporting sales calls, recruiting, selling directly. Each leads to a different site. "All of the above" usually leads to a site that does none of them well.
2. Write the message before designing anything. The headline, the one-sentence description of what you do, the three or four things a buyer needs to believe. Design is much easier and much better when it's given something specific to say.
3. Structure around the visitor's questions. What do you do, have you done it for someone like me, how does it work, what does it cost or how is it priced, how do I start.
4. Collect real evidence. Your own photographs, actual project examples, specific numbers you can stand behind. If you don't have them, getting them is part of the project.
5. Then design. Typography, layout, imagery, motion. This is where a site starts to feel like yours, but it can only express what the first four steps gave it.
6. Build it to be fast. Speed is much cheaper to design in than to retrofit.

That is also, roughly, the order in which a redesign should be budgeted. Most of the value is in the first four steps, which are also the ones most often skipped. If you are pricing a redesign, what a premium website costs in India breaks down where that money actually goes.

The honest version of "modern"

A modern website isn't one that uses this year's gradients. It's one that loads quickly, reads clearly on whatever screen it's on, says something specific, shows real evidence, and feels like a particular business made it on purpose.

Sites like that age slowly. The visual style will date eventually, but a clear, fast, honest site with dated styling still does its job. When the time comes, refreshing its look is a small project rather than a rebuild.

If your site feels old, it is worth working out which of those qualities it's missing before deciding what to change. Often it's fewer than you'd think.

Every business owner who has approved a website has seen it at its fastest: on a good laptop, on office Wi-Fi, usually after visiting it a dozen times so most of it is already cached. That is the one situation almost none of your visitors will ever be in.

Your visitors are on phones. Often mid-range phones, several years old, on mobile data that drops from 4G to something slower as they walk between rooms. They've never been to your site before, so nothing is cached. They clicked from a search result, and if nothing useful appears quickly, they go back and click the next one.

Speed is part of the impression, not a technical detail

People don't experience "page load time" as a number. They experience it as a feeling about your business. A site that appears quickly and responds instantly feels competent. A site that shows a white screen, then a spinner, then text that jumps as an image pops in above it, feels careless, even if the design, once it arrives, is excellent.

That's why we'd argue speed belongs in the design conversation, not only the engineering one. The loading experience is the first thing anyone sees, so it is part of the design whether anyone designed it or not.

How speed is actually measured

"Fast" is vague, so it helps to know the measurements that matter. Google's Core Web Vitals are the most widely used:

Google assesses these at the 75th percentile of real visits, so it's not enough for the site to be fast for your best-connected visitors.

Two tools are worth knowing:

• PageSpeed Insights shows both lab data (a simulated test) and, if your site has enough traffic, field data from real Chrome users. The field data is the truth; the lab score is a diagnostic.
• Lighthouse, built into Chrome's developer tools, runs the same kind of lab test locally and lists specific problems.

A Lighthouse score is useful but easy to over-read. A 95 in the lab doesn't guarantee a good experience for real users, and chasing the last few points is rarely the best use of money. The Core Web Vitals for real visitors are the numbers to care about.

Does speed affect Google rankings?

Somewhat, and it's worth being precise. Google's documentation says Core Web Vitals are used by its ranking systems, but also that great page experience doesn't override relevance: a fast page with the wrong content won't outrank a slower page with the right answer. Treat speed as something that helps you compete when content is comparable, and as something that affects every visitor you do get. Don't expect it to move rankings on its own, and be wary of anyone who promises that it will.

Where the time actually goes

When a business website is slow, it's rarely the server. It's usually the weight and number of things the page asks the phone to download and run.

Images and video

The most common culprit by far. A photographer delivers a 6000-pixel-wide image, it gets uploaded as-is, and every phone downloads several megabytes to display it at 400 pixels wide.

Fixes that make the biggest difference:

• Serve modern formats like WebP or AVIF instead of large JPEGs and PNGs.
• Serve different sizes to different screens (the srcset attribute does this).
• Give every image its width and height so the layout doesn't jump when it arrives. This is most of what fixes CLS.
• Lazy-load images below the fold, but not the main hero image; lazy-loading your LCP image makes it slower.
• For background video, show a small still image first and don't load the video until it's needed. On our own homepage, a product film was pulling a hosted video player of roughly 4.4 MB on first load for a clip most people never scrolled to. It now shows a single still frame until someone asks to play it.

JavaScript

Every script has to be downloaded, parsed and run, and on a slower phone the running is often the expensive part. Heavy JavaScript is the main cause of poor INP: the page looks ready but doesn't respond to taps.

Typical sources: page builders that ship code for every feature whether you use it or not, animation libraries loaded for one effect, sliders, and old code nobody has dared remove. The fix is less JavaScript: remove what isn't used, load what's needed only when it's needed, and prefer plain HTML and CSS for things that don't need scripting.

Fonts

Custom fonts are part of a brand's character and usually worth keeping. The problems come from quantity and loading strategy: four or five weights across two families, each a separate file, loaded in a way that hides text until they arrive. Keep to the weights you actually use, host them yourself where possible, and make sure text is visible while fonts load.

Third-party scripts

Chat widgets, analytics tools, heatmaps, social embeds, cookie banners, ad pixels. Each is small in isolation and each was added for a reason. Together they're often heavier than the entire rest of the site, and you don't control how fast their servers are.

It's worth auditing them once a year. For each one, ask: is anyone actually looking at the data this collects? If not, remove it.

Hosting and caching

Hosting matters most for dynamic sites, WordPress for example, where each page is assembled on request. Without caching, every visit makes the server do that work again. A good host, page caching, and a content delivery network (a CDN, which serves your files from a location near the visitor) make a large difference. Static sites, which are built once and served as ready-made files, sidestep much of this, which is one reason we favour them for marketing websites. The trade-offs are covered in custom website vs WordPress.

An example of how it adds up

Here's a hypothetical but very typical homepage:

• A hero image, uploaded straight from the camera: 3.8 MB.
• Two font families in four weights each: eight font files.
• A page builder's CSS and JavaScript for dozens of features, of which the page uses six.
• A slider library for one testimonial carousel.
• A chat widget, two analytics tools and a social media pixel.

On a fast laptop it loads in under two seconds and nobody notices a thing. On a mid-range phone on an average mobile connection, the headline appears after several seconds, the layout shifts twice as the fonts and image arrive, and the first tap on the menu does nothing for a noticeable moment because the phone is still busy running scripts.

None of those choices was unreasonable on its own. Together they make a site that feels slow to exactly the people it was built to impress.

Performance budgets: the fix that lasts

The most effective single practice is also the least glamorous: agree a performance budget before design starts. A budget might be a maximum page weight, a maximum number of requests, or target Core Web Vitals on a mid-range phone. web.dev's introduction to performance budgets is a good primer.

A budget changes the conversation. Instead of "can we add a video background?", the question becomes "what would we take out to afford one?" That's a design decision the whole team can make together, rather than a problem engineering discovers after launch.

What to do this week

If you're not planning a rebuild, you can still make meaningful progress:

1. Run your homepage and your most-visited page through PageSpeed Insights. Note the LCP, INP and CLS.
2. Compress and resize every image over about 300 KB. This alone often halves page weight.
3. List every third-party script on the site and remove the ones nobody uses.
4. Check your fonts. Remove weights you don't use.
5. If you're on WordPress, make sure page caching is on and your host isn't the cheapest shared plan.
6. Test again, on your own phone, on mobile data.

If the numbers are still poor after that, the problem is usually structural: a heavy theme or page builder, or a design that simply asks for too much. That's when a rebuild starts to make sense.

The fastest request is the one the page never makes.

Some businesses need a website to tell people they exist. Zen Data Shastra needed one to tell people what they are capable of, which is a much harder job.

They are a data consultancy: AI implementation, data science and machine learning, data engineering, ML engineering, analytics, intelligent automation and workforce training, for clients in retail, consumer goods, pharma, media, loyalty, financial services and manufacturing. That is a lot of expertise. Their website, when they came to us, was a basic one. It put the company online and not much more.

The brief behind the brief

The obvious brief was "make the website look modern". We think the real brief was different, and it shaped every decision that followed.

A company buying AI and analytics work is not buying a logo or a colour palette. It is buying confidence that this particular team will turn its data into something that actually changes a decision. Most of those buyers have been burned before, by a pilot that looked impressive in a demo and never made it into the business.

So the website had one job above all others: to make a sceptical buyer believe, within a few seconds, that this firm understands their problem. Looking modern was necessary. It was nowhere near enough. We wrote about why in why most business websites feel outdated: a new coat of paint on an unclear site just gives you an unclear site in new colours.

Starting with the buyer's question, not the company's services

Most consultancy websites open with a capability statement. "End-to-end data and AI solutions." It is accurate, and nobody remembers it.

We opened with the objection instead. The first thing a visitor reads on the new site is:

Tired of AI pilots that go nowhere?

Then, underneath it, the firm's answer in one line: they align data and models around the business objective to ensure practical outcomes. Then a clear next step.

That headline does three things a capability list cannot. It names a frustration the buyer has already felt. It tells them, before they have read a single service name, that this firm is on their side of the table. And it filters: a visitor who has never run an AI pilot is probably not the client, and that is fine.

Straight after it comes proof. The firm's own count of delivered projects sits on the first screen, and the opening section leads into their published thinking on real problems, such as the state of US retail and why manual reporting eats into margins. The page claims something, then immediately shows evidence for it.

An architecture built around how buyers look for help

A data consultancy has two natural ways in. Some buyers arrive with a problem type ("we need our data pipelines fixed"). Others arrive with an industry ("we are a pharma company, have you worked with anyone like us?"). The old website served neither well.

The new one is built around both:

• Seven services, each with a plain description of what it delivers, from AI implementation to workforce training. Each one links through to related case studies, so a claim about a service is always one click from evidence of it.
• Seven industries, each paired with the outcome that matters most in that sector: demand intelligence for retail, clinical analytics for pharma, risk and fraud detection for financial services, operational efficiency for manufacturing.
• A navigation that exposes that structure at once. The main menu opens into services and industries with a one-line description beside each, so a visitor can find their own situation without guessing what a menu label means.
• A resource hub for the firm's insights, which gives the site a reason to be revisited and gives search engines a growing body of expert content to understand.
• About, story, team and careers pages, because in consulting people buy people. A buyer wants to see who they will be working with.

The result is a site where almost any buyer can answer "have they done this, for someone like me?" in two clicks.

Design that earns trust instead of decorating

Data and AI is a crowded, noisy category, full of glowing neural networks and stock photographs of blue circuitry. We went the other way.

The design is calm and structured. There is generous space, a clear type hierarchy, and a restrained palette, so the substance does the talking. Polish helps trust only up to a point. After that point, specifics do the work.

Every section follows the same rhythm: a clear statement, a short explanation, then a route to evidence. It is designed to be scanned by a busy executive and read properly by the analyst they forward it to.

And it is fully responsive, from phones and tablets to laptops and large desktop screens, because a link shared in a WhatsApp group or opened from LinkedIn on a phone is often a buyer's first look.

Built so search engines understand it

A consultancy that sells expertise needs to be found by people searching for that expertise. So search was part of the build from the first page, not a plugin added at the end. That is the approach we describe in how search engines actually understand a website.

In practice that meant a clear heading structure on every page, a descriptive title and meta description for each, clean and crawlable navigation, service and industry pages that each have one clear purpose, and a content hub that builds topical depth over time.

How the new site measures up

We tested the live site with Lighthouse, Google's open-source auditing tool, on 24 September 2026.

A perfect SEO score means every technical search check Lighthouse runs passes: page titles, descriptions, crawlable links, a valid structure, legible text on mobile. A perfect Best Practices score means the site follows current standards for security and modern web development, with no browser errors and no deprecated features.

On desktop the site also scores 85 for performance. Speed is never finished, though, and it matters more than most businesses think: we explain why in why website speed matters.

What changed for Zen Data Shastra

Before, Zen Data Shastra had a website. Now they have a sales tool: something that opens on their buyer's problem, shows the breadth of their services and industries in a structure anyone can navigate, backs its claims with case studies and published thinking, and passes every technical search check Lighthouse runs.

It is also a site the firm can grow into. New case studies, new insights, a new industry or service: each has an obvious place to go.

The best compliment a website can get is that a buyer never thinks about it. They just understand the company faster.

What this means for your business

If your company does serious work and your website does not show it, you are not alone. It is a common gap in growing businesses, and one of the most fixable.

The approach that worked here works for most service businesses:

1. Find the question your best buyers are already asking, and open on it.
2. Organise the site around how buyers look for help, not around your org chart.
3. Put evidence within one click of every claim.
4. Design for calm confidence, not decoration.
5. Build search and speed in from the start.