The 2026 Auto Glass SEO Checklist for Evidence-Backed Local Readiness

Technical review should focus on whether a driver can load the page, understand the service, and complete the intended contact action without a technical defect changing the meaning of the experience.

A previously published internal observation associated poor mobile experiences with a 40-60% bounce rate for roadside searches. Keep that figure as historical context that requires source reconciliation; do not use it as proof that one defect caused one outcome. Apply the controls below to the live site and retain the evidence used to pass them.

Mobile rendering and contact completion Evidence required: live-device captures of representative windshield and glass service pages, a completed phone-link test, a completed quote-form submission using controlled test data, and current mobile diagnostics from Google Search Console or PageSpeed Insights.

Pass or fail condition: Pass when navigation, service information, the phone action, and the quote action remain visible and usable, and each action reaches the intended destination without blocked controls, hidden required fields, or incorrect routing.

Fail when a representative mobile journey cannot reach the expected contact step or when interface behavior materially hides the information needed to make that decision. Severity: Critical. Owner: Web developer with the marketing owner.

Corrective action: repair responsive layout, phone links, form validation, interactive controls, and any script, banner, or consent layer that blocks or misroutes the primary action. Keep the correction limited to the observed failure rather than adding unrelated conversion features.

Validation step: repeat the same live-device journey from page load through the completed contact action, then archive the page, device, result, and review date so another reviewer can reproduce the check.

Business structured data accuracy Evidence required: the rendered JSON-LD, the business information visible to users, the shop's verified name, address or service-area configuration, phone, hours, location type, and substantiated service details, plus a current validation result from Schema.org or Validator.schema.org.

Pass or fail condition: Pass when the markup validates for the properties used and each declared business fact matches both the visible page and the real operation. Fail when the markup invents or duplicates a location, service area, service, review statement, or business detail, or when a declared fact conflicts with what users can see.

Severity: High. Owner: SEO lead and web developer. Corrective action: remove unsupported properties, keep only relevant supported types and properties, and align the markup with visible, verified business information.

Treat structured data as a machine-readable representation of content, not as a guaranteed ranking factor and not as special markup for Google AI Overviews or other Google AI features. Validation step: inspect the rendered source after publication, rerun the validator, and compare each retained property with the live page and the verified operating record.

Core Web Vitals and layout stability around key actions Evidence required: current field data when available, diagnostic traces for representative service pages, and a screen recording that shows loading behavior around the phone, quote, navigation, and service-detail areas.

Pass or fail condition: Pass when there is no unresolved poor field status or repeatable loading behavior that materially prevents reading, navigation, or contact completion. Fail when layout movement, delayed interaction, blocking resources, or heavy media repeatedly disrupts the task on a representative test.

Severity: High. Owner: Performance developer. Corrective action: address the reproducible cause by reserving space for media and interface elements, reducing unnecessary blocking work, compressing required assets, and removing nonessential scripts from the service journey when they create the observed disruption.

Validation step: rerun the same representative pages under comparable test conditions and confirm that the specific failure recorded in the evidence can no longer be reproduced.

HTTPS and form-submission security Evidence required: a current certificate check, a crawl or browser review for insecure resources, redirect verification, and a documented controlled submission through any form that collects a vehicle identification number, insurance information, or customer contact details.

Pass or fail condition: Pass when public pages, required assets, redirects, and form submissions remain on a valid secure connection and no mixed-content or insecure submission endpoint is observed. Fail when any part of the tested customer path drops to an insecure connection or posts sensitive information to an insecure endpoint.

Severity: Critical. Owner: Hosting administrator and web developer. Corrective action: renew or replace invalid certificate coverage, correct redirect chains and asset references, and secure each affected submission endpoint while preserving the intended customer workflow.

Validation step: confirm the live certificate path, repeat the mixed-content review, and submit a controlled test record through the published form to verify that the corrected path remains secure end to end.

Local-search review should match the business a driver can actually visit, contact, or receive mobile service from. Google Business Profile completeness, categories, reviews, profile updates, and location content can improve clarity and customer usability, but this checklist does not treat posting cadence, map embeds, review-response rates, or profile activity as guaranteed or officially documented ranking factors unless the business has separate supporting documentation.

Google Business Profile identity and category accuracy Evidence required: a current capture or export of the profile showing the verified business name, primary category, secondary categories, phone, hours, website, address or service-area setup, and published services, plus the operating records used to verify those fields.

