Author: Jawwad

Event schema is code that tells search engines the basic facts about a concert, class, game, or any other event. You add it to the page, and Google can use it to list your date and venue on Search and Maps.

It’s a type of schema markup that matters because most people actively search for things to do. They type “concerts near me” or “comedy shows this weekend,” and Google answers with a list of dates, venues, and ticket links pulled from pages like yours.

Below, you’ll see what Event schema is, what Google will list in 2026, the properties to fill in, and how to handle multiple dates and last-minute changes in the markup.

So, let’s get started.

Key takeaways

• Event schema, also called Event structured data or Event schema markup, is built on schema.org’s Event type and labels the name, date, venue, tickets, and status for search engines about an event.
• Google uses it for its listings in Search and Maps, but only when an event is public, bookable, and held at a physical venue. Online-only events stopped qualifying in June 2025.
• Google needs three properties: name, startDate, and location with a full address. Images, ticket offers, organizer, performer, and eventStatus make the listing more complete.
• For multiple dates, count the tickets. One ticket for several days means one Event, and a separate ticket for each date means a separate Event.
• When plans change, update eventStatus and keep the original startDate unless the event has a confirmed new date.

What is Event schema in SEO?

In SEO, Event schema is structured data, written with schema.org’s Event type, that describes something happening at a set time and place in a format machines can read without guessing. 

Schema.org’s own definition is “an event happening at a certain time and location, such as a concert, lecture, or festival.”

On a normal event page, a crawler sees a title, a date, an address, and a “Buy tickets” button, and has to work out which is which. Event schema labels each one. The date becomes a startDate, the venue becomes a location, and the ticket price becomes an offer.

It’s one of the most widely used types of schema markup. Schema.org’s own figures quote that up to 1 million websites use Event markup today. And unlike FAQ schema, whose rich results were switched off in May 2026, Event markup still feeds a live Google search.

Where Google shows events with Event schema

Google uses Event markup for its event experience, a list of upcoming public shows, games, and classes with dates, venues, images, and ticket links. 

It appears in Google Search and other Google products like Google Maps. It’s available in the US, the UK, Canada, Australia, India, Germany, Spain, Brazil, and Latin America.

The audience is huge. Ahrefs estimates about 229,000 monthly US searches for “concerts near me,” 159,000 for “events near me,” and 46,000 for “comedy shows near me.” Every one of those searches is someone ready to pick a date and buy a ticket.

Other examples of such high-demand keywords are ‘concerts in [X] this weekend’ or ‘shows in [Y] tonight ’, with X and Y being the city or neighborhood name.

Take a look at the screenshot below.

It shows Google results for the keyword ‘concerts in Austin this weekend.’ Since most people are looking to party on the weekend, appearing for this keyword in the top results can boost your traffic.

Which events qualify after Google’s 2025 update

In June 2025, Google updated its Event guidance and removed the properties it used for online events. Its documentation now says, “Events must be bookable to the general public,” and “Events must take place in a physical location.”

This rules out a few kinds of listings, even when the markup is perfect:

• Webinars, livestreams, and virtual summits
• Any private events that need a membership or an invitation before you can buy a ticket.
• Games and performances held at a school, where the main participants and audience are minors.
• Discount coupons, information about business hours, trip packages, etc., shouldn’t use this markup at all.

Schema.org still supports online events, so markup for a webinar isn’t wrong. It just won’t earn a spot in Google’s event listings.

The event details Google reads

Google needs three properties before a page can appear in its event listings, and recommends several more that make the listing worth clicking. Here’s what goes where:

(Note: Properties marked * are required. The rest are recommended.)

Dates cause more trouble than any other field. Always add a UTC offset, so Google knows the time zone. For all-day events, or when you don’t know the start hour yet, use the date alone, and never enter midnight as a placeholder time.

Event schema example: A comedy club’s Friday show

Here’s an Event schema example for a made-up venue. ‘Bramblewick Comedy Hall’, a comedy club in Denver, is hosting comedian Juno Marrowby on a Friday night, with tickets at $28.50 including fees:

A few choices here are worth copying. The type is ComedyEvent, one of 23 more specific event types on schema.org. The name holds only the show title, while the venue sits in location. 

The price includes fees, as Google asks, and validFrom uses Denver’s daylight saving offset (-06:00) because tickets went on sale on October 1, before the clocks changed.

How to use Event schema for multiple dates

It depends on how people buy tickets. If one ticket covers several days, it’s one Event with a start and end date. If each date has its own ticket, each date gets its own Event.

Here’s how that plays out for the most common setups:

• One event over several days: A three-day conference with a single pass gets one Event markup, with startDate on day one and endDate on day three. Google asks for both dates whenever something runs across several days.
• The same show on different nights: If Juno Marrowby plays Friday, Saturday, and Sunday, and each night is sold separately, add a separate Event for each performance. If each night has its own ticket page, put that night’s markup on that page.
• A class that repeats every week: Schema.org has an eventSchedule property that describes a repeating pattern in one block. Google’s docs don’t mention it, though, so if you want each session in Google’s listings, mark up each upcoming session separately.
• A festival with many acts: Mark up each ticketed performance as its own Event. Schema.org’s superEvent and subEvent properties can tie each set back to the festival, even though Google’s docs don’t cover them.

One more rule applies to all four. Google’s event experience only supports pages that focus on one event, so leave your “What’s on” calendar page unmarked and link from it to each show’s own page.

What to change when an event is cancelled, postponed, or rescheduled

Change the eventStatus property, and leave everything else alone unless there’s a confirmed new date. Google uses startDate to identify the event, so it warns against deleting it, even when the show is called off.

Schema.org also has an EventMovedOnline status, but Google’s current docs don’t list it, since online-only events no longer qualify for its listings.

Remember, a stale page costs people a lot of lost time, which turns into mistrust quickly. Someone who drives across town for a show that was cancelled last week won’t trust your listings again, so update the status the same day plans change.

How to add Event schema to your website

Start by checking whether your ticketing platform already sends your listings to Google or not. If it doesn’t, or the page lives on your own site, add the markup with a plugin or by hand, then test it.

1. Check your ticketing platform first

Some ticketing and social platforms already take part in Google’s event experience. According to Google, “check to see if your event publisher is already participating,” and the quickest way is to search for one of your shows and see if it appears in Google’s results. 

If it does, Google can already list those shows, but the listing points to the platform. Add markup to your own event pages if you want that traffic on your site.

2. Use a WordPress plugin

If you searched for your event but couldn’t find it anywhere on Google, then you can follow the given steps to add it manually (works for WordPress-hosted sites only):

