90 checks in Schema, Local, Trust, Deep Audit. Automated Its subsection has a live automated checker in the engine.
| ID | Check | Passes when |
|---|---|---|
| 6.2.01 | Detect Service or Product schema | Present |
| 6.2.02 | Validate correct top-level type (Service, Product, ProfessionalService, etc.) | Accurate |
| 6.2.03 | Validate each service has unique @id | Unique |
| 6.2.04 | Validate service schema in JSON-LD | Correct |
| 6.2.05 | Validate no mixed schema formats | Clean |
| 6.2.06 | Detect duplicate service schemas for same entity | None |
| 6.2.07 | Validate service name matches page H1 | Exact |
| 6.2.08 | Validate service description meaningful and complete | Clear |
| 6.2.09 | Validate description uses natural language (AI-friendly) | Yes |
| 6.2.10 | Validate description aligns with entity content | Accurate |
| 6.2.11 | Validate description includes deliverables | Present |
| 6.2.12 | Validate description includes target audience | Present |
| 6.2.13 | Validate description includes location/service area | Accurate |
| 6.2.14 | Detect Offer schema | Present |
| 6.2.15 | Validate price or priceRange format | Valid |
| 6.2.16 | Validate priceCurrency present | Yes |
| 6.2.17 | Validate availability (InStock, Available, InStoreOnly) | Correct |
| 6.2.18 | Validate validThrough if present | Correct |
| 6.2.19 | Validate itemCondition if relevant | Correct |
| 6.2.20 | Validate Offer URL matches canonical page | Correct |
| 6.2.21 | Validate serviceArea property present for SAB businesses | Present |
| 6.2.22 | Validate serviceArea entities structured (GeoCircle, GeoShape) | Accurate |
| 6.2.23 | Validate areaServed consistency with service pages | Consistent |
| 6.2.24 | Validate targetAudience (BusinessAudience, Consumer) | Accurate |
| 6.2.25 | Validate audience geographic attributes if used | Correct |
| 6.2.26 | Validate serviceCategory | Present |
| 6.2.27 | Validate serviceType | Present |
| 6.2.28 | Validate serviceClassification (industry codes, NAICS) | Accurate |
| 6.2.29 | Validate category matches page/main service topic | Consistent |
| 6.2.30 | Validate keywords included in schema when appropriate | Present |
| 6.2.31 | Validate provider is linked to Organization schema | Linked |
| 6.2.32 | Validate provider @id matches entity @id | Consistent |
| 6.2.33 | Validate provider details consistent (name, URL, phone) | Accurate |
| 6.2.34 | Validate hasOfferCatalog for multi-service companies | Present |
| 6.2.35 | Validate each OfferCatalogItem name | Accurate |
| 6.2.36 | Validate CategoryHierarchy (hub → spoke → subspoke) | Correct |
| 6.2.37 | Validate Product schema completeness (for product-type pages) | Full |
| 6.2.38 | Validate SKU if applicable | Present |
| 6.2.39 | Validate MPN if applicable | Present |
| 6.2.40 | Validate brand property | Accurate |
| 6.2.41 | Validate product identifiers (UPC/EAN) | Correct |
| 6.2.42 | Validate product category | Correct |
| 6.2.43 | Validate image URLs present in schema | Present |
| 6.2.44 | Validate images accessible (HTTP 200) | OK |
| 6.2.45 | Validate image captions/descriptions | Present |
| 6.2.46 | Validate video content via VideoObject if present | Correct |
| 6.2.47 | Validate video thumbnail accessibility | OK |
| 6.2.48 | Validate multiple images allowed when appropriate | Yes |
| 6.2.49 | Validate sameAs for service-specific references | Present |
| 6.2.50 | Validate isSimilarTo for related services | Logical |
| 6.2.51 | Validate serviceOutput property | Provided |
| 6.2.52 | Validate serviceOperator property | Present |
| 6.2.53 | Validate estimatedCost property | Accurate |
| 6.2.54 | Validate timeRequired | Present |
| 6.2.55 | Validate termsOfService URL | Correct |
| 6.2.56 | Validate serviceWarranty if offered | Correct |
| 6.2.57 | Validate applicableLocation | Accurate |
| 6.2.58 | Validate availableChannel (web, phone, in-person) | Correct |
| 6.2.59 | Validate hasOfferCatalog completeness | Full |
| 6.2.60 | Validate OfferCatalogItem schema correctness | Valid |
| 6.2.61 | Validate hierarchical service grouping (hub → spoke → subspoke) | Logical and consistent |
| 6.2.62 | Validate no redundant or duplicated service definitions across pages | Clean |
| 6.2.63 | Validate cluster coherence using isRelatedTo | Strong semantic relationships |
| 6.2.64 | Validate inclusion of audience, intent, and value propositions inside schema | Rich, descriptive |
| 6.2.65 | Validate machine-readable bullet points included as arrays for features | Present |
| 6.2.66 | Validate semantic anchors (entities, attributes, modalities) are embedded for AI systems | Present |
| 6.2.67 | Validate lateral linking to external authoritative entities | Present |
| 6.2.68 | Validate explicit definitions of outputs/outcomes for each service | Present |
| 6.2.69 | Validate inputRequirements property | Present |
| 6.2.70 | Validate AI agents can extract structured feature lists from JSON-LD | High extraction parity |
| 6.2.71 | Detect service schema duplicated across multiple unrelated pages | None |
| 6.2.72 | Validate service schema is unique for the service page URL | Unique |
| 6.2.73 | Validate canonical URL alignment with service schema | Perfect match |
| 6.2.74 | Detect mismatches between service schema and actual page content | None |
| 6.2.75 | Validate removal of outdated service schema versions or leftovers | Removed |
| 6.2.76 | Detect competing schemas describing the same offering | None |
| 6.2.77 | Validate schema passes Google Rich Results Test | Passed |
| 6.2.78 | Validate schema passes Schema.org validator with zero errors | Passed |
| 6.2.79 | Validate schema fields completeness >= 95% | Superior completeness |
| 6.2.80 | Validate structured data accurately represents real-world offering | Accurate |
| 6.2.81 | Validate no contradictory pricing or availability values across schema and page | Consistent |
| 6.2.82 | Validate no internal JSON-LD parsing errors during rendering | Clean |
| 6.2.83 | Validate schema version consistency across all service pages | Consistent |
| 6.2.84 | Validate image/video attachments properly typed | Correct |
| 6.2.85 | Validate schema is not duplicated across template-based pages (WordPress/React templates) | Unique |
| 6.2.86 | Validate schema load order does not conflict with JS hydration or rendering | Stable |
| 6.2.87 | Validate JSON-LD presence in rendered DOM (post-JS) | Present |
| 6.2.88 | Validate fallback schema remains available if JS fails | Present |
| 6.2.89 | Compute service/product schema completeness score | >= 90% |
| 6.2.90 | Compute full Service/Product/Offering composite score | >= 90% |
← 6.1 Organization / LocalBusiness / NAP Schema Suite6.3 Article / BlogPosting / CreativeWork 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).