Schema markup will not make your nonprofit rank higher, and as of this year it no longer earns FAQ rich results at all. What JSON-LD structured data still does is help Google and AI systems read your pages correctly, and that machine-readable clarity is the foundation for getting cited in AI answers.
The short version
- Google has been clear that structured data does not improve rankings. It makes pages eligible for search features and helps machines understand your content, nothing more.
- Google stopped showing FAQ rich results in May 2026, and Search Console support for them winds down this month. FAQPage markup now produces nothing visible.
- Google says there is no special markup required to appear in AI Overviews or AI Mode. The same content and technical fundamentals apply.
- The schema still worth your time: Organization, Article, Event, BreadcrumbList, and Product or Offer if you sell or take donations.
- AI Mode passed one billion monthly users in 2026, so pages a machine can parse cleanly are now table stakes, not a bonus.
Structured data is a translation layer, not a ranking lever
The single most common mistake I see on nonprofit sites is treating schema like a growth hack. It is not. Google's own guidance draws a hard line here: structured data makes a page eligible for rich results and helps Google understand what the page is about, but it does not give you a ranking boost. If a vendor is selling you "schema for rankings," they are selling you a story.
That distinction matters because it changes where you spend effort. Structured data is a translation layer. It takes what your page already says in human language, your organization name, an event date, an article author, and restates it in a format a machine can parse without guessing. Fewer guesses means fewer mistakes about who you are and what you do. For a nonprofit competing against larger orgs for the same searches, that is the whole game.
So the goal is not "add more schema." It is accurate, minimal markup that matches what a visitor actually sees. Google's guidelines are explicit that your markup has to reflect the visible content of the page. Marking up an event you do not show, or a rating you invented, is a manual-action risk, not a shortcut.
Google just retired FAQ rich results, so delete the busywork
For years, the reflexive advice was to bolt FAQPage schema onto every page for those expandable question boxes in the results. That advice is now dead. Google stopped displaying FAQ rich results in Search in May 2026, and the wind-down of Search Console reporting and API support for them runs through this month. The markup itself will not hurt you, but it will never again show a rich result.
If your site was built in the last five years, a theme or plugin is probably still injecting FAQPage JSON-LD you no longer benefit from. It is not urgent, but on your next content pass, stop generating it for the rich result and keep the on-page FAQ only where it genuinely helps readers. HowTo rich results met the same fate on mobile back in 2023. The pattern is worth internalizing: Google adds schema-driven features, then removes them when they clutter the results or get abused. Betting your visibility on any single feature is fragile. Betting on clean, accurate entity data is not.
The five schema types worth your time
Strip away the deprecated and the decorative, and a nonprofit site needs a short list.
Organization is the one almost everyone gets wrong or skips. This is the block that tells Google, in machine terms, that your nonprofit is a distinct entity: your legal name, logo, and the `sameAs` links to your official social and registry profiles. It is the anchor for your knowledge panel and, increasingly, for how an AI system decides whether to trust and cite you. Put one Organization block sitewide, ideally in the head, and keep it correct.
Article or NewsArticle belongs on your blog and news posts. It names the author, the publish date, and the headline in a structured way, which supports Google's Top Stories and article features and gives AI systems a clean read on authorship and recency. For a mission-driven org publishing research or advocacy pieces, that authorship signal is part of your credibility.
Event is high value and underused. If you run galas, webinars, trainings, or advocacy days, Event schema with a start date, location, and registration URL can surface your event directly in Search. This is one of the few rich-result types that reliably still renders and drives real registrations.
BreadcrumbList is small but earns its keep. It replaces the raw URL in the results with a readable path, which nudges click-through and helps crawlers and AI systems understand your site's structure.
Product or Offer applies if you run a shop or sell memberships. Handle it carefully and only where it maps to something real on the page, because Google polices commercial markup more aggressively than any other type.
Notice what is not on the list: FAQPage, HowTo, and the long tail of speculative types people add hoping something sticks. More schema is not more visibility. Accurate schema is.
How structured data helps you show up in AI answers
Here is the honest version, because there is a lot of confident nonsense in this space. Google's documentation on its AI features states plainly that you do not need special markup or setup to be eligible for AI Overviews or AI Mode. Those experiences are grounded in the same web results and follow the same fundamentals as regular Search. Anyone promising a "schema trick" to get cited in AI answers is guessing.
What is true, and defensible, is quieter. AI systems have to resolve entities: they need confidence that "the Houston literacy nonprofit" on your page is the same organization referenced elsewhere. Clean Organization markup with accurate `sameAs` links makes that resolution easier and less error-prone. When a model is deciding which of three similar orgs to name in an answer, the one whose identity is machine-legible and internally consistent is the safer pick. Schema does not buy you a citation. It removes the ambiguity that costs you one.
The context here is why any of this is worth doing. Google has said AI Mode surpassed one billion monthly users in 2026, with queries more than doubling every quarter. When that many searches route through a system that reads your page programmatically before a human ever sees it, being cleanly parseable stops being a technical nicety. It is the price of showing up.
A JSON-LD implementation that will not break
Keep it boring and it will keep working. Use JSON-LD, not microdata, and place it in the page head. Google recommends JSON-LD and it is the format least likely to break when you redesign, because it lives separately from your markup.
When I rebuilt the site for a state association client last year, we did exactly one thing with schema at launch: a single, correct Organization block rendered sitewide from the content management system, plus Event schema generated automatically from their events collection. No FAQPage, no HowTo, no decorative types. Their events started appearing with dates in Search within a few weeks, and their knowledge panel finally showed the right logo and links. That was the entire program, and it was enough.
Three rules keep you out of trouble. Every field in your markup must correspond to something a visitor can see on that page. Validate with Google's Rich Results Test and the Schema.org validator before you ship, and again after any template change. And generate schema from your content management system so it stays in sync automatically, rather than hand-coding it into pages where it silently drifts out of date. If you are weighing a platform that can do this cleanly, here is my take on what a nonprofit website developer should actually build for you.
What this does not cover
This is a guide to the structured data that earns visibility, not a full technical SEO audit. It does not cover crawlability, indexing, Core Web Vitals, or content quality, all of which matter more than schema for whether you rank at all. It also skips non-Google engines. ChatGPT, Perplexity, and others each ground and cite differently, and clean schema helps them for the same entity-clarity reasons, but none publish a spec you can optimize against the way Google does. Treat schema as one clean layer on a technically sound site, not a substitute for one.
Frequently asked questions
Does schema markup help my nonprofit rank higher on Google?
No. Google has stated that structured data does not improve rankings. It makes your pages eligible for certain search features and helps Google understand your content, which can help you appear for more relevant queries, but there is no direct ranking boost from adding markup.
Should I remove FAQ schema now that Google dropped FAQ rich results?
You do not have to remove it, and leaving it will not cause problems, but it no longer produces any visible result in Google Search. Stop adding FAQPage markup for the rich result. Keep an on-page FAQ only if it genuinely helps your readers.
What schema should a nonprofit website have at minimum?
Start with one accurate Organization block sitewide, including your logo and `sameAs` links to official profiles. Add Article schema to blog and news posts, Event schema to anything with a date and registration, and BreadcrumbList for navigation. That covers most nonprofits.
Will schema markup get me cited in AI Overviews or ChatGPT?
Not directly. Google says no special markup is required to appear in its AI features. Clean structured data helps AI systems resolve who you are and reduces the chance they confuse you with another org, which makes a citation more likely, but no schema guarantees one.
JSON-LD or microdata for structured data?
Use JSON-LD. Google recommends it, and because it lives in a script block separate from your visible markup, it is far less likely to break during a redesign or template change.
If you want me to audit the structured data on your nonprofit's site and tell you exactly what to keep, cut, and add, book a 20-minute schema read-out and I will walk your top templates line by line.