• The Events Calendar: Use this option to add Event structured data to every page it publishes, automatically.
• Rank Math: If you have this extension installed on your WordPress, go to the Schema tab in the post editor, choose Schema Generator, and pick Event schema. You fill in a form, and Rank Math writes the markup for you.

If you use both, let only one of them output Event markup. Two plugins describing the same show create duplicates.

3. Write the code yourself or use a generator

Use the code we gave above as an Event schema template, swap in your own details, and paste it into the page’s head or body. 

If you’re new to writing markup by hand, our schema markup examples show how other common types are built. 

There’s a way to automate this process as well. You can use a free Event schema generator to build the block from a simple form.

The Event block can share one script with your other markup, like Organization or Breadcrumb schema, as long as each piece describes what’s actually on the page.

4. Test it, then help Google find it

Run the page through Google’s Rich Results Test before it goes live and fix any critical errors. After launch, use URL Inspection in Search Console to confirm Google can crawl the page, and make sure it isn’t blocked by robots.txt or a noindex tag.

Then submit a sitemap so Google hears about new and changed pages, and keep an eye on the Events report in Search Console. 

Google notes that it can take several days after publishing for a page to be found and crawled, so don’t panic if a new show doesn’t appear the same afternoon.

Why your event isn’t showing on Google

When valid markup still doesn’t produce a listing, the cause is usually one of these:

Most of these come down to the same thing. Google wants one public, in-person event per page, described exactly the way a ticket buyer would see it.

If you run the same festival every year, watch for one more problem that markup can’t fix. Last year’s page can compete with this year’s page for the same search. 

Contentpen’s SEO opportunities checks your site every 14 days for cannibalization and content decay, so you’ll know when to merge, redirect, or refresh an old page before it pulls clicks away from the new one.

Turn existing content into growth opportunities

Identify pages losing traffic or CTR

Find quick wins to improve clicks and rankings

Find Content Opportunities →

Does Event schema help you show up in AI answers?

Yes, but indirectly. 

Google says no special markup is needed to appear in AI Overviews, and AI assistants answer event questions from what they can read on pages and in listings. 

Look back at the ‘concerts in Austin’ screenshot earlier in this guide. Google’s AI Overview lists each concert with its date, time, and venue, and it credits listing sites like Bandsintown and Visit Austin as its sources. 

The markup makes your facts clear, but the page itself has to carry them too.

Therefore, the more important thing is to make your content AEO-optimized. For that, you need to put the details people actually ask about clearly on the page itself:

• Doors and start time: Schema.org even has a doorTime property for when admission begins to an event.
• Venue and parking: The full address, the nearest parking, and public transit options.
• Price and fees: The total a buyer pays, not a starting price that grows at checkout.
• Age limits and accessibility: Who can attend and what access the venue offers.
• Refunds: What happens to tickets if the show is cancelled or moved.

A page that answers these questions can be quoted as it is, whether the question comes from a search box or a chatbot. For the bigger picture on markup and AI tools, see our guide to schema markup for AI search.

To find which of these questions people ask most about shows like yours, Contentpen’s keyword research tool shows the searches around your event type and city. So you can answer them on the page before buyers go looking elsewhere.

Automated keyword research

Work on keywords worth writing for

Get search terms with real ranking potential, not just high volume.

Try Keyword Research for FREE →

Summing it up

Event schema helps Google understand your page, list your date, and send those ready-to-buy visitors to your ticket page.

The rules are short once you know them. Keep one in-person event per page, fill in the name, date, and full address, count the tickets when there are multiple dates, and update the status the moment plans change. 

Setting up the markup is a one-time job. Keeping it honest is the part that earns trust, one show at a time.

If you’d rather spend that time booking acts than fixing pages, Contentpen is an AI SEO tool whose AI agents research, write, optimize, and publish SEO and GEO-optimized content on autopilot. Try it free for 7 days to boost your search rankings and start winning AI citations today.

Frequently asked questions

For seven years, FAQ schema had one big payoff. A few lines of code on a page with questions and answers could get Google to show those questions as a drop-down list right under your search result.

That payoff disappeared on May 7, 2026, when Google stopped showing FAQ rich results for every site.

The markup itself didn’t go anywhere, though. The code is still valid, and leaving it on your pages does no harm. What changed is the reason to use it. 

Below, you’ll see what Google removed, where the FAQ markup still earns its place, how to write answers that AI tools want to quote, and how to test this schema markup.

So, let’s get started.

Key takeaways

• FAQ schema, also called FAQPage schema or FAQ structured data, is code that labels the questions and answers on a page so search engines and AI tools can read them.
• Google deprecated FAQ rich results for every site on May 7, 2026, then dropped the Search Console report and Rich Results Test support in June of the same year.
• FAQ schema markup already on your pages is still valid, causes no errors, and doesn’t need to be removed.
• The markup doesn’t earn AI citations on its own. Clear, answer-first content on the page is what gets quoted.
• Test the code with the Schema Markup Validator and confirm it’s in the page’s raw HTML.

What is FAQ schema?

FAQ schema is structured data, written with schema.org’s FAQPage type, that marks up a list of questions and their answers. 

Visitors never see it. It sits in your page’s code as a machine-readable copy of your Q&A section, so a crawler knows exactly which text is the question and which text is the answer.

It’s one of the many types of schema markup, and the structure is simple. The page is marked as an FAQPage, and its mainEntity holds a list of Questions. Each Question has a name (the question itself) and an acceptedAnswer (the answer text).

Don’t confuse FAQ schema with Google’s ‘People also ask’ box, shown below for the search ‘what is schema markup’. Google picks those questions and answers from pages across the web on its own. A page doesn’t need FAQ schema to appear there, and the markup doesn’t decide which pages do.

FAQ schema explained with an example

Here’s an FAQ schema example for a made-up cleaning company, Tidewell Home Cleaning, on its pricing page:

“Do I need to be home during the cleaning?

No. Most clients leave a key or door code with us. Your cleaner arrives within a 30-minute window, locks up when they finish, and texts you a photo of the finished rooms.

Do you bring your own cleaning supplies?

Yes. Every team brings vacuums, mops, and plant-based cleaning products. If you’d rather we use your products, leave them on the counter, and we’ll use those instead.”

The FAQ schema code for those two questions will look like this:

Each visible question becomes a name, and each visible answer becomes the text inside acceptedAnswer. Nothing is added, trimmed, or reworded on the way in.

Is FAQ schema still relevant after Google’s 2026 change?

For Google’s results page, no. Since May 7, 2026, Google hasn’t shown FAQ rich results for any site, and no amount of perfect markup brings them back. 

For everything else, the answer is a smaller, quieter yes. The code is still valid, it costs nothing to keep, and it hands other crawlers a clean copy of your questions and answers.

