Article Schema Markup: A Practical Guide for Content Sites

Article schema describes a page as an article

Article schema is structured data that tells search engines a page is an article, blog post, or editorial resource. It can include the headline, description, author, publish date, modified date, publisher, image, and canonical page URL. For content sites, this markup helps reinforce the identity and metadata of each article.

Article schema does not guarantee special search features, but it is still useful. It gives search engines a cleaner interpretation of page details that may otherwise be inferred from HTML. When the markup is accurate, it supports trust and consistency across a large publishing system.

Use JSON-LD for maintainability

JSON-LD is usually the easiest format to manage. It can be generated from the same content fields used for the page title, description, date, and author. This reduces duplication and avoids embedding schema attributes throughout the visible HTML. For static sites, JSON-LD can be generated during the build.

The schema should use the canonical page URL as mainEntityOfPage. The headline should match or closely reflect the visible article title. The description should match the page’s meta description or a clear summary of the article. Avoid stuffing schema fields with extra keywords that are not visible to readers.

Dates must be honest

datePublished should reflect when the article was first published. dateModified should reflect meaningful updates. Changing modified dates automatically on every build can make freshness signals less trustworthy. For technical content, modified dates are valuable when they indicate real maintenance.

If an article is substantially rewritten, adding or updating the modified date makes sense. If only a footer, navigation item, or template style changed, the article itself may not need a new modified date. This distinction keeps metadata honest.

• Generate Article schema from the same source fields used by the page.
• Use the canonical URL for mainEntityOfPage.
• Keep publish and modified dates accurate.
• Validate schema after changing templates or build logic.

Author and publisher fields support trust

Author information can help readers and search engines understand who is responsible for the content. For a single-author site, this may be straightforward. For a multi-author publication, author pages and consistent names become more important. If the site uses organization authorship, make that clear and avoid pretending a person wrote content when the process is different.

Publisher information usually describes the website or organization. Include a name and logo if appropriate. The publisher should be consistent across articles. Inconsistent publisher markup can make the site look sloppy at scale.

Images and validation prevent avoidable errors

Article schema can include images, but the image URLs should be crawlable and appropriate for the article. If a site does not use featured images, do not invent misleading image data. If it does, make sure images are large enough, accessible, and not blocked by robots.txt.

Validate a sample of articles after deployment. Look for missing fields, invalid URLs, date formatting issues, duplicate scripts, and schema that no longer matches the visible article. Article schema is a small detail, but on a large content site, small metadata details compound into stronger technical consistency.