Sources and References: Citation Rules

A sources block is the closing, ordered record that makes a page’s factual claims traceable so readers and answer engines can verify and cite them.

This live specimen shows the minimum complete entry: linked title, publisher, publication date, and accessed date. The URL sits behind the title rather than appearing as a long raw string. Apply the shared element writing rules when adapting the block to another publishing system.

Why this element matters

Readers do not treat all claims alike. A medical recommendation, financial comparison, or performance number carries more risk than a simple capability statement. A complete reference shows who published the evidence, when it was current, and whether it supports the claim. It also gives editors a maintenance trail when facts change.

Ten reputable links dumped at the end do not prove which sentence each supports. Inline citations create the local connection; the closing list preserves the full records. Together, they let a skeptical reader move from claim to evidence without guessing.

Machine extractability means software can identify a bounded record outside the page’s design. Consistent fields expose a title, publisher, URL, publication date, and access date. A retrieval system—software that selects documents or passages for a query—can then compare dates, publishers, and claims.

In answer-engine results, several candidate pages may make similar statements. A page that cites primary material and dates its evidence completes part of the verification work a retrieval system otherwise has to infer. This does not guarantee selection; it creates an auditable evidence chain.

The principle aligns with the site’s E-E-A-T and entity foundations : visible provenance supports trust, while consistent publisher and title fields help identify the entities behind the evidence.

When to use it

Use a sources block whenever an informational or evidence-led page relies on external facts that a reader could reasonably verify. This includes definitions derived from standards, statistics, research findings, laws, policies, market claims, product comparisons, historical claims, quotations, and recommendations based on published evidence. It is explicitly required for health, finance, legal, insurance, safety, and any other regulated or high-consequence vertical.

Use it even when claims already have inline links if the article contains several sources; the block creates one reviewable inventory. In a case study, label internal measurements separately from external benchmarks so first-party data is not mistaken for independent research.

Do not add one to decorate an opinion with no externally verifiable claims. Navigation, recommended reading, related content, and unused bibliography entries do not belong. A source supports the page; “further reading” merely extends the topic.

Near-miss cases need a firm rule:

• A single factual claim: cite it inline. A one-entry closing block is optional unless the vertical is regulated.
• A list of tools: vendor homepages are destinations, not evidence. Include documentation only when it supports specific claims.
• A quotation: cite it inline and include the complete closing record.
• Common knowledge: do not cite facts that the intended reader would not dispute, such as “a week has seven days.” Cite a precise interpretation, measurement, policy, or disputed boundary.
• First-party product copy: link to official documentation for testable capabilities. Do not manufacture the appearance of independence by citing the company’s own marketing page as proof of superiority.

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 sources block is the final editorial block, after the FAQ. Only site-wide chrome, legal notices, or template-level conversion controls may follow it. This position shows that the list supports the completed article and gives reviewers one predictable audit location.

Do not put the only list in a sidebar: sidebars may disappear from mobile layouts, print, feeds, reader modes, or extracted text. Keep the block away from related-content cards, forms, and unrelated calls to action so the evidence boundary stays clear.

Inline citations remain at the point of claim. The closing block does not move evidence away from the sentence it supports; it completes the record. If an FAQ answer introduces a new factual claim, cite it inside that answer and repeat the source in the closing block. If the FAQ only restates supported content, reuse the existing source rather than adding a duplicate entry.

Anatomy

The rendered legend remains in the page if the asset is replaced:

1. Block heading: use “Sources” unless a publication standard requires “References.”
2. Entry number: gives each record a stable identifier across speech, print, and extraction.
3. Title and URL: exact title as descriptive link text, resolving to the cited version.
4. Publisher: the organization responsible for the material.
5. Publication date: when the source was issued or substantively updated.
6. Accessed date: when the author verified the source and claim.
7. Block boundary: one ordered list; the heading and list carry the semantics.

Do not bake this legend into the screenshot. The image documents appearance; the numbered legend defines the content contract.

Stay Updated on AI Visibility Trends

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

Email address

Subscribe

Design examples

The variants change density and available metadata without changing the five-field entry contract.

Standard web sources: the default for articles that cite standards, documentation, reports, and web pages. Each title is linked; publisher and both dates remain visible text.

Mixed source types: a DOI is a persistent identifier for research. Use it for a paper; use canonical URLs for reports and documentation. Keep the common field order when adding volume, issue, or version details.

Long titles: wrap naturally to multiple lines. Never truncate the title until two different documents become indistinguishable.

Mobile: entries remain a single ordered list with no horizontal scrolling. Long URLs stay behind the title, and metadata wraps below it without shrinking the text.

Parameters

The parameter contract separates author-supplied evidence from renderer behavior. “Source” below means where the component obtains the value.

All five entry fields are mandatory. A title without a publisher hides responsibility; a publisher without a URL cannot be inspected. The two dates show when the material claimed to be current and when it was verified. If no publication or update date exists, write n.d.. Replace undated evidence for time-sensitive claims or remove the claim.

Syntax and code examples