To see why its value shrank, look at how the feature rose and fell.

Google launched FAQ rich results on May 8, 2019, alongside How-to markup. 

Adding FAQPage code to a page with questions and answers meant that Google could show a few of those questions as drop-downs right under your blue link in the SERPs. Searchers could open them and read the answers without leaving Google.

Marketers loved them because the extra questions made a listing stand out and pushed competitors further down the results page. It was also one of the easiest rich results to earn, and that popularity became the problem.

In August 2023, Google limited FAQ rich results to “well-known, authoritative government and health websites,” saying it wanted “to provide a cleaner and more consistent search experience.” Every other site lost them overnight.

Then, on May 8, 2026, Google’s Search Central updates log announced that the feature “will no longer appear in Google Search starting May 7, 2026.” That closed the door on government and health sites too, one day short of the feature’s seventh birthday.

What Google removed, and what it left alone

Google pulled more than the search feature. Here’s where every piece stands now:

Search Engine Journal’s coverage has the full Search Console timeline. The short version: nothing breaks if you leave your FAQ markup in place. Google said it plainly back in 2023, and it still holds: “Structured data that’s not being used does not cause problems for Search.”

Why did Google remove FAQ rich results?

Google didn’t give a reason for the 2026 shutdown. However, looking at how the feature was used, three reasons stand out:

• Too many sites used it for space, not answers: The code was easy to add, so FAQ drop-downs spread to product pages, blog posts, and even homepages, often with questions nobody had asked.
• It cluttered the results page: A few listings with long drop-downs pushed everything else down, which works against the clean, consistent search experience Google wanted to carry forward. 
• Google answers many of those questions itself now: People also ask boxes and AI Overviews already show quick answers near the top of the page, so the drop-downs added little value. Google hasn’t named this as a reason, but the overlap is hard to miss.

Lily Ray, who wrote about the markup when it launched in 2019, put the removal in context on LinkedIn. 

She said it “wouldn’t be the first time that Google is playing the cat-and-mouse game when they see too many sites using the same exact techniques ‘for SEO/GEO,’” as PPC Land reported.

FAQ wasn’t the only feature on Google’s cutting list. In June 2025, Google announced it would retire several rich results, including Book Actions, then reversed course on Book Actions that November, as our guide to Book schema explains. FAQ got no such second chance.

What Google’s decision means for businesses

For most businesses, the real loss came in August 2023, when the drop-downs disappeared for every site outside government and health industries. The 2026 change made it permanent. In practice, it means four things:

• No extra space on Google: Your listing looks the same with or without the markup, so FAQ drop-downs can’t help you stand out anymore.
• Some lost clicks may come back: The drop-downs often answered the question right on the results page, so some searchers never needed to visit the site. When the feature launched, Search Engine Land advised testing whether it helped traffic at all.
• No FAQ data in Search Console: The report and the search appearance filter are gone, so you can’t track FAQ performance there anymore.
• The value moved to your page: Clear answers in your visible content are now what earns attention, both in classic results and in AI answers.

So the change costs most businesses a visual perk, not rankings. The effort that used to go into drop-downs now pays off in the answers themselves, starting with AI search.

Does FAQ schema help with AEO and AI citations?

Not on its own. What helps answer engine optimization is the content itself, because answer engines quote the words on your page. The markup is a tidy wrapper around those words and nothing more.

Here’s what we can say with some confidence:

• Google’s AI features don’t need it: Google says no special markup is required to appear in AI Overviews. After the removal, Glenn Gabe of G-Squared Interactive read it as Google “clearly saying FAQ structured data is not important for ranking across its AI surfaces like AI Overviews and AI Mode.”
• AI crawlers only see what’s in your HTML: A 2024 Vercel study found that the main AI crawlers, including OpenAI and Anthropic, don’t run JavaScript. So if your FAQ schema is added by a script, like a Google Tag Manager tag, they never see it.
• The research is thin: The studies on markup and AI citations, which we break down in our guide to schema markup for AI search, show small or mixed effects. None of them show this markup working as a reliable citation switch.

So treat the markup as a clean label, not a strategy. The real work is writing answers an AI system can quote as they are, then checking whether it does.

Contentpen’s AI visibility tool helps here by tracking how AI models mention your brand across the prompts you care about. So you can see whether a rewritten answer on your page actually changes anything or not.

Find your brand in AI search

Track AI citations, share of voice, and brand sentiment

Find the top sources driving citations

Try AI Visibility →

FAQPage or QAPage: Which one fits your page?

To use FAQPage or QAPage, check who wrote the answers. If your business wrote them, use FAQPage. If your users wrote them, use QAPage.

QAPage is still very much alive at Google. Its QAPage documentation says properly marked up pages “are eligible to have a rich result displayed,” and Google added new supported properties for it in March 2026 as well.

Don’t take that as a loophole. The same page warns, “Don’t use QAPage markup for FAQ pages or pages where there are multiple questions per page.” Switching to QAPage just to win back a rich result isn’t a wise move.

What does a good FAQ look like?

A good FAQ section answers questions real people ask, puts each answer in its first sentence, and makes sense even if someone reads only one answer. The same traits make it easy to quote in AI search, because answer engines pull short passages, not whole pages.

Use these rules when you write or rewrite yours:

1. Start with questions people already ask: Pull them from Google’s People also ask box, Autocomplete, related searches, your support inbox, sales calls, and Search Console queries that start with ‘how’, ‘can’, or ‘does’.
2. Put the answer in the first sentence: Lead with yes, no, a number, or a name. Add the detail that helps someone decide after that.
3. Make each answer stand on its own: Skip phrases like “as mentioned above.” Name the product or service instead of writing “it,” so the answer still works when it’s quoted somewhere else.
4. Keep one question per intent: Three versions of the same question don’t add value. They only spread one answer thin.
5. Match the questions to the page: A pricing page answers pricing questions. A returns page answers returns questions. You get where we’re going with this?
6. Leave the sales pitch out: Google’s old guidelines banned this markup for advertising, and a pitch rarely answers the question a user has anyway.

Notice that none of these rules is about code. Get the writing right, and the markup becomes a copy-and-paste job.

Short, complete answers take longer to write than long ones, so give them that extra time to draft.

If you’d rather catch weak spots before a post goes live, Contentpen’s SEO and GEO scoring checks for an answer-box paragraph under your H1 and for FAQ-style blocks. This helps you to notice gaps in your content before publishing while they’re still easy to fix.

Get your content cited by AI, not just ranked on Google!

See your real-time GEO score as you write to make every piece citation-ready.

Try GEO Scoring →

