Article Schema Markup: Article and FAQ Guide

After you publish an article, you may want to tell search engines in a machine-readable way: this page is an article, it has this headline, it was published on this date and written by this person. Article schema markup does exactly that. Set up well, it clarifies what the page is. Set up badly, it becomes a pile of tags that contradict the visible content.

This guide covers the Article types, how to choose fields, how to keep dates and author data accurate, the current state of FAQ markup and how to test. Google's documentation changes over time, so recheck the details on the Search Central pages before you publish.

What Article Schema Markup Does

Structured data is a way of labeling the information on a page with a shared vocabulary (schema.org). For an article, that means declaring the headline, publication date, author and image as separate fields. A search engine can compare those fields with the visible text and interpret the page more accurately.

It helps to know up front what markup does not do. Adding schema does not raise rankings. Google describes structured data as a way to help it understand a page and, where eligible, to show richer results. In other words, markup is a description tool, not a ranking signal.

In practice you can expect three benefits:

• Clarity: It states that the page is an article and which text is the headline and the date.
• Consistency: When every post is generated from one template, the error rate drops.
• Auditability: Testing tools catch syntax errors, and the team can see what is declared in one place.

This guide is about the technical description of a finished article, not about writing it. For the writing side, see our guide on writing website content for business pages. Here the text is assumed ready and the focus stays on the markup layer.

Article Types and How to Choose

Google says three schema.org types are accepted for article markup: Article, NewsArticle and BlogPosting. All three can use the same fields. The difference lies in the nature of the content.

• Article: The general type. A safe choice for guides, analysis and company articles.
• BlogPosting: For posts that follow a blog format with a regular publishing flow.
• NewsArticle: For news reporting. Marking up a non-news guide with this type misdescribes the content.

When choosing, ask how a reader would describe the page. A regular blog entry is a BlogPosting, a general knowledge guide is an Article, and a piece reporting a current event is a NewsArticle. If you are unsure, Article is a consistent default because it is the broadest.

Once you pick a type, use it for all similar posts. If some posts on the same site are Article and others BlogPosting for no reason, template maintenance and reporting become harder.

Required and Recommended Fields

According to Google's Article documentation, no property is required; instead you add the properties that apply to your content. The recommended fields are:

• headline: The article title. Keeping it concise is advised because long titles may be truncated on some devices.
• image: A representative image. The field can be repeated.
• datePublished: The date and time of first publication.
• dateModified: The date and time of the latest change.
• author: A person or an organization. Use author.name for the name and author.url for a page that identifies the author.

The list may look long, but you do not have to fill every field. Incomplete but accurate markup is worth more than complete but wrong markup. If you do not show a piece of information on the page, do not declare it in the markup either.

Keep one distinction in mind: headline, image and dates describe the page itself, while author describes who prepared it.

Accuracy of Date, Author and Image Data

Most field mistakes happen in these three areas. The principle is the same for all of them: the markup must mirror the visible content exactly.

Dates

Google recommends ISO 8601 dates with timezone information. Without a timezone, the one Googlebot uses is assumed. Write the publication date only as the real first publication time. Update dateModified when you make a meaningful change; moving the date forward on every small fix misleads readers.

Author

Put only the person's name in author.name. Leave out job titles, honorifics such as "Dr.", publisher names or words like "written by". For author.url, use a page on your site that genuinely introduces the author. If there is no known author, do not invent a name. For the wider picture of author trust, read how E-E-A-T and backlinks connect.

Image

Google asks for an image relevant to the article, preferring content over a logo or a caption. The image URL must be crawlable and indexable, in a supported format. Providing high-resolution images in different aspect ratios (16:9, 4:3, 1:1) is recommended.

FAQ Markup and Its Current Limits

FAQPage markup makes the questions and answers on a page machine-readable. This is the part that changes most, so read it carefully.

In September 2023 Google updated its documentation to say that FAQ rich results were shown only for well-known, authoritative government and health websites. Later, Google's search updates log announced that the feature would no longer appear in Search starting May 7, 2026, and in June 2026 the feature's documentation was removed. So FAQ markup does not earn rich results on every site; according to Google's announcement, the display is no longer shown at all.

That leaves three possible decisions about FAQ markup:

1. Do not add it: If your only goal is a rich appearance on Google, this markup returns nothing for you.
2. Do not break existing markup: If your site already has a correct FAQPage, you do not have to remove it as long as it matches the visible FAQ, but do not expect a benefit.
3. Keep the visible FAQ section: With or without markup, a section that answers readers' questions clearly keeps its value.