Pass or fail condition: Pass when the profile name reflects the real business name, the primary category describes the core operation, Auto Glass Shop is selected when available and appropriate, secondary categories correspond to services actually provided, and the phone, hours, website, location setup, and service list match current operations.

Fail when a field is inaccurate, keyword text is added to the business name without real-world support, or a category or service exists only to target search terms. Severity: Critical. Owner: Location manager and local SEO owner.

Corrective action: reconcile each profile field with the real operation, remove unsupported name additions, categories, or services, and document the business reason for each retained category and location setting.

Validation step: compare the published profile with the website, business records or signage where applicable, current service menu, operating hours, and a live call-routing test.

Mobile service coverage and dispatch consistency Evidence required: the current dispatch coverage list, travel limits, excluded areas, mobile-service conditions, and the corresponding service areas shown on the profile and website.

Pass or fail condition: Pass when every published city, postal area, or service zone is regularly served under the stated conditions and no service area is presented as a staffed customer-facing location unless it truly is one.

Fail when the website or profile claims coverage that dispatch does not support or implies a physical presence that does not exist. Severity: High. Owner: Dispatch manager and local SEO owner. Corrective action: align public coverage with current dispatch practice, remove unsupported areas, and explain relevant mobile availability, travel conditions, or limitations in language a driver can understand before contacting the shop.

Validation step: sample published coverage statements against current dispatch records and confirm through staff review that the same eligibility answer would be given to a caller.

Consistent and honest review requests Evidence required: the review-request message, the documented eligibility rule, the event that triggers the request, opt-out handling, staff instructions, and a recent sample showing how eligible customers were selected.

Pass or fail condition: Pass when all eligible customers are asked consistently for honest feedback without incentives, review gating, discouraging negative feedback, or selecting only customers expected to leave a favorable review.

Fail when staff or software filters recipients by sentiment, offers a benefit for a review, or diverts criticism away from the same public feedback option offered to others. Severity: High. Owner: Customer operations manager.

Corrective action: replace selective or incentivized review flows with neutral language sent after the documented service-completion event, apply the same eligibility rule consistently, and train staff not to screen customers by expected sentiment.

Validation step: inspect a recent request sample, compare recipients with the documented eligibility rule, and confirm that the wording, trigger, opt-out handling, and destination match the approved process.

Genuine location pages and useful service-area pages Evidence required: for a location page, proof of a genuine staffed customer-facing location and the public details tied to it; for a service-area page, a content brief containing useful verified local coverage information, contact routing, access or dispatch details, service limitations, and operational context specific to that area.

Pass or fail condition: Pass when a dedicated location page represents a genuine location or when a service-area page provides substantial accurate information that helps a driver determine availability in that area.

Fail when a page exists mainly because a place name was swapped into duplicated copy, when a map or address implies a location that is not real, or when nominal markets repeat the same information without location-specific value.

Severity: High. Owner: Content lead and location operations manager. Corrective action: consolidate thin or duplicative pages, rewrite retained pages from verified local evidence, and keep dedicated pages only where the business can substantively describe a real location or useful area-specific service conditions.

Validation step: compare the live page with operating records, contact routing, and another market page to confirm that the retained information is accurate, materially distinct, and useful to a driver deciding whether to contact the business.

Service content should answer the questions that determine a driver's next step while staying inside the services, procedures, limitations, and customer process the operator can prove. Passing a content control requires operational evidence, not merely polished copy or broad industry language.

ADAS calibration capability and handoff Evidence required: the current calibration service menu, equipment and procedure documentation used by the operation, service-manager or technician review, supported job or vehicle conditions, and the documented handoff when calibration is not performed by the shop.

Pass or fail condition: Pass when the page accurately explains which calibration services the operator performs, who performs them, the prerequisites or limitations that affect the job, and what happens when the work must be referred elsewhere.

Fail when the page implies a universal process for every vehicle, claims equipment or capability the operator cannot substantiate, or promises a safety, search, or service outcome that exceeds the documented process.

Severity: Critical. Owner: ADAS service lead and content editor. Corrective action: replace generic calibration claims with reviewed operating details, state material limitations, clarify referral or partner handoffs when relevant, and remove any claim that the service lead cannot verify.

