Article Schema vs BlogPosting Schema: Does It Matter for SEO?
BlogPosting is not a rival to Article schema. It is a child type of it, sitting one level down in the Schema.org hierarchy. That single fact changes how you should think about the choice. Most of the debate about which one to use misses the point entirely, because Google does not treat them as competing formats. What Google cares about is whether your structured data is accurate, complete, and matches what is actually on the page.
On this page
What the Two Schema Types Are
Both Article and BlogPosting come from Schema.org, the shared vocabulary that search engines use to read structured data. Article is the parent type. BlogPosting inherits everything from it and adds semantic precision for one specific kind of content, a post published in reverse-chronological order, typically on a blog, with a named author.
Because BlogPosting extends Article rather than replacing it, every property you can attach to an Article, headline, author, datePublished, image, publisher, is equally valid on a BlogPosting. There is no field you lose by choosing one over the other. The decision is about semantic fit, not capability.
How Google Reads Each One
Google’s structured data documentation groups Article and its subtypes together for rich result eligibility. A BlogPosting does not get treated differently from an Article when Google decides whether to show an author byline, a date, or an image in search results. The crawler is looking at the fields you have populated, not at which branch of the Schema.org tree you picked.
Where the distinction does matter is in how accurately the type label describes the content. Google’s systems are built to understand page context, and a mismatch between schema type and actual content is a signal that the markup was applied lazily. It is unlikely to cause a penalty, but it adds noise where there should be clarity.
When BlogPosting Is the Cleaner Choice
If you are writing a dated post on a blog, attributed to a named author, and it will appear in a feed ordered by date, BlogPosting is the semantically correct pick. The type tells Google’s parsers exactly what they are looking at before they read a single field value.
Practical signals that point to BlogPosting:
- The page is part of a blog or news feed with a visible published date
- A single, named human author is clearly attributed
- The content is time-specific or written in a first-person or editorial voice
- The post would look out of place if the date were removed
For most business blogs and content marketing posts, BlogPosting is the right call and requires no further justification.
When Article or a Tighter Subtype Fits Better
Evergreen guides, long-form technical references, and formally structured how-to content often suit the broader Article type because they are not tied to a publication date in the way a blog post is. A comprehensive reference on, say, server configuration does not really belong in a chronological feed, and labelling it BlogPosting would be a stretch.
Tighter subtypes to consider
Schema.org also provides more specific options. NewsArticle fits content published by a journalistic outlet with a clear news hook. TechArticle works well for documentation and technical tutorials. If your content matches one of these precisely, using the specific type is better than defaulting to the generic Article. The logic throughout is the same, match the schema to what the content is, rather than reaching for the nearest familiar label.
The Fields That Move the Needle
The type declaration is table stakes. The fields you complete are where the real SEO work happens. Google uses a specific set of properties to generate rich result features, and leaving them empty means leaving that display real estate on the table.
Fields Google uses for Article rich results, and what each one affects:
| Field | What Google Does With It | Priority |
|---|---|---|
| headline | Displays in the rich result title | High |
| author | Powers author byline in search features | High |
| datePublished | Shows freshness signals in results | High |
| image | Required for Top Stories carousel eligibility | High |
| publisher | Associates content with a known entity | Medium |
A thinly populated BlogPosting with only a headline set will underperform a well-populated Article every time. Fill the fields properly, and the type label becomes secondary.
Implementing This in WordPress
Checking your current output
Most WordPress SEO plugins, Yoast, Rank Math, and similar tools, auto-assign a schema type at the site level and let you override it on a per-post basis. Yoast defaults to Article for posts unless you manually switch it. Rank Math gives you a dropdown in the post sidebar where you can select BlogPosting without touching any code.
To check what your site is currently outputting, paste a post URL into Google’s Rich Results Test and look at the JSON-LD block for the @type value. If it says Article but you are running a blog with dated posts and named authors, switching to BlogPosting is a five-second change in your plugin settings that makes the markup more honest.
Beyond the plugin defaults
For sites that need a more considered approach across multiple content types, the decisions around what schema properties to include and what to leave out are worth working through carefully rather than just accepting whatever the plugin outputs.
We’d argue that pumping out schema-decorated content at volume rarely helps. A handful of well-marked-up pages on topics you genuinely own will do more than a hundred thinly populated posts where the structured data is just another checkbox ticked on the way to publish.
So does the Article vs BlogPosting choice matter? Less than most people think. Does getting the fields right matter? Considerably more than most people bother with. Which of those two things is your site currently neglecting?