Write the Page for a Reader, Not a Robot

Somewhere in the last twenty years, a myth took hold that writing for search engines and writing for people are two different jobs. So businesses commission two kinds of page. One sounds like a person wrote it and does nothing. The other is stuffed with "best CA firm in Laxmi Nagar" eleven times and makes the reader close the tab.

The useful thing to understand is that the two jobs have converged almost completely. A search engine is trying to guess what a reader wants and whether your page gives it. The closer your page is to genuinely giving it, the less work you have to do to convince anything. This is not a feel-good sentiment — it has practical consequences for how you lay a page out, sentence by sentence.

A page is read in three passes

Watch anyone read a business website on a phone. They do not read. They scroll fast, stop at two or three places, and decide in maybe eight seconds whether this page is about their problem. Only then do they read a paragraph. Only then, if they are still there, do they read properly.

So the page has three audiences, all of them the same person at different moments:

• The scroller, who sees only headings, bold text and the shape of the page.
• The scanner, who reads first sentences of paragraphs and stops where something matches.
• The reader, who has decided you might be relevant and now wants the detail.

Now notice something. A search engine crawling that page also works from structure — the heading tags, the order of things, the words in close proximity to each other. Google's own guidance for site owners talks about descriptive headings and about writing content that helps people. The scroller and the crawler want the same thing: a page whose skeleton announces what it is about.

Which means you do not need to choose. You need headings that would genuinely help a human skim. That is it. That is most of the job.

Headings are answers, not labels

Here is the single change that improves most business pages. Stop using nouns as headings. Use the thing the reader is actually wondering.

The label version	The answer version
Our Process	What happens in the first two weeks
Services	GST filing, TDS returns and annual ROC compliance
Why Choose Us	We do not take on clients with more than one pending assessment
Pricing	What a 12-page site costs and what moves the number
FAQ	Do I need to be physically present for registration?

The left column tells the scroller nothing. "Our Process" is on every website in India. The scroller's eye slides past it because it carries no information. The right column stops them, because it contains the specific thing they came to find out.

And the right column happens to be full of the words people actually type. Not because you stuffed keywords in, but because you wrote down the question. "Do I need to be physically present for registration" is a real search. Somebody types roughly that into Google at eleven at night. You did not have to research it — you just had to stop writing in corporate noun-phrases.

Use real heading tags for these, not bold paragraphs. An h2 is a structural signal; bold text is a visual one. Screen readers, search crawlers and the browser's own outline all read the first and ignore the second.

One idea per section, and say it in the first sentence

Under each heading, answer it immediately. Not background, not a run-up. The scanner reads first sentences. If your first sentence under "What happens in the first two weeks" is "Every business is unique, and we believe in a collaborative approach", you have wasted the only sentence they were going to read.

Write instead: "We take a full copy of your books, list every notice you have received, and come back within ten working days with a written position on each one." Now the scanner has what they need. The paragraph after it can expand.

Specificity is the whole trick

Vague writing and bad SEO are the same illness. Consider two sentences about the same business:

We offer comprehensive interior solutions for residential and commercial clients across Delhi NCR.

We do modular kitchens and full 2BHK fit-outs in Mayur Vihar, Patparganj and Indirapuram — usually a ten to fourteen week job, and we do not take on anything below about six lakh.

The second sentence does five things at once. It tells the right reader they are in the right place. It tells the wrong reader to leave, which saves everyone time. It contains the actual words a buyer would use — "modular kitchen", "2BHK", the locality names. It sets an expectation about budget, so your phone rings less and better. And it sounds like a person, because people say numbers and place names and humans give ranges.

Nobody searches for "comprehensive interior solutions". People search for "modular kitchen Patparganj" and "2bhk interior cost delhi". You do not need a keyword tool to work that out. You need to write the way you talk on the phone. Your sales calls already contain the vocabulary — the words customers use before they know your jargon.