How to add FAQ schema to your website

Pick the method that matches how your site is built. Whichever you choose, two rules stay the same. The markup has to be in the page’s HTML when it loads, and it has to match the visible questions and answers word for word.

1. Write the JSON-LD yourself

Hand-written JSON-LD gives you full control. Use the Tidewell block above as an FAQ schema template, swap in your own questions, and paste it into the page’s head or body. Google reads JSON-LD in either place.

Two details trip people up most:

• Watch out for double quotes inside answers: Each answer already sits inside double quotes, so an extra quote in the text cuts it short and breaks the whole block. Add a backslash before it, or use single quotes to get around this problem.

“text”: “Use the code “SPRING10″ at checkout.” ❌
“text”: “Use the code \”SPRING10\” at checkout.” ✅

• Keep HTML in answers basic: Google’s old guidelines allowed simple tags like links, paragraphs, lists, and bold text. A link inside an answer needs escaped quotes too, as in <a href=\”/pricing\”>.

If typing JSON isn’t your thing, a free FAQ schema generator builds the same block from a simple form. You still need to paste it in the right place and test it, which we cover below.

2. On WordPress with Yoast, Rank Math, or Elementor

Most WordPress sites never touch the code, because the SEO plugin writes it for them:

• Yoast SEO: Add the free Yoast FAQ block in the block editor and type your questions into it. Yoast outputs the markup automatically, and it still does after Google’s change.
• Rank Math: Use Rank Math’s FAQ block in the block editor, or its Schema Generator in the Pro version if you’d rather build the markup separately.
• Elementor: Turn on the FAQ Schema switch in the Accordion widget’s settings. Rank Math Pro adds its own FAQ option to the same widget, so use only one. With both on, the page gets the markup twice, as Rank Math’s own guide warns.

Whichever plugin you use, let only one of them output the markup. If you built your questions with a newer Elementor accordion, check the page source before you assume the markup is there, because not every accordion version outputs it.

3. On Shopify, Webflow, and other site builders

On Shopify, open the theme editor, add a Custom Liquid section to the page template, and paste your script there. Don’t paste it into the page’s rich text editor. Shopify strips script tags when you save, so the markup quietly disappears. 

If you have ‘Q&A’ sections on many pages, store the questions and answers in metafields and generate the JSON-LD with one Liquid snippet.

On Webflow, open the page settings and paste the script into the custom code box for the head tag. Most other builders have a similar custom code or code injection setting that does the same job.

4. Combine FAQ schema with your WebPage and Article markup

FAQPage is a more specific kind of WebPage on schema.org, so you don’t need separate WebPage and FAQPage blocks for one URL. Yoast’s schema documentation handles it by giving the page both types at once.

On a blog post with an FAQ section, keep your Article schema and connect everything in one @graph. Each node gets an @id, so the pieces can point to each other instead of repeating themselves:

The page is both a WebPage and an FAQPage. The blog post sits inside it, and the question hangs off the page through mainEntity. Your Breadcrumb schema can join the same graph as one more node.

How to test FAQ schema?

Now that Google’s Rich Results Test has dropped checking FAQ schema, you need an alternative way to go about this process.

Run the code through the Schema Markup Validator, then check the live page’s HTML yourself. Google’s Rich Results Test dropped support in June 2026, and the matching Search Console report went with it, so nothing will warn you when the markup breaks.

Use this four-step checking process:

1. Validate the code: Paste the URL or the script into the Schema Markup Validator. It checks syntax and vocabulary and lists every Question it finds for the page.
2. Confirm it’s in the raw HTML: Open View Page Source for a page (not Inspect) and search for FAQPage. If it shows up only in Inspect, a script added it after the page loaded, and crawlers that don’t run JavaScript won’t see it.
3. Count the FAQPage blocks: One page should have one FAQPage. Two usually means a plugin and a page builder are both writing markup.
4. Compare it with the page: Read the markup against the visible questions and answers. After any edit to the page, check whether both changed or not.

Add these checks to your regular SEO audit. Without a Search Console report, an audit is now the only thing that catches broken markup.

You can use tools like Screaming Frog SEO Spider to carry out your technical audits (free for up to 500 URLs) or any other service you like.

FAQ schema problems to catch in your next audit

Since Google’s tools no longer flag this markup, these problems can sit on a page for months. Here’s what to look for:

Most of these issues come from treating the markup as a separate task from the content. When the answers and the code come from one source, almost none of them can happen.

Should you keep, add, or remove FAQ schema?

It depends on where your markup came from and whether the questions help readers:

• Keep it if a plugin or block already outputs it. It costs nothing, and Google says it causes no problems.
• Add it to new pages when your CMS builds it automatically from a visible FAQ. Hand-coding it across hundreds of pages, just in case it helps, isn’t a good use of your time in 2026.
• Fix it before you add more. Start with your highest-traffic pages, where broken or stale markup gets read the most.
• Remove the FAQ section itself if it was written only to win the old rich result. Generic questions and answers nobody needed don’t help readers or answer engines, with or without markup.

In short, the code is optional now. A clear, honest set of answers isn’t.

Rich results came and went. Clear questions with direct answers never went out of style, and they’re the same thing that helps a page rank on Google and get cited in AI answers. 

If you’d like that work handled for you, Contentpen is an SEO and AEO tool whose AI agents research, write, optimize, and publish SEO and GEO-optimized articles on autopilot. It also puts useful FAQs in your content, which become the building blocks of your FAQ schema.

Write content that’s built to rank, not just read

Create search-optimized blogs aligned with SEO and GEO signals, so your content performs well across search and AI-driven discovery.

Try SEO Blogging FREE →

Frequently asked questions

Search for almost anything and look just under the site name in the results. On well-built sites, you won’t see a messy URL there. You’ll see a short path, like Blog › What is SEO › How to do an SEO audit. Ever wondered where that line comes from?

That path is a breadcrumb trail. 

Breadcrumb schema, also called Breadcrumb structured data or BreadcrumbList markup, is a schema markup that tells search engines the route from the top of your site to the page someone is on.

It’s also one of the most widely used types of schema markup. The schema.org BreadcrumbList page counts it on more than 10 million domains, and Google still shows it in desktop results in 2026.

This guide explains how the markup is built, where Google shows it, and how to add it to your pages.

So, let’s get started.

Key takeaways

• Breadcrumb schema is BreadcrumbList structured data that describes where a page sits in your site, with one ListItem for each step in the trail.
• Each step needs a position, a name, and an item (its URL).
• Since January 2025, Google shows breadcrumbs only on desktop. Mobile results show the domain alone, but the markup is still supported.
• Google recommends trails that follow a typical user path rather than your URL folders.

