Coder Legion - Recent posts tagged visible

Article Schema Guide: Author, Dates, and Breadcrumbs

Sat, 03 Oct 2026 15:50:00 +0000

Article schema helps a search engine identify an article, its author, publication and update dates, primary image, publisher, and place in the site hierarchy. It does not make weak content trustworthy, and valid markup does not guarantee a special search appearance.

For a small business site, the safest implementation is a short JSON-LD graph that describes facts already visible on the page. The page should show the same author and dates that the markup declares. Keep those values in one content source when possible so a template change does not create dozens of contradictory blocks.

What Google supports for articles

Google documents Article, NewsArticle, and BlogPosting as supported types for article pages. A normal company guide can use BlogPosting or Article. The type should describe the page honestly. Using NewsArticle does not turn a company blog post into news.

Google's Article documentation currently lists recommended properties rather than a separate set of required properties. That does not make an empty Article object useful. Include the applicable properties that identify the page and match its visible content:

headline;
image;
datePublished;
dateModified;
author;
publisher;
mainEntityOfPage.

Add a separate BreadcrumbList when the page has a visible hierarchy that helps people understand where they are.

Match the visible page first

Structured data is a description of the page, not a hidden SEO version of it.

Visible page element	JSON-LD property	Check
Article H1	`headline`	Same meaning and no exaggerated alternate title
Author byline	`author.name`	Same person or organization
Author profile link	`author.url`	Resolves to the entity's canonical page
Published date	`datePublished`	Same calendar date
Last updated date	`dateModified`	Shown only after a substantive update
Hero or representative image	`image`	Crawlable and relevant to the article
Site or business name	`publisher.name`	Correct publishing entity
Visible navigation trail	`BreadcrumbList`	Same logical hierarchy

If the page says "By Stepan Nikonov" but the markup says the author is FloxoLab, fix the mismatch. If the page shows only a publication date, do not invent a newer modification date to make the result look fresh.

A practical JSON-LD example

This example uses one @graph with a BlogPosting and a BreadcrumbList. Replace every example value with the final canonical URL, image, title, dates, and entity IDs for the real page.

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "BlogPosting",
      "@id": "https://example.com/guides/article-schema#article",
      "url": "https://example.com/guides/article-schema",
      "mainEntityOfPage": {
        "@type": "WebPage",
        "@id": "https://example.com/guides/article-schema"
      },
      "headline": "Article Schema Guide: Author, Dates, and Breadcrumbs",
      "description": "A practical guide to matching article JSON-LD with visible authors, dates, images, and breadcrumbs.",
      "image": [
        "https://example.com/images/article-schema-cover.webp"
      ],
      "datePublished": "2026-07-25",
      "dateModified": "2026-07-25",
      "author": {
        "@type": "Person",
        "@id": "https://example.com/about/jordan-lee#person",
        "name": "Jordan Lee",
        "url": "https://example.com/about/jordan-lee"
      },
      "publisher": {
        "@type": "Organization",
        "@id": "https://example.com/#organization",
        "name": "Example Company",
        "url": "https://example.com/",
        "logo": {
          "@type": "ImageObject",
          "url": "https://example.com/images/logo.png"
        }
      }
    },
    {
      "@type": "BreadcrumbList",
      "@id": "https://example.com/guides/article-schema#breadcrumb",
      "itemListElement": [
        {
          "@type": "ListItem",
          "position": 1,
          "name": "Home",
          "item": "https://example.com/"
        },
        {
          "@type": "ListItem",
          "position": 2,
          "name": "SEO Guides",
          "item": "https://example.com/guides"
        },
        {
          "@type": "ListItem",
          "position": 3,
          "name": "Article Schema Guide"
        }
      ]
    }
  ]
}

The final breadcrumb item can omit item when it represents the current page. Google's breadcrumb examples allow the last item to contain only a name. The positions still need to run in order.

Step 1: choose the correct article type

Use the most specific honest type:

BlogPosting for a normal blog or educational guide;
NewsArticle for actual news reporting;
Article when neither narrower type is a better description.