Each notation carries the same fields and order. The component may transform source data, but it must not infer publishers or dates from fragile page markup.

Portable Markdown directive

:::sources{heading="Sources"}
1. [citation — Schema.org Property](https://schema.org/citation) — Schema.org. Published 2026-03-19. Accessed 2026-08-27.
2. [Understanding SC 2.4.4: Link Purpose (In Context)](https://www.w3.org/WAI/WCAG22/Understanding/link-purpose-in-context.html) — W3C Web Accessibility Initiative. Updated 2026-05-18. Accessed 2026-08-27.
:::

Hugo shortcode

{{< sources heading="Sources" >}}
1. [citation — Schema.org Property](https://schema.org/citation) — Schema.org. Published 2026-03-19. Accessed 2026-08-27.
2. [Understanding SC 2.4.4: Link Purpose (In Context)](https://www.w3.org/WAI/WCAG22/Understanding/link-purpose-in-context.html) — W3C Web Accessibility Initiative. Updated 2026-05-18. Accessed 2026-08-27.
{{< /sources >}}

This is a portable contract, not a claim that this shortcode exists. Until a renderer implements it, use a native heading and ordered Markdown list.

WordPress block or shortcode

[sources heading="Sources"]
[source title="citation — Schema.org Property" publisher="Schema.org" url="https://schema.org/citation" publication_date="2026-03-19" accessed_date="2026-08-27"]
[source title="Understanding SC 2.4.4: Link Purpose (In Context)" publisher="W3C Web Accessibility Initiative" url="https://www.w3.org/WAI/WCAG22/Understanding/link-purpose-in-context.html" publication_date="2026-05-18" accessed_date="2026-08-27"]
[/sources]

A WordPress block may expose form controls, but it must render a heading and native ordered list and preserve dates in exported content.

Examples

Good: complete, attributable, and dated

Sources

1. “Understanding Success Criterion 2.4.4: Link Purpose (In Context).” W3C Web Accessibility Initiative. Updated 18 May 2026. Accessed 27 August 2026.
2. “citation — Schema.org Property.” Schema.org. Published 19 March 2026. Accessed 27 August 2026.

This works because a reviewer can identify each document, publisher, source date, verification date, and destination. The entries are primary documentation, ordered by first appearance so inline numbers and closing records are easy to reconcile.

Bad: a pile of domains

References

• Google
• Some accessibility blog
• schema.org
• https://example.com/article?id=18492

This fails because no entry identifies a document or dates. “Google” is an organization, not evidence. “Some accessibility blog” conceals publisher and quality tier. The raw URL lacks a usable title, and no entry maps to a claim. Repair it by selecting evidence for each claim, adding inline citations, and recording every mandatory field.

Inline citation versus the closing sources list

Cite at the point of claim when the reader needs to know which source supports it; include the complete closing record when the page relies on that source. Most evidence-led pages need both.

Inline citation is required for a number, quotation, study finding, law, policy, disputed assertion, safety instruction, time-sensitive product fact, or source-dependent conclusion. Place it in or immediately after the sentence. One citation cannot support a paragraph of unrelated claims.

The closing list is required for multiple sources, a mandated inventory, or a regulated subject. Repeated citations get one entry; materially different versions get separate entries.

Source quality tiers

Quality is fitness for the claim, not fame. Use the highest appropriate tier that can directly support the statement:

The tier does not rescue a mismatched claim. A regulator’s filing page cannot support a clinical claim, and a paper cannot prove a feature released after the study. A vendor pricing page can prove its current price but not that it offers the best value.

When sources conflict, state the scope or date that explains the difference, favor the controlling primary record, and narrow the claim. If unresolved, say the evidence conflicts.

Link handling and source loss

External links stay in the current tab by default. Use HTTPS and a canonical or persistent URL; remove tracking parameters, session identifiers, and redirect wrappers. Link the title, not “click here.” Do not add nofollow to ordinary editorial citations; reserve relationship values for links that have those relationships.

If the product deliberately opens external sources in a new tab, output target="_blank" rel="noopener" and warn the user in visible text or a programmatically associated description. noopener prevents the opened page from receiving a reference to the originating window. Add noreferrer only when the site’s privacy policy requires suppressing referrer information; it is not a universal editorial-citation requirement.

Check every source before publication and during scheduled reviews. A dead link is a URL that no longer resolves to the cited material. When one dies:

1. Look for a publisher-controlled replacement, canonical redirect, newer version, DOI, or official archive.
2. Confirm that the replacement supports the same claim; a working homepage is not a substitute for a missing report.
3. Update the URL, publication date if the version changed, accessed date, and any claim affected by the new source.
4. If only a credible archive preserves the exact document, link the archive and label it as archived.
5. If the evidence cannot be recovered, replace the source and re-evaluate the claim. Remove or qualify the claim when no appropriate evidence remains.

Never point an old citation at a replacement that makes a different claim.

Schema markup and accessibility

A sources block does not create a standalone Schema.org entity. It remains part of the enclosing Article, TechArticle, Report, or other valid CreativeWork. Schema.org’s citation property may carry a reference as text or another CreativeWork. When structured data is generated, map each genuine editorial reference to citation; do not mark navigation, affiliate destinations, or merely related reading as citations.

Visible content and structured data must agree. JSON-LD—JavaScript Object Notation for Linked Data—must not introduce absent sources or omit visible qualifiers. It never replaces the visible list or inline links.

For accessibility, use a heading followed by <ol> and <li>. Ordered entries give stable item counts and identifiers. Use the source title as link text; keep publisher and dates in the same item. Never use color, favicon, or logo as the only identification.

Avoid role="list" on native lists, interactive accordions that hide the evidence by default, and tables for a simple one-dimensional reference sequence. If a link opens a new tab, the warning must be available visually and to assistive technology. Keyboard focus must remain visible, and long titles must wrap without clipping or horizontal page scroll.

Writing rules

Use the exact title and recognizable publisher name. Keep this sequence: title, publisher, publication or update date, accessed date. Add author, edition, pages, DOI, or version only when needed to identify the work or meet a publication standard.

Order entries by first appearance unless a required style says otherwise. Deduplicate identical records, but keep editions or versions separate when the difference affects the claim.

Every entry must support a claim, and every material external claim must map to evidence. The title must match the destination. The accessed date records when the destination and its support were checked, not when the CMS saved the page.

Do not put calls to action, affiliate labels, related articles, recommended books not used as evidence, author biographies, methodology prose, promotional descriptions, star ratings, or commentary about whether a source is “great” inside the block. Explain source limitations beside the relevant claim or in a methods section. Keep the closing block an evidence inventory.

There is no arbitrary maximum. A report may need dozens of records. Above twenty entries, use stable reference numbers and test narrow-screen wrapping; never split one article’s evidence into unrelated sidebars.

Post types that use it

The postTypes frontmatter creates the machine-readable join to the nine evidence-led page types below. The visible table adds the placement and strength of requirement.

Product, category, and use-case pages still cite factual claims when they make them, but a closing list is conditional when the page is primarily transactional and relies only on first-party capability information. In every post type, health, finance, legal, and other regulated content requires a complete sources block regardless of length.

QA checklist

• Every externally verifiable material claim has an appropriate source.
• Claims that require exact attribution have inline citations at the point of claim.
• Every inline citation maps unambiguously to one complete closing entry.
• Every closing entry supports at least one claim actually made on the page.
• Each entry includes title, publisher, canonical URL, publication date or n.d., and exact accessed date.
• Publication dates were not inferred from copyright footers, search snippets, or URL patterns.
• Accessed dates record real verification rather than a bulk CMS migration date.
• Source quality matches the claim; vendor material is not used to prove superiority.
• Primary or controlling official material replaces secondary coverage when it is available and usable.
• Study claims preserve the population, method, date, and limitations that affect interpretation.
• Conflicting evidence is disclosed, scoped, or resolved rather than silently omitted.
• Titles are descriptive link text and match their destinations.
• External URLs use HTTPS, omit tracking parameters, and resolve to the cited version.
• Links open in the current tab unless a documented product rule says otherwise.
• Any new-tab link uses noopener and warns users that a new tab will open.
• Dead or redirected links were repaired without changing the supported claim unnoticed.
• The block is a heading plus ordered list in the main document flow.
• The block is the final editorial section after FAQ and is not mixed with related content or calls to action.
• Visible references and any Schema.org citation values agree.
• The block remains readable, keyboard accessible, and free of horizontal page scroll on narrow screens.

FAQ

Does every article need a sources block?

Use one for informational or evidence-led content that depends on external facts. A short product page containing only first-party capability statements may not need a closing block, although each factual claim still needs an appropriate source. Health, finance, legal, and other regulated content always requires one.

Does a sources block replace inline citations?

No. Put an inline citation at the claim when a reader must know which source supports that exact statement. The closing block provides complete reference records and a page-level evidence inventory; it does not make distant claim-to-source relationships obvious.

What if a source has no publication date?

Record the publication date as n.d. and include an exact accessed date. Do not invent a date or omit the field. For a time-sensitive claim, find a dated replacement or remove the claim because an undated page cannot establish when the information was current.

Can vendor material appear in the sources block?

Yes, for claims the vendor controls, such as its documented features, prices, release notes, or contractual terms. Vendor material must not be used as independent evidence that its product is the best, safest, fastest, or most effective option.

Should external source links open in a new tab?

Keep normal links in the current tab by default so the reader controls navigation. If the product deliberately opens a new tab, use target="_blank" with rel="noopener" and provide a visible or programmatically associated warning that a new tab will open.

Sources

1. “citation — Schema.org Property.” Schema.org. Published 19 March 2026. Accessed 27 August 2026.
2. “Understanding Success Criterion 2.4.4: Link Purpose (In Context).” W3C Web Accessibility Initiative. Updated 18 May 2026. Accessed 27 August 2026.
3. “Technique G201: Giving Users Advanced Warning When Opening a New Window.” W3C Web Accessibility Initiative. Updated 18 May 2026. Accessed 27 August 2026.