اللغات

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.
 
     
  
  
 
 
 
 
     
حول الأداة
لصق ترميز أو واحد عنوان URL و قارن مكتشف مخطط أنواع مع ال Google rich-result متطلبات هذا الأداة tracks. Google بمفرده يحدّد ما إذا واحد منسّق نتيجة يظهر.
مجاني, من دون تسجيل. صالح مخطط يفعل ليس يخبر أنت ما فعليًا يعرض up في ال SERP — أهلية يفعل. لصق الخاص بك البيانات المنظَّمة, واحد كامل HTML صفحة, أو جلب واحد حي عنوان URL, و من أجل كل rich-result اكتب Google يدعم, هذا أسماء ما إذا ال صفحة هو مؤهل, أو ال دقيق مطلوب حقل قائم في ال way.
الميزات
  • Per-feature أحكام: من أجل كل مكتشف اكتب, مؤهل أو ال دقيق مطلوب حقل حظر إنه — بالإضافة ال موصى به حقول يستحق إضافة.
  • Three إدخالات: لصق JSON-LD, لصق واحد كامل HTML صفحة, أو جلب واحد حي عنوان URL server-side.
  • اكتشاف تلقائي وضع ذلك يخبر JSON-LD من HTML من أجل أنت.
  • Handles @رسم بياني ترميز و @id إحالات متقاطعة, resolving قيم عبر مرتبط nodes بالضبط مثل ال مدقق.
  • الأكثر تحديدًا اكتب مطابق, لذلك واحد subtype هو مُقيَّم مقابل الخاص به الخاص ميزة, ليس الخاص به أساس.
  • بصدق تسميات restricted, مهجور, و متقاعد ميزات بدلًا من يتظاهر هم ما زال draw واحد نتيجة.
  • مؤرّخ "متطلبات تم التحقّق منه" stamp و واحد قواعد إصدار على كل شغّل, لذلك أنت يمكن انظر كيف حالي ال جدول هو.
  • Shareable-link مخرجات ذلك حزم ال إدخال إلى ال عنوان URL جزء — لا شيء مخزّن.
كيفية العمل
هذا الأداة يمتد ال مخطط مدقق بدلًا من تفريع إنه: التحليل, HTML استخراج, و @id رسم بياني دقة هي معاد استخدامه جملة. ال جديد طبقة هو ال أهلية فرق — إنه يمر كل node’s اكتب أصل, يطابق إنه إلى ال Google rich-result ميزات ذلك تطبيق (الأكثر تحديدًا اكتب يفوز, لذلك واحد Recipe هو judged باعتباره واحد Recipe, ليس باعتباره الخاص به HowTo أساس), ثم تحقّقات كل feature’s مطلوب و موصى به خصائص مقابل واحد curated متطلبات جدول mirrored من Google مستندات.
القيود
  • أهلية هو ليس عرض. اجتماع كل مطلوب حقل يمسح Google متطلبات شريط, لكن Google بمفرده يحدّد ما إذا إلى draw واحد منسّق نتيجة, مبني على على جودة, استعلام, جهاز, و الخاص به الخاص مرشحات. هذا الأداة لا يمكن يتنبأ ذلك.
  • إنه تحقّقات ال rich-result ميزات backed بواسطة واحد موثق متطلبات جدول, لذلك واحد niche أو brand-new ميزة قد ليس يظهر. إنه يقرأ ال البيانات المنظَّمة موجود في ال ترميز: بيانات injected بواسطة client-side JavaScript هو invisible في عنوان URL و HTML أوضاع — لصق إنه مباشرة. و ال متطلبات جدول هو واحد curated mirror من Google مستندات في واحد نقطة في وقت; Google يمكن غيّر متطلبات بين تحديثات, أي هو لماذا كل بطاقة يحمل واحد تم التحقّق منه تاريخ.
الأسئلة الشائعة
يفعل يكون مؤهل يعني my منسّق نتيجة سوف اعرض?
لا. أهلية يعني ال صفحة يستوفي Google موثق مطلوب حقول من أجل ذلك ميزة, أي هو ال price من admission — لا شيء أكثر. Google ما زال يحدّد حالة بواسطة حالة ما إذا إلى اعرض واحد منسّق نتيجة, مبني على على صفحة جودة, استعلام, جهاز, و الخاص به الخاص manual و algorithmic مرشحات. واحد صفحة يمكن يكون perfectly مؤهل و أبدًا يكسب ال تحسين. هذا الأداة يخبر أنت ما إذا أنت يحتوي cleared ال متطلبات شريط, ليس ما إذا Google سوف draw ال نتيجة.
لماذا يفعل ال فاحص يقول I am مفقود واحد مطلوب حقل عندما ال مخطط مدقق ناجح?
هم إجابة مختلف أسئلة. ال مخطط مدقق تحقّقات ما إذا الخاص بك JSON-LD هو صالح و يستخدم فعلي schema.org مفردات. هذا فاحص diffs الخاص بك ترميز مقابل Google per-feature متطلبات جدول — ال محدد خصائص Google يتطلب من أجل واحد معطى منسّق نتيجة. ترميز يمكن يكون flawless schema.org مع ذلك ما زال يفوّت واحد Google-required حقل (من أجل مثال واحد منتج مع لا price أو لا مراجعة), لذلك إنه validates بصورة نظيفة لكن هو ليس مع ذلك مؤهل.
لماذا يفعل my FAQ اعرض باعتباره "متقاعد" بدلًا من مؤهل?
Google stopped عرض FAQ منسّق نتائج على قد 7, 2026 و لاحقًا مزال ال ميزة توثيق. FAQPage يبقى صالح schema.org ترميز و قد ما زال help آخر consumers من البيانات المنظَّمة, لكن إنه لا أطول ينتج واحد Google بحث منسّق نتيجة. ال الأداة يبلّغ ذلك باعتباره متقاعد بدلًا من يتظاهر ال تحسين هو ما زال متاح.
يمكن إنه تحقّق واحد حي عنوان URL, أو فقط ملصق ترميز?
كلاهما. لصق JSON-LD أو واحد كامل HTML صفحة, أو أدخل واحد عنوان URL و ال الأداة يجلب ال صفحة HTML server-side و يستخرج الخاص به البيانات المنظَّمة في الخاص بك متصفح. لأن استخراج تشغيل على ال مجلوب HTML, البيانات المنظَّمة injected بواسطة client-side JavaScript سوف ليس يكون مرئي — لصق إنه مباشرة في ذلك حالة.
أي rich-result أنواع يفعل إنه تحقّق?
إنه يغطي ال Google بحث ميزات backed بواسطة واحد موثق متطلبات جدول — منتج, مقال, Recipe, حدث, فيديو, JobPosting, مسار التنقل, مؤسسة, Q&واحد, و أكثر. إنه أيضًا يتعرّف متقاعد ميزات مثل باعتباره FAQ و ال sitelinks بحث مربع, labeling هم بدلًا من بصمت تجاهل هم. أنواع مع لا Google منسّق نتيجة (أو لا شيء نحن يتتبّع) هي مدرج تحت "لا qualifying ترميز" بدلًا من الحصول على واحد بطاقة.