This post is for a doctor or clinic manager who owns a website and wants to know what to put on the pages that say who you are and how your content is made. They are not the pages that bring in traffic. They are the pages that someone opens after a search result has made them wonder: who is behind this, and can I believe it?
Google's guidance for creating helpful content frames it as three questions, Who, How and Why: who created the content, how it was created, and why. The rater guidelines test the same thing from the other end. A worked example in the General Guidelines describes a medical site with "literally no information about who is responsible for the content or the website" and rates it as untrustworthy because "medical pages require a high level of user trust". The cheapest fix in healthcare SEO is to make sure that never describes your site.
Five pages carry most of the weight. None needs to be long. All need to be true.
1. The About page
Purpose: say who runs the clinic, what it does, where it is, and why a reader should believe the rest of the site.
What to include:
- The legal or trading name of the practice, and the people behind it. For a solo doctor, that is your name, qualifications and registration details. For a clinic, name the founder and the medical lead.
- What you treat, in plain language, and where. Address, city, hours.
- Your registrations and accreditations that can be verified, with the registration number and issuing body. For doctors in India, the National Medical Commission's October 2026 notice asks for name, qualifications, registration status and registration number on electronic posts by practitioners (Explanation III to paragraph 3.2 of the notice).
- A short, factual description of how the clinic is run and how patients are looked after.
- Links to the Contact page, the Editorial Policy and the doctor profiles.
What to leave out: "best", "leading", "most trusted", "number one", unless you can meet the independent verification test in paragraph 8.1(ix). Left-out claims are not a loss. The guideline wording tells raters to be sceptical of how sites describe themselves.
Layout: first screen answers who, what, where. Photograph of the real premises and real clinicians. Facts in a short list; story below.
2. The Contact page
Purpose: show that a real, reachable organisation sits behind the site.
Include: street address, a working phone number, an email address monitored by a person, hours, a map link, the name of the person responsible for patient queries, and a separate route for complaints. State clearly that emergencies should go to the emergency number and the nearest hospital, using wording your clinical lead approves.
Avoid: a form as the only option; a PO box; a number that goes to a call centre that cannot answer clinical or billing questions without explaining so.
Link to it from the footer of every page. The rater guidelines tell raters to look for how to contact the site's owner as part of working out who is responsible (section 2.5.2).
3. The Editorial Policy page
Purpose: explain how health content is produced, checked and updated. This is the "How" in Google's framework.
This is the page most clinic sites lack. A good one is about 400 words and covers:
- Who writes. Say whether articles are written by clinicians, by an editorial team, or both, and what the roles are.
- Who reviews. Every clinical article is reviewed by a registered practitioner in the relevant specialty before publication. State this only if it is true for all content.
- Sources. What counts as a source: clinical practice guidelines, peer-reviewed research, government health bodies, regulators. Say that product claims and statistics are linked to the source.
- Updating. Review interval (for example, every 12 months, or sooner if guidance changes), and where the review date appears on pages.
- Corrections. How readers report an error and what happens next. Give a real email address.
- Independence and advertising. Say whether content is sponsored; whether the clinic's own services are mentioned in educational content; and that paid relationships are disclosed. The NMC notice expects material commercial relationships in informational content to be disclosed (paragraph 8.1(xi)).
- Use of AI. If AI tools help with drafting, research or translation, say how. Paragraph 7.2 of the NMC notice treats AI-generated promotional content strictly and requires an AI source mark on content that is permitted, so check with counsel on your own use.
- What the content is not. General information, not a substitute for individual medical advice.
Write it in first person plural and keep it factual. Avoid promising a perfect process. A policy you do not follow is worse than none, because it is a claim a reviewer can test.
4. The Medical Review page (or a visible review block on each article)
Purpose: show that a named clinician stands behind the clinical content.
There are two ways to do this and most clinics should do both:
A. A page listing your reviewers. Name, specialty, qualifications, registration number, the topics they review, link to their full profile. Doctors on this page should appear in your content register.
B. A short review block on each clinical article. For example:
Medically reviewed by Dr [Name], [qualification], [Council] registration no. [number]. Last reviewed [date]. Next review due [date].
The block links to the reviewer's profile page. The date should change only when a review actually takes place. A date refreshed automatically by the CMS on every save is a false claim.
For the full set of boundaries on who may draft and who must review, see our post on doctor bylines, ghostwriting and NMC limits, and our explainer on what Indian doctors may say online. Paragraph 4.4 of the NMC notice makes the practitioner answerable for content published in their name, so reviewers need to read what they sign.
Structured data. schema.org has a MedicalWebPage type with reviewedBy and lastReviewed properties. Add them on clinical pages, with the same reviewer and date as the visible block. Google does not give a rich result for this, so the benefit is clarity for machines, not a visual feature. Never mark up a review that did not happen.