The key point is that FAQ markup should not be presented as a method that produces rich results. No firm claim is made here about how other systems might use it.

JSON-LD Placement and Match With Visible Content

Google recommends the JSON-LD format for structured data. Instead of being mixed into the HTML, it sits on the page as a separate script block, which makes it easy to add to a template and maintain.

Points to watch for placement:

• The block can go in the head or the body of the article page; what matters is that it describes that page.
• Each article page should carry its own markup. Do not put one article's markup on a list or category page.
• Every marked-up value must be visible on the page. Headline, date and author name should match the text readers see.
• If values are generated from a template, the template should read the real data from your publishing system; hand-copied fixed values go stale over time.

The match-with-visible-content principle is the most important safety rule of markup. Marking up an author who is not on the page, an FAQ readers cannot see or an invented publication date goes against Google's structured data guidelines and puts the page's eligibility for rich results at risk.

Validating With a Testing Tool

Test the markup in two layers before it goes live. The first is syntax: is the JSON block valid? The schema.org validator gives a general check on that front. The second is Google's side: the Rich Results Test shows whether the page is eligible for the features Google supports.

After publication, watch the enhancement reports in Search Console. They list the errors and warnings Google found on the pages it crawled. A missing-field warning does not always mean something is wrong; missing recommended fields can appear as warnings.

Use this order of checks:

1. Confirm the JSON is valid.
2. Check the spelling of the type and field names.
3. Confirm that dates use ISO 8601 with a timezone.
4. Compare headline, author and date with the visible page by hand.
5. Confirm that the image URL opens and is not blocked.

Passing a tool is not proof that the markup is right; tools check only the format and the supported rules. The check for meaning stays with a person.

Common Markup Mistakes

These mistakes repeat, especially on template-based sites:

• Same date on every page: A fixed date in the template says every article was published on the same day.
• Wrong author: Entering the publisher name or a generic "Editor" as the author name.
• Broken or blocked image URL: Marking up an image blocked by robots rules or behind a login.
• Invisible content: Adding a question, answer or rating to the markup that is not on the page.
• Duplicate markup: A plugin and a theme each producing a separate Article block for the same post.
• Stale dateModified: The field stays old after an update, or changes automatically on every visit.

The common cause is treating markup as an add-on detached from the content. Make it part of the publishing process: no article goes out until headline, date, author and image fields are filled.

For title and description preparation, use our guide on writing SEO titles and meta descriptions. For deciding which fields to collect at the brief stage, see how to write an SEO content brief.

Sample Template: Article Schema Field Check Table

Imagine a fictional kitchenware store that is about to publish a new guide on its blog, and the template owner wants to check the markup before launch. The table below shows what to verify for each field. All entries are fictional.

Sample template: article schema field check table

The template owner, editor and developer can use the table together. An article does not go live until every row gets a yes. This simple gate noticeably reduces post-publication fixes.

Frequently Asked Questions

Does adding schema raise rankings?

No, structured data cannot be presented as a ranking booster. Its purpose is to describe the page content in a machine-readable way. Rankings depend on content quality, relevance and many other factors.

Does FAQ markup earn rich results on every site?

No. In 2023 Google limited FAQ rich results to well-known government and health sites, and according to its updates log the feature has not been shown in Search since May 2026. Check the current status on the Search Central pages.

Is there a difference between Article and BlogPosting?

BlogPosting is a more specific type of Article for blog posts, and Google accepts both. The fields are the same. You can choose BlogPosting for blog-style posts and Article for general guides; consistency is what matters.

Is marking up invisible content a problem?

Yes, it creates risk. Marked-up information must be visible to readers on the page. Declaring a question, author or rating that is not visible conflicts with Google's structured data guidelines and can affect the page's eligibility for rich results.

Should I use JSON-LD or Microdata?

Google recommends JSON-LD for structured data. Microdata is also a valid format, but because it is embedded in the HTML it is harder to maintain. For a new setup, JSON-LD is usually more practical.

What should I do about a markup error warning?

First separate a real error from a missing recommended field. Reproduce errors in the testing tool, fix them in the template, then request validation in Search Console.

Conclusion and Next Step

Article schema markup is a small but regular piece of technical preparation: choose the right type, declare only real and visible information, write dates in ISO 8601 with a timezone, keep the author field clean and do not expect rich results from FAQ markup. Then test it with a tool and monitor it in Search Console.

Markup only adds value on top of strong text. To write the articles for your site, read the SEO article writing guide, see how brands appear in AI answers in sponsored articles and brand mentions in AI search, and if you would rather have an expert write the piece, take a look at our content writing service page.