Do not add several types merely to cover every possibility. One accurate primary type is easier to maintain and validate. Schema.org permits many properties and nested types, while Google's search features use a documented subset. A property can be valid Schema.org and still have no effect on Google Search.

A purchasable product page is not an article merely because it contains descriptive copy. Use the product and category page SEO guide to align the visible offer, variants, availability, media, links, and Product data with the actual store template.

Step 2: identify the author as an entity

Google recommends marking each author separately and using Person for a person or Organization for an organization. Do not place several names in one name string.

"author": {
  "@type": "Person",
  "@id": "https://example.com/about/jordan-lee#person",
  "name": "Jordan Lee",
  "url": "https://example.com/about/jordan-lee"
}

For two authors, use an array of separate entities:

"author": [
  {
    "@type": "Person",
    "name": "Jordan Lee",
    "url": "https://example.com/about/jordan-lee"
  },
  {
    "@type": "Person",
    "name": "Morgan Cruz",
    "url": "https://example.com/about/morgan-cruz"
  }
]

The profile page should help identify the author. A useful page can explain role, experience, areas of work, and published material. Google specifically recommends an internal author page linked with author.url when available. sameAs can point to another page that unambiguously identifies the same person or organization, but it is not a substitute for a useful on-site profile. The author authority guide shows how to connect that identity to firsthand evidence, sourcing, and update ownership without treating markup as proof.

Keep authorship factual. Do not create a fictional expert, use a reviewer who did not review the page, or add credentials that are not visible and verifiable.

Step 3: handle publication and update dates honestly

Use ISO 8601 date or date-time values:

"datePublished": "2026-07-25",
"dateModified": "2026-08-14T10:30:00+08:00"

Google recommends including timezone information when a time is supplied. A date without time can use YYYY-MM-DD. datePublished records when the article was first published, while dateModified records the most recent substantive update.

Correcting a typo, changing a button color, or rebuilding a shared footer is not a reason to tell readers that the guide was freshly updated. Change dateModified when the article's useful content, evidence, instructions, or conclusions materially change. Show that updated date on the page. The old-content decision guide explains when an existing page deserves a real update instead of a cosmetic freshness signal.

Keep dates consistent across visible copy, JSON-LD, Open Graph metadata where used, the content manifest, and sitemap lastmod.

Step 4: use a representative, crawlable image

The image property should point to an image that represents the article and can be crawled. Use an absolute HTTPS URL, not a private asset path or a CSS background reference.

Google recommends high-resolution images and supports several aspect ratios. A site does not need to manufacture misleading crops solely to fill an array. Supply the real, indexable image variants the page owns, keep their URLs stable, and ensure the visible hero corresponds to the declared image.

Step 5: connect the article to its canonical page

mainEntityOfPage identifies the page whose primary subject is the article. Its @id should normally match the clean canonical URL. Keep these values aligned:

HTML canonical;
og:url;
structured data url;
structured data mainEntityOfPage.@id;
sitemap URL;
internal links.

Mixed .html, trailing-slash, HTTP, HTTPS, and parameter versions create unnecessary ambiguity. Choose the public canonical format and use it consistently. If the sitemap lists redirects or alternate versions, use the sitemap and canonical cleanup workflow before treating structured data as the fix.

Step 6: describe the publisher once

Use Organization for a business publication and give the organization a stable @id, such as the homepage plus #organization. Reuse that ID across articles instead of creating a slightly different publisher on each page.

The logo should belong to the publisher, be crawlable, and use a stable URL. The article author and publisher do not have to be the same entity. A person can write an article published by a company.

Step 7: add breadcrumbs that match the site

A breadcrumb trail describes a typical route from a broader section to the current page. It is not a list of keywords.

Home > SEO Guides > Article Schema Guide

Each ListItem needs a numeric position and a name. Include item for linked breadcrumb pages. Use canonical URLs and the same hierarchy that the visible page and internal navigation imply.

Google can use breadcrumb markup to categorize page information in search results, but it can also choose a different display. Valid breadcrumb markup is not a promise that the full trail will appear.

Common implementation mistakes

Markup that disagrees with the page

