How to write a page that answers what your client actually typed.

A page that answers what your client typed starts with the question, not the keyword. You read the search the way the person meant it, then you write the direct answer in the first sentence. Everything else on the page supports that answer.

Most pages fail here. They chase a keyword phrase and forget there is a human behind it with a real problem and a narrow window of patience. Someone types "how much does an uncontested divorce cost in San Diego" and lands on a page that opens with "Our firm has served families since 1998." That page will lose. Not because the firm is bad, but because the first thing the reader sees is not the thing they asked for.

I have spent most of my career watching what people do after they click. The gap between what they typed and what the page gives them is where the money leaks out. Close that gap and the same traffic starts converting. Here is how to write the page that closes it.

What does it mean to answer what someone actually typed?

Answering what someone typed means matching the intent behind the words, not just the words themselves. The search phrase is a clue to a state of mind. Your job is to read that state of mind and respond to it in plain language before you do anything else.

Take three searches that look similar. "Divorce lawyer San Diego" is someone ready to hire. "How long does divorce take in California" is someone still deciding. "Can I get divorced without going to court" is someone with a specific fear. Same topic. Three different people. Three different pages.

The first person wants a lawyer, a phone number, and a reason to trust you. The second wants a timeline and no pressure. The third wants a yes or no, then the details. If you write one generic "family law" page and point all three searches at it, you disappoint all three. The page that wins reads the intent and answers it head-on.

This is the difference between a keyword and a question. A keyword is a string of text. A question has a person, a problem, and a moment attached to it. Write for the person.

How do you find the real question behind the keyword?

You find the real question by reading how people phrase the search, not just what they search for. The phrasing tells you what they already know, what they are afraid of, and what they want next. Read enough of these and the page writes itself.

Start with the search box itself. Type the topic into Google and read the autocomplete suggestions. Those are real searches, ranked by volume. Type "root canal" and you get "root canal cost," "root canal pain," "root canal near me," "root canal recovery." Four different states of mind in one dropdown. Each one deserves its own answer.

Scroll to the "People also ask" box. Those are the follow-up questions Google knows people have. They are a free outline for your page. If someone searching "root canal cost" also asks "does insurance cover a root canal" and "how much is a root canal without insurance," put both answers on the page. You are not guessing anymore. Google told you.

Then read your own inbox. The questions clients ask you on the phone, in the first consult, in the email before they book — those are the exact words your future clients will type. You already have the research. You just have not written it down.

Here is a short diagnostic I run on any page that is not converting:

1. Read the target search out loud as a full question.
2. Read the first sentence of your page.
3. Does the sentence answer the question? If not, that is the problem.

Most of the time it does not. The page opens with the firm's history or a stock line about commitment. Fix that one sentence and the page starts working.

What does the page structure look like once you have the question?

The page structure follows the reader's thinking: direct answer first, supporting detail second, next step last. You lead with the answer they came for, then earn the right to say more. This order is not a style choice. It is how people read on a screen.

Open with the answer in the first sentence. If the search is "how much does an uncontested divorce cost in San Diego," the first line reads: "An uncontested divorce in San Diego usually costs between $1,500 and $4,000 in attorney fees, plus the $435 court filing fee." No preamble. The reader relaxes because you gave them the number. Now they will keep reading.

Follow with the context that answer raises. Why the range? What moves the price up? When does uncontested become contested? Each of these is a follow-up question the reader now has. Answer them in order, one short section each.

Use headings that match how people ask. "What affects the cost" beats "Fee Structures." "How long it takes" beats "Process Timeline." The heading should read like a question a person would actually type or ask. This helps the reader scan and it helps search engines match your page to the query.

End with the next step. Someone who just learned what a divorce costs is closer to acting than when they arrived. Give them one clear action: book a consult, call the office, ask a question. Not five options. One.

This structure is part of what we build in a Search Foundations engagement, because a page that answers the real question is worth nothing if the site underneath it is slow, broken, or invisible.

How do you write the answer so it reads like a person wrote it?

You write the answer in the words your client already uses, in short sentences, with the specifics they need to decide. Plain language wins because the reader is stressed, distracted, and skimming. Every complicated sentence gives them a reason to leave.

Use their words, not your jargon. A client does not search "dissolution of marriage." They search "divorce." They do not search "periodontal scaling." They search "deep cleaning teeth." Write the page in the language of the search, then define the technical term once if you need it. The reader should never have to translate.

Be specific. "Affordable rates" tells the reader nothing. "$1,500 to $4,000" tells them everything. Numbers, timelines, and named steps build trust faster than any adjective. When you cannot give an exact number, give a range and explain what moves it. Vagueness reads as evasion.

Keep sentences short. One idea each. Read the page out loud. Anywhere you run out of breath, add a period. The reader is on a phone with three tabs open. Give them sentences they can absorb in a glance.

Watch the speed too. A page that answers the question perfectly still loses if it takes four seconds to load. The reader hits back before your answer renders. We wrote about why in why your slow site is a sales problem, not an IT problem, and it holds here: the best answer on a slow page is an answer nobody reads. If you want the specific numbers Google watches, Core Web Vitals is the three numbers that decide if Google bothers.

How do you know the page is actually working?

You know the page is working when it ranks for the question, holds the reader, and turns readers into contacts. Three signals, in that order. Miss any one and the page has a specific problem you can fix.

First, does it rank for the search you wrote it for? Search the exact phrase in an incognito window. If your page is not on the first screen after a few weeks, the match is off. Either the page does not answer the question well enough or a stronger page already does. Read the pages that beat you and find what they answer that you skipped.

Second, do people stay? A page that ranks but sends everyone back to Google in five seconds is answering the wrong question, or answering it badly. Look at time on page and bounce. A high bounce on an informational page is not always bad. A high bounce on a page meant to book a consult is a warning.

Third, does anyone act? The only metric that pays the bills is the contact. Track how many people who land on the page call, book, or fill the form. If traffic is high and contacts are low, the answer is good but the next step is weak or missing. If traffic is low, the ranking is the problem, not the page.

We took a small firm through exactly this. When we rebuilt the pages for McShanes Solicitors around the real questions clients typed — cost, timeline, process, the specific fear behind each search — the traffic that already existed started turning into enquiries. Same firm. Same expertise. The difference was pages that answered the question in the first sentence instead of the fifth paragraph.

Where this breaks down

This approach does not fix a business problem dressed up as a marketing problem. If your prices are out of line, your reviews are bad, or your intake ignores calls for two days, a well-written page will surface those problems faster, not hide them. A page that answers the question honestly sends you more qualified leads. What happens next is on the business. We write the page that gets the right person to raise their hand. We cannot make you a good fit for them.

Write for the question, not the keyword. Read the search the way the person meant it, answer it in the first sentence, and give them one clear next step. Do that on every page and the traffic you already have starts earning its keep. Foundations first.