What is Breadcrumb schema?

In SEO and digital marketing, a breadcrumb is the row of links near the top of a page that shows where it sits on a website. For example, Blog › What is AEO › Best AI visibility tools, or Home › Women › Running shoes on an online e-commerce store. This is your breadcrumb navigation.

Breadcrumb schema is the same row written as JSON-LD, so search engines can read it without guessing about the internal hierarchy of your pages.

Breadcrumbs vs Breadcrumb schema

The table below summarizes the differences between breadcrumbs and Breadcrumb schema:

Google’s structured data guidelines ask you to mark up only what readers can see, so the trail in your code should be the trail on your page.

Here’s that idea on our own blog. 

The trail above our Book schema guide tells readers it belongs to the schema markup hub, and that same parent and child relationship is what Breadcrumb schema hands to Google.

Where Google shows your breadcrumbs in 2026

On desktop, Google shows the trail in the URL line under your site name. On mobile, it doesn’t. Since January 23, 2025, mobile results show only the domain of the page.

Google made the change because breadcrumbs were often cut off on small screens, as Search Engine Journal reported. Desktop kept them, and Google’s breadcrumb documentation still lists the feature as available on desktop in every region and language where Search runs. 

If you already have the markup, there’s nothing to change.

What if you skip the markup? 

In case you don’t add the Breadcrumb schema, Google usually falls back to your URL, so readers see folder names like › blog › book-schema instead of the labels you’d pick to show the exact cluster. 

Markup lets you decide what that line says. Before anyone clicks, the trail tells users which part of your site the page belongs to so that they can navigate your site with ease.

The four building blocks of a BreadcrumbList

Every BreadcrumbList follows the same pattern: one list, one ListItem for each step in the trail, and three properties inside each step.

One detail trips people up: the order of items in your code isn’t what sets the order of the trail. Schema.org notes that position is what search engines use to rebuild it, so number every step.

Here’s a Breadcrumb schema example for a three-step trail like the one on our blog:

Swap in your own labels and URLs in the Breadcrumb schema template, and leave the item off the last step. A blog post usually carries this list alongside a page-level type, such as Article schema for the post itself.

How to plan a breadcrumb trail worth marking up

Plan the trail around how people reach the page, not around your URL folders. Google says so directly: “We recommend providing breadcrumbs that represent a typical user path to a page, instead of mirroring the URL structure.”

Hierarchy trails for blogs and service sites

Most pages need one trail: the top section, then the hub or category, then the page. On a blog built around topic clusters, the middle step is the pillar page. That’s why every schema guide on our blog sits under What is schema markup, and why the trail doubles as a map of the cluster.

Those crumbs are also real internal links, pointing from detailed posts back to their hub, which our guide to internal linking covers in depth. 

Contentpen’s AI linking assistant follows the same logic in your content. It reads your sitemap and links each new article to its pillar and related posts as it writes, so the links inside your posts match the hierarchy your breadcrumbs show.

Improve SEO with automated linking that fills them

Adds context-aware internal and external links automatically

Uses relevant anchor text to improve SEO and content flow

Try Auto-Interlinking →

Two trails for one page

Some pages live in two places at once. A cast-iron skillet might sit under Kitchen › Cookware and also under Gifts › Housewarming. 

Google lets you add a separate BreadcrumbList for each path, somewhat like this:

Stick to paths a shopper would actually take. Two or three trails are plenty, and a trail for every tag adds noise without giving Google a clearer picture.

Filter and history trails: What to leave out

Trails built from filters, like Cookware › Material: Cast iron › Size: 10 in, change with every visit, and filtered URLs usually aren’t pages you want indexed. 

So, it is important to mark up the category path behind them instead.

History trails, like a “Back to results” link, come from one visitor’s clicks, so there’s no fixed path to describe. Keep those as on-page navigation only.

Adding Breadcrumb schema on WordPress, Shopify, or a custom site

Most WordPress SEO plugins output BreadcrumbList for you once breadcrumbs are turned on. On Shopify, it depends on your theme. On custom sites, the markup should come from the same data that renders the visible trail.

1. WordPress with Yoast SEO or Rank Math

Both plugins on WP need breadcrumbs switched on first, since the feature is off by default:

• Yoast SEO: Go to Yoast SEO -> Settings -> Advanced -> Breadcrumbs and turn on ‘Enable breadcrumbs for your theme’. Show the trail with the Yoast Breadcrumbs block, the Home » Archives for Jawwad shortcode, or the yoast_breadcrumb() function in your theme. After this, Yoast adds the breadcrumb JSON-LD to your page source.
• Rank Math: Turn on the Schema module, then go to Rank Math SEO -> General Settings -> Breadcrumbs and enable them (switch to Advanced Mode if you don’t see the option). Show the trail with the [rank_math_breadcrumb] shortcode or the rank_math_the_breadcrumbs() function.

Once the visible trail appears on your posts, open the page source or run a test to confirm the BreadcrumbList is there too.

2. Shopify

Breadcrumbs on Shopify come from your theme. 

Some themes, including Shopify’s free Dawn theme, don’t include a breadcrumb section out of the box, so store owners add one with a theme snippet or an app. Whichever route you take, check that it outputs BreadcrumbList markup and not just the visible links.

3. Custom and headless sites

For headless and custom sites, generate the JSON-LD from the same source that draws the visible trail, such as your category tree or route config. With one source, the markup and the page can’t drift apart.

The visible trail needs clean breadcrumb HTML too. Following the W3C’s breadcrumb pattern, wrap the trail in a nav element with an aria-label, list the steps in order, and mark the current page with aria-current:

A Breadcrumb schema generator works for a single page. On a site with hundreds of pages, a template is the only setup that stays accurate as your structure changes. 

If you can’t edit your templates, Google Tag Manager can inject the JSON-LD for you. However, use it as a temporary fix. 

Google only sees the markup after it renders the page’s JavaScript. But many other crawlers, including most AI crawlers, don’t run JavaScript at all. So, it is crucial to move the markup into your templates as soon as you can.

Checking your markup and fixing Search Console breadcrumb errors

It is important to check your pages and fix any breadcrumb issues if they persist. To do this, test one page before you roll the markup out, then let Search Console watch the rest of the site.

1. Rich Results Test: Run a URL through Google’s Rich Results Test to confirm it detects Breadcrumbs and to see any errors.

2. Schema Markup Validator: Use the Schema Markup Validator as a free schema checker to validate the full schema.org syntax.
3. Google Search Console: Open the Breadcrumbs report to spot errors across every page Google has crawled.

When Search Console flags a problem, the message usually points straight at the fix:

