Describe the actual article
Article structured data is machine-readable information about an article page. It can describe the headline, image, author and publication details. Its purpose is to represent the content that exists, not to turn a draft into an authoritative publication. Choose a type that fits the page and ensure every asserted property can be explained to a human reviewer.
For social media marketing articles, markup should identify the real resource and supporting image without inventing a reviewer or customer result.
Begin with the visible page. Confirm the final headline, public URL, relevant image, actual publication date and genuine authorship information. Do not copy a sample author name or example date into the production template. A syntactically valid sample can still contain false information when used without replacing its illustrative values.
Make authorship truthful
If a named person wrote or reviewed the article, obtain their approval before attributing that work. Their public author profile should describe their real role and experience. If an organization is the author, use the organization accurately rather than fabricating an individual profile to make the page look more personal.
The author field should describe actual authorship. Google: Article structured data [1] documents Article properties and author identification. Retain the draft status until the required review occurs; do not manufacture a person or credential merely to populate the markup.
An AI-assisted draft awaiting human review is not a human-approved article. Keep its editorial status clear in the publishing workflow. When a reviewer approves the final article, record the reviewed version and what the person checked. Structured data should follow that truthful state rather than concealing a gap between the public byline and the production record.
Keep dates and images consistent
Use publication and modification dates that reflect actual events. A substantive update can justify a modification date. A new automated build or a request to make the site look fresh does not mean the article itself was editorially updated. Maintain a revision note when the change affects a method, source, example or product claim.
Choose an image relevant to the article. A typographic cover can identify the topic, while a diagram can support the explanation. Do not point every article to an unrelated stock image and imply that it documents the subject. Verify the image URL resolves and that access rules allow the intended public use. Ensure the visible page and machine-readable image reference remain aligned.
Worked example: a draft becomes a reviewed page
This is a hypothetical release example. A team has an article about client approvals with a draft headline, a demonstration diagram and an empty reviewer field. The publishing process creates a review preview and keeps it out of the indexing release. The draft includes a clear AI-assisted status for the editor. No person is inserted into the author property merely to satisfy a template requirement.
A human editor then checks the method, the illustration, the sources and the final wording. The product owner verifies the workflow claim. The editor approves version C on a recorded date. The release process uses the actual final headline and approved public author information. The public publication date reflects when the reviewed page is released, not when the original draft file was generated.
The diagram shows an approved asset changing to a revised version. Its caption states that it is an explanatory illustration, so the image does not imply observed customer results. The article markup identifies the page as an article and references the relevant cover. It does not invent review stars, customer ratings or product awards that the article never supplied.
Validate syntax and meaning
Use a parser to check that the JSON-LD is valid JSON. Confirm the relevant keys, value types and full URLs. Run the appropriate rich-result validation tool for the supported feature. Then inspect the rendered page and compare every important property with what the reader can actually see.
Technical validation is only part of release QA. Google: Structured data policies [2] requires markup to match visible content and says correct markup does not guarantee search appearance. Review the page, dates, image and authorship alongside the JSON-LD.
A validator may not know that an author name is fabricated or that a publication date is misleading. Add a human content review to the release checklist. The reviewer should ask whether the markup's claims are accurate, relevant and consistent with the article's public presentation.
Apply a release checklist
- The article type matches the actual content rather than a desired search appearance.
- The headline agrees with the visible main heading and the article's scope.
- The public URL and canonical reference identify the intended page.
- The author or organization information is genuine and approved.
- The image is relevant, accessible and correctly referenced.
- Publication and modification dates represent actual editorial events.
- The markup parses and the page renders with the same central content.
Repeat the meaning check after template changes. A global website update can accidentally insert the same date, author or image into all articles. Test a broad guide, a narrow workflow article and a page with a substantive revision. Those cases are more useful than checking only a single untouched sample page.
Understand the limits
Structured data does not make an article original, replace evidence or establish a first-page position. Search engines control whether a supported presentation appears. Valid markup is a useful representation of a useful article, but it is not a performance receipt.
Avoid adding unrelated schema types simply because they are associated with prominent search displays. An operational guide is not automatically a product review, a news report or a dataset. If the page genuinely includes additional content types, describe them accurately and consult the current documentation for those types. Keep FAQs useful for readers without promising a particular FAQ search treatment.
Check feature availability before promising a search display. Google: Search documentation updates — FAQ feature retirement [3] states that FAQ rich results stopped appearing in Google Search on May 7, 2026. A visible question-and-answer section can still help readers. Use accurate article markup and useful FAQs without advertising a Google FAQ result or an AEO certification.
Frequently asked questions
Should a blog use Article or BlogPosting?
Choose an appropriate supported type for the actual page. BlogPosting is an article-related type intended for blog posts. Consult the current documentation and keep the selection consistent with the publisher's content model.
Can validation guarantee a rich result?
No. Validation can identify technical problems, while search systems still decide presentation. The quality and truthfulness of the page and markup also require review.
Can the organization be the author?
Use accurate authorship supported by the content workflow. Do not invent a person merely because an example shows a person. The public information should explain who is responsible for the published work.
Should every deployment update dateModified?
No. Use a modification date for a real article update. Infrastructure deployment and editorial revision are different events and should be recorded separately.
References and source scope
- Google: Article structured data
Google Article/BlogPosting properties and truthful author identification; represents the actual page.
Source link checked 2026-10-03 - Google: Structured data policies
Google structured-data policies require visible, relevant, truthful content; correct markup does not guarantee a search feature.
Source link checked 2026-10-03 - Google: Search documentation updates — FAQ feature retirement
Official 2026 changelog says Google FAQ rich results no longer appear starting May 7, 2026; this does not invalidate visible FAQ content or general Schema.org vocabulary.
Source link checked 2026-10-03