Hidden dates, alternate authors, inflated headlines, and images unrelated to the article break the principle that structured data should represent visible content.

A new modification date on every build

If a deployment script sets dateModified to today on every release, unchanged articles appear freshly updated. Derive the date from actual editorial changes, not the build clock.

One author string containing several people

Use an array of separate Person objects. This lets each author have a name and identity URL.

Relative or noncanonical URLs

Use absolute public URLs in JSON-LD. Do not expose staging hosts, .html paths, tracking parameters, or image paths that require authentication.

Duplicate blocks that contradict each other

One template may generate JSON-LD while a plugin or tag manager injects another version. Inspect the rendered HTML, not only the source template. Remove or reconcile duplicate entities. Template-generated conflicts are among the technical SEO fixes that require code access, because editing one article cannot correct every generated page.

FAQ schema added to ordinary Q&A

Visible questions can still help readers. However, Google retired FAQ rich results on May 7, 2026. Do not add FAQPage markup to a guide in the hope of restoring that search feature.

Google also says its AI Overviews and AI Mode require no special schema.org markup. The AI search citation guide separates supported crawl and content practices from unsupported citation shortcuts, while the llms.txt crawler-control guide explains why an optional AI text file does not replace robots.txt or schema that matches the visible page.

Validate before and after release

Confirm the visible author, dates, headline, image, and breadcrumb hierarchy.
Validate the JSON syntax.
Test the public or preview code in Google's Rich Results Test.
Check the page in Schema.org Validator for vocabulary-level issues.
Inspect the rendered HTML for duplicate or stale JSON-LD.
Publish a small set first rather than changing every template at once.
Use URL Inspection after launch to confirm Google can access the canonical page and resources.
Monitor Search Console enhancement reports when Google provides a relevant report.

The Rich Results Test reports eligibility and errors for supported Google features. It cannot guarantee that a rich result will be displayed. Google's structured data policies explicitly state that correct markup does not guarantee special search appearance.

A compact maintenance rule

Treat article schema as generated content tied to the same source fields that render the visible page:

title -> H1 + headline
author entity -> byline + author object
published date -> visible published date + datePublished
modified date -> visible updated date + dateModified + sitemap lastmod
cover -> visible hero + image
canonical -> canonical + url + mainEntityOfPage

One source of truth prevents the most common drift. It also makes a sitewide author or URL correction safer than editing dozens of independent JSON blocks.

Sources checked

Google and Schema.org guidance was verified from primary sources on July 25, 2026.

Author Authority for SEO: Evidence Without E-E-A-T Theater

Mon, 14 Sep 2026 15:50:00 +0000

Direct answer: build author authority by assigning a real content owner, linking every accurate byline to a useful author profile, showing firsthand evidence and sources inside the article, and making review and update ownership visible. Do not chase an invented E-E-A-T score. A biography, badge, or schema field can describe authorship, but it cannot replace relevant experience, inspectable work, and accountable maintenance.

This guide covers the visible editorial evidence behind an author: ownership, relevant background, firsthand work, sourcing, external corroboration, and maintenance. It does not teach the technical implementation of Person or Article structured data, which belongs in the separate Article schema guide.

According to Google's people-first content guidance, E-E-A-T is not one specific ranking factor. Its systems use a mix of factors that can identify experience, expertise, authoritativeness, and trustworthiness, with trust described as the most important of those qualities. Google also says the quality rater guidelines do not directly influence ranking. That makes an invented E-E-A-T score, a decorative expert badge, or a biography padded with vague claims the wrong target.

What author authority can and cannot do

Element	Useful job	What it does not prove
Accurate byline	Names the person or organization responsible for the page	That the article is correct or deserves a ranking
Author profile	Shows relevant role, scope, work, and other publications	Expertise in every topic on the site
Firsthand evidence	Shows how the creator tested, measured, built, or observed something	That one example applies universally
Sources and review	Let readers trace claims and see who checked sensitive advice	That a source list can replace original analysis
External identity signals	Help confirm that the same creator exists and works in the stated field	That more profile links automatically mean more authority
Author structured data	Describes the visible author relationship in a machine-readable form	Trust that the visible page has not earned

