90 checks in Schema, Local, Trust, Deep Audit. Automated Its subsection has a live automated checker in the engine.
| ID | Check | Passes when |
|---|---|---|
| 6.16.01 | Detect Service schema | Present |
| 6.16.02 | Validate @type = Service | Accurate |
| 6.16.03 | Validate service name present and matches page H1 | Exact |
| 6.16.04 | Validate service description present and matches on‑page content | High parity |
| 6.16.05 | Validate service @id unique and stable | Unique |
| 6.16.06 | Validate provider property links to LocalBusiness @id | Present |
| 6.16.07 | Validate LocalBusiness name matches provider name | Exact |
| 6.16.08 | Validate provider URL matches LocalBusiness URL | Exact |
| 6.16.09 | Validate no conflicting providers across service schemas | Clean |
| 6.16.10 | Validate consistent provider across multilingual versions | High parity |
| 6.16.11 | Validate serviceCategory present | Present |
| 6.16.12 | Validate category taxonomy correct (industry‑recognized) | Accurate |
| 6.16.13 | Validate subcategory relationships (Service → Category → ParentCategory) | Correct |
| 6.16.14 | Validate no category conflicts among services | Clean |
| 6.16.15 | Validate category labels match navigation/breadcrumb structure | Accurate |
| 6.16.16 | Validate main ServicePage exists for each Service schema | Present |
| 6.16.17 | Validate H1 matches service name | Exact |
| 6.16.18 | Validate meta title/description reference same service | Accurate |
| 6.16.19 | Validate hero section aligns with service description | High parity |
| 6.16.20 | Validate CTA aligns with service intent (e.g., “Book inspection”) | Correct |
| 6.16.21 | Validate AreaServed property | Present |
| 6.16.22 | Validate cities/regions listed match actual coverage | Accurate |
| 6.16.23 | Validate AreaServed naming format (City, Region, Country) | Standard |
| 6.16.24 | Validate no duplicate or overlapping areas | Clean |
| 6.16.25 | Validate image array exists | Present |
| 6.16.26 | Validate image resolution ≥ 800px | Pass |
| 6.16.27 | Validate image URLs return 200 status | OK |
| 6.16.28 | Validate images match actual service content (no stock mismatch) | Accurate |
| 6.16.29 | Validate Service schema passes Rich Results test | Pass |
| 6.16.30 | Compute partial service score for Chunk 1 | Complete |
| 6.16.31 | Detect Offer object inside Service schema (if pricing exists) | Present |
| 6.16.32 | Validate pricing transparency (fixed, hourly, quote-only) | Accurate |
| 6.16.33 | Validate priceCurrency is correct ISO format | Accurate |
| 6.16.34 | Validate priceRange property (if no fixed price) | Present |
| 6.16.35 | Validate Offer → url matches ServicePage booking/CTA link | Exact |
| 6.16.36 | Validate serviceFeature array present (if applicable) | Present |
| 6.16.37 | Validate features match on‑page service bullets | High parity |
| 6.16.38 | Validate use of descriptive, semantic feature labels | Strong |
| 6.16.39 | Validate no duplicate feature bullets | Clean |
| 6.16.40 | Validate feature bullets reflect actual service scope | Accurate |
| 6.16.41 | Validate service description includes main semantic entities | Strong |
| 6.16.42 | Validate formatting supports AI retrieval (clear segments) | Strong |
| 6.16.43 | Validate service includes problem → solution → outcome pattern | Present |
| 6.16.44 | Validate sentiment-rich phrasing appropriate for AI | Present |
| 6.16.45 | Validate entity disambiguation for multi-meaning service names | Clear |
| 6.16.46 | Validate ServicePage appears in service navigation/category | Present |
| 6.16.47 | Validate ServicePage internally links to related services | Present |
| 6.16.48 | Validate breadcrumb consistency with service hierarchy | Exact |
| 6.16.49 | Validate logical navigation path from ServicePage to homepage (<3 clicks) | True |
| 6.16.50 | Validate cross-service linking avoids keyword cannibalization | Clean |
| 6.16.51 | Validate Service schema exists for each language variant | Present |
| 6.16.52 | Validate service names consistent across languages | High parity |
| 6.16.53 | Validate service descriptions are correctly translated | High parity |
| 6.16.54 | Validate AreaServed translations match correct regions | Accurate |
| 6.16.55 | Validate image URLs remain language‑agnostic | Consistent |
| 6.16.56 | Validate inclusion of supporting service images/videos | Present |
| 6.16.57 | Validate video objects follow proper schema rules | Accurate |
| 6.16.58 | Validate video thumbnails meet resolution requirements | High quality |
| 6.16.59 | Validate alt text for all service images | Present |
| 6.16.60 | Compute partial service score for Chunk 2 | Complete |
| 6.16.61 | Validate clear content structure (intro → benefits → process → CTA) | Strong |
| 6.16.62 | Validate service benefits clearly listed | Present |
| 6.16.63 | Validate step-by-step service process (if applicable) | Present |
| 6.16.64 | Validate FAQs present and semantically relevant | Present |
| 6.16.65 | Validate testimonials linked or embedded | Present |
| 6.16.66 | Validate trust signals present (licenses, certifications, insurance) | Present |
| 6.16.67 | Validate experience / expertise statements | Clear |
| 6.16.68 | Validate before/after visuals (if applicable) | Present |
| 6.16.69 | Validate service guarantees/assurances stated | Present |
| 6.16.70 | Validate no duplicated service descriptions across services | Clean |
| 6.16.71 | Validate service uniqueness in entire domain | Unique |
| 6.16.72 | Detect service keyword cannibalization risk | None |
| 6.16.73 | Validate no duplicated schema across multi-location service pages | Clean |
| 6.16.74 | Validate service variations correctly separated (e.g., “Repair” vs “Replacement”) | Accurate |
| 6.16.75 | Validate Service schema loads properly in initial DOM | Present |
| 6.16.76 | Validate minimal CLS on service hero section | Pass |
| 6.16.77 | Validate service page LCP < 2.5s | Pass |
| 6.16.78 | Validate all service images optimized (WebP/AVIF) | Optimized |
| 6.16.79 | Validate no unused JS or CSS bloating service pages | Clean |
| 6.16.80 | Validate ServicePage translations align with schema content | High parity |
| 6.16.81 | Validate hreflang references correct ServicePage variants | Accurate |
| 6.16.82 | Validate cross-language navigation consistent | Smooth |
| 6.16.83 | Validate no mismatched service names across languages | Consistent |
| 6.16.84 | Validate consistent @id references across all service entities | Exact |
| 6.16.85 | Validate ServicePage → Organization → LocalBusiness → Service graph | Complete |
| 6.16.86 | Validate ServicePage included in sitemap.xml | Present |
| 6.16.87 | Validate ServicePage receives internal links from relevant pages | Present |
| 6.16.88 | Validate external links (if any) relevant and high‑quality | Strong |
| 6.16.89 | Validate entire Service schema passes all validators | Pass |
| 6.16.90 | Compute full service composite score for Section 6.16 | >= 90% |
← 6.15 Organization / LocalBusiness / Brand Schema Suite6.17 Review / Testimonial / AggregateRating 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).