What the Article Schema Generator does
This tool builds valid Article structured data in JSON-LD format for blog posts, news stories, guides, and editorial pages. You fill in the headline, author, publish date, publisher, and image, and the generator produces a spec-compliant script block you can drop straight into the head of your page. There is no manual JSON to write, no missing commas to chase, and no broken brackets to debug. Article markup tells Google and AI systems exactly who wrote a piece, when it was published, who published it, and what image represents it, which is the metadata that powers Top Stories, the news carousel, and the headline-and-byline treatment you see in search results.
Article is an umbrella type with three practical flavors. Plain Article fits evergreen guides and general blog content. BlogPosting is the right type for a personal or company blog where the content is opinion, commentary, or how-to writing rather than reported news. NewsArticle is reserved for journalism produced by a publication with editorial standards, and it is the only one of the three that is eligible for the Top Stories news features. This generator lets you pick the correct subtype so you do not accidentally claim news eligibility for a marketing blog, which is a fast way to get markup ignored.
Required and recommended properties for Article
Schema.org technically requires very little from an Article, but Google has its own effective requirements that matter far more for rich-result eligibility. The properties Google actually leans on are headline, image, datePublished, dateModified, author, and publisher. The headline should match the visible H1 or title and stay under 110 characters, because Google truncates longer headlines and may drop the markup entirely if the headline looks padded with keywords. The image property should point to a high-resolution file, ideally provided in multiple aspect ratios (16x9, 4x3, and 1x1) so Google can choose the best crop for each surface. Low-resolution or tiny images are a common reason a valid Article still never earns a visual treatment.
The author property deserves special attention because Google has tightened how it reads bylines. Author should be a Person or Organization object with a name, and increasingly Google wants an author URL or sameAs link that points to a page describing the writer. A bare author string still validates, but a structured author with a link to an author bio page sends a far stronger expertise signal. The publisher property must be an Organization with a name and a logo, and the logo should be a clean, rectangular image on a transparent or white background. Both datePublished and dateModified should be real ISO 8601 dates that match what a reader can see on the page, never fabricated freshness dates.
How Article schema earns rich results
The headline rich result, the byline, the publish date, and the thumbnail in search are all driven by Article markup combined with Google deciding your page deserves that treatment. For general blog content, the most visible payoff is the article thumbnail and date that can appear next to your listing, plus eligibility to surface in Discover, where a strong image and a clear headline carry enormous weight. For genuine news publishers, NewsArticle markup is what makes a page eligible for the Top Stories carousel and the news tab, though eligibility there also depends on being accepted into Google News and meeting its content policies.
Article markup has quietly become one of the strongest levers for AI search visibility too. When an AI Overview or a chatbot summarizes a topic and attributes a source, it relies heavily on the author, publisher, and date signals in your structured data to decide whether your page is a credible, current source worth citing. A page with a named expert author, a recognizable publisher, and a recent dateModified is materially more likely to be lifted into an AI answer than an identical page with no byline and no dates. In 2026, Article schema is as much about being citable by machines as it is about earning a thumbnail in the blue links.
How to read the generated output
The output is a single script block with a type of application slash ld plus json. Inside it you will see the at-context pointing to schema.org, the at-type set to Article, BlogPosting, or NewsArticle, and then your filled-in properties. Read it top to bottom and confirm every value matches what a visitor sees on the rendered page. The headline in the JSON should be the same words as your visible heading. The author name should be the same person credited on the page. The dates should be the same dates shown to readers. This mirror-matching is not optional polish; it is the single rule Google enforces most aggressively for structured data.
If you provided a mainEntityOfPage value, it should be the canonical URL of the article itself. This property tells search engines that this Article is the primary thing the page is about, which removes ambiguity on pages that also carry breadcrumb, organization, or website markup. When you copy the block out, paste it into the head of the specific article template, not a site-wide layout, so that each article carries its own unique headline, author, and dates rather than a single shared set of values across your whole blog.
Common Article schema mistakes
The most common error is a mismatch between the markup and the visible page. People paste an old headline into the schema, change the visible title later, and forget to update the JSON. Google sees the conflict and may discount the markup. The second most common error is a missing or malformed publisher logo. The logo must be a real image URL on an ImageObject or a direct URL, and if it is missing, broken, or the wrong shape, the rich result quietly fails to appear even though the schema validates as syntactically correct.
A third frequent mistake is faking the dateModified to look fresh. Updating the modified date without actually changing the content is a pattern Google has learned to detect, and it erodes trust rather than building it. A fourth mistake is choosing NewsArticle for content that is not news, which can cause the markup to be ignored because the page clearly is not journalism. A fifth is stuffing keywords into the headline so it reads like a search query rather than a real title; an over-optimized headline is both a poor user signal and a reason the headline feature may be suppressed. Keep the headline honest, human, and matched to the page.
Article versus the schema types it is confused with
Article is frequently confused with WebPage, BlogPosting, and CreativeWork. WebPage is a generic type for any page and should not replace Article on editorial content, because it does not unlock the byline and date features. BlogPosting is a subtype of Article and is the better choice for blog content specifically; it inherits everything Article supports and signals the content is a blog post. CreativeWork is the broad parent of Article and is too generic to earn article rich results on its own. When in doubt for a written editorial page, Article or BlogPosting is almost always the right call, and NewsArticle is the narrow exception for true journalism.
Article markup also pairs naturally with other types on the same page. A typical well-marked blog post carries Article for the content, BreadcrumbList for the navigation path, and an Organization or WebSite block for the publisher identity. These should live in separate script tags rather than being forced into one nested object. Keeping each type in its own clean block makes debugging far easier and avoids the validation errors that come from over-nesting unrelated entities.
What to do after you generate it
Paste the block into the head of the article template and publish or redeploy. Then run the URL through Google's Rich Results Test to confirm it is eligible for the Article rich result and to catch any warnings about missing recommended fields like image or author. Follow that with the Schema Markup Validator for a pure syntax check that is independent of Google's eligibility rules. A week or so after publishing, open the Enhancements and the Article reports in Search Console to confirm Google has actually parsed the markup and is not reporting errors at scale across your posts.
Remember that valid Article schema makes a page eligible for rich treatment but never guarantees it. Google decides per query and per page whether to show a thumbnail, a date, or a Top Stories slot, and that decision factors in your site's authority, the quality and originality of the content, and whether the query is one where a rich result helps the searcher. Keep the markup accurate, keep your author and publisher identities consistent across the site, refresh the dateModified only when you genuinely update the piece, and let Google make the final call on how it presents you. Done consistently across a blog, correct Article markup compounds into stronger visibility in both classic search and the AI answers that increasingly sit above it.