Treatment pages and the query they are meant to answer

The treatment page is the workhorse of every clinic website and the place where the most effort is wasted. The usual construction is keyword first: pick the term, write a page containing it, add a call to action. That method produces pages that are structurally identical to every competitor's, which is a poor position in the organic band and a hopeless one in an answer engine, where a passage has to be worth lifting.

The alternative is to build the page around a question. Not a search term, a question, phrased the way a person would ask it out loud.

Finding the actual question

Three sources give you real questions rather than invented ones. The first is the Search Console Performance report filtered to the pages you already have, read for queries rather than for volume: the long specific ones are the questions. The second is the reception log, which in most clinics is the most under-used research asset in the building. The third is the Q and A section of the Business Profile and the text of your own reviews, where patients describe what they were worried about in their own words.

What consistently appears in clinic questions: how long it lasts, what it costs, whether it hurts, what the recovery looks like, who should not have it, what happens if it goes wrong, and how to choose between two options that sound similar. Very little of that is served by a page that opens with a paragraph about the clinic's commitment to natural results.

Answer near the top, then earn the rest

Put the answer in the first screen. A short, self-contained paragraph that answers the question directly, without hedging and without a preamble. This is good service to a reader who is deciding in fifteen seconds whether the page is worth their time, and it happens also to be the passage structure that an answer engine can extract cleanly.

Specifics are the only defensible advantage

Generic treatment description is a commodity. Every clinic has the same paragraph about how the product works, because it comes from the same manufacturer material. What cannot be copied is the specific practice of a specific clinic: which technique is used and why, what the review appointment schedule is, what the clinic does differently for a first-time patient, what the practitioner will decline to do and on what grounds, what happens if the result is not what the patient wanted.

That material has to come from the clinician. It is slow to gather and it is the entire reason the page exists. A treatment page that contains nothing only that clinic could have written is a page that has no argument for being indexed.

What UK rules will not let you write

Before drafting, know the boundary. UK advertising rules restrict how prescription-only medicines may be promoted to the public, and clinic web copy is advertising. The CAP Code and the MHRA publish the applicable positions, and the practical effect is that certain product names cannot be used to promote the treatment to the public at all. Writing a page around a term you are not permitted to advertise is a poor foundation, however well it ranks in a keyword tool.

This is a discovery constraint as much as a legal one. It shapes which pages you can build, and it is far cheaper to know that before writing than after a complaint.

One page per question, not one page per keyword variation

Keyword tools return dozens of variants of the same question. Building a page for each produces the duplication problem described elsewhere on this site. Build one page per genuine question and let it cover the variants naturally, because a system that can match a page to a paraphrase does not need a separate page for each phrasing.

The exception is a genuinely different decision. "How long does it last" and "what does it cost" are the same visit to the same page. "Which of these two treatments suits my problem" is a different page, because it is a different decision with a different answer.

Connecting commercial and informational pages

Most treatment queries have mixed intent, and the results page usually shows both informational and commercial documents. A clinic can serve both, but not on one page. The workable structure is a substantial informational page that answers the question thoroughly and links to a shorter commercial page that describes the clinic's own service, pricing approach and booking route.

Link them in both directions with descriptive anchor text. Internal linking is one of the few inputs entirely within your control, and on clinic sites it is usually left to whatever the navigation template produces.

Marking up what the page already says

Structured data describes the page, it does not improve it. Where a treatment page genuinely answers a set of questions, FAQPage markup makes that structure explicit. Where the page is clinical information, MedicalWebPage is the appropriate type. Google's structured data policies require the markup to reflect visible content, so the discipline is to write first and mark up second, never the reverse.

Length is an output, not a target

There is no length that ranks. Word count targets produce padding, and padding is the fastest way to dilute the passage quality that answer engines depend on. The right length is the length required to answer the question and its immediate follow-ups with specifics. For most clinic treatment questions that lands somewhere between eight hundred and two thousand words, and if a page reaches that naturally it is because there was something to say.

Reviewing a page against its question

Once a quarter, take each treatment page and ask four things. Does it still answer its question first? Has the clinical practice changed since it was written? Do the Performance report queries for that URL match the question it was built for? Does it contain at least three paragraphs that survive the extraction test? Pages that fail the third question are usually ranking for something else entirely, and that is useful information rather than a failure.