Disclaimer Block: Placement and Writing Rules

A disclaimer block is a plain-language statement that defines the limits, status, uncertainty, or commercial relationship behind a page before the reader relies on its content.

That specimen is intentionally direct. It tells the reader what the page is, what it is not, which decisions need outside help, and whether compensation may influence the content. A real page should include only the clauses that apply; copying all four categories into every article would make the disclosure less credible and less useful.

Why this element matters

A reader approaches medical, financial, and legal material with a different level of dependence than ordinary explanatory content. They may treat a confident paragraph as personalized advice even when the author intended only general education. A disclaimer corrects that expectation before reliance forms. An affiliate disclosure solves a related trust problem: it reveals a commercial relationship before the reader evaluates or acts on a recommendation.

Reader psychology makes timing as important as wording. A disclosure discovered after a recommendation feels withheld, even when the same sentence exists in a footer. Predictable placement lets returning readers find it without hunting. Plain language also signals respect: boilerplate fails when readers cannot explain what the limitation means.

Machine extractability is the ability of software to isolate the statement and preserve its meaning outside the visual page. A typed disclaimer with a stable label, bounded body, and fixed position can survive reader mode, syndication, content migration, and passage extraction. Search systems and AI agents can distinguish publisher-supplied qualifications from the factual body instead of treating a buried sentence as an unrelated footer.

Apply the element writing rules by purpose. A small gray paragraph is not a disclaimer merely because it looks legal, and a section called “Please note” is not enough unless it clearly states scope or relationship. Conversely, content that performs this job belongs in the disclaimer element even when a legacy page calls it a notice, disclosure, or important information.

When to use it

Use a disclaimer when omitting a material qualification or relationship could cause a reasonable reader to misunderstand the content’s status, scope, or incentives.

• Legal: the page explains laws, contracts, rights, compliance, disputes, or procedures but does not provide advice for the reader’s particular facts or jurisdiction.
• Medical: the page discusses symptoms, diagnoses, treatment, medication, supplements, or health behavior but cannot establish a clinician–patient relationship or replace individualized care.
• Financial: the page discusses investing, lending, insurance, tax, trading, returns, or financial products but does not assess the reader’s objectives, circumstances, or risk tolerance.
• Affiliate: the publisher may earn money, credit, products, services, or another benefit from a link, purchase, lead, or recommendation.

The triggering fact controls the variant. Do not add a medical disclaimer because an article mentions sleep, or label a link “affiliate” when no compensation relationship exists. Over-disclosure obscures what matters.

Several near misses belong elsewhere. Put a methodology limitation with the method or findings, a correction in an update log, terms of sale in the transaction flow, and a privacy notice where data is collected. A destructive step that can erase data requires a warning box , not a disclaimer.

A disclaimer cannot cure flawed content. “Not medical advice” does not make unsafe dosing instructions acceptable, and affiliate wording does not correct a ranking designed solely around commissions. Fix the underlying problem first, then disclose the legitimate scope or relationship.

Ready to Monitor Your AI Visibility?

Track how AI chatbots mention your brand across ChatGPT, Perplexity, and other platforms.

Get Started Contact

Where to place it

The default page-level slot is immediately after the opening direct answer or introduction and before the first substantive recommendation, analysis, instruction, or product comparison. The reason comes first: the reader must know the page’s status before interpreting advice, while the opening still needs enough context to make the disclosure intelligible. This fixed slot should remain the same across desktop, mobile, print, and syndicated output.

Affiliate disclosure has an additional hard boundary: it must appear before the first affiliate link, compensated recommendation, ranked product, or purchasing control. If the standard post-introduction slot already meets that rule, do not repeat it immediately. If a reusable product module can appear independently, include a concise disclosure in or directly before that module as well as the page-level statement.

Add a local reminder only when a section changes the relationship or may be consumed independently, such as a sponsored comparison or exported medical calculator. It must add context, not repeat boilerplate every few paragraphs.

Do not place the block only in the footer, author biography, terms link, hover text, collapsed accordion, cookie banner, or image caption. Those positions separate the qualification from the content it governs. It may not sit directly beside a call to action, advertisement, coupon, product price, or newsletter form, because the disclosure can look like promotional fine print. It also may not sit directly beside a warning: separate the page-level disclaimer with ordinary explanatory content, then place the warning immediately before the hazardous action. When both rules compete, the warning’s point-of-action position stays fixed and the disclaimer keeps its opening slot.

Anatomy

The element has six identifiable regions:

1. Label: names the block “Disclaimer” or uses a specific approved label such as “Affiliate disclosure.”
2. Scope: identifies which content, relationship, recommendation, or page section the statement qualifies.
3. Status: says what the content is and is not, such as general education rather than individualized advice.
4. Material fact: states the relevant limitation, uncertainty, professional status, or compensation relationship.
5. Reader action: tells the reader when to seek qualified help, verify current requirements, or apply independent judgment.
6. Fixed position: ties the block to its required place before reliance, recommendation, or affiliate interaction.

