Authority framework

Building Topical Authority Around a Medical Specialty

Topical authority is one of the most misused ideas in healthcare content. It is routinely translated into a page count. A clinic decides it wants authority in cardiology, commissions two hundred articles covering every cardiac term with search volume, publishes them over eighteen months and finds that almost none of them rank, almost none are read and none of them produce an appointment.

A medical editor and specialist organizing clinical knowledge into a focused specialty authority map.

01

Executive thesis

The translation is wrong at the first step. Authority in a medical specialty is not coverage of a subject. It is coverage of the decisions patients make within a subject, restricted to the decisions the organization is actually competent to support. Those are much narrower sets, and building them well takes fewer assets than the encyclopedia approach, not more.

Google has now said a version of this directly. In its guide to optimizing for generative AI features, published on 15 May 2026, Google warns against creating separate content for every possible variation of how people might search, states that doing so primarily to manipulate rankings violates its scaled content abuse policy, and adds that it is an ineffective long-term strategy because a high quantity of pages does not make a website higher quality or more relevant. The same guide states that its generative AI features are rooted in the core Search ranking and quality systems, and that what will likely influence a site's presence in generative AI search more than anything else is creating content people find unique, compelling and useful.

The strategic implication for healthcare is uncomfortable for anyone selling volume. The constraint on medical authority is not writing capacity. It is clinician time, and the coverage plan has to be built around that constraint rather than around a keyword export.

02

What topical authority means in healthcare

Three things distinguish medical topical authority from the general case.

The subject has a hard boundary and the organization has a harder one. A cardiology department can write credibly about the conditions it manages and the procedures it performs. It cannot write credibly about everything cardiac, and publishing about interventions it does not offer creates a referral it cannot fulfil. The scope of authority is the scope of practice, and that is a clinical fact rather than an editorial preference.

The content carries clinical risk. Every core asset needs qualified review. That review is the bottleneck, and any plan that ignores it produces either unreviewed content or a backlog.

Commodity content is the default output and the worst outcome. Google's guide draws the distinction plainly, contrasting content based on common knowledge that could have originated with anyone against content offering an expert or experienced take that goes beyond the ordinary. Most medical educational content is the former. It is a restatement of what a dozen international health libraries already publish, and it is exactly what a generative model can produce without a clinician in the room.

For Arabic content in Saudi Arabia, this is where the opportunity sits, and it is a large one. The published assessments of Arabic web health information are consistent and unflattering. A 2024 infodemiological study in the Journal of Medical Internet Research assessed 267 Arabic websites on halitosis and found that not one scored highly against the DISCERN quality threshold. A 2024 assessment of Arabic content on oral cancer and precancerous disorders, published in the Saudi Journal of Health Systems Research, found websites achieved an average of 2.5 of the four JAMA quality benchmarks, that attribution and disclosure were missing from more than 70 percent of them, and that only 15 percent of the material reached an acceptable level of actionability.

Read that as a market description rather than a complaint. The two benchmarks most often missing, attribution and disclosure, are the two that a clinical organization can satisfy trivially and that a content farm cannot satisfy at all. Named clinical authorship with credentials and a review date is not a sophisticated tactic. In Arabic healthcare content it is close to a differentiator on its own.

03

The Specialty Authority Coverage Map

The map organizes a specialty into three zones and one exclusion. The purpose is to decide what to build, what to state briefly and what not to publish at all.

Core topics. The decisions the organization is competent to support and equipped to deliver. Each core topic earns a complete asset set. This zone is deep and narrow.

Supporting topics. The questions patients ask at the same moment as a core decision that are not themselves conditions or procedures. Cost and insurance eligibility, preparation, recovery timelines, when to seek urgent care, how to get a second opinion, what happens at the first appointment. These are shallow and broad, and they are frequently the highest-traffic assets in a cluster because no competitor bothers with them.

Boundary topics. Subjects adjacent to the core that the organization does not handle. These are published as short, explicit statements of scope with routing to the appropriate care, not as full articles. A boundary statement costs two hundred words and prevents a mismatched appointment.

Out of scope. Everything else. General medical encyclopedia entries with no relationship to what the organization does. This zone is not a gap to be filled later. It is a decision, and it should be recorded as one so that nobody rediscovers it as an opportunity every planning cycle.

The zones are decided by two tests applied in order. Does the organization deliver care for this, and does a patient make a decision here. Core requires both. Supporting requires the second. Boundary requires neither but sits close enough to the core that silence would mislead.

04

Core, supporting and boundary topics

Depth is defined per zone, as an asset set rather than a word count.

