90 checks in Schema, Local, Trust, Deep Audit. Automated Its subsection has a live automated checker in the engine.
| ID | Check | Passes when |
|---|---|---|
| 6.12.01 | Detect FAQPage schema | Present |
| 6.12.02 | Validate correct schema type (FAQPage) | Accurate |
| 6.12.03 | Validate mainEntity array exists | Present |
| 6.12.04 | Validate each mainEntity is a Question object | Accurate |
| 6.12.05 | Validate each Question contains acceptedAnswer | Present |
| 6.12.06 | Validate question name (text) present | Present |
| 6.12.07 | Validate question clarity (not vague/ambiguous) | Clear |
| 6.12.08 | Validate question matches the visible on-page FAQ | Exact |
| 6.12.09 | Validate no duplicate Question objects in schema | None |
| 6.12.10 | Validate no duplicate questions across the entire website | Clean |
| 6.12.11 | Validate acceptedAnswer is an Answer object | Accurate |
| 6.12.12 | Validate acceptedAnswer text exists | Present |
| 6.12.13 | Validate answer text matches on-page FAQ answer | High parity |
| 6.12.14 | Ensure answer is factually correct and relevant | Accurate |
| 6.12.15 | Validate answer avoids fluff or irrelevant filler content | Clean |
| 6.12.16 | Validate answers are written in AI-friendly structured paragraphs | Strong |
| 6.12.17 | Validate answers include semantic entities relevant to the topic | Present |
| 6.12.18 | Validate answers include contextual examples | Present |
| 6.12.19 | Validate answers include causes, impacts, solutions (if relevant) | Present |
| 6.12.20 | Validate FAQPage schema belongs only on FAQ-containing pages | Accurate |
| 6.12.21 | Validate FAQPage does not conflict with QAPage schema | Clean |
| 6.12.22 | Validate FAQ section title visibility (e.g., “FAQ”, “Frequently Asked Questions”) | Present |
| 6.12.23 | Validate FAQ section visually matches schema questions | Exact |
| 6.12.24 | Detect multilingual Question / Answer blocks | Present |
| 6.12.25 | Validate inLanguage field for multilingual FAQ entries | Accurate |
| 6.12.26 | Validate translations preserve meaning & intent | High parity |
| 6.12.27 | Validate FAQPage schema appears once per page | Correct |
| 6.12.28 | Validate FAQ section is accessible and expandable on UI | Functional |
| 6.12.29 | Validate FAQ markup passes Rich Results test | Pass |
| 6.12.30 | Compute partial FAQ score before aggregation | Complete |
| 6.12.31 | Validate FAQ items link to the correct service @id | Exact |
| 6.12.32 | Validate FAQ belongs to the correct service context (no cross‑service mixing) | Accurate |
| 6.12.33 | Validate FAQ references correct organization/provider | Accurate |
| 6.12.34 | Validate FAQ internally links to service pages where relevant | Present |
| 6.12.35 | Validate FAQ links do not conflict with canonical URLs | Clean |
| 6.12.36 | Detect duplicate questions across all service/location pages | None |
| 6.12.37 | Detect duplicate answers across website | None |
| 6.12.38 | Detect overlaps between FAQPage questions & blog Q/A blocks | Clean |
| 6.12.39 | Detect near-duplicate semantic questions | Clean |
| 6.12.40 | Detect near-duplicate answers with light wording changes | Clean |
| 6.12.41 | Validate FAQ questions include semantic triggers for AI retrieval | Strong |
| 6.12.42 | Validate answers include high-clarity context vectors (problem, cause, solution) | Present |
| 6.12.43 | Validate topic entities embedded within answers | Present |
| 6.12.44 | Validate readability for multimodal AI models | Strong |
| 6.12.45 | Validate expand/collapse works correctly | Functional |
| 6.12.46 | Validate FAQ mobile responsiveness | Fully responsive |
| 6.12.47 | Validate keyboard accessibility for FAQ toggles | Accessible |
| 6.12.48 | Validate ARIA labels for Question/Answer blocks | Present |
| 6.12.49 | Validate hreflang equivalents include FAQ where relevant | Present |
| 6.12.50 | Validate accurate translation of technical terms in FAQ content | Accurate |
| 6.12.51 | Validate Question/Answer pairs are aligned across languages | High parity |
| 6.12.52 | Validate FAQ questions match search intent patterns found in PAA | Strong |
| 6.12.53 | Validate answers provide direct responses suitable for PAA extraction | Clear |
| 6.12.54 | Validate FAQ includes long-tail queries related to service | Present |
| 6.12.55 | Validate FAQ includes symptom-based and how-to questions | Present |
| 6.12.56 | Validate JSON-LD FAQ structure loads without JS errors | Clean |
| 6.12.57 | Validate FAQ structured data appears once and not duplicated | Correct |
| 6.12.58 | Validate FAQ markup passes Google Rich Results test | Pass |
| 6.12.59 | Validate no hidden/invisible FAQ content is misleading | Clean |
| 6.12.60 | Compute partial FAQ score for Chunk 2 before full aggregation | Complete |
| 6.12.61 | Validate FAQ items do not conflict with other service FAQs | Clean |
| 6.12.62 | Validate FAQ content aligns with location-specific constraints | Accurate |
| 6.12.63 | Validate no FAQ contradicts pricing, availability, or policies | Consistent |
| 6.12.64 | Validate all FAQs match the business category and niche | Accurate |
| 6.12.65 | Validate no cross‑location duplicated FAQs for chain businesses | Clean |
| 6.12.66 | Validate inclusion of problem‑based questions | Present |
| 6.12.67 | Validate inclusion of process‑based questions | Present |
| 6.12.68 | Validate inclusion of cost‑based questions | Present |
| 6.12.69 | Validate inclusion of timeframe‑based questions | Present |
| 6.12.70 | Validate inclusion of troubleshooting questions | Present |
| 6.12.71 | Validate each answer includes core semantic entities for AI retrieval | Strong |
| 6.12.72 | Validate presence of actionable steps in answers (if relevant) | Present |
| 6.12.73 | Validate detection of “answerability” (directly answers the question) | High |
| 6.12.74 | Validate presence of supporting examples | Present |
| 6.12.75 | Validate entity disambiguation across multi-meaning questions | Clear |
| 6.12.76 | Validate FAQ loads without render-blocking scripts | Clean |
| 6.12.77 | Validate all FAQ icons/images/icons load (200 status) | OK |
| 6.12.78 | Validate FAQ toggles do not cause layout shifts (CLS stable) | Stable |
| 6.12.79 | Validate FAQ list ordering (grouped logically per service/theme) | Organized |
| 6.12.80 | Validate screen reader compatibility for question/answer pairs | Accessible |
| 6.12.81 | Validate proper heading hierarchy inside FAQ section | Correct |
| 6.12.82 | Validate tab order for FAQ interactions | Logical |
| 6.12.83 | Validate color contrast for FAQ text | Accessible |
| 6.12.84 | Validate multilingual FAQ pages use correct hreflang directory structure | Accurate |
| 6.12.85 | Validate multilingual FAQ answers are contextually consistent | High parity |
| 6.12.86 | Validate translated FAQPage schema references correct @ids | Accurate |
| 6.12.87 | Validate FAQ structured data passes all validators (Google + Schema.org) | Pass |
| 6.12.88 | Validate no conflicting FAQ schema blocks exist on page | Clean |
| 6.12.89 | Validate FAQ fully matches on-page visual content | Exact |
| 6.12.90 | Compute full FAQPage composite score for Section 6.12 | >= 90% |
← 6.11 Review / AggregateRating / Testimonial Schema Suite6.13 Breadcrumb / Navigation / Site Structure Schema Suite →
A Deep Audit scores every check here that applies to your page, then an AI pass of up to 150 checks. Included on Pro and Ultra, or $9 for one audit.
See plansMachine-readable: catalog totals and the full catalog as JSON (IDs, section, weight, status).