How Article and NewsArticle schema work
Article is the general type for editorial content. NewsArticle and BlogPosting are narrower versions of it: NewsArticle for reporting produced by a news publication, BlogPosting for a post on a blog. All three carry the same core properties, so choosing between them is a question of describing the page accurately rather than unlocking different features.
The properties that matter are the headline, the image or images that illustrate the piece, the author, the publisher, and the two dates — when it was first published and when it was last meaningfully changed. The headline property has a documented maximum length, so a long title should be trimmed to fit rather than pasted in whole and truncated by the search engine.
Author deserves particular care. It should identify the person or organisation who actually wrote the piece, ideally linked to a page about them, rather than repeating the site name in a field meant for a byline.
Why Article and NewsArticle schema matter
They tell a search engine what kind of page it is looking at before it has parsed a word of the body. That distinction — editorial content with an author and a date, as opposed to a service page or a product listing — is the difference between a page being considered for news and article surfaces and being treated as an ordinary web page.
The dates carry weight of their own. For anything where currency matters — a guide to an advertising platform that changes constantly, a piece about a policy that has since been revised — an honest updated date tells both readers and machines that the page has been maintained. It is also the field most often abused, which is why an unearned one is worse than none.
Common mistakes with Article and NewsArticle schema
Touching the modified date without changing the content is the one I see most. Republishing a post with a fresh date and no new substance is a transparent trick, it damages trust with readers who notice, and it tells you nothing useful about your own archive when you come to audit it.
Next is the missing or fake author. A byline that says the company name, or a made-up writer with a stock photograph, works against the credibility the markup is supposed to support. Then there is the misuse of NewsArticle by businesses that are not news publishers: a company blog post is a BlogPosting, and dressing it as news describes the page inaccurately without buying anything.
How to act on it
Let the content management system generate the markup from the fields it already stores, so the headline, dates and byline in the schema are the same ones on the page. Hand-written article markup drifts out of date the moment somebody edits a post, and nobody notices for months.
Give every writer a real author page with a genuine biography and credentials, and point the author property at it — that is the practical, on-page half of experience, expertise, authoritativeness and trust. Update the modified date only when the content actually changed, and note what changed. If you are running a blog seriously, build this into the publishing template once as part of the content SEO setup rather than fixing it post by post.
