Reviewed-by Block: Expert Review and Credential Rules

A reviewed-by block identifies the qualified person who independently checked a page, states the claims they checked, and records when that review occurred. It is evidence of a completed editorial action, not a decorative trust badge.

The specimen answers four questions: who reviewed the page, why that person is qualified, when the review happened, and what the review covered. Its final sentence clarifies role and relationship rather than claiming that one reviewer guarantees the entire page.

Why this element matters

Readers often use visible expertise as a shortcut when they cannot personally verify a technical, medical, legal, financial, or statistical claim. A named reviewer can reduce uncertainty, but only when the attribution is specific enough to be challenged. “Expert reviewed” asks for trust without evidence. A name, relevant credential, date, and bounded scope let the reader judge whether the review matches the claim they are about to rely on.

The psychology cuts both ways. A row of initials can create an authority halo: readers may assume the reviewer tested the product, approved every recommendation, or accepts responsibility for future updates. The block must prevent that overreach by describing an actual review event and its limits.

Machine extractability means software can isolate the review relationship without guessing from nearby prose. A typed block gives content systems stable fields for reviewer identity, credentials, review date, and scope. Search engines, AI agents, syndication feeds, accessibility tools, and migration scripts can then distinguish reviewer from author, review date from modification date, and verified scope from the rest of the page.

Follow the element writing rules by purpose. Any passage whose job is to assert independent subject-matter review uses this element, whatever its heading or visual style. A byline that happens to include two names is not equivalent because it does not preserve their different responsibilities.

When to use it

Use the block when an identifiable expert has completed a meaningful second-person check and a plausible error would have material consequences.

• Health and safety content: a qualified clinician or safety specialist checks the specific claims, contraindications, escalation advice, or procedures within their competence.
• Legal, regulatory, and financial content: a relevant professional checks jurisdiction, effective dates, assumptions, calculations, and the line between general information and individualized advice.
• Technical documentation: an engineer or product specialist verifies commands, version support, prerequisites, expected results, and recovery steps in a clean or representative environment.
• Research and statistics: a methodologist, analyst, or domain expert checks definitions, sampling, transformations, calculations, limitations, and whether the conclusions follow from the data.
• Decision content: a subject specialist checks evaluation criteria and factual claims in a review, buying guide, or cost guide when those claims fall outside the writer’s competence.

The trigger is completed review, not topic seriousness alone. A page does not earn the block because an expert was copied on an email, supplied a quote, approved the general topic, or reviewed an earlier version. Consultation may inform the article, but consultation is not independent review unless the person received the relevant final material, checked a stated scope, returned findings, and authorized attribution.

Near misses include grammar editing, self-review, customer testimonials, source quotations, disclaimers, and managerial approval. None proves subject-matter verification. Job seniority is not a credential: a CEO is not automatically qualified to verify tax, dosage, or statistical claims.

Use no block when review cannot be evidenced. An unattributed “reviewed by our experts” line is worse than silence because it creates a testable trust claim with no accountable person, date, or scope.

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

Place the primary reviewed-by block in the provenance cluster directly below the author attribution and freshness stamp , before the opening answer or introduction. The reason is interpretive: readers should know who created and checked the material before they begin relying on it. Keep this order on mobile, in print, in reader mode, and in syndicated copies.

When the block is too detailed for the opening, render a compact line there and link it to one expanded block immediately before the sources block . Both must use the same record so dates and scopes cannot drift.

The block may not be merged with the author bio , because authorship and review must remain separate roles. It may not sit inside or directly beside a testimonial, review score, product offer, price, affiliate button, trust-badge strip, or call to action. Those neighbors can make factual review look like endorsement. Keep an ordinary content boundary between the review attribution and commercial persuasion.

Do not hide the only attribution in a footer, hover state, image, accordion, policy page, or reviewer profile. The page-level block must state the event and scope.

Anatomy

The block has seven identifiable regions:

1. Role label: says “Reviewed by,” “Medically reviewed by,” or another declared variant without confusing review with authorship.
2. Reviewer name: uses the person’s public professional name and links to a stable profile when available.
3. Relevant credentials: includes only qualifications that support this review scope.
4. Affiliation or relationship: identifies the current organization or material publisher relationship where it helps the reader judge independence.
5. Review date: records the most recent completed review of the stated scope.
6. Scope statement: names the claims, calculations, procedures, or sections actually checked.
7. Role boundary: clarifies meaningful limits, conflicts, or whether the reviewer did not author, test, or endorse the subject.

Keep those labels in live text. An annotated screenshot explains the design, but it cannot become the only source of the review details.

Stay Updated on AI Visibility Trends

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

Email address

Subscribe

Design examples

Variants change the label and evidence, not the core data contract.

Standard expert review

Use “Reviewed by” when a domain specialist checks accuracy and completeness without a regulated professional label. Show the discipline in the credential line and name the reviewed sections.

Medical review

Use “Medically reviewed by” only when the reviewer holds a relevant, current health credential and the review falls within that professional scope. Display the credential plainly; do not compress different professions into “Dr.”

Legal or compliance review