Most of these come from a plugin or theme template, not hand-written code. Fix the template once, and every page that uses it is corrected on the next crawl.

Are breadcrumbs good for SEO after Google dropped them on mobile?

Yes, even though they don’t lift rankings on their own. On desktop, they make your result easier to understand. On every device, they give readers a one-click way up a level, and they add consistent internal links that show search engines how your pages relate.

That structure matters in AI search too. 

Google says no special markup is needed to appear in AI Overviews, but a page that clearly sits under a well-covered hub is easier to read in context. For what the research says about markup and AI citations, see our guide to schema markup for AI search.

That said, the structure of your site only pays off when the pages inside it are worth ranking and citing. 

Contentpen is an SEO and AEO tool whose AI agents research, write, optimize, and publish SEO and GEO-optimized articles on autopilot for each cluster. This helps your hubs and the posts beneath them gain organic traffic and grow together.

Write better blogs in less time, without sacrificing quality.

Let AI handle structure, clarity, and flow while you stay in control of the message.

Try AI blog writing →

Your Breadcrumb schema checklist

Run through this list on one Breadcrumb schema template before you roll it out across the site:

• The visible trail and the markup show the same steps.
• Every step has a position starting at 1, a name, and a URL, except the current page.
• Each list has at least two steps.
• Trails follow how people browse, not just your URL folders.
• Pages in two categories get one BreadcrumbList per path.
• The Rich Results Test detects Breadcrumbs, and Search Console shows no errors.

Tick these off once, and every page on that template gets a trail readers can click, and Google can show.

Frequently asked questions

A shopper searches for a novel you stock and lands on the audiobook instead, or sees an older edition’s cover. What do you think happens next? They click a bigger retailer’s listing instead of yours, and you lose a potential buyer.

Search engines have to work out each book’s details from the page it sells on, whatever they find on it. When that data is vague, they guess about the information, and a wrong guess sends a ready buyer to the wrong listing or to another store.

Book schema fixes that. It’s a short block of code that tells search engines each book’s title, author, ISBN, format, and edition. So, they can match every listing in your store to the exact book a shopper is looking for.

This guide covers what Book schema is, where Google still uses it in 2026, the properties that matter, and how to mark up the hardcover, ebook, and audiobook versions of one title.

So, let’s get started, shall we?

Key takeaways

• Book schema is structured data that uses the schema.org Book type to describe a book’s title, author, ISBN, format, and edition.
• Google still supports Book markup in 2026. It planned to retire Book actions in June 2025, then reversed that decision in November 2025.
• Google uses Book markup for Book actions (buy or borrow links for large catalogs) and for review stars on pages that review a book.
• One book is a “work” with several “editions.” Each edition, such as the hardcover, ebook, or audiobook, gets its own ISBN and format.
• Author and indie press sites won’t get a new rich result from it, but clean book data helps search engines, and AI tools match the right title.

What is book schema?

Book schema is structured data that uses the schema.org Book type to describe a book in a format search engines can read, including its title, author, ISBN, format, and edition. It’s a specific type of schema markup, usually added to a book’s page as a JSON-LD script.

Think of it as your book’s copyright page, rewritten for machines. The copyright page lists the details in a fixed spot so librarians and booksellers can catalog the book. Book schema puts the same facts in a fixed format so search engines can do the same.

Book is a niche type. The schema.org Book page shows it on 10,000 to 100,000 domains, based on Google’s web index, while the Article type appears on more than 10 million. Fewer sites describe their books clearly, so the ones that do leave search engines less to guess about.

Book schema describes the book itself. If your page is a blog post or news story about a book rather than the book’s own page, start with article schema instead.

Does Google still support Book schema?

Yes. Google still uses Book markup in 2026, but only in two places: Book actions for large book providers, and review snippets on pages that review a book. On other pages, the markup describes the book without changing how the result looks.

Its status changed twice in 2025. In June, Google listed Book actions among seven structured data features it planned to phase out, adding that “this update won’t affect how pages are ranked.” 

In November, Google reversed course and kept Book actions because some Search features still use the markup, as Search Engine Land reported. Google’s Book actions documentation is live today with no deprecation notice.

In short, the markup does its most visible work for big catalogs and review sites. For an author or small press, it’s about accuracy, not a new look in search. To see how other types fared in Google’s 2025 cleanup, read our guide to the types of schema markup.

Which properties does Book schema use?

Book schema has six properties of its own: isbn, bookFormat, bookEdition, numberOfPages, illustrator, and abridged. It also inherits general properties from CreativeWork, such as name, author, publisher, datePublished, and inLanguage. 

These are the ones worth filling in:

Two of these have strict values. Schema.org lists six bookFormat values: AudiobookFormat, EBook, GraphicNovel, Hardcover, Pamphlet, and Paperback. 

Google’s Book actions accept four of them: AudiobookFormat, EBook, Hardcover, and Paperback. For the ISBN, Google says it “prefers ISBN-13,” so use the 13-digit number from your copyright page.

Work vs edition: How to mark up hardcover, ebook, and audiobook versions

Book schema splits a book into a work and its editions. Google defines the work as “the abstract concept of a book” and an edition as “a concrete copy of the book.” 

The work holds what never changes, like the title and author. Each edition holds what does change, like the ISBN, format, and page count.

In the markup, the work is a Book with a workExample property that lists each edition. Each edition is also a Book, or an Audiobook for audio versions, with its own ISBN and bookFormat. An edition can point back to its work with exampleOfWork.

Keep one work per title and add an edition each time you release a format. A new paperback printing gets a new edition entry, not a new book.

Book schema examples in JSON-LD

Google recommends JSON-LD for structured data because it sits in its own script tag, apart from your page’s visible content. 

The two schema markup examples below use a fictional novel. Use them as a free book schema template, and swap in your own titles, ISBNs, and URLs for uniqueness.

Example 1: A book with three editions

Why this setup works:

• One work, three editions: Each format has its own ISBN, so search engines never mix up the hardcover and the ebook.
• A proper audiobook entry: The Audiobook type unlocks readBy and duration, which plain Book doesn’t have.
• Linked author profiles: The sameAs links tie Imogen Hale to profiles search engines already know, which helps separate her from anyone else with the same name.

This is the setup most author and indie press sites need. It won’t add a buy button by itself, but it gives search engines every fact they need to match the book to its proper listing.

Example 2: A book review with star ratings

Google’s review snippet documentation lists Book as a valid item to review, so a page that reviews one book can be eligible for star ratings in search. 

Here’s a review from Quiet Margins, a fictional book blog made for the sake of this post:

Keep in mind that the rating of books you provide must be your own. Google’s guidelines say, “Don’t aggregate reviews or ratings from other websites,” so star averages copied from Amazon or Goodreads don’t belong in this markup.

