What to fill in and what to leave out
Required: a headline. Everything else is optional and most of it earns its
place only if it is accurate.
Worth including:
authorwith a name. An organisation is acceptable; a bare string is weaker than aPersonobject.datePublishedin ISO 8601. Any other format is silently ignored.imageas an absolute URL. Relative paths do not resolve.
Not worth inventing: wordCount, articleSection and the rest of the long tail
add nothing unless something in your stack consumes them.
Dates are where this breaks
27/08/2026 is not a date to a machine. Schema.org accepts ISO 8601 only, so a
localised format is not parsed — it is dropped, with no error anywhere. The
generator emits the right format; the trap is editing it by hand afterwards.
Match the visible page
The headline in the markup should be the headline on the page, and the author should be the author shown. Markup that describes a different article than the one rendered is a manual-action risk, not a shortcut.
Questions
Article, NewsArticle or BlogPosting?+
NewsArticle for reporting with a publication date that matters. BlogPosting for a personal or company blog. Article for everything else. Google treats them similarly; the specificity helps other consumers more than it helps search.
Does this get me into Top Stories?+
No. Top Stories requires being an approved news publisher, and markup is a prerequisite rather than a qualification. For an ordinary site, Article markup mainly helps a crawler understand authorship and dates.
Which date should datePublished be?+
The date the article first appeared, in ISO 8601. Use dateModified for substantive updates only — changing it every time a typo is fixed teaches consumers to ignore it, and it will not make the page look fresh.
Is a headline over 110 characters a problem?+
It is truncated by Google, which the validator warns about. It is not an error, but the tail is wasted — and if your headline needs 110 characters, the title tag has the same problem.