Use these checks first because brand, service, local, and conversion work cannot be evaluated reliably when important pages are difficult to crawl, duplicate, insecure, or slow.
Build a vehicle-specific page architecture around genuine services
Evidence required: A crawl export, sitemap, canonical map, navigation review, and service inventory showing how Audi, VW, Mercedes-Benz, and other supported marques connect to model-specific services.
Pass/fail condition: Pass when each important topic has one clear primary URL, pages are reachable through useful navigation, and a structure such as /services/brand/model-specific-service is used consistently where it fits the site's architecture.
Fail when dynamic parameters, duplicate slugs, orphan pages, or thin model variants compete for the same intent. Severity: High. Owner: SEO lead and developer. Corrective action: Consolidate duplicate pages, choose the preferred URL for each topic, update internal links and canonicals, and redirect obsolete versions where appropriate.
Validation step: Re-crawl with Screaming Frog, compare the old and new URL inventories, and confirm that sitemap, canonicals, redirects, and navigation agree. WordPress or another CMS is an implementation layer, not evidence of correctness.
Measure mobile Core Web Vitals and LCP against the real template
Evidence required: PageSpeed Insights, field data where available, Search Console reports, and manual mobile tests for representative brand, service, gallery, and contact pages.
Pass/fail condition: Pass when important pages remain usable and any LCP target under 2.5s is evaluated as a performance objective within the site's own measurement context. Fail when oversized media, blocking scripts, layout instability, or slow forms prevent customers from reaching service information.
Severity: Critical. Owner: Developer or performance owner. Corrective action: Resize and compress media, reduce blocking resources, stabilize layout, cache appropriately, and remove unnecessary scripts from service templates.
Validation step: Retest the same URLs after deployment with Google PageSpeed Insights and a real mobile device. WP Rocket may assist implementation, but a single laboratory score should not be the only sign-off condition.
Keep LocalBusiness and AutoRepair structured data accurate
Evidence required: The rendered JSON-LD, visible page content, current business details, opening hours, service scope, and any published price range.
Pass/fail condition: Pass when LocalBusiness and AutoRepair properties describe the real workshop and match visible information. Fail when markup invents brands, prices, credentials, services, or relationships, or when it is added primarily to promise Rich Snippets.
Severity: High. Owner: SEO or development owner with business approval. Corrective action: Remove unsupported properties, align contact and service data with the page, and use only schema types that fit the entity being described.
Validation step: Compare the markup with the live page, then check syntax or eligibility using TechnicalSEO Schema Generator output as a drafting aid and Google Rich Results Test where applicable. Valid structured data does not guarantee a rich result or ranking benefit.
Audit mobile-first crawl and rendering behavior
Evidence required: Google Search Console indexing reports, rendered page inspection, mobile navigation tests, robots directives, and a crawl of important service and contact URLs.
Pass/fail condition: Pass when the mobile version exposes the same essential service information, links, structured data, and contact actions that users and search engines need. Fail when content is hidden, blocked, truncated, or functionally unavailable on mobile.
Severity: Critical. Owner: Developer and SEO lead. Corrective action: Repair blocked resources, mobile-only navigation problems, hidden content, inaccessible forms, and template differences that affect discovery or use.
Validation step: Inspect representative URLs in Google Search Console, compare rendered mobile and desktop content, and manually complete the service inquiry path on a phone.