Example 3: Markup for multiple authors, illustrators, and translators

In case of multiple writers, give every contributor their own entry. Put co-authors in an author array, and use the illustrator and translator properties for those roles instead of listing them as authors:

Keep names clean: one person per entry, with no roles or “by” in the name field. Search engines then credit each contributor correctly.

Example 4: Markup for a book series

Use the BookSeries type for a book series, link each book to it with isPartOf, and add position to show where the book falls in the reading order:

Add these lines to each book’s work entry. Readers often search for a series’ reading order, and this gives search engines that order directly.

Which Book markup does your site need?

The right markup depends on what your site does with books. An author’s site needs different markup than a review blog, a library, or an online store.

• Author and indie press sites: One Book work per title with every edition, plus Person markup for the author with sameAs links.
• Book review blogs: Review markup with the book as itemReviewed, on a page that reviews one book.
• Large publishers, retailers, and libraries: Fill out Google’s Book actions interest form, then send a daily data feed. Google says it fetches feeds “once a day and typically indexes the content within two days.”
• Online stores selling books: Add Product markup with an offer for price and availability on each buy page, since Google’s product results read Product, not Book schema.

Most sites fit one of the first two groups. The feed route only makes sense with a large catalog, and Google approves providers case by case.

How to add book schema to your website

Most WordPress sites add Book schema through an SEO plugin that includes a Book type, while custom-built sites add JSON-LD to their book page template.

1. With a WordPress plugin

Rank Math includes a Book schema type with fields for editions, ISBN, and book format. Open a post’s Schema tab, click Schema Generator, and choose Book. 

All in One SEO (AIOSEO) also offers Book schema. Yoast SEO doesn’t include a Book type in its settings, so Yoast users add the JSON-LD through a custom code block or a separate schema plugin.

2. On custom-built sites

Add the JSON-LD to your book page template and fill it from your catalog fields, so every new title gets markup automatically. Store each edition’s ISBN and format as separate fields, which keeps your editions from collapsing into one.

3. With a book schema generator

Free generators work well for a single book page. Before you paste the output, check that it uses 13-digit ISBNs, a full bookFormat URL, and a separate entry for each edition.

Testing the book schema

After getting your Book schema through either of the ways mentioned above, run it through the Schema Markup Validator to check every Book property.

On review pages, use Google’s Rich Results Test to confirm the review is eligible for star ratings. Book actions feeds go through a separate check in Google’s Data Feed validation tool.

Validation takes a minute and catches most of the problems before Google or searchers ever see them.

Common Book schema mistakes to avoid

Most Book schema errors pass syntax checks but still confuse search engines, because the code is valid while the facts are muddled.

The first three cause the most trouble, because they blur the line between a book and its editions. Get that structure right, and the rest is mostly cleanup.

Does Book schema help SEO and AI search?

Book schema won’t push a page up the rankings on its own. What it does is remove doubt. 

A title like “The Lantern Keeper” could match several books. An ISBN, an author with sameAs links, and a clear list of editions tell search engines exactly which one your page covers. It’s the same entity-first thinking behind semantic SEO.

That clarity helps in AI search too. When someone asks an assistant which edition has an audiobook or who narrated it, the answer depends on sources with clean, consistent facts. 

Google says no special schema is needed to appear in AI Overviews, but structured facts make your page easier to quote correctly. For the research on how markup relates to AI citations, see our guide to schema markup for AI search.

How Contentpen helps authors get found

Book schema tells search engines which book a page is about. The page still needs content worth ranking and citing.

Contentpen is an SEO and AEO tool whose AI agents research keywords and write SEO and GEO-optimized articles for your site, from launch announcements to series reading-order guides. 

Its AI visibility tool tracks whether AI assistants like ChatGPT and Perplexity mention your books and brand, so you can see which titles they already know and which need more coverage.

However, Contentpen doesn’t write Book schema for you. So, keep your SEO plugin or page template in charge of the markup, and let Contentpen create content worth citing.

Write content that’s built to rank, not just read

Create search-optimized blogs aligned with SEO and GEO signals, so your content performs well across search and AI-driven discovery.

Try SEO Blogging FREE →

Final thoughts

Book schema has a narrow but real job in 2026. Large catalogs can earn buy and borrow links, review sites can earn stars, and every other book page gets data that search engines and AI tools can trust.

Start with one title. List its editions with their own ISBNs, link the author’s profiles, validate the markup, and then roll the template out to the rest of your catalog.

Frequently asked questions

Don’t you just hate it when you publish a well-researched post, and Google shows it with an old date, your logo as the thumbnail, or a title it rewrote on its own? Most of the time, that happens because Google had to guess while building your SERP tile for the data it didn’t get.

Article schema takes the guesswork away. It is a short block of code that tells search engines exactly what your headline is, who wrote the piece, when it went live, and which image represents it.

This guide explains what Article schema is, which of its three types to pick, and the properties Google actually looks at. You will also get two copy-ready JSON-LD examples, the easiest ways to add the markup, how to test it, and the mistakes that quietly break it.

So, let’s get started.

Key takeaways

• Article schema is a type of schema markup (structured data) that labels a page’s headline, author, publish dates, and images so Google can show them correctly in search results.
• Google supports three article types: Article, BlogPosting, and NewsArticle. Use the most specific one that fits the page.
• Google has no required properties for Article markup. It recommends headline, image, datePublished, dateModified, and author.
• Yoast SEO and Rank Math add Article schema to WordPress posts by default, so most sites only need to check and fine-tune it.
• Article schema won’t raise your rankings on its own, but it helps your result show the right title, image, and date.

What is Article schema?

Article schema is a type of structured data, written with the schema.org vocabulary. It tells search engines that a page contains an article and describes its key details, including the headline, author, publish date, and images.

Think of it as the label on a book inside a large library. The book reads the same with or without it, but the label tells anyone scanning the shelf what it is, who wrote it, and when it came out.

Article schema is one of many types of schema markup, and one of the most widely used ones on the web. The schema.org Article type appears on more than 10 million domains, based on Google’s web index.

According to Google’s article structured data documentation, the markup can help Google “understand more about the web page and show better title text, images, and date information” in search results.

What are the three types of article schema?

Google supports three article schema types: Article, BlogPosting, and NewsArticle. They share the same properties, so the choice of using them depends on what the page represents. 

Google’s structured data guidelines ask you to “use the most specific applicable type.” In other words, pick the type that describes your page most precisely. 

BlogPosting and NewsArticle are narrower versions of Article, so a blog post should use BlogPosting and a news report should use NewsArticle.

