An important web page should be built around one claim the business can explain, support and maintain. The claim may define a service, identify who it suits, describe a method, distinguish two options or report a bounded result. It does not need to be a boast.
The usual production sequence runs backwards. A writer creates the page, an editor sharpens the promises and proof is sprinkled over the finished copy. A testimonial is asked to support a technical claim. An official source appears after a paragraph containing four unrelated assertions. A credential badge sits beside trusted specialists, although nobody can explain what the badge establishes. The page looks more credible. Its central claim remains unsupported.
I do not begin a commercial rewrite by choosing headings. I ask what the reader needs to decide, what the business is entitled to say and which evidence can carry that statement without a private explanation from sales.
TL;DR
- A topic names the territory; a claim gives the page a job. Write the page contract before the public copy.
- Classify the claim before choosing the proof, and shrink the sentence when the evidence is smaller.
- One primary claim holds the page together; supporting claims are reasoning, not extra keywords.
- Put proof where doubt begins, give every fact one public owner, and choose structure only after the claim survives.
A topic names the territory; a claim gives the page a job
Technical SEO services is a topic. “The technical SEO audit separates discovery, rendering, indexation, canonical and template risks before recommendations are prioritised” is a claim about scope and method. The actual audit process must support it.
Experienced family solicitor is promotional language. Named people, regulated roles, qualifications, practice areas and responsibility records may support a narrower expertise claim. They do not prove that every team member holds every credential or that experience guarantees an outcome. Sustainable packaging is a category. A named material, current certification, measured property or disposal instruction may support a bounded environmental proposition.
A page without a claim tends to repeat its topic. A page with an unsupported claim repeats the company’s ambition. Neither helps a buyer make a responsible decision.
Write the page contract before the public copy
Complete this internal sentence:
This page helps [reader] decide or understand [job] by establishing [primary claim], supported by [evidence], subject to [material limit], before leading to [appropriate next action].
Each field prevents a different failure:
- Reader stops the page addressing everybody and nobody.
- Job turns a subject into a decision or task.
- Claim identifies what the page must earn.
- Evidence prevents research becoming decoration.
- Limit keeps the proposition within defensible scope.
- Next action prevents education jumping straight to a sales demand.
The contract is not a mandatory opening paragraph or hard-wired website template. It is the standard the eventual page must fulfil in whatever structure fits the decision. If two existing pages complete the same contract, resolve ownership before adding another URL. Different keywords, towns or buyer labels do not automatically create different jobs.
Classify the claim before choosing the proof
Evidence is relational. The correct source depends on the proposition.
| Claim type | Suitable evidence may include | Common mismatch |
|---|---|---|
| Identity | Company records, maintained profiles and legal details | Treating copied directory text as authoritative identity evidence |
| Scope | Current service documentation, exclusions and accountable owner | Using a testimonial to prove what is included |
| Method | Approved process, responsibilities and sample output | Claiming the method guarantees performance |
| Expertise | Named role, qualification, authorship and relevant experience | Assigning one person’s credential to the company |
| Comparison | Shared criteria, specifications, prices or disclosed method | Applying different standards to the preferred option |
| Performance | Metric, unit, denominator, sample, method, period and limit | Presenting one selected case as typical |
| Customer experience | Approved review or testimonial with context | Treating reported satisfaction as objective superiority |
| Current rule | Primary documentation and applicable date | Using an old secondary summary for a live platform rule |
| Professional judgement | Named reasoning, relevant competence and boundary | Disguising an opinion as universal industry fact |
A source can be genuine and still be wrong for the claim. A customer may honestly praise responsiveness; that does not prove compliance. Google can document a Search feature; that does not prove an agency implements it well. My evidence test is not “do we have a citation?” It is “what exact sentence does this source permit us to write?”
Make the sentence smaller when the evidence is smaller
Do not stretch proof to rescue confident copy. Reduce the claim. Suppose a page says: “Our process delivers faster SEO growth.” A process document can establish that the method exists and describe its sequence. It cannot establish faster growth without a comparator, metric, relevant sample, period and defensible analysis. Responsible alternatives include:
- describe what the process examines and produces;
- explain which decision or risk it is designed to address;
- publish an approved example while stating that it is not a typical result;
- conduct suitable measurement if performance matters commercially;
- remove the sentence.
The final option is underused. Empty space does not require a replacement promise. Google’s people-first guidance asks whether content presents information in a trustworthy way, demonstrates relevant expertise and provides substantial value for its intended audience (Google Search Central). Increasing the confidence of an unsupported statement does none of those things.
Build a hierarchy, not a pile of claims
One primary claim should hold the page together. Supporting claims help the reader understand, test or act on it. For a technical audit page, the hierarchy might be:
- Primary claimThe audit separates several technical failure classes before prioritisation.
- Supporting claimEach failure class requires different evidence.
- Supporting claimCommercial impact and implementation dependency affect priority.
- Supporting claimThe output records finding, confidence, action and owner.
- LimitThe audit does not guarantee implementation or ranking recovery.
This prevents a familiar commercial page from emerging: one section promises traffic, another technical health, another AI search optimisation and the CTA asks for guaranteed business growth. Every sentence sounds related to SEO. Together they describe no accountable service. Supporting claims are not additional keywords. They are the reasoning that lets the primary claim survive scrutiny.
Put proof where doubt begins
Proof is valuable when it resolves a specific hesitation.
Do not herd every badge, logo and statistic into a decorative trust section at the bottom. The evidence may be real and still arrive too late to repair the doubt created higher up the page. The strongest proof placement often looks unremarkable: claim, evidence, explanation and limit sit close enough that the reader does not have to assemble the argument. This is where website design carries commercial meaning. Visual hierarchy should connect the proposition to its proof, not simply make both elements attractive in different parts of the layout.
Name the subject when extraction creates ambiguity
Clear entity naming is not an incantation for AI SEO. It prevents a proposition floating away from its subject. Weak: “We provide this across the region and our specialists review every case.” Stronger: “Example Ltd provides the survey across East Sussex. A named surveyor reviews each report before issue.” The stronger version makes two claims with identifiable subjects. It can still be false, but it can now be checked.
Name the company, service, person, product, location, issuer or method when a detached sentence would otherwise become unclear. Do not repeat names mechanically when normal prose already makes the subject obvious. Entity clarity is accountable noun choice, not keyword stuffing with a diagram attached.
Want to know which pages are asking readers to take too much on trust? We audit the consequential claims, match each to its evidence and tell you what to keep, narrow or remove.
Give every important fact one public owner
Repeated facts drift when nobody maintains the authoritative version. Assign one primary page for each material fact family: service scope; location and availability; price or pricing method; qualification and role; operating process; case result; policy or current rule; comparison decision; company identity. Other pages may summarise what their own reader needs. They should preserve the same scope and direct the reader towards maintained evidence when necessary. They should not invent variations to sound original.
Ownership also exists inside the company. A service lead can approve operational scope. A named practitioner can approve attributed judgement. Marketing can improve clarity. Higher-risk claims may require legal, compliance or specialist review. An AI-readiness score cannot assume those responsibilities. Record who approves the fact, who maintains the page and which business change forces review.
Choose structure after the claim survives
Only after claim and evidence agree should the page’s natural structure be selected. A service page may move through situation, suitability, scope, method, proof, exclusions and next action. A comparison may begin with its decision rule and apply symmetrical criteria. A diagnostic article may lead from symptom to evidence, competing causes, checks and escalation. A case study may follow context, intervention, observed result and limitation. Do not force Overview, Benefits, Why Choose Us and FAQs onto every subject. Those headings organise website furniture. They do not necessarily advance the reader’s reasoning.
Likewise, do not compress every heading into a slogan. Headings should mark a meaningful turn in the argument. The prose still has to do the work. This order matters. Polishing before the evidence review makes weak promises emotionally expensive to remove. Teams begin defending a sentence because it is good copy instead of because it is true.
Separate fact, example and judgement
Readers can accept strong professional opinion when its role is visible.
- Fact: a checkable statement about an entity, service, rule or event.
- Evidence: the record supporting a proposition.
- Example: a real, anonymised, schematic or fictional illustration labelled accurately.
- Judgement: an attributed professional conclusion with reasoning and limits.
- Prediction: an uncertain future proposition under stated assumptions.
Do not present judgement as platform documentation. Do not turn one case into expected performance. Do not label a schematic example as lived experience. Do not hide opinion behind research shows when the exact source and proposition can be named. First-person authority should change the decision. “I remove the performance promise when the evidence establishes only the process” is useful professional judgement. A decorative story about noticing the problem over coffee is not.
Audit claims before editing tone
For each consequential statement on an existing page, record:
- exact public wording;
- claim type;
- intended reader decision;
- supporting evidence;
- what that evidence actually establishes;
- scope and material limit;
- primary public-page owner;
- business approver;
- review trigger;
- keep, narrow, support, move or remove.
The audit should delete as often as it adds. A page carrying three defensible claims can be stronger than one carrying fifteen statements nobody has approved. Then edit the angle, headings, examples, rhythm and conversion. Evidence governs what the page may say. It should not dictate a lifeless literary structure. For performance marketing and conversion rate optimisation, this is particularly important. Stronger persuasion is useful only after the proposition has earned the right to become stronger.
Use different reviewers for different failures
Give reviewers distinct jobs. A subject reviewer asks whether the page describes the service, product or business accurately. An evidence reviewer asks whether each source supports the exact proposition, scope and date. A reader reviewer asks whether a representative reader can explain the answer, proof, limitation and next action. Add qualified professional or compliance review where the subject requires it. Do not settle disagreement by making the sentence vague. Identify whether the dispute concerns fact, evidence, scope, ownership, explanation or reader fit.
The reader review is often the most revealing. Internal teams know what broad words such as support, coverage, integrated and end-to-end are supposed to mean. A new visitor receives only what the page says.
Know when the page should say less, or nothing
Hold or remove a proposition when:
The honest replacement may be a process explanation, conditional answer, question the reader should ask, or nothing at all. Search and AI systems may rank, quote, link to, summarise or ignore the eventual page. Those outcomes remain external. The company still controls whether its public claims are specific, supported and fair.
Make the claim earn the page
Choose the reader and decision. Write the primary claim. Classify it. Match the evidence. Reduce the wording when proof is narrower. Put support where doubt appears. Keep the limitation attached. Assign public and business owners. Then build the page in the form the decision naturally requires.
My approval threshold is simple: the page should never ask a reader to believe more than the business can show. Clear claims, explicit subjects and visible proof are not an AI-search formula. They are the basis of useful branding, defensible sales and digital growth without charitable interpretation.
Good to know
FAQs
A topic names the territory, such as “technical SEO services”. A claim gives the page a job: a statement about scope, method, suitability or a bounded result that the business must be able to explain, support and maintain.
Reduce the claim, not the honesty. Describe what the process examines and produces, explain which risk it addresses, publish an approved example labelled as not typical, measure properly if performance matters, or remove the sentence. Empty space does not need a replacement promise.
Where doubt begins: the qualification beside the expertise claim, inclusions and exclusions beside the scope, method and measurement beside a result, and the limitation attached to any summarised case. A trust section at the bottom often arrives too late.
No. Those headings organise website furniture. Choose structure after the claim and evidence agree, in the form the decision naturally requires, with headings that mark a real turn in the argument.
Next step
Is your page asking readers to believe too much?
We write the page contract with you, classify and evidence every consequential claim, and rebuild the page around the one claim the business can actually show.