Validation step: have the service lead compare the live page with the current workflow and retain a dated approval showing that the published description still matches the service delivered.

OEM and aftermarket glass decision content Evidence required: the shop's current sourcing options, supplier terminology used by the operation, customer decision factors discussed by staff, applicable warranty terms, and technical review of safety, fit, compatibility, or feature statements.

Pass or fail condition: Pass when the comparison explains the choices the shop can actually source, the relevant tradeoffs and questions a customer should ask, and any availability limitations without presenting one option as universally superior.

Fail when it relies on unsupported performance claims, unexplained authority language, or product terminology that staff cannot substantiate. Severity: High. Owner: Procurement or service manager with the content editor.

Corrective action: rewrite the comparison around verifiable sourcing choices, documentation, availability, warranty terms, and customer questions, then remove unsupported safety, quality, or performance claims.

Validation step: compare the published explanation with current supplier and service information and confirm that customer-facing staff can give a consistent explanation without contradicting the page.

Insurance assistance process and decision ownership Evidence required: the actual intake workflow, information requested from customers, insurer communication steps, billing responsibility, exclusions, escalation rules, and approved language for uncertainty about coverage or payment.

Pass or fail condition: Pass when the page explains what the shop can assist with, what information the customer may need to provide, and which decisions remain dependent on the applicable policy, insurer process, and customer responsibility.

Fail when the page promises coverage, approval, reimbursement, payment, waiver, or a guaranteed claim outcome. Severity: Critical. Owner: Insurance coordinator and content owner. Corrective action: replace outcome language with a step-by-step explanation of the shop's assistance role, required information, decision points, limits, and customer responsibilities.

Validation step: walk the live page through a current representative intake scenario and confirm with the responsible staff member that every published step and limitation matches present practice.

Distinct pages for materially different glass services Evidence required: a current service inventory covering windshield repair, full replacement, back glass, side windows, sunroofs, mobile service, and any other published offering, together with the eligibility, limitations, and correct phone or quote path for each retained page.

Pass or fail condition: Pass when each page serves a distinct customer decision, accurately explains eligibility and limits, includes useful process detail, and leads to the correct next action. Fail when materially different services are merged into vague copy that prevents a driver from identifying the right service, or when separate pages repeat nearly identical language without service-specific value.

Severity: High. Owner: Service manager and content lead. Corrective action: separate services that require meaningfully different decisions, consolidate pages that do not justify separate coverage, and rewrite retained pages from verified service information rather than keyword variations.

Validation step: map every retained page to the current service inventory and ask responsible staff to confirm that the page can be used to answer a real inquiry without adding material facts that the page omits or misstating what the shop provides.

Sticky mobile contact control Evidence required: a live mobile service page showing the contact control, a completed call or quote-action test, and a visual check confirming that the control does not cover required service information, navigation, form fields, or consent choices.

Pass or fail condition: Pass when the control remains usable on representative pages, sends the user to the correct phone number or quote step, and does not obstruct the content needed to decide whether to contact the shop.

Fail when it covers required information, breaks navigation, or routes to an incorrect destination. Severity: High. Estimated effort: 1 hour. Owner: Web developer. Corrective action: add or repair a restrained mobile contact control that supports the existing customer journey without hiding content or creating a competing action.

Validation step: test the published control across representative mobile service pages, complete the intended action, and save the result.

Current real-business image set Evidence required: a reviewed inventory containing 10+ current and accurate images of the shop, mobile units, technicians where permitted, work environment, or service process, together with source records that confirm what each image depicts.

Pass or fail condition: Pass when the selected images are authentic, current, relevant to the business, and do not imply a location, service, staff member, vehicle, or capability that the operator cannot verify.

Fail when the set depends mainly on stock imagery, outdated branding, or photographs that misrepresent the present operation. Severity: Medium. Estimated effort: 2 hours. Owner: Location manager and marketing owner.

Corrective action: capture or select accurate real-business imagery, obtain the required internal approval, and publish it with clear context where useful without making unverified service or location claims.

Validation step: compare each published image with the current business and its source record, and remove any image the responsible team cannot verify.

Relevant directory record accuracy Evidence required: the live directory record, ownership or verification status where available, business details, destination URL, and confirmation that the directory or organization is genuinely relevant to the shop.