ZoneRequired assets per topicClinician inputReview cycle
CoreDecision page, procedure or management page, eligibility and cost, what to expect, practitioner links, condition-to-procedure linksRequired for eachAnnual, or on guideline change
SupportingOne page, linked from every relevant core topicReview onlyEvery two years
BoundaryOne short scope statement with routingConfirmation of scopeAnnual
Out of scopeNoneNoneRecorded as a decision

Three rules keep the zones honest.

A core topic is not complete until the whole asset set exists. A cluster with twenty half-covered core topics is weaker than one with eight fully covered. Half-covered means the patient reaches the condition page, learns what the condition is and cannot find out whether this provider treats it, what it costs, who does it or what happens next. That is the encyclopedia failure with better branding.

Supporting topics belong to the cluster, not to a blog. Cost, eligibility and recovery content that sits in a general blog is disconnected from the decisions it supports. It should be linked from every core topic it serves.

Boundary topics are stated, not avoided. The instinct is to say nothing about what you do not treat. Saying nothing means the patient discovers the mismatch at the appointment. A boundary statement is also, incidentally, an authority signal, since declining a subject is something only an organization with a real scope can do.

05

Connecting education to services and practitioners

An education cluster that does not connect to care is a library. The connections are what convert it into an authority asset.

Every core topic connects in four directions. To the procedures or management pathways the organization provides for it. To the named clinicians who deliver those. To the locations where they are delivered. To an access path that states eligibility and the next step. The page-type discipline behind these relationships is set out in the healthcare search architecture, and the practitioner end of the relationship is covered in the twelve-signal profile standard.

Two failure modes recur.

The first is education that terminates. An excellent condition page with no route to care produces informed patients who go elsewhere to act. The route does not need to be a hard call to action. It needs to exist.

The second is a claim that outruns the service. A cluster that covers a treatment the organization does not provide generates enquiries it must decline. In healthcare that is worse than a wasted click, because the patient has already invested in the decision.

The differentiating input is clinician insight, and it is also the scarcest. Google's guidance is explicit that a unique point of view based on real experience is what distinguishes content from a restatement of what is already available. In a medical cluster that means the clinician's judgement about the decision, not their explanation of the pathophysiology. What patients get wrong about this condition. Which cases are referred and why. What the recovery actually looks like in week three rather than in the brochure. What this clinic does differently and on what basis. None of that can be sourced from a search results page, and all of it requires the clinician for perhaps ninety minutes per topic. The method for extracting it efficiently is a separate discipline, and it is the practical constraint on the whole model.

06

Avoiding thin content and topic sprawl

Sprawl has a specific origin in healthcare. A keyword tool returns four hundred related terms, each is treated as a page and the resulting plan is defended on the grounds of coverage.

Google's guide removes the technical justification for that plan. Query fan-out means a single query generates a set of concurrent related queries, so visibility depends on being relevant across a cluster of related questions. The guide's response to this is not to build a page per fan-out query. It says the opposite, warning that creating separate content for every variation of how people search violates the scaled content abuse policy when done to manipulate rankings, and noting that Google's systems can understand the relevance of a page even where there is no exact match with the query.

Compare the two plans for the same specialty.

Encyclopedia planCoverage map plan
Assets, English30043
Assets, bilingual60086
Clinician hours required for genuine input45027
Clinician hours actually available in a year3030
ConsequenceContent is written without clinical input, producing commodity materialEvery core asset carries clinician input

The arithmetic is the argument. At an hour and a half of clinician time per asset requiring genuine input, three hundred assets need roughly four hundred and fifty clinician hours. No specialty department has that. So the pages get written without the clinician, which produces precisely the commodity content that will not perform, and the organization has spent its budget manufacturing the thing it was trying to avoid.

Clinician input hours = core topics × assets requiring clinical input × hours per asset

Run that calculation before approving a content plan. It is the fastest way to discover whether a plan is real.

07

A specialty cluster worked example

The following is illustrative. Figures are planning assumptions for a hypothetical Saudi bariatric and metabolic surgery service, not measurements.

ZoneCountAssetsBilingual
Core topics63060
Supporting topics8816
Boundary statements5510
Total4386

Core topics: eligibility and candidacy assessment, sleeve gastrectomy, gastric bypass, revision surgery, post-operative nutrition and follow-up, weight regain after surgery.

Supporting topics: insurance coverage and eligibility, cost and payment, preparing for surgery, the first consultation, recovery timeline, returning to work, complications and when to seek urgent care, how to get a second opinion.

Boundary statements: paediatric bariatric surgery, endocrine management of obesity, cosmetic body contouring after weight loss, eating disorder treatment, pharmacological weight management where not provided. Each states what the service does not deliver and where to go instead.

