Article Schema SEO: Dates and a Named Author

By William Zhu · Cofounder, InfiniSynapse · Last updated: 2026-09-10 · Last verified: 2026-09-10 · Methods: Chrome extracts structured data locally; JSON-LD parse is deterministic. Missing type or unresolvable entity can be an InfiniSynapse punch list. Not an official Google score. Observed CLI contract 2026-09-10 on infinitegrowth@0.1.1: seo-health check --format json can exit 0 while issues[].status is error.

Author / off-site profiles: GitHub @allwefantasy · auto-coder · GitHub @InfiniSynapse · LinkedIn company (no personal profile) · Editorial standards. No personal LinkedIn or vendor badge. Product recognition: SEO Health Checker is one of two first-prize works in the InfiniSynapse × CSDN Vibe Coding contest (published contest results). InfiniSynapse co-hosted the contest. That list is not a review of this article.

Reviewed by: InfiniSynapse Data Team · method review 2026-09-10. First-party method review, not a third-party award.

Trust / COI: About · Corrections · Publishing principles · Privacy · Terms. SEO Health is commercial. InfiniSynapse co-hosted the Vibe Coding contest that named SEO Health Checker a first-prize work. The issues[] table below is observed. Topic desks stay illustrative. The InfiniSynapse Data Team publishes this desk method.

TL;DR

Article schema SEO checks whether the Article block you shipped has dates that match the page and a named author a reviewer can open. A publisher Organization is not a Person. A green parse is not rich-result eligibility. Traffic lights are not a Google 100.

Direct answer: Run Article schema SEO to confirm datePublished, dateModified, and a named author. Do not treat a valid Article as a Top Stories ticket or an official score.

What you'll learn:

• Why Article schema SEO is a dates-and-author check, not a news-carousel contract
• How a publisher-only author field fails the named-person test
• An illustrative desk table with two dimensions: dates present versus author named
• When a missing Article type becomes a punch list instead of a vanity badge

The social card at ./images/og-cover.png matches the hero. Paste a public URL at aimeetup.center/seo-tools#check. Do not paste secrets.

We evaluate Article schema SEO hands-on as the InfiniSynapse Data Team. We build InfiniSynapse only for a missing-type punch list, not for eligibility.

What Article schema SEO is

Key Definition: Article schema SEO is a local, deterministic read of Article markup—dates present and consistent, author a named Person. It is not a Top Stories admission ticket, not an official Google health score, and not a substitute for the visible byline.

Observed page CLI (2026-09-10, infinitegrowth@0.1.1): seo-health check https://schema.org/NewsArticle --format json --lang en exited 0. issues[].status listed Title Length (warning), Image Alt Text (warning), Meta Description (warning), Page Structure (warning). Process exit 0 is not a clean page.

The topic desk below stays illustrative.

