- A publisher needs clean starting examples.
- Different article templates need distinct subtypes.
- Author and publisher nodes must be reused consistently.
- The team needs a reference without a workflow prompt.
Examples and reference
Choose the article subtype that matches the visible editorial asset
Article examples should demonstrate real editorial page types, visible authorship, publication dates, modification dates, images, publisher identity, and the canonical page relationship.
Current platform reality
Separate Schema.org meaning from Google feature eligibility.
Google supports Article structured data for news, blog, and sports articles. TechArticle and BlogPosting can provide more specific Schema.org meaning when they accurately describe the visible content.
Use and avoid
Apply the type only when the visible role and evidence support it.
- Using Article on product or category pages.
- Publishing dates that differ from visible content.
- Using an author name without a canonical profile.
- Adding decorative images as the main article image.
Implementation model
Make the page role, identity, fields, and validation decisions in order.
Choose the subtype
Match Article, BlogPosting, or TechArticle to the visible role.
Connect the author
Use a stable Person or Organization identity.
Connect the publisher
Reference the canonical Organization node.
Use visible dates
datePublished and dateModified must match the article.
Provide crawlable images
Use relevant image URLs in suitable aspect ratios.
Acceptance checks
Do not approve the markup because the JSON parses.
The content, entity ownership, canonical URLs, policy state, and maintenance source must also pass.
Editorial page
The URL is genuinely an article or guide.
Subtype fit
The selected type is specific and accurate.
Author identity
The author is visible and linked.
Publisher identity
The publisher node is stable.
Date accuracy
Dates reflect real editorial events.
Image relevance
Images belong to the article and are crawlable.
Implementation examples
Use the examples as a starting structure, not production data.
Replace every placeholder with approved visible values. The examples do not create eligibility or guarantee a search appearance.
Primary sources
Use current Google and Schema.org documentation as the source of truth.
Google structured data introduction
Open the official sourceGoogle general structured data guidelines
Open the official sourceGoogle structured data testing tools
Open the official sourceGoogle article structured data
Open the official sourceSchema.org Article
Open the official sourceSchema.org BlogPosting
Open the official sourceSchema.org TechArticle
Open the official sourceQuestions
Article Schema Examples for Editorial, Blog, and SEO Content Pages questions.
Which article type should be used?
Use the most specific accurate subtype supported by the visible editorial role.
Are there required Google Article properties?
Google currently says there are no required Article properties, but recommends adding the properties that apply.
Should every author have a Person node?
Use a stable identity pattern and visible author profile where appropriate.
Can an example be copied unchanged?
Replace every placeholder with approved visible data and validate the final live URL.
Next route
Prepare schema cues after visible copy, entity ownership, and URLs are approved.
MIRENA can audit the page role, identity, fields, current feature support, and validation route. Production markup still needs human review and live testing.
Founder access is €20 every 30 days excluding VAT for one seat and one active MIRENA instance. OpenAI account rules and usage limits remain separate.