The same logic applies to the things that are increasingly quoted back by AI assistants. When a language model summarises the web to answer "how much does a modular kitchen cost in East Delhi", it has to find pages that contain something answerable. A page of adjectives gives it nothing to work with. A page with a number, a locality and a timeframe gives it a sentence it can lift. Nobody can tell you reliably how these systems weight sources — that part is genuinely uncertain and anyone who tells you otherwise is guessing — but writing things that are quotable is a low-risk bet either way. We go into this properly on our AI visibility page.

What not to buy

A few things sold in this category that you should decline, including when an agency offers them.

Word-count targets. "Every page should be 1,500 words for SEO." There is no such rule. A page should be as long as the answer takes. Padding a 400-word answer to 1,500 words adds three paragraphs the reader has to wade through, and those paragraphs are, by definition, the weakest writing on the page. If your page is genuinely thin — three sentences and a phone number — the fix is more information, not more words.

Keyword density. The idea that your target phrase should appear some percentage of the time is a relic. Write naturally and your phrase appears where it needs to — in the heading, once or twice in the body, in the page title. If you have to force it in a fourth time, the sentence will read badly and a human will feel it.

Bulk AI-generated pages. Twenty near-identical pages, one per locality, differing only in the place name. They read like what they are. Google has published guidance specifically about scaled content produced mainly to manipulate rankings. More practically: a reader in Preet Vihar can tell instantly that you have never worked in Preet Vihar, because the page contains nothing a person who had worked there would know.

"Content refreshes" that only change the date. Updating the published date without changing the content is a trick, and a shallow one. If the information is still right, leave it. If it is not, rewrite the wrong part properly.

A practical order to write in

1. Write the questions first. Six to ten things a real buyer asks you, in their words. Take them from your call history, WhatsApp, email — not your imagination.
2. Cut to the four or five that matter most for this page. Each becomes an h2.
3. Answer each in one sentence. Plainly, with a number or a name in it wherever you honestly can.
4. Expand each answer to a paragraph or two. Stop when the answer is complete.
5. Write the opening last. Two or three sentences saying who this page is for and what it covers. Openings written first are always throat-clearing.
6. Read it aloud. Anywhere you stumble or feel embarrassed, that sentence is dishonest or bloated. Fix those and you are done.

Step six is not a flourish. Reading aloud is the most reliable test anyone has for whether writing sounds like a person, and it takes four minutes.

The technical bits that still matter

Structure gets you most of the way; a handful of mechanical things finish the job.

• The title tag — the text that shows as the clickable headline in search results. Google will often rewrite it, but give it a good one anyway: say what the page is and where you are. Around 55 to 60 characters is what tends to display without truncation on desktop.
• One h1 per page, and it should say the same thing as the title tag, not something cleverer.
• Descriptive link text. "Read our note on how local search rankings actually work" beats "click here". Both the reader and the crawler learn something from the words in the link.
• Speed. None of this writing gets read if the page takes six seconds on a 4G connection in a lift. Google's Core Web Vitals thresholds are public: Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 milliseconds, Cumulative Layout Shift under 0.1. Those are checkable numbers, not opinions.

That is the whole list. It is short because the mechanical part of on-page SEO has always been short. The long part is having something specific to say.

What to do this week

Open your most important service page. Read only the headings, in order, and nothing else. Ask whether a stranger could tell from those headings alone what you do, who for, and roughly what it costs. If they could not, you have found your afternoon's work — and it is writing work, not technical work.

Rewrite each heading as a question your customers actually ask. Answer each one in the first sentence below it. Put a real number, place or timeframe in at least three of the answers. That alone will make the page more useful to a reader and more legible to a search engine, without a single line of code changing.

If you want a second pair of eyes on the pages that matter most — or the structural and speed side handled alongside the writing — tell us which page is underperforming and we will look at it. There is more on the underlying mechanics across our writing on search and site performance.

Questions we get asked