Google’s Rich Results Test Now Supports Article Markup

Google’s Rich Results Test Tool Now supports ‘Article’ Structured Data Markup, and this update is a significant shift for publishers, bloggers, and content teams who rely on structured data to earn enhanced search appearances. If you have been manually validating your Article schema through workarounds or third-party validators, that friction is now gone. Google’s own testing tool can now read, interpret, and report on Article markup directly, giving you a more authoritative source of truth for your structured data implementation.

This guide walks you through exactly what changed, why it matters, and how to use the tool correctly to improve your search performance step by step.

What Is Article Structured Data and Why Does It Matter for SEO?

Article structured data is a type of schema markup from Schema.org that tells Google what kind of content is on your page. It is written in JSON-LD (the format Google recommends), Microdata, or RDFa, and it signals metadata such as the article headline, author name, publication date, and featured image. This metadata helps Google understand your content beyond what it reads in the HTML, which can influence how your page appears in search results.

According to Google Search Central documentation (2024), pages with valid Article structured data are eligible for enhanced features in Google Search, including display in Top Stories carousels, article-specific rich results, and better representation in Google Discover. While Google does not guarantee rich results for any page that implements schema, valid markup is a prerequisite for eligibility.

A 2023 study by Searchmetrics found that pages appearing in rich results receive a click-through rate increase of up to 30% compared to standard blue-link results. That is a meaningful traffic differential, especially for high-traffic editorial sites. For anyone working on Google News article ranking strategies, getting Article schema right has become a baseline requirement rather than an optional extra.

Structured data also feeds into how Google’s AI-powered features process and cite content. As covered in our breakdown of Google AI Mode vs AI Overviews, the way Google surfaces editorial content in AI-driven contexts is increasingly tied to how well that content is structured and attributed. Article schema contributes directly to attribution signals.

What Changed: Google Rich Results Test Tool Now Supports Article Markup

Before this update, the Rich Results Test Tool supported a range of schema types including FAQ, HowTo, Product, Review, Event, and Recipe, but Article was notably absent from the list of tested types. Publishers had to rely on Google’s Structured Data Testing Tool (now deprecated) or third-party tools like Schema Markup Validator to check Article markup specifically.

With the update, Google’s Rich Results Test Tool at search.google.com/test/rich-results now processes Article, NewsArticle, and BlogPosting types. When you submit a URL or paste HTML code, the tool will detect Article markup, parse all declared fields, and report on whether the markup is valid, what required fields are present or missing, and whether any warnings or errors exist that could prevent rich result eligibility.

This matters because Google’s own tool uses the same rendering engine (Googlebot) to evaluate your page, whereas third-party tools may not accurately simulate how Google actually sees your markup when JavaScript is involved. Getting a clean result in the Rich Results Test Tool is the most reliable signal that your Article schema is correctly implemented from Google’s perspective.

Step 1: Understand the Three Article Schema Types

Before you write or test any markup, you need to know which Article type applies to your content. Google supports three variants under the Article umbrella:

• Article: The broadest type. Use it for general editorial content that does not fit a more specific category. Google recommends this for content that covers news, sports, technology, or any general-purpose written format.
• NewsArticle: Specifically for news reporting from recognized news publishers. If your site is registered with Google News or primarily publishes journalistic content, this is the correct type. It places additional emphasis on the author identity and publication timeliness.
• BlogPosting: Used for blog-style content such as opinion pieces, tutorials, and personal publishing. If you run a company blog or an individual content site, this is typically the right choice.

Choosing the wrong type is not a hard error, but it is a missed opportunity. Google’s documentation (2024) notes that using the most specific applicable type improves the relevance of the metadata signal. For teams working across CMS platforms, this is worth standardizing early. If you manage a WordPress-based content site, a WordPress development partner can help automate the correct schema type assignment at the template level.

Step 2: Build Your Article Structured Data Correctly

Google specifies both required and recommended properties for Article schema. Here is what each category includes:

Property	Type	Status	Notes
@type	Text	Required	Article, NewsArticle, or BlogPosting
headline	Text	Required	Max 110 characters recommended
author	Person or Organization	Required	Include @type, name, and ideally a URL
datePublished	DateTime (ISO 8601)	Required	Include time and timezone for NewsArticle
image	ImageObject or URL	Required	Minimum 1200px wide for Top Stories eligibility
dateModified	DateTime (ISO 8601)	Recommended	Helps Google understand content freshness
publisher	Organization	Recommended	Include name and logo as ImageObject
description	Text	Recommended	A brief summary of the article
mainEntityOfPage	WebPage URL	Recommended	Canonical URL of the article page