Use the reader test. If a visitor follows the byline, can they understand who owns the article, why that person is relevant, what evidence supports the advice, and when the work was last checked?

Start with content ownership, not biography length

Assign one real owner before writing the profile. The owner should be able to defend the page's scope, correct an error, and decide when an update is substantive. A general editor may own grammar and publishing consistency, while a practitioner, reviewer, or subject specialist owns the technical or professional claims.

The correct authorship model depends on how the work was produced:

One practitioner wrote and checked the page: use that person as the author.
A writer interviewed a specialist: name the writer and describe the specialist's contribution where it matters.
A specialist reviewed sensitive advice: show a factual reviewer credit only if the review happened and its scope is clear.
An organization maintains operational documentation: an organization author can be honest when responsibility is genuinely collective and a contact or editorial owner is available.
Automation assisted production: keep the responsible human or organization as the author and disclose the process when a reader would reasonably want to know how the content was created.

Do not appoint the founder as author of every page because the name looks impressive. If the support lead owns customer troubleshooting and the engineer owns an integration guide, accurate attribution is more useful than one famous byline across unrelated topics.

Build an author page that answers relevance

A useful author page is a compact evidence index, not a motivational biography. It should let a reader understand the creator without requiring a search across social platforms.

Use the same public name shown in article bylines.
State the current role and the specific subjects the person covers.
Describe relevant work with concrete boundaries, such as implementations completed, systems maintained, industries served, or research methods used.
Link to selected articles, cases, tools, talks, repositories, or publications that demonstrate the stated work.
List credentials only when they are relevant, current, and verifiable.
Provide a correction or contact route appropriate to the site.
Link only to public external profiles that genuinely identify the same person.

FloxoLab's author profile, for example, connects the byline to a defined automation and technical SEO scope, selected work, public profiles, and a contact route. The profile supports the articles, but each article still has to carry its own useful evidence.

A profile does not need a certificate wall. A local contractor can show years in the trade, service area, licenses where applicable, photographed work, and the practical topics they cover. A software reviewer can show the test environment, screenshots, version, dataset, and limitations. Relevance matters more than the number of claims.

Connect every byline to the same author entity

Use the same canonical author page across visible bylines and the article metadata you control. Keep the displayed name, profile URL, role, and external identity links consistent enough to describe one real entity. Legitimate name changes, multiple roles, and localized biographies can be documented. Consistency does not require copying the same paragraph everywhere.

Google's Article documentation recommends identifying each author separately and using a valid url or sameAs value to help disambiguate the author. That is the technical description layer. The Article schema guide covers Person, author URLs, dates, and validation in detail. Do not duplicate that implementation inside every editorial policy.

Before adding structured data, check the visible page:

the byline names the actual author;
the byline links to the canonical profile;
the profile explains relevant background;
the structured author matches the visible author;
co-authors are separate people, not one comma-separated name;
the publisher is not mislabeled as an individual author.

Show how the author knows

The strongest authority evidence usually lives inside the article. Google's Who, How, and Why framework specifically points creators toward clear authorship, process context when useful, firsthand expertise, sourcing, and background about the author or publishing site.

Match the evidence format to the claim:

Claim type	Evidence to show	Boundary to state
Product review	What was tested, setup, screenshots, observations, and comparison method	Plan, version, test period, and untested features
Technical fix	Symptoms, configuration, commands, before and after checks, and failure path	Environment, permissions, and rollback conditions
Business result	Baseline, intervention, measured outcome, time period, and calculation	Sample size, confounders, and whether the result is typical
Professional advice	Applicable standards, primary sources, reviewer scope, and practical examples	Jurisdiction, date, and when individual advice is required
Experience report	What the creator used, visited, built, or observed	That one experience is not universal evidence

Use an inspectable method instead of saying “our experts found.” Name the dataset, sample, tool version, query, date, or project constraint. Label a planning estimate as an estimate. Link an unstable fact to its primary source in the paragraph it supports. This also makes a page easier to assess and quote accurately. The AI citation guide explains how to keep claim scope, evidence, and limitations together without promising a citation.

