Why News Publishers need this
A scoop goes up at 9:02, a rewrite from a bigger outlet lands at 9:20, and the rewrite takes the Top Stories slot. Google tends to favour more recent articles, so being first does not protect you, and AI Overviews are trimming clicks even on pages that rank. With so little room for error, the signals you control have to be clean. Google News policies expect visible publication dates and author credits, and repeated problems can cost a site its place on news surfaces. Markup that disagrees with the page is an easy way to look careless to a machine reader. The Structured Data (Schema) Checker fetches a single article URL and lists the JSON-LD and Microdata types served in the HTML, with their key properties. For a news publisher that means you can read the headline, author and date values the page declares and hold them against what appears on screen. It will not tell you how a story will rank, but it shows what a crawler is handed.
News Publishers specific guidance
Pick the right URLs first
Run one live article URL, such as https://example.com/news/2026/10/council-budget-vote, then a section front and a live blog if you publish them. The checker reads the HTML as served and runs no JavaScript, so markup injected later by a tag manager will not show. In the Structured Data Overview, check the chips first: you want an Article-type entry, and a BreadcrumbList is a bonus. Then open JSON-LD Source and open the story in a second tab to compare the headline, author and date. That takes about five minutes. A detected Article type does not prove the values are right, and it says nothing about whether the story is indexed or shown in Top Stories. Do the same on an older story, since archive templates often differ from new ones.
Compare the source with the byline
The pretty-printed block is where newsroom mismatches show. Look for datePublished and dateModified, confirm that dateModified moves when an editor updates a running story, and check both against the dates readers see under the headline. Google's guidance on publication dates asks for markup that agrees with the visible date, so a template printing a build time or cache timestamp is worth reporting to your developers. Check that the author property names a person, not only the outlet. If the panel says Invalid JSON-LD block detected, look for a trailing comma or a smart quote pasted from a headline. The result cannot tell you whether the visible date is itself correct for the story. Sort out the date fields before anything else, because they matter most on time-sensitive stories.
What to change, and in what order
Fix the article template first, because one change reaches every story. Ask your developer to map datePublished to the original publish time, dateModified to the last editorial update and author to the byline field in your CMS. If a type is missing, build clean JSON-LD in the schema generator and place it in the article template. Rerun the same URL plus one older story to confirm both changed. Repair any invalid block before adding new types. The Rich Result Eligibility table is only a type lookup, so confirm in Google's Rich Results Test; it does not check required properties, values or policies. Sponsored content also needs visible disclosure, which markup cannot supply. Make the template change on staging and rerun the staging URL before release.
Example scenarios
1. Update time stuck on the original
- Situation
- Illustrative example: A desk updates a flood story three times during the afternoon and the page now shows 'Updated 15:40'. The article template's dateModified was never mapped to the CMS update field, so it still prints the first save time.
- Input
https://example.com/news/2026/10/river-flooding-live- Reading the result
- The JSON-LD Source would typically show datePublished and dateModified both at 08:12 while the page says Updated 15:40. That mismatch points to a template mapping problem, not an editor mistake. After the fix, rerun the URL and confirm dateModified follows the visible update time.
2. Author is the outlet, not the reporter
- Situation
- Illustrative example: A wire-copy template fills the author property with the site name for roughly 1,200 syndicated pieces, while the visible byline reads a reporter's name. The template was built before bylines were shown on the page.
- Input
https://example.com/world/2026/10/ministers-meet-trade-talks- Reading the result
- The overview would list an Article-type chip, and the source block would show an author value that is the organization name. Compare it with the byline on screen. If they differ, ask for the author property to read from the byline field and rerun one wire story and one staff story.
3. Markup added by tag manager is invisible
- Situation
- Illustrative example: After a redesign, a team adds Article markup through a tag manager container rather than the template. Browser extensions show it, but the HTML sent by the server contains none.
- Input
https://example.com/politics/2026/10/election-explainer- Reading the result
- The checker would typically return 'No JSON-LD or Microdata structured data found on this page.' View the page source and search for application/ld+json to confirm. If it is absent, move the markup into the server-rendered template and rerun the same URL.
Common mistakes
- Testing only the home page. The home page rarely carries Article markup, so a clean result there says little about stories. Test an article, a section front and a live blog separately.
- Trusting the type chip alone. An Article chip means the type is present, not that the headline, author and dates are right. Open JSON-LD Source and read the values.
- Bumping dateModified on trivial edits. Changing the modified date for a typo fix just to look fresh makes markup drift from the visible update line. Tie it to real editorial updates.
- Hand-editing JSON in a word processor. Smart quotes and trailing commas break a block and the checker will report an invalid JSON-LD block. Edit in a plain text editor and rerun.
- Reading eligibility as a promise. The Rich Result Eligibility table is a type lookup, not a guarantee of any result. Confirm in Google's Rich Results Test and expect no ranking effect from it.
Frequently asked questions
Does article schema help my story reach Top Stories?
Markup alone does not decide Top Stories. Google tends to favour more recent articles, and a scoop can still be outranked by a later rewrite. What structured data does is make your headline, author and dates machine-readable and consistent with the page. The checker shows which types your article page serves and the values inside them. Treat it as a way to remove avoidable inconsistencies, not as a lever for position, and check the page itself, not only the markup, for visible dates and credits.
Can I check my news sitemap with this checker?
No. The checker reads one article URL at a time and lists the structured data in its HTML. It does not read XML sitemaps, so a news sitemap needs a separate validator. It also does not crawl your site, so to see coverage you run one URL per page type: an article, a section front, a live blog, a video story. Each run shows what that template outputs, which is usually enough to catch a template-wide fault.
Why does my news article show no structured data when a plugin is installed?
The checker fetches the HTML as served and does not run JavaScript. If markup is added after load by a script or tag manager, it will not appear, even though a browser-based tool might show it. Markup printed in the page source is read. View the page source and search for application/ld+json to confirm. If the block is absent there, the plugin or template is not outputting it. If it is only in the rendered page, ask for server-side output.
Should dateModified change every time I update a running story?
It should reflect a real editorial update, and Google's guidance on publication dates asks that dates in markup match the dates shown on the page. Read the JSON-LD Source in the checker after you update a live story: if dateModified still shows the original time while the page says Updated 14:40, the template is not wired to your update field. Avoid bumping it for trivial edits just to look fresh. It cannot tell you whether the visible time is itself accurate.
Will fixing schema bring back traffic lost to AI Overviews?
No promise there. Publishers have reported click-through falling sharply when an AI Overview appears, even on page-one results, and structured data does not reverse that. Accurate markup removes one source of confusion about who wrote a story and when, and the checker confirms what the page declares. Treat traffic decisions separately, and use the result as housekeeping that supports clear authorship and dating. Nothing in the result measures citations, clicks or visibility in AI answers.
Reference: Google Search Central's byline date guidance explains why datePublished and dateModified should agree with the dates visible on the page, which matters for time-sensitive news.