Why does the author URL matter so much?

An author is only a useful trust signal if the engine can resolve it to a real entity. A Person node with a name and nothing else is a name in a box. Point the URL at a genuine author page with a bio and their other work, and the byline starts carrying weight.

Do I need dateModified?

Include it when the article has genuinely changed. Bumping it on every deploy to look fresh is a well-known trick and worth avoiding, because it costs trust when the visible content clearly has not changed.

Free tool · Structured data

Article Schema Generator

Build Article JSON-LD from a post URL, with the author fields that carry E-E-A-T.

No sign-up. We read the page to fill this in. Nothing is stored.

In the output

What you get

Valid Article or BlogPosting JSON-LD
Author as a named entity with a URL
Published and modified dates
The canonical page reference

That author, datePublished, dateModified and mainEntityOfPage are all populated, which is the set that carries E-E-A-T signals.
That the author is a named entity with a URL rather than a bare string, which is what lets an engine connect the piece to a person.
That the headline matches the page, since a mismatched headline is a common reason the markup is ignored.
That the output validates as Article or BlogPosting before it ships.

Three steps

How to use the Article Schema Generator

Enter the article URL

We read the headline, description, image, dates and author the page already publishes.

Name the author properly

A name plus a profile URL. This is the field most often left as plain text, and the one that carries the most weight.

Paste the block into the page head

One Article block per article.

Why it matters

Why article markup carries more weight than it used to

Author fields are credibility signals.

A named author with a profile URL is one of the clearest things a retrieval system can use to decide whether to trust a page.

Dates decide freshness.

datePublished and dateModified are how an engine tells a current piece from a stale one. Omitting them makes everything look undated.

The information already exists.

It is on the page, in the byline. Markup is only the act of saying it in a form a machine parses.

It stops happening by hand.

Doing this per post is fine for a month. It is why generated markup, tied to the content, is the version that survives.

After you run it

What to do with the result

Complete author and date fields are among the clearest credibility signals a retrieval system can read, and they are cheap: the information already exists, it just is not marked up. If you publish regularly, doing this by hand once per post is the part that stops happening by month three, which is the argument for having it generated where the content is written.

AI SEO content writer

Frequently asked questions

BlogPosting is a subtype of Article and Google treats them interchangeably for rich results. Use Article unless your CMS already emits BlogPosting; consistency across your site matters more than the choice itself.

Same cluster

More free tools

Organization Schema Generator

Define who your company is, once, in the markup search and answer engines read.

LocalBusiness Schema Generator

Generate the LocalBusiness markup behind local pack and map results, from a location page.

llms.txt from Sitemap

Turn any domain’s sitemap into a first-draft llms.txt, grouped into sections automatically.

See where you actually stand.

A free tool checks one thing once. Veritas watches all of it, continuously, across every engine that decides whether you get cited.

GOOGLE · CHATGPT · PERPLEXITY · GEMINI · AI OVERVIEWS