Keep this legend as live text so assistive technology and content exports retain every region.

Stay Updated on AI Visibility Trends

Get the latest insights on AI mentions, brand monitoring, and optimization strategies.

Email address

Subscribe

Design examples

The four variants differ by trigger, not decoration. All use a restrained container, readable label, normal text size, and stable position.

Legal disclaimer

State that the material is general information, identify any relevant jurisdiction or date, and direct fact-specific questions to a qualified professional. Do not imply a professional relationship.

Medical disclaimer

State that the page is educational and does not diagnose or replace individualized care. A general disclaimer must never absorb a symptom-specific emergency warning.

Financial disclaimer

Name the subject—investment, tax, lending, insurance, or another financial context—rather than using “financial content” as a vague umbrella. State the limits that matter, such as lack of personalization and the possibility of loss, without turning the block into a list of every conceivable market risk.

Affiliate disclosure

Name the economic relationship and its consequence in ordinary words: the publisher may receive compensation if the reader acts through a link. If compensation affects price, ranking eligibility, review access, or another material condition, say so. Never conceal the disclosure behind “support us” or “partner link.”

On narrow screens, the body must wrap naturally, keep its label visible, and never clip approved wording.

Parameters

The component captures the statement and placement contract. Approval metadata stays outside the visible body unless policy requires it.

The combined variant is for pages where more than one trigger genuinely applies, such as a financial comparison containing affiliate links. It is not the safe default. Keep each clause independently understandable, and omit categories that do not apply.

Syntax and code examples

The portable directive is canonical. Hugo uses the existing note callout until a dedicated renderer exists; this does not change the fields or placement rule.

Portable Markdown directive

:::disclaimer{variant="affiliate" title="Affiliate disclosure"}
We may receive a commission if you buy through links in this guide. Compensation does not change the price you pay or the criteria used to evaluate products.
:::

Hugo shortcode

{{< callout type="note" title="Affiliate disclosure" >}}We may receive a commission if you buy through links in this guide. Compensation does not change the price you pay or the criteria used to evaluate products.{{< /callout >}}

Use named parameters together. Never combine a positional note parameter with a named title, because Hugo does not permit positional and named parameters in one shortcode call.

WordPress block or shortcode

<!-- wp:amicited/disclaimer {"variant":"affiliate","title":"Affiliate disclosure"} -->
<p>We may receive a commission if you buy through links in this guide. Compensation does not change the price you pay or the criteria used to evaluate products.</p>
<!-- /wp:amicited/disclaimer -->

[disclaimer variant="affiliate" title="Affiliate disclosure"]We may receive a commission if you buy through links in this guide. Compensation does not change the price you pay or the criteria used to evaluate products.[/disclaimer]

These WordPress forms are implementation contracts. The component must preserve visible wording, variant identity, and position in exports.

Examples

Good: a financial comparison with affiliate links

This works because it identifies both triggers, limits the comparison, states the compensation relationship, and gives a proportionate next action without promising independence or suitability.

Bad: vague boilerplate after the recommendation

Important: This is not advice. We may be compensated. Use at your own risk. Terms apply.

This fails for both wording and position. It does not say what kind of advice, who may pay whom, whether compensation relates to the links, or which terms matter. “Use at your own risk” transfers responsibility without helping the reader interpret the content. Placing it after the ranked products means the reader has already evaluated recommendations without the material relationship. Repair it by naming the page scope and relationship in the opening slot, then stating any action-specific risk in a separate warning where that action occurs.

Schema markup and accessibility

A disclaimer does not have a dedicated Schema.org type and should not create a standalone Schema markup entity or fabricated property. Keep it as visible content within the enclosing article, product, review, or other valid page type. Do not copy the disclaimer into citation, description, reviewBody, or another unrelated property merely to make it machine-readable.

JSON-LD must agree with the visible page. If structured data identifies an author, reviewer, offer, or reviewed product, those facts cannot contradict the disclaimer. An affiliate relationship generally belongs in visible disclosure and publisher governance rather than an invented structured-data field. Structured data never substitutes for the on-page block.

Use a semantic region or aside with an accessible name when the renderer supports it. The title must be text, not an icon or color. Keep the block in normal document order and do not use role="alert" for content present at page load; an alert role is designed for urgent dynamic updates and can create disruptive announcements.

Text must meet the article body’s contrast, zoom, and reflow requirements. Do not shrink, truncate, or hide it. Links need descriptive text and visible keyboard focus; screen readers must encounter the disclosure first. Meaning must survive without the border, background, or icon.

Writing rules

