Skip to content
    AI Search & GEO

    How to Check Article Schema Against the Page Readers See

    By Tim White•Published •3 min read
    How to Check Article Schema Against the Page Readers See

    TL;DR

    • Validate the markup, then compare its values with the public article. Fix inaccurate template fields and retest more than one page.

    To check article schema, validate the markup and compare its fields with the live page readers see. A validator can accept a date in the right format even when it describes the wrong event.

    Suppose your blog template marks every post as updated on today's date. The markup looks tidy. A reader opening a guide that hasn't changed in months would get a different story. That's a publishing bug worth fixing at the template level.

    Which fields should you check?

    Open a published article and note the visible headline, author, dates and featured image. Use Google's Rich Results Test to inspect detected markup, or read the page's JSON-LD, the structured block that describes the article. Find the Article, BlogPosting or NewsArticle item that represents the main content. Google's Article documentation lists supported properties and how they are used.

    FieldCheck against the live page
    Headline and authorDo they describe this article and identify the actual bylined author?
    Publication and modification datesDo they reflect the real publish and update events? Check time zones when the visible date differs.
    ImageDoes the URL load an image that represents this article? If there are several versions, check they show the intended artwork.

    What can a validator miss?

    Here's a fictional example. An editor republishes a revised guide. The visible byline says Priya, while the BlogPosting item names the account that imported the post. Both are valid strings. The right repair is to connect the markup to the author assigned to the post. Try it on another author and an older article before calling it fixed.

    Google's structured data policies require markup to represent the page. Passing a test doesn't guarantee a rich result. And a correct Article item gives you no evidence that an assistant used the page as a source. That requires checking the citation against the claim.

    How do you keep the fix from regressing?

    Record one old article, one newly published article and one revised article as regression examples. After changing the template, compare each public page with its markup. If some fields depend on client-side code, inspect the rendered result too. Keep the dates and identities tied to the same editorial records that drive the visible page.

    What does a useful markup bug report include?

    Save the exact article URL, the rendered heading or byline and the conflicting value from the structured block. Include the other pages you sampled. A team can usually fix one shared mapping more reliably than hand-editing six posts that use the same template.

    1. Check the production page first. A saved CMS field and the published value can differ if a build hasn't picked up the edit.
    2. If the validator shows several structured items, identify which one describes the main article before changing any properties. A page can also carry breadcrumb or organization markup.
    3. Compare an article with a named author and one with a different author record. Check whether the same value appears where it should vary.
    4. After the fix, rerun the validator and open each public example. Save the expected values with the test so the next editor knows what should change when an article is updated.

    Pay special attention to changes that update a whole template. A new header image on one article shouldn't change the structured image on every article. A correction to a byline should flow to both the visible page and its markup. For a date discrepancy, compare the underlying timestamps with the time zone used on the page before changing the stored date.

    Use the same check for a page after a redesign. The acceptance criterion is that readers and the markup see accurate information about the same article.


    Know where you stand.Know what to do next.

    Start a free trial and see which AI answers leave you out, who shows up instead, and what to fix first.