Schema markup isn't just a technical embellishment that only developers understand. It's the language that allows Google and generative AIs to correctly interpret what's on your page, rather than having to guess from the running text.
The part that confuses most companies is thinking that schema is only for earning those rich results on Google, like star ratings or expandable questions. This has changed significantly in 2026, and it's worth understanding what still works before investing development time in the wrong place.
Schema Types That Still Generate Visible Results on Google
Organization is the foundation: company name, logo, social media, contact details. This schema helps Google build your brand's "identity card" in the knowledge graph, and also informs how AI systems identify the company behind the content.
Article remains one of the schemas with the clearest practical effect. Implemented with publication date, author, and responsible organization, it enables features like a site search box and author display directly in Google search results, according to Google's structured data documentation.
Having correct schema isn't the same as being ready to be cited by AI. The article on AI search readiness details the practical tests to measure this beyond technical markup, including direct citation testing and content gap mapping.
What Changed with FAQPage and HowTo (and Why It Matters for Your Planning)
Until recently, it was common to recommend FAQ and HowTo schema as a priority to get those expandable question-and-answer results on Google. This is no longer the case.
Google completely discontinued FAQ rich results in May 2026, according to a report by Search Engine Journal. The restriction had already been in place since 2023, when the feature was limited to government and health sites, and now even that exception no longer exists. HowTo had already lost its rich result on desktop since 2023.
This doesn't mean that maintaining a FAQ section in your content is no longer useful. The reason has simply changed: today the value lies in GEO, not traditional SEO. Content structured in direct question-and-answer format helps generative AI systems identify and extract the correct answer, regardless of whether FAQPage markup is applied. Google itself has publicly confirmed that no schema guarantees citation in an AI response; the decisive factor is content clarity, not the presence of markup.
This principle of structuring content into self-sufficient blocks is explored in depth in the article on content chunks, which specifically addresses how to write to be extracted by AI, beyond the schema itself.
Common Errors That Cause Schema to Fail
Empty or outdated required fields are the most frequent error, and also the easiest to avoid with recurring validation. Schema that describes something different from what is visible on the page can also lead to rejection, as Google requires consistency between the markup and the actual content.
It's advisable to use the JSON-LD format as standard, instead of microdata or RDFa, because it's the format Google itself recommends and the simplest to maintain separately from the page's HTML.
| Schema Type | Still Generates Rich Result on Google | Current Function |
|---|---|---|
| Organization | Yes | Brand identity in the knowledge graph |
| Article | Yes | Author, date, site search box |
| FAQPage | No (discontinued in May/2026) | Content structure for GEO |
| HowTo | No (discontinued on desktop since 2023) | Content structure for GEO |
Why Incomplete Schema Loses to Competitors Who Implement Everything
Even schemas that don't generate rich results help Google and AI systems better understand the page, which is a factor when deciding which source to cite or display more prominently. A company with well-implemented Organization and Article, updated data, and content consistent with the markup has an advantage over a competitor who hasn't reviewed their schema since its initial implementation.
Receba os próximos artigos por e-mail
Conteúdo novo de Draivv direto na sua caixa de entrada. Sem spam.
Well-executed technical schema also yields more when the content itself is already organized by topic. The article on topical authority and content clusters shows how the structure of pillar pages and supporting articles reinforces precisely this type of authority signal that technical schema alone doesn't deliver.
How to Keep Schema Updated Without Constant Manual Review
Maintenance is where most implementations fail: prices change, articles are updated, company data changes, and the schema silently becomes outdated, without generating visible errors until someone checks.
How to Apply This to Your Operations
The first practical step is to audit what is already implemented today: Are Organization and Article complete and up-to-date? Is there FAQ or HowTo schema intended only for rich results that has already lost its original function?
The Draivv Rank automatically applies and maintains this technical layer, including schema, sitemap, canonical, and llms.txt, precisely solving the manual maintenance problem that often leaves schema outdated over time.
Learn more about Draivv!
Frequently Asked Questions
Does schema markup still directly affect ranking on Google?
It's not a direct ranking factor, but it affects eligibility for rich results (for the types that still exist) and helps Google and AIs better interpret content, which indirectly influences visibility and citation.
What types of schema are a priority for a B2B company today?
Organization and Article continue to be the ones that generate visible practical results on Google. FAQPage and HowTo are more valuable for the content structure they help create than for the markup itself, as they no longer generate rich results.
How often should implemented schema be reviewed?
Ideally, review whenever the related page is updated (new data, new author, new information), in addition to a general audit every quarter to catch unnoticed inconsistencies.