Plain Article schema is the fallback for written content that fits neither category, but it should not be used as the default for every page.

What about TechArticle, ScholarlyArticle, and other subtypes?

Schema.org also lists more specific article types, including TechArticle for technical posts, ScholarlyArticle for academic papers, Report, SatiricalArticle, and AdvertiserContentArticle for sponsored content. They are all valid schema.org types, and other platforms may read them.

Google’s article documentation only names Article, BlogPosting, and NewsArticle. If you use another subtype, run the page through the Rich Results Test to confirm if Google still detects it as an article. For more guidance, see our schema markup examples post.

Which Article schema properties does Google recommend?

Google keeps its guidance short: “There are no required properties. Instead, add the properties that apply to your content.” 

In practice, five properties do most of the work.

Author markup rules Google spells out

The author property gets the most detailed guidance, because it tells Google who stands behind the content:

• Include every author: Mark up each person shown as an author on the page.
• One author per field: List co-authors in separate author entries, never as “Jane Smith and Ali Khan” in one name.
• Name only: Leave out job titles, the publisher’s name, and phrases like “Posted by.” Use jobTitle or publisher property for that information.
• Correct type: Use the Person type for people and Organization for companies.
• Point to a profile: Add a URL to the author’s bio page or another page that identifies them, or use sameAs.

Optional properties worth adding

Beyond Google’s list, a few schema.org properties make your markup more complete:

• publisher: The organization that owns the site, with its name and logo.
• mainEntityOfPage: The URL of the page the article lives on.
• description: A one-line summary of the article.
• articleSection and wordCount: The category the piece belongs to and its length.

Article schema examples in JSON-LD

Google recommends JSON-LD for structured data, and it is the most common format on the web. According to W3Techs, 57.4% of websites have their structured data in JSON-LD. It sits in its own script tag, so it never touches the visible content of your page.

The two Article schema examples below use fictional sites to show you how they’re created. Swap in your own URLs, names, and dates, and use them as an Article schema template for any post.

Example 1: BlogPosting for a gardening blog

What makes this example good to use:

• It supplies the same image in all three ratios Google asks for.
• Both dates carry a timezone offset (-05:00), so they can’t shift by a day.
• The author’s URL points to a bio page, which helps Google tie the post to a real person.

Example 2: NewsArticle with two reporters

Notice that each reporter gets a separate entry in the author array, and dateModified records the overnight update to the story.

How to add article schema to your website

How you add article schema depends on your platform. Check what is already there first. Start by pasting a published post into the Rich Results Test, because many sites already output Article markup without anyone setting it up.

1. On WordPress with Yoast SEO or Rank Math

Both Yoast and Rank Math plugins add Article schema to posts by default and fill it from your post title, author profile, dates, and featured image. 

Go to each plugin’s settings to see which type of Article schema they’re adding to your posts:

• Yoast SEO: Go to Yoast SEO -> Settings -> Content types – > Posts, and see the article type under Schema. Options include Blog Post and News Article.
• Rank Math: Set the site-wide default schema under Rank Math -> Titles & Meta -> Posts, or change a single post from the Schema tab in its editor sidebar.

For most blogs, switching the default from Article to Blog Post is the only change you need.

2. Manually on custom-built sites

If your CMS has no schema setting, add the JSON-LD script to your article template so it fills in each post’s title, author, dates, and image automatically. Keep in mind that hardcoding a separate block into every post works for a few pages but gets tedious fast.

No access to your theme files? Add the script in Google Tag Manager as a Custom HTML tag, use variables like {{Page URL}} so each post gets its own details, fire it on DOM Ready for your blog URLs, and test the live URL in the Rich Results Test.

Treat Tag Manager as a fallback, though. Google sees the markup only after it renders JavaScript, and a Vercel study found that most AI crawlers, including GPTBot and ClaudeBot, don’t render JavaScript at all, so they would miss it.

3. With an Article schema generator

Free blog schema generators provide you with JSON-LD code that you can paste into your page instantly. They work for one-off pages, but check the output before you use it, as many tools leave out time zones, author URLs, and extra image sizes in the file.

How to test Article schema

Run these checks after you add or change the markup:

1. Rich Results Test: Enter your URL in Google’s Rich Results Test to see whether Google detects article markup and whether it flags errors.
2. Schema Markup Validator: Use the Schema Markup Validator to check the full schema.org syntax, including optional properties Google doesn’t use.
3. Match the page: Compare the markup with what readers see. Google’s guidelines say, “Don’t mark up content that is not visible to readers of the page,” so the headline, author, and dates should match the visible ones.
4. URL Inspection: In Search Console, inspect the live URL to confirm Google can crawl it and that robots.txt, noindex, or a login wall isn’t blocking it.

Common Article schema mistakes to avoid

Most Article schema problems are small and easy to miss, and they rarely show up as errors in testing tools.

Does Article schema help SEO and AI search?

Not as a direct ranking boost. Google’s John Mueller put it plainly in a 2025 post on Bluesky:

“Structured data won’t make your site rank better… Use it if your pages map to & are appropriate for any of those features.”

What Article schema does is make your result accurate with the right title, thumbnail, and date. On a crowded results page, a recent date and a relevant image give searchers a reason to pick your link instead of many others.

AI search works in a similar way. For AI Overviews, Google’s AI features guide says you don’t need special markup or files, and the same goes for an llms.txt file. That said, clear authors and dates still help any system judge who wrote a page and how current it is. 

For the research on schema and AI citations, read our guide to schema markup for AI search.

How Contentpen helps your articles show up online

Article schema only describes the article underneath it, so the content still has to earn the click and the citation.

That’s where Contentpen comes in. As an SEO and AEO tool, its AI agents research keywords, write SEO and GEO-optimized articles with clear headings, and create on-brand featured images that can double as your schema image. 

With one-click publishing, posts go straight to WordPress, Webflow, Shopify, Ghost, Wix, EmDash, and BigCommerce, where your SEO plugin adds Article schema automatically.

Publish content directly to your CMS, without copy-pasting

Move from draft to live post in a single step. No hassle, no errors!

Try One-click Publishing →

Contentpen doesn’t write JSON-LD itself, so keep Yoast, Rank Math, or your plugin in charge of the markup. Contentpen keeps the articles coming, and with Autopilot it can research, write, and publish on a schedule, with your approval before anything goes live.

Final thoughts

Article schema is one of the simplest structured data wins in 2026. There is one block of JSON-LD, five recommended properties, and three types to choose from. It won’t lift rankings by itself, but it makes sure Google shows your headline, image, and dates the way you intended.

Start by testing a few published posts, fix what’s missing, and let your CMS handle the markup from there.

Frequently asked questions