A properly structured JSON-LD block for a BlogPosting should be placed inside a <script type="application/ld+json"> tag in the <head> or <body> of your page. Google supports both placements as of 2024, though head placement is the conventional standard.

Step 3: Run Your Article Markup Through the Rich Results Test Tool

Here is the step-by-step process for testing your Article structured data:

1. Go to search.google.com/test/rich-results in your browser. No login is required for basic tests, though signing in with a Google account gives you access to saved test history.
2. Choose your input method. You can paste a live URL or enter raw HTML code. For a published article, start with the URL. For markup you are drafting before publishing, use the code input.
3. Click “Test URL” or “Test Code.” The tool will fetch the page using a Googlebot-simulated crawl and render any JavaScript before evaluating the structured data.
4. Review the results panel. The tool will display detected structured data types on the left. Look for “Article,” “NewsArticle,” or “BlogPosting” in the list. Click on it to expand the field-level report.
5. Read the errors and warnings. Errors are shown in red and indicate missing required fields or invalid values. Warnings are shown in orange and indicate recommended fields that are absent or incomplete. Both affect your rich result eligibility.
6. Fix identified issues in your CMS, plugin settings, or code, then re-test. Repeat until the tool shows a green “Valid item detected” status with no errors.

Step 4: Fix Common Article Schema Errors

Most Article schema errors fall into a predictable set of categories. Here is how to resolve the most frequent ones:

Missing or Invalid Image

Google requires an image for Top Stories eligibility. The image must be at least 1200 pixels wide, have a 16×9 aspect ratio (preferred), and be accessible to Googlebot. If your CMS generates featured images automatically, check that the schema is pulling the correct URL and not a thumbnail version. Using an ImageObject with explicit width and height properties removes ambiguity.

Author Without a URL

Google’s documentation increasingly emphasizes E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness). Including only an author name satisfies the required field, but adding a URL pointing to the author’s bio page or a credible external profile significantly strengthens the markup’s value. This is especially important for sites that want to rank well for topics requiring demonstrated expertise. Understanding how to boost SEO through thorough content analysis includes author authority signals.

Headline Exceeding Character Limits

While there is no hard character limit that produces an error, Google recommends keeping article headlines under 110 characters. Headlines that are truncated or mismatched with your page’s H1 can create inconsistency signals. The headline in your schema should match or closely reflect the visible H1 on the page.

Incorrect Date Format

Dates must follow ISO 8601 format. For example: 2025-06-15T08:00:00+05:30. A common error is using a human-readable format like “June 15, 2025” instead of the machine-readable version. Most CMS plugins handle this automatically, but custom implementations frequently get this wrong.

Missing Publisher Logo

The publisher logo must be a valid ImageObject with a URL pointing to a logo image. Google specifies the logo should be at most 600×60 pixels and must be accessible to crawlers. A logo that returns a 404 error will produce a warning in the test tool.

Step 5: Validate Using Google Search Console After Publishing

The Rich Results Test Tool tells you whether your markup is valid at a point in time. Google Search Console’s Enhancements reports tell you whether Google has successfully processed that markup across your site over time. After implementing or updating Article schema:

1. Open Google Search Console and navigate to the Enhancements section in the left sidebar.
2. Look for an “Articles” report if Google has detected Article markup across multiple pages. This report aggregates errors, warnings, and valid items at scale.
3. Use the URL Inspection tool on individual article URLs to see the last crawled version and whether rich result eligibility has been confirmed.
4. Monitor the report weekly for the first month after implementation. New errors can appear if your CMS updates or plugin configurations change.

If your pages are not appearing in Search Console’s enhancement reports at all, it may indicate an indexing issue rather than a schema issue. Our guide on why Google is not indexing your pages covers the most common root causes and how to resolve them.

How Article Schema Fits Into a Broader SEO Strategy

Structured data is one layer of a multi-layered SEO approach. According to a 2024 BrightEdge report, organic search drives over 53% of all website traffic, and structured data is among the top technical signals that influence how that traffic is captured in modern search features. But schema alone does not move rankings. It is a prerequisite, not a guarantee.

Article schema works best when it is combined with:

• High-quality content that satisfies search intent and demonstrates topical expertise.
• Fast page load times and good Core Web Vitals scores, which affect rich result eligibility independently of schema.
• A clean internal linking structure that distributes authority to your article pages. Learn more about using internal links to boost backlink impact.
• Consistent crawlability and indexability across your site.
• Strong author and brand E-E-A-T signals, including linked author bios, external mentions, and editorial credibility.

For publishers who want to maximize their presence in Google’s evolving search landscape, including AI-powered features, it is also worth understanding how structured data interacts with new protocols. Our overview of WebMCP and its SEO implications covers how structured, well-attributed content performs better in machine-readable contexts.