Clinician input: 6 core topics, 3 assets per topic requiring genuine clinical input, 1.5 hours each, giving 27 hours. That fits inside a realistic annual allocation and it is why this plan is deliverable while a three hundred page plan is not.

Note what the boundary zone does here. Weight regain is core because the service manages it. Eating disorder treatment is a boundary because the service does not, even though the search demand overlaps heavily and a keyword-led plan would have built it.

08

Coverage and authority metrics

Evaluate the cluster, not the article. Individual article performance in a specialty cluster is noisy and it produces bad decisions, usually the deletion of a page that was doing supporting work.

MetricDefinitionReview threshold
Decision coverageShare of core topics with the complete asset setBelow 80%
Boundary declarationShare of identified boundary topics with a published statementBelow 90%
Clinical attributionShare of core assets with a named clinician, credentials and a review dateBelow 100%
Commodity ratioShare of core assets containing no original clinical inputAbove 20%
Cluster visibilityNon-branded impressions across the whole cluster, tracked as one numberDeclining quarter on quarter
Bilingual parityShare of core assets with a genuine Arabic equivalentBelow 90%
Route to careShare of core assets linking to an eligibility statement and a next stepBelow 95%

Clinical attribution is the only metric here with a threshold of 100 percent. Given that attribution and disclosure are missing from more than 70 percent of assessed Arabic health websites, it is also the cheapest competitive gap in the list.

Commodity ratio requires an editorial judgement rather than a tool. Ask of each core asset whether it contains at least one thing that could only have come from this organization's clinicians. If not, it is commodity, and it should be either upgraded or retired.

Thresholds are editorial starting points, not validated benchmarks. Calibrate to your own baseline.

09

Research and governance requirements

Fix now, within thirty days. Classify every existing asset in the specialty into core, supporting, boundary or out of scope. Expect the out of scope pile to be large. Add a named clinical author or reviewer, with credentials and a review date, to every core asset that lacks one. Publish boundary statements for the three most commonly misdirected enquiries, which the appointments team can name without a study.

Build next, within one to two quarters. Complete the asset set for core topics rather than adding new core topics. Run the clinician input calculation on any proposed plan before approving it. Book clinician time as a recurring commitment rather than requesting it per article, since the per-article request is what fails. Build the Arabic cluster as an equivalent rather than a translation, which matters more in this pillar than any other.

Measure continuously. Report the seven metrics quarterly at cluster level. Retire commodity assets rather than refreshing them. Re-review core assets annually or whenever clinical guidance changes, whichever comes first.

One governance rule underpins the rest. No core asset publishes without a named clinical reviewer. It is the single control that prevents the encyclopedia plan from reasserting itself, because a plan that cannot pass clinical review at volume cannot be built at volume.

Related reading: why healthcare SEO is a market-access system for the strategic frame, the clinical authority signal map for how expertise becomes visible, Arabic healthcare content is not translation for the bilingual requirement, and orthopedic digital demand for a worked specialty demand picture.

10

Method, limitations and compliance boundary

This article presents a framework and an illustrative planning model. It does not present original DEMA research findings.

The bariatric cluster, the asset counts and the clinician hour calculations are planning assumptions for a hypothetical service. They are not measurements, benchmarks or client results. The seven metric thresholds are editorial judgements offered as starting points.

Platform guidance is drawn from Google's guide to optimizing for generative AI features on Google Search, published 15 May 2026 and current at the date of review. Google documentation changes without notice and should be re-verified. Nothing in Google's guidance guarantees rankings, inclusion in AI Overviews or citation in AI Mode, and no recommendation here should be read as promising any of those outcomes.

Evidence on Arabic health content quality is drawn from two 2024 peer-reviewed infodemiological studies, one assessing 267 Arabic websites on halitosis and one assessing Arabic content on oral cancer and precancerous disorders. Both are single-topic studies within dentistry and oral health. They demonstrate a consistent pattern in the Arabic corpora examined and they are not a general measurement of all Arabic health content across all specialties. Treat the pattern as indicative and the specific percentages as topic-specific.

All core clinical content requires qualified medical review before publication and none of it should present individualized medical advice. Scope statements should be confirmed with the clinical lead, since a published boundary is an operational commitment. Claims about outcomes, comparative superiority or clinician expertise require substantiation and review against Saudi health advertising rules.

Last reviewed August 2026. Review cycle annual.

Request a Specialty Authority Map. DEMA classifies an existing specialty estate into core, supporting, boundary and out of scope, measures decision coverage and commodity ratio, and returns a build sequence sized to the clinician time actually available.

Continue exploring

Related reading from the same authority programme.

Use the insight to identify the next decision.

Request a Growth Diagnosis