Start with evidence from crawling, indexing, page rendering, and mobile performance. A technically weak solar site can prevent useful service and project content from being discovered or used effectively.
Check mobile page performance and Core Web Vitals. Evidence required: PageSpeed Insights, Search Console reports, and representative mobile URLs. Pass when important templates have no unresolved critical performance issue and the main content is usable without unnecessary delay.
The source benchmark for LCP is 2.5 seconds. Severity: high when slow rendering affects core service, location, or lead pages. Owner: developer or technical SEO. Corrective action: reduce oversized media, unnecessary scripts, rendering bottlenecks, and layout instability. Validation: rerun the same URLs after deployment and compare field and lab evidence where available.
Check structured data against visible page content. Evidence required: the rendered page, deployed JSON-LD, and Schema.org definitions. Pass when markup describes the actual business, services, and visible facts without inventing service areas, certifications, reviews, or attributes.
Severity: medium unless invalid markup blocks another implementation dependency. Owner: developer or SEO. Corrective action: remove unsupported properties, repair syntax, and keep business details consistent with the page. Validation: retest the live URL and manually compare marked-up facts with visible content.
Check site architecture for services and genuine locations. Evidence required: crawl map, navigation, internal links, and the list of real locations or service areas. Pass when users and crawlers can reach important service content through a logical hierarchy and each dedicated location page represents a genuine location with useful location-specific information.
Severity: high for orphaned commercial pages, duplication, or inaccessible sections. Owner: SEO and content lead. Corrective action: simplify navigation, consolidate thin duplicates, and strengthen contextual internal links. Validation: recrawl and confirm the intended pages are reachable, indexable, and distinct.
Check HTTPS and form security. Evidence required: browser inspection, certificate status, mixed-content checks, and test submissions. Pass when important pages load securely and forms do not trigger browser security warnings.
Severity: critical for broken certificates or insecure lead forms. Owner: developer or hosting administrator. Corrective action: repair the certificate chain, redirects, mixed resources, and form endpoints. Validation: retest representative URLs and submission flows from a clean browser session.