Idiomas

Rich-Result Eligibility Checker

Free, no signup. Valid schema doesn't tell you what actually shows up in the SERP — eligibility does. Paste your structured data, a full HTML page, or fetch a live URL, and for every rich-result type Google supports, this names whether the page is eligible, or the exact required field standing in the way.

Built by Patrick Stox

or fetch a live URL

Client-rendered (JS-only) markup won't be seen when fetching a URL; paste it in that case.

compare with a competitor URL

Runs entirely in your browser — nothing you paste is uploaded or stored. Fetch a live URL sends only that address to our server to retrieve the HTML; extraction and checking still happen in your browser. Anonymous run-level outcome counters may be used for aggregate research; URLs, domains, IPs, and identifiers are never included, and no statistic is released below 100 runs.

Feedback
Report a bug

Found something broken in Rich Result Eligibility? Let us know what happened — this goes straight to a private triage queue, not a public list.

What will be sent 
 No tool inputs, uploads, pasted source, complete results, query parameters, or URL fragments are attached automatically. You can edit or remove the selected passage above. Browser and anti-abuse metadata is processed for spam prevention. 
  
 
  
 
 
  
 
 
   
 
Sample report
 
Say you paste this graph — a Product offer missing its price, plus an FAQPage:
 
 
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Product",
      "name": "Trailhead Running Shoe",
      "image": "https://example.com/shoe.jpg",
      "brand": { "@type": "Brand", "name": "Example" },
      "offers": { "@type": "Offer", "priceCurrency": "USD" }
    },
    {
      "@type": "FAQPage",
      "mainEntity": [{
        "@type": "Question",
        "name": "Is it fast?",
        "acceptedAnswer": { "@type": "Answer", "text": "Yes." }
      }]
    }
  ]
}
 
 
…and it returns cards like these:
 
Example data — captured by running this page's own checker against the JSON-LD above
 
 
 2 rich-result types detected 1 field away 1 unavailable 
 
 
 
Product snippet
✗ Not yet eligible
 
Product · required 2/3 · recommended 3/8
 
Required — blocks the rich result
 
     
  • ✗ Needs an offer price (offers.price or offers.priceSpecification.price)Add price or priceSpecification.price to the Offer.
    •  
 
 
Recommended — improves the result
 
     
  • ⚠ Add description
    •  
  • ⚠ Add sku
    •  
  • ⚠ Add offers.availabilityMerchant listing experiences use availability.
    •  
  • ⚠ Add review
    •  
  • ⚠ Add aggregateRating
    •  
 
 
Google docs → requirements verified 2026-07-12
 
 
 
FAQ
Retired
 
FAQPage · required 0/0 · recommended 0/0
 
Google stopped showing FAQ rich results on May 7, 2026 and removed the feature documentation. FAQPage remains valid schema.org markup, but it no longer produces a Google Search rich result.
 
Google update → requirements verified 2026-07-12
 
 
 
 
     
  • The one blocking field is an offer price, not a review — this Product has an
            Offer and a currency code but no price or priceSpecification.price,
            so it's one field away: 2 of 3 required checks are already met.
            See what the badges mean ↓.
    •  
  • Five recommended fields are still open (description, sku, availability, review,
            aggregateRating) — none of them block eligibility, but each strengthens the result Google might draw.
    •  
  • FAQ is valid markup but Retired, so no required-field checklist is shown at
            all — Google no longer shows the enhancement on any site, no matter how complete the markup is.
    •  
  • Clearing the one required field is not a guarantee — eligibility only means the
            page cleared Google's documented bar; Google still decides whether to draw the result. Compare
            against the Schema Validator if the underlying JSON-LD
            itself needs checking first.
    •  
 
 
 
How to use it
 
     
  1. Choose an input mode. Auto-detect figures out whether you pasted
            JSON-LD or an HTML page; or force JSON-LD / HTML page
explicitly.
    2.  
  2. Paste your structured data into the box — a JSON-LD block, or a full HTML document with
            its <script type="application/ld+json"> tags. Or skip pasting: enter a
            live URL in the fetch a live URL row and press Fetch & check.
    3.  
  3. Press Check eligibility. Not sure what output looks like? Hit
Try an example to load a sample graph and run it.
    4.  
  4. Read the summary line, then the per-type cards. Fix anything marked
required first — those block the rich result — then work through the
            recommended fields.
    5.  
  5. Use Copy shareable link to hand the exact input and result to a
            teammate; the markup is packed into the URL, nothing is stored.
    6.  
 
 
 
       
     
     
 

Need to build or fix the markup?
Schema Generator scaffolds it ·
Schema Validator checks syntax & vocabulary in depth.

 
 
← All free tools
  
 
What the results mean
 