Use external signals as corroboration, not decoration

External evidence can help a reader confirm that the creator is active in the stated field. Useful examples include a complete professional profile, a public repository, a conference page, an industry association listing, a credited contribution, an interview, or a publication hosted by another relevant organization.

Choose quality and relevance over volume. A dormant profile on ten networks adds little. A real case, maintained repository, or credited article may say much more. Never create fake interviews, empty profiles, reciprocal “expert” pages, or paid awards merely to populate sameAs.

Keep editorial evidence separate from reputation management. The brand SERP audit covers how to inventory official, managed, influenceable, and independent results. An author page should not pretend that every third-party mention is controlled or positive.

Make update ownership visible and honest

An old article does not become current because a script changes its date. Record who owns the review, what can go stale, and what must be rechecked. Pricing, product behavior, regulations, platform limits, and interface steps may need shorter review cycles than durable concepts.

When the page changes substantially, update the visible modified or verified date according to the site's editorial policy. Keep a short revision note when the change affects a conclusion, method, safety boundary, or recommendation. Fixing punctuation does not justify presenting the article as newly reviewed.

If the original author is no longer available, assign a new maintenance owner and describe the relationship honestly. Do not leave a former employee apparently responsible for advice they can no longer review.

A small-site authority audit

Start with the pages where identity and evidence matter most: reviews, comparisons, original research, professional advice, safety-sensitive instructions, and articles that drive commercial decisions.

Export indexable articles. Record the visible author, profile destination, topic, published date, modified date, and current owner.
Flag generic or broken attribution. Look for missing bylines, dead profiles, organization names used as people, and authors assigned outside their scope.
Score evidence gaps by consequence. Prioritize unsupported financial, health, legal, security, and high-cost buying advice before low-risk definitions.
Improve the article first. Add the method, source, example, limitation, and correction path that the claim needs.
Improve the profile second. State relevant scope and link to representative work rather than repeating marketing copy.
Align technical identity. Make visible bylines, profile links, Article markup, feeds, and templates describe the same author.
Assign the next review. Record an owner and date based on volatility, not a universal freshness schedule.

A spreadsheet can track gaps, but do not turn the result into a proprietary E-E-A-T score. Use factual states such as missing, inconsistent, unsupported, stale, or verified. Those states tell an editor what to fix.

What not to do

Do not publish invented author personas. A polished headshot and biography do not make a fictional expert accountable.
Do not give every article to the founder. Attribute the person or organization that actually owns the work.
Do not add a reviewer who did not review the page. Record the review scope when specialist review matters.
Do not write credentials into author.name. Keep the name clean and describe role or qualifications in the appropriate visible field.
Do not mass-create thin profiles. One accurate profile with representative work is better than a directory of empty biographies.
Do not treat structured data as evidence. Markup describes authorship; it does not manufacture experience or trust.
Do not fake freshness. Change dates only when the content or verification work justifies it.
Do not promise rankings from E-E-A-T work. Google does not publish a single E-E-A-T score or an author-authority switch.

Verification checklist

Every important article names a real, accountable author or organization.
The byline links to one canonical profile that explains relevant scope.
The article shows how its important claims were produced or verified.
Primary sources sit close to unstable or consequential claims.
Examples, measurements, and reviews state their limits.
External profile links identify the same person and are worth visiting.
Visible authorship and Article markup agree.
Modified and verified dates reflect real work.
A current owner is responsible for corrections and the next review.

Author authority becomes credible when the whole page tells the same story: a real creator with a relevant scope produced useful work, showed enough evidence to inspect it, linked the sources that constrain it, and remains accountable for corrections. Everything else is presentation.

Sources checked

Google's guidance on people-first content, E-E-A-T, author identification, structured data, and quality rater use was verified on August 7, 2026.

Need an evidence audit, not an authority score?

FloxoLab can review authorship, source quality, claim boundaries, structured data, and content ownership, then turn the gaps into a practical correction queue.

Explore the SEO audit

Originally published on FloxoLab.