A practical article schema template and implementation checklist that helps publishers and SEO teams structure content markup correctly. We break down which properties matter, common implementation errors, and how to adapt the template for different article types without getting lost in edge-case fields.
Article schema is structured data markup that tells search engines what kind of content they're indexing—news piece, blog post, technical article, opinion column—and its key attributes like publication date, author, headline, and images. It doesn't guarantee rich results, but without it you forfeit eligibility for article-specific features like Top Stories, publisher carousels, and Google Discover placements.
The schema sits in JSON-LD format in your page's head or body, separate from visible content. Google reads it to understand context: Is this fresh reporting or evergreen guidance? Who wrote it? When was it last updated? This context helps the algorithm decide which SERP features fit and whether the content matches informational, news-intent, or expertise-driven queries.
Most importantly, article schema supports E-E-A-T signals by tying content to verifiable authors and organizations. When you declare an author entity with a matching Person schema, you create a link Google can follow. When you specify a publisher with a consistent logo and name, you reinforce brand identity across your domain. These aren't ranking factors in isolation, but they build the credibility scaffolding that supports topical authority.
Start with headline, which should match your H1 or title tag closely. Google uses this to confirm the page is about what the markup claims. Next, datePublished and dateModified—use ISO 8601 format with timezone. If you've never updated the post, set both to the same timestamp. If you refresh content, update dateModified to reflect the revision.
Author is critical. You can reference an Organization or Person. If you choose Person, link to an author bio page with its own Person schema. This creates a two-way validation: the article claims an author, and the author page confirms they write for this publisher. For image, provide a high-resolution URL, ideally 1200px wide or larger, in 16:9 or 4:3 ratio. Google may pull this for rich results.
Publisher is required and should be an Organization with name, logo, and ideally a sameAs array pointing to your official social profiles or Wikipedia entry. Description and articleBody are optional but useful—description can be your meta description, and articleBody can be the full text or a sanitized version. These help Google understand content depth without relying solely on visible HTML parsing.
A single article schema template rarely fits all content types. Blog posts benefit from BlogPosting schema, which is a subtype of Article and signals evergreen or opinion-driven content. News pieces should use NewsArticle, which tells Google this is timely reporting eligible for Top Stories if your site meets news publisher criteria.
Technical content—white papers, research summaries, case studies without client specifics—can use TechArticle. This subtype allows properties like dependencies and proficiencyLevel, though most publishers skip these and stick with Article. The key difference is semantic: TechArticle signals instructional depth, which can influence how Google surfaces the page in educational or developer-focused queries.
If you publish across categories, maintain two or three template files: one for blog posts, one for news, one for technical guides. Use template variables or CMS custom fields to populate properties dynamically. This avoids copy-paste errors and keeps markup consistent as you scale. Most WordPress SEO plugins let you set default schemas per post type, so you can automate much of this without touching code.
The most frequent error is mismatched dates—datePublished later than dateModified, or dates in the future due to timezone confusion. Always use UTC or clearly specify your timezone, and validate timestamps before pushing live. Another common issue is broken image URLs. If your CDN changes or you migrate hosts, image paths break and Google can't fetch the asset, disqualifying the page from image-dependent rich results.
Author mismatches are subtle but damaging. If your schema declares Jane Doe but the byline says J. Doe or the author page uses a different name variant, Google may not connect them. Use a single canonical name across all markup and visible text. Missing or incorrect publisher logo URLs also prevent rich results—Google expects a square logo, typically 600x600px, hosted on a stable path.
Validation tools catch syntax errors but not logical ones. Google's Rich Results Test will confirm your JSON-LD parses correctly, but it won't flag that your author has no bio page or that your logo is a 404. After running automated tests, manually review the properties: Do the URLs resolve? Do the names match? Is the date format consistent across your site? These checks prevent silent failures where markup is technically valid but functionally useless.
An article schema checklist works best when embedded in your content workflow, not bolted on at the end. Before a post goes live, confirm headline matches H1, datePublished reflects the actual publish time, and author has a valid bio page. If you're updating old content, change dateModified and verify the image is still current and high-resolution.
For teams, assign schema review to your editor or SEO lead. They should spot-check five properties: headline, dates, author, image, publisher. If any are missing or misformatted, send the draft back before publication. This takes two minutes per post but prevents weeks of troubleshooting later when rich results don't appear.
If you're working with a CMS like WordPress, Drupal, or a headless setup, automate as much as possible. Use custom fields or structured content models to pull schema values from the same source as your visible content. This reduces human error and ensures consistency across hundreds or thousands of articles. For smaller sites, a simple spreadsheet checklist tied to your editorial calendar is enough—just make schema review a required step before hitting publish.
Success with article schema is incremental and contextual, not dramatic. You won't see overnight ranking jumps, but you may notice your articles appearing in Google Discover feeds, publisher carousels in mobile search, or Top Stories boxes if you run a news site. These placements depend on multiple factors—site authority, topical relevance, freshness—but without valid schema, you're invisible to those features.
In Search Console, monitor the Enhancements report for Article errors or warnings. A clean report means Google can read your markup. If you see errors, prioritize fixing them by volume: address issues affecting hundreds of pages before one-off problems. Over weeks or months, watch for increases in impressions from non-traditional SERP features. These won't appear in standard organic metrics but show up in Discover or News performance reports.
Another outcome is improved author visibility. If you consistently mark up articles with the same author and link to a robust Person schema on their bio page, Google may start showing that author in knowledge panels or author carousels. This builds personal brand equity and reinforces expertise signals. The effect compounds—each new article strengthens the author entity, which in turn lends credibility to future content.
Schema.org updates its vocabulary periodically, and Google adjusts which properties it reads for rich results. Set a quarterly reminder to review Schema.org's Article documentation and Google's structured data guidelines for any new recommended fields. Usually changes are minor—new optional properties or deprecated fields—but catching them early prevents technical debt.
If you add new content types—podcasts, video transcripts, interview roundups—extend your template rather than creating entirely new schemas. Use the same publisher and author structures, but add type-specific properties like speakable for voice search or video objects for embedded media. This keeps your markup ecosystem cohesive and easier to audit.
When you migrate your site or redesign, schema often breaks silently. URLs change, image paths shift, author pages move. After any major change, re-validate a sample of articles across different templates. Use Google's Rich Results Test and the Schema Markup Validator, then manually check a few live pages in Search Console's URL Inspection tool. This catches issues before they erode months of structured data work. Think of schema maintenance like backups—boring, unglamorous, and essential.
Yes, if you publish distinct content types like news, blog posts, and technical guides. Use NewsArticle for timely reporting, BlogPosting for opinion or evergreen content, and TechArticle for instructional material. Each subtype signals different intent to Google and can influence eligibility for specific rich results like Top Stories or knowledge panels. Two or three template variants cover most publishing needs without overcomplicating your workflow.
Your article schema will validate structurally but lose eligibility for many rich results. Author and publisher properties tie content to entities Google can verify, which supports E-E-A-T signals. Without them, your articles may appear in standard search results but won't qualify for publisher carousels, author panels, or Google Discover features. These properties also help Google understand who's behind the content, which matters for expertise and trustworthiness assessments.
Use an array for the author property, listing each contributor as a separate Person or Organization object. Make sure each author has a corresponding bio page with its own Person schema, so Google can link them. If one author is primary, list them first. This approach works for co-authored posts, guest contributions, or editorial teams. Just keep author names consistent across markup, bylines, and bio pages to avoid entity confusion.
Not directly. Video and podcast content need VideoObject or PodcastEpisode schema in addition to or instead of Article schema. If you embed a video in an article, add a VideoObject to the article schema to describe the video's URL, thumbnail, duration, and upload date. For standalone podcast episodes, use PodcastEpisode or PodcastSeries schema. Mixing these correctly tells Google the content type and unlocks video or podcast-specific rich results.
Update dateModified whenever you make substantive changes to the content—rewrites, new sections, updated data, or significant edits. Don't change it for minor typo fixes or formatting tweaks. Google uses this timestamp to assess freshness, especially for topics where recency matters. If you never update articles, leave dateModified equal to datePublished. Changing dates arbitrarily to fake freshness can backfire if the content doesn't actually reflect the new timestamp.
Google recommends images at least 1200 pixels wide in 16:9, 4:3, or 1:1 aspect ratios. Higher resolution improves eligibility for image-rich features like Google Discover and Top Stories. Avoid images smaller than 696 pixels wide, as they may not qualify. Use stable, fast-loading URLs on your own domain or a reliable CDN. If your image path changes or returns a 404, Google can't fetch it, which disqualifies the article from rich results that rely on visuals.