The summary line tallies the detected rich-result types, then each type gets a card with a badge:
 
     
  • ✓ Eligible (green) — every documented required field and one-of
            group is present. The page has cleared Google's requirements bar for that feature.
    •  
  • ✗ Not yet eligible (red) — one or more required fields are
            missing. The card lists exactly which, with a short "add this" hint. This is your fix list.
    •  
  • Restricted (grey) — valid markup, but Google limits the feature to a
            documented subset of sites. It will not draw the rich result for most sites.
    •  
  • Deprecated / Retired (grey) — the feature was removed from Search (e.g.
            HowTo) or retired (e.g. the sitelinks search box). The card names the status instead of
            nagging about fields for a dead feature.
    •  
 
Inside a card, items are split into two tiers:
 
     
  • Required — blocks the rich result: missing required properties, and
            "needs one of" groups where at least one of several properties must be present. Any of
            these unmet means not-yet-eligible.
    •  
  • Recommended — improves the result: fields Google suggests to enrich or
            stabilise the enhancement. Absent ones never block eligibility.
    •  
 
Each card also shows required X/Y and recommended X/Y counts, the
        matched schema.org type, the node's @id, and a dated "requirements verified" note.
 
How it works
 

This tool extends the Schema Validator
rather than forking it: parsing, HTML extraction, and @id graph resolution are
          reused wholesale. The new layer is the eligibility diff — it walks each node's type ancestry,
          matches it to the Google rich-result features that apply (most-specific type wins, so a Recipe
          is judged as a Recipe, not as its HowTo base), then checks each feature's required and
          recommended properties against a curated requirements table mirrored from Google's docs.

 

Paste mode (JSON-LD or full HTML) runs entirely in your browser — no network
          call. URL mode reuses a shared, SSRF-guarded, rate-limited fetch proxy to pull the page HTML
          server-side; extraction and the eligibility check still run client-side. Property lookups
          follow dotted paths through nested objects and @id references, and a value only
          counts as present if it carries real content (an empty string or empty object does not).

 
Features
 
     
  • Per-feature verdicts: for every detected type, eligible or the exact required field
            blocking it — plus the recommended fields worth adding.
    •  
  • Three inputs: paste JSON-LD, paste a full HTML page, or fetch a live URL server-side.
    •  
  • Auto-detect mode that tells JSON-LD from HTML for you.
    •  
  • Handles @graph markup and @id cross-references, resolving values
            across linked nodes exactly like the validator.
    •  
  • Most-specific type matching, so a subtype is scored against its own feature, not its base.
    •  
  • Honestly labels restricted, deprecated, and retired features instead of pretending they
            still draw a result.
    •  
  • Dated "requirements verified" stamp and a rules version on every run, so you can see how
            current the table is.
    •  
  • Shareable-link output that packs the input into the URL fragment — nothing stored.
    •  
 
Limitations
 
 Eligibility is not display. Meeting every required field clears Google's
          requirements bar, but Google alone decides whether to draw a rich result, based on quality,
          query, device, and its own filters. This tool cannot predict that.

 

It checks the rich-result features backed by a documented requirements table, so a niche or
          brand-new feature may not appear. It reads the structured data present in the markup:
          data injected by client-side JavaScript is invisible in URL and HTML modes — paste it directly.
          And the requirements table is a curated mirror of Google's docs at a point in time; Google can
          change requirements between updates, which is why every card carries a verified date.

 
Frequently asked questions
 
Does being eligible mean my rich result will show?
No. Eligibility means the page meets Google’s documented required fields for that feature, which is the price of admission — nothing more. Google still decides case by case whether to show a rich result, based on page quality, query, device, and its own manual and algorithmic filters. A page can be perfectly eligible and never earn the enhancement. This tool tells you whether you have cleared the requirements bar, not whether Google will draw the result.
Why does the checker say I am missing a required field when the Schema Validator passed?
They answer different questions. The Schema Validator checks whether your JSON-LD is valid and uses real schema.org vocabulary. This checker diffs your markup against Google’s per-feature requirements table — the specific properties Google requires for a given rich result. Markup can be flawless schema.org yet still miss a Google-required field (for example a Product with no price or no review), so it validates cleanly but is not yet eligible.
Why does my FAQ show as "Retired" instead of eligible?
Google stopped showing FAQ rich results on May 7, 2026 and later removed the feature documentation. FAQPage remains valid schema.org markup and may still help other consumers of structured data, but it no longer produces a Google Search rich result. The tool reports that as Retired rather than pretending the enhancement is still available.
Can it check a live URL, or only pasted markup?
Both. Paste JSON-LD or a full HTML page, or enter a URL and the tool fetches the page HTML server-side and extracts its structured data in your browser. Because extraction runs on the fetched HTML, structured data injected by client-side JavaScript will not be seen — paste it directly in that case.
Which rich-result types does it check?
It covers the Google Search features backed by a documented requirements table — Product, Article, Recipe, Event, Video, JobPosting, Breadcrumb, Organization, Q&A, and more. It also recognizes retired features such as FAQ and the sitelinks search box, labeling them instead of silently ignoring them. Types with no Google rich result (or none we track) are listed under "no qualifying markup" instead of getting a card.
 
 
 
   
Rich-result requirements last reviewed Jul 12, 2026.
 
