Structured data is a short block of code that tells search engines, in a shared vocabulary, what a page contains: this page is an event, it starts on this date, it happens at this address. Google says the markup helps it understand a page and can make the page eligible for rich results, the listings with dates, logos or breadcrumbs.
Our guide to what SEO is gave this topic one short section. This piece is the on-ramp. It covers JSON-LD versus microdata, the schema.org vocabulary, the types that matter for nonprofits and associations, a simple example, how WordPress and Drupal add the markup, and how to test it.
The short version: use JSON-LD, start with Organization on your home page or about page, and add Article and Event where they fit. Let your SEO plugin or CMS module write it. Check it in the Rich Results Test and Search Console. Keep expectations modest. Google dropped FAQ rich results in 2026, members-only events do not qualify for event listings, and Google says structured data is not required for its AI features.
What structured data is, in plain terms
A web page is written for people. A search engine has to guess which text is the date, the venue or the price. Structured data labels each fact.
Google’s introduction to structured data calls it a standardized format for providing information about a page and classifying its content. It does two jobs. It confirms facts such as your official name, logo and address. And some types let a page qualify for a rich result, with no promise that one will appear.
One rule applies to every type: the markup has to describe what a visitor can see. Google’s guidelines say "don’t add structured data about information that is not visible to the user, even if the information is accurate." Markup that breaks the guidelines can make a page ineligible for rich results.
JSON-LD vs microdata (and RDFa)
Google supports three formats. All three carry the same schema.org facts. They differ in where the code lives.
JSON-LD keeps all the facts in one script block, usually in the page head, separate from the layout. This is what SEO plugins and CMS modules output.
Microdata adds attributes to the visible HTML tags. A developer marks the wrapper with itemscope and itemtype, then tags the event title with itemprop="name" and the date with itemprop="startDate". The labels sit inside the design, so a theme change can break them.
RDFa works much like microdata, with different attributes.
Google recommends JSON-LD where a site’s setup allows, calling it the easiest option to implement and maintain at scale. It also says all three formats are equally fine, as long as the markup is valid. If your site already uses microdata that tests clean, there is no reason to rush a rewrite.
How the schema.org vocabulary works
Schema.org is a shared dictionary of types and properties. A type says what something is. A property says something about it. Organization is a type. Its name, logo and address are properties.
Types nest. Schema.org lists NGO (non-governmental organization) as a more specific kind of Organization. Organization also has a nonprofitStatus property. For US groups, its values follow IRS section codes, such as Nonprofit501c3 and Nonprofit501c6.
Google uses only part of the vocabulary and says its own Search Central documentation is definitive for Search. A type can be valid schema.org and still do nothing visible in Google.
Structured data types that matter for nonprofits and associations
Organization. Google’s Organization documentation says the markup helps Google tell your organization apart from others and can affect the logo and knowledge panel it shows. It has no required properties. Put it on the home page or one about page, not every page. Google recommends the most specific subtype that fits. Its page does not name NGO, so test NGO before relying on it.
Article. For news, blog posts and similar articles. Article, NewsArticle and BlogPosting are accepted, with no required properties. Google recommends headline, image, datePublished, dateModified and author.
BreadcrumbList. Shows where a page sits, such as Home, then Events, then Annual Conference. Since January 2025, Google shows breadcrumbs on desktop results only.
Event. The type associations ask about most, with the strictest rules. See the next section.
LocalBusiness. Built for places with a public address and hours. For an association office, Organization plus an accurate Google Business Profile usually does more. Our guide to Google Business Profile for nonprofits covers the profile side.
Event structured data: the association catch
Google’s event documentation requires four properties: name, startDate, location and location.address. Each event needs its own page, focused on that one event.
The eligibility rules rule out a lot of association programming:
- Members-only events. Events that require a membership or invitation before buying a ticket or attending are ineligible.
- Virtual events. Online events with no real-world component are not supported. Google removed the online event properties in June 2025.
- Closed events. Tickets must be bookable by the general public.
So a public annual conference at a hotel qualifies. A members-only webinar series does not.
The event experience is also limited by country and language. The United States, Canada and the United Kingdom are on Google’s list as of October 2026.
Where Google’s rich results stand, as of October 2026
Google changes this list often. Check the search gallery (last updated October 16, 2026) and the documentation updates log before you plan.
| Type | Google rich result status | What changed |
|---|---|---|
| Organization | Supported | In the gallery; no required properties |
| Article | Supported | In the gallery; no required properties |
| BreadcrumbList | Supported, desktop only | Dropped from mobile results in January 2025 |
| Event | Supported, with limits | Public, physical events only since June 2025 |
| LocalBusiness | Supported | In the gallery as Local business |
| FAQPage | No longer shown | Dropped from Google Search on May 7, 2026; docs removed June 15, 2026 |
| HowTo | Not in the gallery | No rich result listed |
| Course info, Learning video, Special announcement | No longer shown | Removed in September 2025 |
FAQPage is still a valid schema.org type, and plugins still output it. It no longer earns a rich result in Google, so it is not a reason to add FAQ sections to pages.
A simple Organization example in JSON-LD
Here is Organization markup for a made-up association, using Google’s recommended properties.
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Example Association of Educators",
"url": "https://www.example.org/",
"logo": "https://www.example.org/images/logo.png",
"telephone": "+1-202-555-0100",
"address": {
"@type": "PostalAddress",
"streetAddress": "100 Main Street",
"addressLocality": "Washington",
"addressRegion": "DC",
"postalCode": "20001",
"addressCountry": "US"
},
"sameAs": ["https://www.linkedin.com/company/example"]
}
On a real page, this block sits inside a script tag with the type application/ld+json. @context names the vocabulary. @type names what is described. Every other line is a property. sameAs lists your official profiles elsewhere.
Every value has to match what visitors see. Most teams never type this by hand, because the CMS writes it.
How WordPress SEO plugins add structured data
On WordPress, an SEO plugin usually handles the markup with no code.
Yoast SEO. Yoast’s schema documentation says every page should output Organization, WebSite and WebPage pieces, linked as one graph in JSON-LD. Single posts add Article. A page with a Yoast FAQ block adds FAQPage. If the site represents a person, Yoast adds Person.
Rank Math. Its WordPress.org listing advertises 16+ schema types in the free version. It names Article, Event, Organization, Local Business and Breadcrumb among them, without saying which are free. More types and templates sit in the paid version.
Custom content needs more work. An events content type built with custom fields will not map itself to Event. Our ACF 6.8 schema.org mapping walkthrough shows how to connect custom fields to Event and Article properties.
How Drupal adds structured data
Drupal sites usually use the Schema.org Metatag module. It extends the Metatag module to output structured data as JSON-LD in the page head. About 83,700 sites report using it, as of October 2026.
The module adds schema.org fields to Metatag’s settings for types such as Organization, Article, Event and WebPage. You fill them with fixed values or tokens, the same way Metatag handles titles. Defaults can apply site-wide, per content type or per node. The 3.1.0 release from October 6, 2026 lists support for Drupal 9, 10 and 11.
Map your event content type to the Event fields and point location.address at the venue fields. Then check that member-only events are not marked up as public ones.
How to test structured data
Three free tools cover testing.
Rich Results Test. Google’s Rich Results Test asks whether a page is eligible for a Google rich result. It accepts a live URL or pasted code, reads JSON-LD, microdata and RDFa, and tests as a smartphone by default. It checks only types on Google’s list.
Schema Markup Validator. Google provides the Schema Markup Validator as a service to the schema.org community. It is based on the retired Structured Data Testing Tool. It checks any schema.org markup, such as NGO, with no Google eligibility verdict.
Search Console. Rich result reports sit under Enhancements, one per type Google found on your site. Google’s report help page says they show a sample, not every page. Use URL Inspection to check a single page.
When structured data is worth the effort
For most small teams the work is light: confirm the plugin or module is on, fill in the Organization details once, and fix errors Search Console reports.
Beyond that, be selective. Add Event markup where events are public and in person. Skip types Google does not show unless another platform you care about uses them. Google’s AI optimization guide also says: "Structured data isn’t required for generative AI search."
Our posts on Schema.org for GEO and schema markup for Google AI Overviews argue for wider markup for AI answers. Read them alongside Google’s statement and the FAQ change above.
Frequently Asked Questions
Should I use JSON-LD or microdata?
Use JSON-LD for new work. Google recommends it where your setup allows and says all three formats are fine if the markup is valid. Working microdata does not need a rush rewrite.
Does structured data improve rankings?
Google’s documentation describes it as a way to understand pages and qualify for rich results. It does not call it a ranking boost, and eligibility does not guarantee a rich result.
Do FAQ rich results still show in Google?
No. Google stopped showing them on May 7, 2026, and removed the documentation on June 15, 2026. FAQPage is still valid schema.org markup.
Can members-only events get event rich results?
No. Google rules out events that need a membership or invitation before buying a ticket or attending. Virtual events with no physical location are also ineligible.
Should a nonprofit use Organization or NGO?
NGO is a valid schema.org subtype of Organization, and Google recommends the most specific subtype. Google’s page does not name NGO, so test it first. Organization is the safe default.
Do I need structured data for AI Overviews?
Google says structured data isn’t required for generative AI search and that no special schema.org markup is needed for its AI features.
Does Yoast or Rank Math add structured data automatically?
Yes, for the basics. Yoast outputs Organization, WebSite and WebPage on every page and Article on posts. Rank Math advertises 16+ schema types in its free version.
Why does Search Console show no rich result report for my site?
Search Console shows a report only for supported types it has found with valid markup. Check a page in URL Inspection or the Rich Results Test to see what Google detects.