Write the disclaimer because a material limit or relationship exists, then say exactly what it is. The reason precedes the production rule: readers cannot adjust their reliance when the wording hides behind broad legal phrases. Use direct subjects and verbs—“We may receive a commission,” “This article provides general information,” and “The calculator does not consider your tax position.”

Keep the visible body to 35–120 words in one or two short paragraphs. Use a one-to-four-word title. Name the scope in the first sentence, then state status or relationship, the material limitation, and any necessary reader action. A combined block may use two short paragraphs when separating professional-scope and affiliate clauses improves comprehension.

Match the wording to the trigger and page. State jurisdiction, review date, data delay, author credentials, compensation effect, or other qualifiers only when they materially affect interpretation or an approved policy requires them. Do not invent assurances such as “completely unbiased,” “no conflict of interest,” or “guaranteed accurate.” If the relationship can affect inclusion or ranking, disclose that fact rather than making a blanket independence claim.

Never put these items inside the disclaimer:

• a hazard-specific instruction that belongs in a warning;
• individualized legal, medical, tax, or investment advice;
• product benefits, promotional claims, coupons, urgency, or a call to action;
• terms that require acceptance, a privacy-consent control, or a waiver disguised as editorial copy;
• a complete methodology, evidence list, author biography, or review;
• unsupported promises that the wording removes liability or makes unsafe content acceptable.

Preserve approved wording exactly where regulation, counsel, platform policy, or a commercial agreement controls it. The editorial limits in this specification do not authorize cutting mandatory language. If approved wording exceeds 120 words, keep it intact, request a plain-language lead sentence, and review the design for readable presentation instead of reducing type size.

Most importantly, a disclaimer never substitutes for a warning. A disclaimer says how to interpret content; a warning says what foreseeable harm may occur and what the reader must do before a specific action. When both apply, publish both in their required positions.

Post types that use it

The postTypes frontmatter creates the machine-readable relationship to formats where these triggers recur. Inclusion remains conditional on the page’s subject or commercial relationship.

Other post types use the element whenever the same trigger exists. A format missing from the array is not exempt from an applicable disclosure requirement, and a format included in the array does not need empty boilerplate when no trigger applies.

QA checklist

• A real legal, medical, financial, affiliate, or combined trigger justifies the block.
• The selected variant matches the trigger; irrelevant clauses have been removed.
• The first sentence clearly identifies the page, section, or relationship being qualified.
• Legal, medical, or financial wording states what the content is and is not.
• Affiliate wording names the compensation relationship and any material effect on price, inclusion, or ranking.
• The body uses plain language and direct subjects rather than vague phrases such as “terms apply.”
• The disclaimer appears in the fixed opening slot before substantive reliance.
• Affiliate disclosure appears before the first affiliate link, product ranking, or compensated recommendation.
• The block is visible in normal reading order and is not hidden only in a footer, accordion, image, or terms link.
• It does not sit directly beside a warning, advertisement, price, coupon, call to action, or consent control.
• Every action-specific hazard still has its own warning at the decision point.
• The body stays within 35–120 words unless approved mandatory language requires more.
• The block contains no promotion, individualized advice, waiver, methodology, or unsupported legal promise.
• Required wording has the appropriate subject-matter, compliance, or legal approval and has not been silently edited.
• The title and meaning remain clear without color, icons, borders, or reduced type.
• Static content does not use role="alert", and the region has an accessible textual name.
• Markdown, Hugo, and WordPress mappings preserve the same words, variant, and placement.
• Visible content does not conflict with author, review, offer, or product facts in structured data.
• Screenshot comments name future captures only; no nonexistent image is rendered.

FAQ

Does every page need a disclaimer?

No. Use a disclaimer when the subject, relationship, or applicable policy creates information a reasonable reader needs to interpret the page correctly. Adding one to harmless general content creates noise and can weaken attention to disclosures that matter.

Where should a disclaimer block appear?

Use the fixed slot immediately after the opening answer or introduction and before substantive advice. An affiliate disclosure must also appear before the first compensated recommendation or affiliate link. Repeat only when a long or reused section could otherwise separate the disclosure from the content it qualifies.

Can a disclaimer replace a warning?

No. A disclaimer explains scope, status, uncertainty, or a commercial relationship. A warning identifies a foreseeable hazard and tells the reader what to do at the decision point. A page may require both.

Can a disclaimer prevent legal liability?

A content specification cannot promise that result. Required wording and legal effect depend on the page, jurisdiction, relationship, and current rules. Use approved language and obtain qualified review where the stakes require it.

Should the disclaimer be hidden in an accordion or footer?

No when it materially affects how the reader should interpret the page. Keep it visible in the main reading order. A site-wide footer notice may supplement the page-level disclosure, but it does not replace it.

A useful disclaimer earns trust by making boundaries visible early. State the applicable limit or relationship plainly, keep the block in its fixed position, and preserve every point-of-action warning separately.