Audit article structured data by comparing the markup with the article a visitor can actually read. Check the declared type, headline, author, dates and image references; then validate the deployed page. Valid JSON alone does not establish that the information is accurate or useful.
Start with the visible article
Before inspecting a script, write down the page’s headline, credited author, publication information and representative image. If a value is unknown, resolve the editorial record or omit unsupported optional information. Do not fill gaps with a fictional expert or an assumed publication date.
Google documents Article, NewsArticle and BlogPosting for applicable article content and explains supported properties in its Article structured-data documentation. Use that documentation for implementation requirements rather than copying an unrelated publisher’s entire markup graph.
Our practical recommendation is to maintain one authoritative set of article metadata in the CMS. The visible page and structured data should draw from the same editorial values wherever your existing publishing system allows it.
Run three separate checks
First, check syntax. A broken JSON string cannot express the intended data. Inspect the production response, not only an editor preview, because templates and escaping can alter the result.
Second, check meaning. A syntactically valid author named “Admin” may be an unhelpful default. An image URL may point to a logo when the field was intended to represent the article. A future publication date may reveal a timezone or scheduling error.
Third, check consistency. Compare the markup with the visible headline and dates, the page’s canonical URL, and the author’s public profile when one exists. Record mismatches with their exact field names so the person maintaining the template can reproduce the problem.
Example: a refresh is not a new publication
Suppose a fictional documentation team publishes a guide in March and revises its instructions in September. During the revision, a template accidentally replaces the original publication date with September’s date and labels an internal reviewer as the author.
The repair starts in the editorial record: preserve the actual original publication information, record the meaningful revision accurately, and distinguish authorship from review in the visible page. Then make the markup reflect those decisions. Do not manufacture a complete-looking set of fields before agreeing on what happened.
Check an untouched article using the same template as well. If its dates also changed, this is a shared publishing defect rather than a one-page typo.
Validate without overstating the result
Use Google’s testing tools for Google-specific feature eligibility, and inspect any warnings in context. Google’s structured-data introduction explains that correct markup does not guarantee a particular search appearance.
The schema checker is a starting point for inspecting supported raw-page structured-data observations. Read its stated scope; do not substitute a generic checker result for a full provider-specific eligibility review. Keep a small record of the URL, tested version, defect and correction.
Mistakes to avoid
Do not create a new organization identity on every article, insert invented credentials, or add review ratings to a guide simply because another site has stars. Also check whether a CMS plugin and a theme both generate conflicting article objects. Remove the conflicting source of data rather than adding a third object to compensate.
For the human side of provenance, read source citations and editorial trust. Use the content refresh audit when the dates expose a larger maintenance problem.
Frequently asked questions
Is BlogPosting markup an AI citation requirement?
Do not treat it as one. Describe the page accurately, and evaluate each search provider’s documented requirements separately. Markup is not evidence that an answer system cited the article.
Should every edit change the publication date?
Preserve the true publication history. Establish a clear editorial policy for recording meaningful modifications, and avoid making unchanged material appear newly published.