Name the jurisdiction, standard, or regulatory area checked because legal accuracy is scope-dependent. The label must not imply representation or individualized advice.

Financial review

Identify whether the reviewer checked tax, accounting, lending, insurance, investment, or pricing claims. A broad “financial expert” label does not establish relevance.

Technical review

State the product, version, environment, or implementation area the reviewer verified. If commands were executed, say so; if the review was desk-based, do not imply testing.

Methodology and data review

Name the statistical or domain methods checked, including calculations, denominators, exclusions, and inference limits. Do not call it peer review unless an actual documented peer-review process occurred.

The compact rendering uses one wrapping line for label, name, credential, and date, followed by a visible scope sentence or link. The expanded rendering uses two short paragraphs. Neither may truncate scope.

Parameters

The source record must support both compact and expanded renderings without duplicating facts.

credentials records relevant public qualifications, not every suffix earned. scope is visible and mandatory because a name cannot tell readers what was checked. Keep private review correspondence outside the component.

Syntax and code examples

The portable directive is canonical. Until a dedicated Hugo renderer exists, use the callout adapter while preserving every canonical fact.

Portable Markdown directive

:::reviewed-by{reviewType="technical" reviewerName="Alex Rivera" credentials="Senior platform engineer" affiliation="Northstar Cloud" reviewedOn="2026-08-27" display="expanded"}
## Technically reviewed by

Scope: installation commands, supported versions 4.2–4.4, Linux prerequisites, expected output, and rollback steps were checked in clean Ubuntu 24.04 and Debian 13 environments.

The reviewer verified the procedure but did not assess third-party plugins or custom infrastructure.
:::

The first heading maps to title; the first paragraph maps to scope; the remaining paragraph maps to roleBoundary.

Hugo shortcode

{{< callout type="note" title="Technically reviewed by" >}}**Alex Rivera — Senior platform engineer, Northstar Cloud**  
Reviewed 27 August 2026. Scope: installation commands, supported versions 4.2–4.4, Linux prerequisites, expected output, and rollback steps were checked in clean Ubuntu 24.04 and Debian 13 environments.

The reviewer verified the procedure but did not assess third-party plugins or custom infrastructure.{{< /callout >}}

All Hugo parameters are named. Do not combine a positional callout type with the named title parameter.

WordPress block and shortcode

<!-- wp:amicited/reviewed-by {"reviewType":"technical","reviewerName":"Alex Rivera","credentials":"Senior platform engineer","affiliation":"Northstar Cloud","reviewedOn":"2026-08-27","display":"expanded"} -->
<p>Scope: installation commands, supported versions 4.2–4.4, Linux prerequisites, expected output, and rollback steps were checked in clean Ubuntu 24.04 and Debian 13 environments.</p>
<p>The reviewer verified the procedure but did not assess third-party plugins or custom infrastructure.</p>
<!-- /wp:amicited/reviewed-by -->

[reviewed_by review_type="technical" reviewer_name="Alex Rivera" credentials="Senior platform engineer" affiliation="Northstar Cloud" reviewed_on="2026-08-27"]Scope: installation commands, supported versions 4.2–4.4, Linux prerequisites, expected output, and rollback steps were checked in clean Ubuntu 24.04 and Debian 13 environments.[/reviewed_by]

Imports and exports must preserve the reviewer role, date, scope, and boundaries even when the theme presents them differently.

Examples

Good: bounded methodology review

This works because the qualification is relevant, the checks are concrete, and the final sentence prevents readers from extending statistical review to data collection or purchasing advice.

Bad: borrowed authority

Expert verified ✓ Reviewed by Dr. Sam. All facts are accurate and approved.

This fails because the reviewer cannot be identified, “Dr.” does not reveal a relevant discipline, there is no date, and “all facts” sets an unlimited scope. The checkmark makes an unsupported governance claim look like certification. “Approved” also suggests endorsement without explaining whether the person checked evidence, calculations, safety, style, or merely saw the draft. Repair it by naming the reviewer, qualification, date, reviewed claims, excluded areas, and any material relationship.

Schema markup and accessibility

For a WebPage, map a real reviewer to Schema.org reviewedBy as a Person or Organization, and map the completed review date to lastReviewed. The visible name and date must match the structured values. Keep dateModified separate: editing a page and reviewing it are different events, so one date must not be copied into the other automatically.

The reviewer Person may include a stable url, affiliation, knowsAbout, and verifiable hasCredential when supported. Do not invent credentials. Do not use author unless the person also genuinely authored content and both roles are visible.

This is not a consumer Review, rating, testimonial, endorsement, or ClaimReview. Do not generate stars, reviewRating, itemReviewed, or product-review markup from it.

Render the block as a semantic <aside> or labelled region in normal order. Use the visible label as its accessible name and the person’s name as link text. Keep credentials in text; a checkmark alone cannot indicate review.

The component must reflow at 200% zoom and preserve name–credential–date–scope order. An avatar is supplementary: use empty alternative text when adjacent text names the person, and never make it the only link. Avoid live-status roles for static provenance.

Writing rules