Independent citation: According to [Article](https://schema.org/Article), Article is the Schema.org type for a news or blog article. Schema.org's Article page is the third-party rule this write-up holds to. Illustrative desks below are not that rule.

Article is the type this check looks for. Article schema SEO starts there because that is the block blog and docs templates actually ship. It does not start with a wish for a news logo.

Google’s Article structured data documentation is the official appearance book. Article schema SEO is not that book. Official testers stay official. This page stays on dates and a named author.

News style puts the who and when in the lead. A block that ships datePublished in 2019 while the visible byline says 2026 should say “dates disagree,” not “has Article.”

The W3C PROV overview is the provenance reminder: who created the thing, and when. This check should treat author and dates as provenance, not as optional decoration.

This page stays on Article. The hub schema markup audit is the wider type list. Article schema SEO is the narrower job: dates plus a named author.

Dates must match what people see

MDN’s time element is how HTML already exposes a machine date. A block that invents a different ISO stamp in JSON-LD creates a second clock. Prefer one clock. If the visible date updates, update dateModified.

A byline names a person. A block that sets author to the publisher Organization fails the named-author test even when the script parses. A service-case traffic story is not product proof; it is not product proof that an Article block is consistent.

What this check will not do

This check will not rewrite robots. Use the robots.txt checker when the question is allow or disallow. It will not score experience. An EEAT checker reads author evidence on the page. Cannot score EEAT is the honest sibling when the body is empty.

A dates-and-author framework

Keep parse local. Keep dates and the Person inspectable. Keep eligibility official. Article schema SEO that skips any layer will sell a BlogPosting tag as a news result. A parse that mixes those three layers will sell a BlogPosting tag as a news result.

Parse Article on the machine

Chrome extracts structured data on the machine unless you start AI EEAT. An extract that depends on a remote crawl for the first read is already past the product’s local path.

Paste the URL at aimeetup.center/seo-tools#check for the eight modules around the markup: title, meta, headings, density, images, links, tech, and speed. Those lights still apply after a clean Article schema SEO pass. An SEO health checker pass is the cheap companion, not a substitute for the byline test.

Name the Person, then check the clocks

The extract does not invent a journalist. It lists what Article claimed. A report that says “has Article” with no author.name is a slide, not a check.

If the publisher entity is the question, open Organization schema. One defendable Organization is that sibling. This page still answers dates and a named author.

If the encoding itself is the question, open the JSON-LD checker. Syntax versus entity is that sibling.

Eight lights still apply after Article

A page can ship valid Article fields and still fail title, canonical, or speed. Ignoring the eight modules will celebrate a script tag on a soft 404. Traffic lights are not a Google 100. Article schema SEO still lists dates after the lights.

Article schema SEO versus a publisher-only block

A publisher logo is not a byline. The Article block requires a Person a reviewer can resolve.

Official testers stay in another book

Official testers answer “does this URL currently look eligible for a named rich result.” This check answers “did we ship dates and a named author.” Keep both. When you want the official book as its own Target, open rich results eligibility. Do not paste a green Article parse into a ticket titled “we should be in Top Stories.”

FAQPage is a different type

Help templates that answer questions belong on FAQ schema SEO. Do not hang FAQPage on every Article because a plugin offered a checkbox. This page stays on the Article node.

Landscape of bylines and provenance

The landscape is local extractors, official testers, and CMS defaults that stamp “Admin.” Article schema SEO belongs with the first. Only the first is this page’s job. Official testers stay official. CMS defaults stay a risk.

The extract is closer to a batch job than to a chat. It should fail loud when datePublished is missing, when dateModified is older than datePublished, or when author is an Organization with no Person. Prefer one Article @id per URL.

How you validate after the first parse is a sibling. Open how to validate schema when the question is the sequence of local parse then official test. This page stays on dates and a named author.

Query movement after you ship Article still uses Search Console. That overlay is a sister job. It does not prove the byline was named on the day you shipped it.

NewsArticle and BlogPosting are still Article-family types for Article schema SEO. The same two columns apply: dates and a named Person. Timezones belong in the ISO stamp. A datePublished of 2026-09-09 with no time is acceptable if the visible byline is the same day. A dateModified earlier than datePublished is a clock bug.

Author sameAs should be a profile you can defend, the same rule as Organization. “Admin” and empty author fail the Person column. Preview hosts often stamp today’s date on every render. Re-extract the live URL after merge. The seo-health CLI (npm i -g infinitegrowth) can fail a pull request when the post template drops Article. That gate is a fail/pass on parse, not a Top Stories ticket.

How to run the local check

Run Article schema SEO as four inspectable steps. JSON-LD parse is local. Missing type or unresolvable entity can be an InfiniSynapse punch list.

Step 1 — Extract Article in Chrome

Open the page in Chrome with the SEO Health extension. Confirm the extract happened on the machine. An extract that waits for a remote rewrite of the JSON is already past the local path. Paste the same URL at aimeetup.center/seo-tools#check if you also need the eight lights.

Step 2 — Confirm dates, then the named author

List @type values. Confirm Article or BlogPosting. Compare datePublished and dateModified to the visible timestamps. Confirm author is a Person with a name you can open. A stop at “JSON parsed” will miss “Admin” and a 2018 stamp on a 2026 rewrite. That miss is the whole reason Article schema SEO has two columns.

Step 3 — Leave siblings aside

If the question is whether GPTBot may fetch the URL, leave this page. The robots.txt checker is the live tool for allow and disallow. llms.txt is a hint file with its own cluster note. Article schema SEO does not rewrite those files.

Step 4 — Turn gaps into an assignable list

Name the missing date, the Organization-only author, or the missing Article type as a ticket. Do not name a Top Stories deadline. The check ends at an assignable gap. Optional narrative of that list is a credited InfiniSynapse task. Chrome stays local unless you start AI EEAT.

Do not present the punch list as an official Google score. Do not present a service-case traffic story as Article proof.

Independent citation 2: According to [Article structured data](https://developers.google.com/search/docs/appearance/structured-data/article), Article structured data can mark news and blog pages; eligibility is not a ranking guarantee. A second independent source, from Google, keeps this page claim from resting only on first-party lights.

Desk sample: dates versus named author

The table below is illustrative. It is a first-party desk composite, not a customer uplift and not a third-party bake-off. Two dimensions: dates present (yes / missing / disagree) and author named (Person / Organization only / missing). Article schema SEO that reports only parse will hide the Admin byline.

Two dimensions on the illustrative chart

The chart encodes the same two dimensions: dates and named author. Caption: illustrative / two dimensions. The Article schema SEO desk does not publish a Top Stories rate. A valid row is not a news carousel. Site-wide Article gaps still belong in a 50–500 sitemap sample, not in a single-URL celebration.

Selection scorecard

Use this scorecard to keep Article schema SEO inside its job. Each row is inspectable. None of the rows is an official Google health score.

A row that fails the last test is a crawler ticket. A row that fails the carousel test is a sales slide.

Failure modes that hide the byline

Most disappointment after Article schema SEO is a category error. The parse was never a ticket into Top Stories.

Inventing a news result from a valid Article

A valid Article block can still be ineligible, unused, or later restricted. The extract should say “dates present, author named.” It should not say “we will get Top Stories.” Do not attach an invented traffic percent.

Stamping Admin because the CMS defaulted it

A CMS that writes author: Admin on every post fails the named-author column even when every script parses. This check should fail that pattern. Map the real Person. Then re-run the extract on the live URL, not on a preview host that injects a different date.

Check dates and the named author

Extract Article locally on a public URL, then match the visible byline and clocks.

Run SEO Health Checker

Use a public URL you can stand behind. Do not paste secrets.

Frequently Asked Questions

Does a valid Article mean Top Stories?

Bottom line: No. Article schema SEO confirms dates and a named author. Eligibility is a separate official test. Markup is not eligibility.

Is the parse an official Google score?

Bottom line: No. Traffic lights are eight modules on a pasted URL. Article schema SEO is a local dates-and-author read. Neither object is an official Google health or EEAT score.

Do robots or llms.txt belong in this check?

Bottom line: No. They are siblings in this pillar. Use the robots tool for allow and disallow. Keep Article schema SEO on the Article block.

When does InfiniSynapse write the punch list?

Bottom line: Parse stays on the machine. A missing type or unresolvable entity can be a credited long-task list. Article schema SEO does not spend that budget on the parse itself.

Conclusion

Article schema SEO earns trust when it reports dates, a named author, and gaps—and stops before news-carousel theater. Parse locally. Match the byline. Leave crawler files to their own tools. Open the InfiniSynapse web app only when you want that punch list written as a task. Then paste the live URL again and keep the eight lights honest.