Use when several named people deliver the service and you need to decide who gets a page of their own.
practitioner-bio-pages.md
You are deciding which named people at a local business deserve a page of their own. You are not writing every biography yet.
The people, with role, qualifications, years in the job, specialisms, languages and which site they work from: {{PRACTITIONERS}}
Service and sector: {{SERVICE_AND_SECTOR}}
What our regulator or professional body allows us to claim: {{REGULATOR_RULES}}
How someone books a named person: {{BOOKING_ROUTE}}
Produce:
1. A verdict table: Person from {{PRACTITIONERS}}, Verdict (own page, section on a team page, name only), Reason in one line, What a searcher would be looking for when they land there.
2. A page template for the own page group: heading structure, what each section covers, where {{BOOKING_ROUTE}} appears, and the schema properties worth adding.
3. A collection sheet: the facts to gather from each person before writing, including registration numbers, training and the sort of case they take most often in {{SERVICE_AND_SECTOR}}.
4. A bio of 120 words for the strongest candidate, using only what {{PRACTITIONERS}} gives you.
5. Linking rules between practitioner pages, service pages and location pages.
Rules:
- Never invent a qualification, registration number, year or specialism. Write [NEEDS INPUT] instead.
- Check every claim against {{REGULATOR_RULES}} and flag restricted wording such as specialist, expert, or any promise of an outcome.
- Do not recommend a page for someone with nothing a searcher would look for.
- No em dashes.
Replace each placeholder with your own detail. The more specific you are, the less the model invents.
When should I use this rather than writing the bios?
When several named people deliver the service and someone has proposed a page for everyone. It decides who warrants one before any writing happens, which is cheaper than building eleven pages and orphaning six of them. Where nobody books a named person, the answer is usually a single team page.
What do I need to collect first?
Each person with role, qualifications, years in the job, specialisms, languages and which site they work from, plus {{REGULATOR_RULES}} for what your professional body allows you to claim, and the {{BOOKING_ROUTE}} for booking a named person. Missing qualifications come back as [NEEDS INPUT], never invented, so gather registration numbers early.
What comes back?
A verdict per person of own page, section on a team page or name only, a page template with schema properties, a collection sheet of facts to gather, one 120 word bio and linking rules. The verdict table is the decision; the sample bio only exists to set the standard for the rest.
What is the mistake?
Building pages for people who will not be there in a year. Practitioner pages age badly and orphan fast. The other cost is regulated wording: specialist, expert and any promise of an outcome get flagged for good reason, so have each person read their own page before it goes live.