If you want professional support implementing and monitoring structured data at scale as part of a comprehensive search engine optimization strategy, working with an experienced agency significantly reduces implementation errors and accelerates results.

Practical Action Plan: Article Schema Implementation Priorities

Use this prioritized action framework to implement and optimize Article structured data without wasting time on low-impact tasks:

• Do This Now: Run your top 10 article URLs through the Rich Results Test Tool today. Document every error and warning. Fix required field errors (missing image, author, headline, datePublished) immediately, as these block rich result eligibility entirely.
• Do This Now: If your site runs on WordPress with Yoast SEO, RankMath, or a similar plugin, check the schema settings in the plugin dashboard. Most plugins auto-generate Article schema but may require manual configuration to include author URLs, image dimensions, or publisher logos.
• Worth Doing: Standardize Article schema type selection across your content categories. Create a documented rule for when to use Article versus BlogPosting versus NewsArticle so editors and developers apply it consistently.
• Worth Doing: Add author URL fields pointing to credible author bio pages or professional profiles. This directly supports E-E-A-T signals that Google uses to evaluate content quality beyond the schema itself.
• Worth Doing: Set up a Google Search Console alert or weekly review schedule for the Articles enhancement report so new errors are caught quickly rather than accumulating over weeks.
• Low Priority: Explore adding additional recommended properties such as keywords, articleSection, or wordCount. These do not affect current rich result eligibility but may improve how Google categorizes and surfaces your content in the future.
• Low Priority: Investigate breadcrumb schema alongside Article schema. While separate, breadcrumbs appear in search results alongside Article rich results and contribute to a cleaner, more informative search snippet overall.

Google’s Rich Results Test Tool Now Supports Article Structured Data: Conclusion

Google’s Rich Results Test Tool Now supports ‘Article’ Structured Data Markup, and that closes a long-standing gap for publishers and content teams who needed an authoritative, Google-native way to validate their Article schema. The process is straightforward when you follow it systematically: choose the right Article type, implement all required fields correctly, test using the tool, fix errors and warnings, and monitor through Search Console after publishing.

The honest trade-off is that valid Article schema does not automatically produce rich results. Google’s eligibility criteria also include content quality, page experience, and E-E-A-T signals that no schema block can substitute for. But without valid markup, you are not even in consideration for those enhanced search features. Getting the markup right is the baseline.

For editorial sites, news publishers, and content marketers, this update simplifies the validation workflow and removes the guesswork of using tools that do not accurately reflect Google’s rendering behavior. Use the Rich Results Test Tool as your primary validation step, supplement it with Search Console monitoring, and pair your schema implementation with a strong content and digital marketing strategy to maximize the impact of every article you publish.

If you are working to improve your content’s performance in Google News specifically, also review our guide on key SEO strategies for Google News article ranking to understand the full picture of what Google expects from news-eligible content.

---

Frequently Asked Questions

Does valid Article schema guarantee that my pages will appear as rich results in Google Search?

No. Valid Article schema makes your pages eligible for rich results, but Google does not guarantee enhanced appearances for any page. Other factors including content quality, page experience scores, E-E-A-T signals, and crawlability all contribute to whether a rich result is actually shown. Schema is a necessary prerequisite, not a sufficient one on its own.

What is the difference between Article, NewsArticle, and BlogPosting schema types?

All three are subtypes of the Article schema. Article is the most general and applies to editorial content broadly. NewsArticle is intended for journalism and news reporting, particularly from recognized news publishers. BlogPosting is for blog-style content including tutorials, opinion pieces, and company blog posts. Google recommends using the most specific type that accurately describes your content.

Can I test Article schema for pages that are not yet published?

Yes. The Rich Results Test Tool includes a “Code” input option where you can paste raw HTML including your JSON-LD script block. This lets you validate your markup before publishing the page. It is a good practice to test schema in the code view first, especially when building new page templates or adding schema to a new content type.

My Rich Results Test shows warnings but no errors. Should I still fix the warnings?

Yes, you should address warnings as a priority. Warnings typically indicate missing recommended fields such as dateModified, publisher, or a high-quality image. While they do not block rich result processing entirely, they reduce your eligibility and can affect how Google displays your content in enhanced features. Fixing warnings also future-proofs your markup against stricter requirements Google may introduce later.

How often should I re-test my Article schema after initial implementation?

Test your schema after any significant CMS update, plugin upgrade, or template change, as these events can inadvertently break or alter your structured data output. Beyond that, a monthly audit of your Search Console Enhancements report is sufficient for most sites. High-volume publishers with frequent template changes may benefit from automated monitoring using tools that regularly crawl and validate schema across the site.