Next stepSchema Markup Generator — generate the corrected version.

People also explore
ToolSchema Markup ValidatorToolEntity Coverage AnalyzerToolGoogle Knowledge Graph ExplorerArticleItemList SchemaArticleLocalBusiness SchemaArticleJobPosting Schema
 
 
 
Feature requests for Rich Result Eligibility
 

Upvote what you want most. New ideas can be submitted from the floating Feedback menu;
      requests appear here once approved, and the most-wanted rise to the top.

   
Loading…
  
  ➕ Request a feature   
New requests are reviewed before they appear here.
 
     
  
  
 
 
 
 
     
Sobre a ferramenta
Grátis, sem cadastro. A validação de esquema não diz o que realmente aparece na SERP; a verificação de elegibilidade diz. Cole JSON-LD, cole uma página HTML completa ou busque uma URL ativa no servidor.
Há três entradas: JSON-LD colado, HTML completo colado ou uma URL ativa buscada pelo servidor.
Recursos
  • A ferramenta cobre as funcionalidades da Pesquisa Google respaldadas por uma tabela de requisitos documentada — Product, Article, Recipe, Event, Video, JobPosting, Breadcrumb, Organization, Q&A e outras. Também reconhece funcionalidades aposentadas, como FAQ e a caixa de pesquisa de sitelinks, e as rotula em vez de ignorá-las silenciosamente. Tipos sem resultado avançado do Google (ou sem correspondência rastreada) aparecem em “Marcação sem qualificação”.
  • A linha de resumo conta os tipos de resultado avançado detectados e cada tipo recebe um cartão com um selo.
  • Dentro de um cartão, os itens são divididos em dois níveis: obrigatórios ausentes e recomendações opcionais.
  • Validador de esquema e verificador de elegibilidade respondem a perguntas diferentes. O primeiro verifica se o JSON-LD é válido e usa o vocabulário real do schema.org; o segundo compara sua marcação com a tabela de requisitos do Google. Uma marcação pode estar correta no schema.org e ainda faltar um campo exigido pelo Google, portanto pode validar sem ser elegível.
Como funciona
Cada entidade detectada é comparada ao tipo de resultado avançado mais específico aplicável. A ferramenta então verifica os campos obrigatórios e recomendados da tabela, agrupa os achados por entidade e apresenta a diferença entre “válido no schema.org” e “elegível para o Google”.
Limitações
  • A tabela de requisitos é um espelho mantido da documentação do Google em um determinado momento; o Google pode alterar os requisitos e as políticas depois.
  • No modo de URL, a extração e a verificação de elegibilidade continuam no navegador. Consultas de propriedade e marcação injetada por JavaScript podem não estar disponíveis no HTML buscado.
Perguntas frequentes
Que tipos de resultado avançado esta ferramenta verifica?
Ela cobre as funcionalidades da Pesquisa Google respaldadas por uma tabela de requisitos documentada — Product, Article, Recipe, Event, Video, JobPosting, Breadcrumb, Organization, Q&A e outras. Também reconhece FAQ e a caixa de pesquisa de sitelinks como funcionalidades aposentadas, em vez de fingir que ainda estão disponíveis.
Ser elegível significa que meu resultado avançado vai aparecer?
Não. Elegibilidade significa que a página atende aos campos obrigatórios documentados da funcionalidade, o preço de entrada — nada além disso. O Google decide caso a caso com base em qualidade, consulta, dispositivo e filtros manuais ou algorítmicos. A ferramenta informa se você passou pela barreira de requisitos, não se o Google exibirá o resultado.
Por que o verificador diz que falta um campo obrigatório quando o Validador de esquema aprovou?
As ferramentas respondem a perguntas diferentes. O Validador de esquema verifica a validade do JSON-LD e o vocabulário schema.org; este verificador compara a marcação com os requisitos do Google. Ela pode estar correta no schema.org e ainda não ter um campo exigido pelo Google.
Por que minha FAQ aparece como “Retired” em vez de elegível?
O Google deixou de mostrar resultados avançados de FAQ em 7 de maio de 2026 e depois removeu a funcionalidade da documentação. FAQPage continua sendo uma marcação válida do schema.org e pode ajudar outros consumidores de dados estruturados, mas não produz mais um resultado avançado da Pesquisa Google. A ferramenta a informa como Retired.
A ferramenta verifica uma URL ativa ou somente marcação colada?
Ambos. Cole JSON-LD ou HTML completo, ou informe uma URL para a ferramenta buscar o HTML no servidor e extrair os dados estruturados no navegador. Como a extração usa o HTML buscado, dados estruturados injetados por JavaScript no cliente não serão vistos; nesse caso, cole o HTML diretamente.