Scope converts a trust claim into an auditable statement. State what the reviewer did. Prefer checked, reproduced, tested, compared, verified, or reviewed over oversaw, validated quality, or ensured excellence.

Use the reviewer’s public professional name. List one to three qualifications that directly support the scope, keeping the credential line within 120 characters. Spell out an unfamiliar qualification on the profile or first use. A degree, license, certification, role, or years of domain practice can establish relevance; prestige that does not match the subject cannot.

Write the scope in 12–60 words and one or two sentences. Name concrete claim groups, sections, calculations, versions, jurisdictions, source classes, or procedures. Add a role boundary of no more than 35 words whenever readers could reasonably infer authorship, hands-on testing, legal representation, endorsement, or broader review than occurred.

Record the date on which the reviewer completed the stated check. If a substantive edit changes a reviewed claim, either obtain a new review and date or remove the attribution from the affected scope until review is complete. Copy edits outside the scope do not reset it. Coordinate the page’s published and modified dates through the freshness element rather than silently treating review as publication.

Keep the tone factual. Do not argue the page’s conclusion. Obtain consent to attribution and record the version, scope, findings, resolutions, date, and approver internally.

Never put these inside a reviewed-by block:

• promotional praise, a testimonial, star rating, recommendation, or product endorsement;
• a claim that the reviewer guarantees accuracy, safety, outcomes, compliance, or future freshness;
• irrelevant credentials, honorific inflation, or an unverifiable “expert” label;
• the full reviewer biography, career history, contact pitch, or social follower count;
• article conclusions, new factual claims, sources, or methodology that belong in the body;
• private email, license numbers not intended for publication, or internal review comments;
• an affiliate button, offer, price, newsletter form, or other conversion control.

“Independent” requires care. It means the reviewer had a separate checking role and freedom to challenge the author; it does not automatically mean the person has no financial relationship with the publisher. State employment, consulting, supplied-product, or other material relationships plainly when they could affect the reader’s judgment.

Post types that use it

The postTypes array creates the machine-readable relationship. It identifies formats where an expert review event commonly adds material assurance; it does not require a ceremonial reviewer on every page.

Other post types use the element when the same risk and completed review exist. Inclusion in the array never authorizes a publisher to add a reviewer’s name before the work is done.

QA checklist

• A person other than the author completed a real subject-matter review of the relevant page version.
• The reviewer’s expertise directly matches the stated scope.
• The public name, one to three relevant credentials, and any material affiliation are accurate and verifiable.
• The reviewer consented to the attribution and its exact wording.
• The visible date records completed review, not publication, editing, approval, or a scheduled future check.
• The scope names specific claims, sections, procedures, versions, jurisdictions, or calculations.
• A boundary sentence prevents any likely confusion about authorship, testing, endorsement, advice, or excluded material.
• “Independent,” “peer reviewed,” “tested,” “approved,” and “verified” appear only when evidence supports those exact claims.
• The block sits below author and freshness information and before the opening answer, or a compact attribution links to one synchronized expanded block before sources.
• It is not merged with the author bio or hidden only in a footer, image, hover state, accordion, or generic policy page.
• It does not sit directly beside a testimonial, rating, trust badges, price, offer, affiliate link, or call to action.
• A substantive change inside the reviewed scope triggered re-review or removal of stale attribution.
• Internal records preserve the reviewed version, scope, findings, resolutions, date, and consent.
• reviewedBy and lastReviewed, when emitted, match the visible reviewer and date; dateModified remains independent.
• The component does not emit consumer Review, rating, testimonial, or product-endorsement schema.
• The label, name, credentials, date, and scope remain understandable without color, icon, avatar, or layout.
• Reviewer links use descriptive names, focus is visible, text reflows, and static content has no alert role.
• Markdown, Hugo, and WordPress representations preserve the same canonical facts.
• Screenshot comments name future captures only; no nonexistent image is rendered.

FAQ

Is a reviewed-by block the same as an author bio?

No. The author created the page; the reviewer independently checked a defined part of it. Name both roles separately, even when both people have similar credentials.

Does every article need an expert reviewer?

No. Use independent review when errors could materially affect health, money, legal rights, safety, technical implementation, or the validity of data-led conclusions. Routine low-risk editorial content normally needs an editor, not a ceremonial expert name.

What should the review scope say?

Name the claims or sections actually checked, such as dosage safety, tax assumptions, methodology and calculations, or compatibility steps. Avoid unlimited phrases such as “fully verified” unless the reviewer checked the complete page against an explicit standard.

Should the review date change after every edit?

No. Change it only when the reviewer checks the affected scope again. Copy edits outside that scope do not reset the review date, while a substantive change to a reviewed claim makes the existing attribution stale until re-review.

Can an employee be the independent reviewer?

Yes, if the person did not author the material, has relevant expertise, can challenge it, and any employment or commercial relationship is visible. Independent review describes the editorial role, not necessarily financial independence.

A reviewed-by block earns trust only when it exposes accountable work. Name the reviewer, connect expertise to scope, preserve the date, disclose meaningful limits, and remove the attribution whenever the reviewed version no longer matches the page.