Pass or fail condition: Pass when the record is legitimate, accurate, consistent with the website and business profile, and verified where the directory supports a relevant verification process. Fail when the record is duplicated, materially inaccurate, irrelevant to the business, or created only to manufacture the appearance of authority.

Severity: Medium. Estimated effort: 3 hours. Owner: Local SEO owner. Corrective action: claim or correct legitimate records when appropriate, request removal or consolidation of duplicate submissions where possible, and document discrepancies that cannot be directly changed.

Validation step: open the public record after correction, compare the visible business details with the verified operating information, and retain the review date and any unresolved exception.

• Repair and replacement intent is unclear. Evidence required: the current service inventory, the live landing pages, eligibility language, and the contact paths used for windshield repair and replacement. Pass or fail condition: Pass when a driver can distinguish repair from replacement, understand the relevant next step, or use an intentionally consolidated page with clearly separated service sections; fail when the page blurs the services or routes both intents through vague copy. Severity: High. Owner: Service manager and content lead. Corrective action: separate or restructure the content around verified eligibility, process, limitations, and contact steps. Validation step: test the live experience against representative repair and replacement inquiries and confirm that each inquiry reaches an accurate next step.
• Public customer questions contain outdated or unsupported answers. Evidence required: the current Google Business Profile questions and answers, profile access, and approved operating information for services, hours, insurance assistance, mobile coverage, and calibration. Pass or fail condition: Pass when material questions have accurate current answers and unsupported public answers are reported, corrected, or otherwise addressed where the platform allows; fail when incorrect information that could change a driver's decision remains unaddressed. Severity: Medium. Owner: Location manager. Corrective action: respond from verified operating information and correct material inaccuracies without treating question activity or response frequency as a guaranteed ranking factor. Validation step: review the public profile after the corrective work and reconcile each material answer with the website and staff process.
• ADAS capability is implied without substantiation. Evidence required: the live calibration statements, the current workflow, equipment or partner documentation, applicable limitations, and service-lead approval. Pass or fail condition: Pass when every calibration claim is supported by the real operation and limitations or referral conditions are visible; fail when generic ADAS wording implies equipment, procedures, in-house work, or safety outcomes that cannot be verified. Severity: Critical. Owner: ADAS service lead. Corrective action: remove unsupported claims and publish the actual workflow, prerequisites, limitations, and handoff. Validation step: obtain a dated service-lead review of the live page and compare it with the current service process.
• Generic imagery substitutes for verifiable business evidence. Evidence required: the image source record and confirmation of the depicted location, mobile unit, technician where applicable, vehicle, work environment, or process. Pass or fail condition: Pass when imagery is authentic or clearly illustrative and cannot reasonably misrepresent the operator; fail when stock or outdated images imply facilities, staff, equipment, locations, or work the business cannot verify. Severity: Medium. Owner: Marketing owner. Corrective action: replace misleading imagery with approved real-business evidence or clearly contextualized illustrative media. A previously published internal observation cited a 20-30% conversion-rate difference, but that figure requires source reconciliation and should not be presented as causal proof. Validation step: audit each live image against its source record and the current operation.
• Insurance assistance is written as though the outcome is controlled by the shop. Evidence required: current intake scripts, billing steps, policy disclaimers, escalation rules, and the published insurance content. Pass or fail condition: Pass when the page distinguishes the shop's assistance from insurer decisions and customer responsibility; fail when it promises coverage, approval, payment, reimbursement, or waiver. Severity: Critical. Owner: Insurance coordinator. Corrective action: rewrite the content around verified assistance steps, required information, decision ownership, limits, and customer responsibilities. Validation step: compare the live copy with a current intake scenario and the explanation staff provide to customers.
• Nominal city pages exist without meaningful local evidence. Evidence required: proof of a genuine staffed location or a service-area brief containing useful local coverage, access or dispatch information, contact routing, service limitations, and other verified area-specific details. Pass or fail condition: Pass when every retained page is accurate, materially distinct, and useful to a driver deciding whether the business serves that area; fail when only the place name changes, when a map implies a location that does not exist, or when the page adds no substantive local decision value. Severity: High. Owner: Content lead and operations manager. Corrective action: consolidate thin or duplicative pages and retain dedicated pages only for genuine locations or service areas supported by substantial accurate local information. Validation step: compare each retained page with operating records and another market page to verify both factual accuracy and meaningful distinction.