The 2026 Solar SEO Checklist for Evidence-Based Installer Audits

Technical SEO should establish whether search engines and users can access the pages that matter. Audit evidence should come from crawls, indexation data, performance tests, browser checks, and analytics rather than from a single site-health score.

Crawl and Indexation Evidence required: crawl the public site, inspect Search Console coverage for priority URLs, review canonicals, redirects, robots directives, and sitemap entries. Pass condition: important service, market, project, and informational pages are crawlable and indexable when intended, without material canonical or redirect conflicts.

Severity: critical when priority pages are blocked or miscanonicalized. Owner: technical SEO or developer. Corrective action: repair blocking directives, redirect chains, canonical errors, broken internal links, or sitemap inconsistencies.

Validation: re-crawl affected templates and confirm the intended URLs can be requested, rendered, and indexed where appropriate.

Structured Business and Service Information Evidence required: compare visible business information and any structured data with the actual services and locations represented on the page. Pass condition: markup, when used, matches visible content and valid business facts.

Severity: medium unless incorrect markup materially misrepresents the business. Owner: technical SEO with content or operations review. Corrective action: remove unsupported properties and use documented schema vocabulary only where eligible. Validation: test the final markup and manually compare it with the visible page.

Mobile Performance and Usability Evidence required: representative PageSpeed Insights or Lighthouse tests, field data where available, mobile browser checks, and form testing. Pass condition: important pages are usable on mobile, key content appears without avoidable delay, and lead forms work reliably.

Severity: high when performance or interaction defects block evaluation or contact. Owner: developer. Corrective action: reduce unnecessary scripts, optimize media delivery, stabilize layout, and fix interaction failures. Validation: retest representative service, project, and lead pages after deployment.

HTTPS and Lead-Form Security Evidence required: certificate inspection, redirect behavior, mixed-content checks, and live form testing. Pass condition: public pages and form submissions use HTTPS without certificate or mixed-content errors.

Severity: critical when users encounter security warnings. Owner: developer or infrastructure owner. Corrective action: repair certificates, redirects, and insecure resource calls. Validation: test the canonical site and form flow from a clean browser session.

Service-Area URL Architecture Evidence required: crawl the hierarchy and compare location URLs with genuine markets and actual location-specific content. Preserve the existing example /locations/california/san-diego when reviewing the source architecture.

Pass condition: URLs are predictable, internally linked, and only represent markets for which the installer can provide useful distinct information. Severity: high when templated location proliferation creates duplication or misleading coverage.

Owner: SEO strategist and content owner. Corrective action: consolidate weak pages, improve genuine market pages, and redirect redundant URLs where appropriate. Validation: re-crawl the final hierarchy and confirm each retained location page has a defensible purpose.

Local SEO should reflect the installer's real-world operating structure. Audit the profile, website, directories, reviews, and location pages for factual consistency without treating any single activity as a guaranteed Map Pack lever.

Google Business Profile Accuracy Evidence required: inspect profile category, name, address or service-area configuration, phone, website, hours, services, and verification status. Pass condition: the profile is eligible, accurate, and consistent with the real business and website.

Severity: critical for false or ineligible location information; high for material factual conflicts. Owner: local SEO owner with operations approval. Corrective action: correct inaccurate details and remove unsupported location representations. Validation: compare the live profile with the source-of-truth business record.

Project Photos and Profile Updates Evidence required: inspect whether uploaded media is genuine, relevant, appropriately described, and useful to customers. Pass condition: media represents real work or the real business and does not contain misleading location or service claims.

Severity: medium. Owner: local marketing or content owner. Corrective action: replace misleading assets and establish an evidence-based media workflow. Validation: review live profile and website media for consistency. Do not treat a weekly posting cadence as an official ranking requirement.

Local Citations Evidence required: compare important directory listings with the business source-of-truth record and identify material Name, Address, Phone, website, or location conflicts. Pass condition: priority listings are accurate and do not represent fabricated locations.

Severity: high when customers encounter conflicting business information. Owner: local SEO or operations. Corrective action: correct material inconsistencies and remove or merge invalid listings where the platform permits. Validation: recheck priority listings after changes are processed.

Genuine Location Pages Evidence required: compare each market page with the actual service footprint and inspect whether the page contains useful information specific to that location. Pass condition: every retained page corresponds to a genuine market and adds distinct service, utility, permitting, project, or contact context where relevant.

Severity: high for mass-produced pages that only substitute place names. Owner: SEO strategist with operations and content review. Corrective action: improve, consolidate, redirect, or remove weak location pages according to their actual purpose. Validation: compare retained pages side by side and confirm each has a materially distinct reason to exist.

Solar content should help a buyer make a better decision, not merely expand keyword coverage. Every topic needs an identifiable audience, factual-review requirement, internal destination, and measurement plan.

Federal Incentive Content Evidence required: identify every page that discusses tax credits or incentive rules and record the source used for the current claim. Pass condition: the page explains the issue accurately for 2026, distinguishes general information from business-specific advice, and is scheduled for review when the underlying rule can change.

Tools referenced in the source include Ahrefs and IRS.gov. Severity: critical when outdated or unsupported financial claims could mislead a buyer. Owner: content owner with appropriate factual review.

Corrective action: reconcile claims with authoritative current material and remove unsupported certainty. Validation: compare the published wording with the current source and record the review date.

Solar ROI Calculator Evidence required: inspect methodology, assumptions, mobile behavior, loading, tracking, and explanatory text. Pass condition: assumptions are visible enough for a user to understand the output, the tool functions on representative devices, and tracking records completion reliably.

Severity: high when the tool is broken or presents unsupported savings as certain. Owner: developer with content and analytics review. Corrective action: repair functionality, disclose assumptions, and separate estimates from guarantees. Validation: run test cases through the live tool and confirm expected analytics events.

Battery and Equipment Comparisons Evidence required: identify manufacturer or technical material supporting specifications and verify that the comparison matches the installer's real offering. Pass condition: products are compared on relevant documented attributes without unsupported superiority claims.

Severity: medium to high depending on the claim. Owner: technical content reviewer. Corrective action: update specifications, clarify compatibility limits, and remove unsupported statements. Validation: compare the final page with retained source material.

Residential and Commercial Case Studies Evidence required: project records, approved images, system scope, constraints, and any measured or modeled outcome used in the page. Pass condition: the case study can be traced to real work and clearly distinguishes measured results from modeled estimates.

Severity: high for unsupported production, savings, or performance claims. Owner: content owner with project or operations review. Corrective action: reconcile the page with project records and remove claims that cannot be substantiated. Validation: complete a final evidence check before publication and review time-sensitive context when necessary.

Trust evidence should help readers understand who is responsible for the work and why the information is credible. It should not be converted into a checklist of supposed ranking factors.

Certifications and Credentials Evidence required: current credential records and permission to display them. Pass condition: certifications shown on the site are real, current, relevant, and attributed accurately to the individual or business that holds them.

Severity: critical for false credentials. Owner: operations or compliance owner with web-content support. Corrective action: correct, qualify, or remove unsupported credential claims. Validation: compare the live page with the source record.

Technical Author and Reviewer Information Evidence required: identify who wrote or reviewed technical, incentive, financing, equipment, and policy-sensitive content. Pass condition: responsibility is clear where specialist review materially improves reader trust, and biographies do not invent expertise or credentials.

Severity: high for sensitive content with unsupported authority claims. Owner: editorial lead. Corrective action: add accurate reviewer information or revise claims to match available expertise. Validation: verify biographies and role descriptions against internal records.

Third-Party Reviews Evidence required: inspect how reviews are requested, displayed, attributed, and updated. Pass condition: eligible customers are asked consistently for honest feedback without incentives, review gating, discouraging negative reviews, or selectively requesting only positive feedback.

Severity: high for manipulative review practices or misleading review presentation. Owner: customer experience or local marketing owner. Corrective action: standardize compliant review requests and correct misleading embeds or excerpts. Validation: audit the request workflow and sample displayed reviews against the originating platform.

Improve one priority solar service or market title so it clearly describes the page's real purpose - high - 1 hour

Test the primary mobile call and form path from landing page to successful submission - very high - 30 min

Verify one important secondary local business listing against the source-of-truth business record - medium - 45 min

• Leaving policy or utility content unchanged after a material rule update, including references such as NEM 3.0 that require current source verification.
• Using stock photography instead of real photos of local installation crews and completed projects when first-party evidence is available.
• Failing to separate commercial solar intent when its decision process, service scope, evidence, and conversion path materially differ from residential solar.
• Fixing visible content while leaving crawl, indexation, internal-linking, mobile, tracking, or conversion defects unresolved.