The 2026 Auto Glass SEO Checklist for Verifiable Local Readiness

A previously published internal observation associated poor mobile experiences with a 40-60% bounce rate for roadside searches. Treat that figure as historical context requiring source reconciliation, not as proof that a specific technical defect caused a specific result. Use the controls below to verify the live experience.

Mobile rendering and contact path Evidence required: live-device screenshots of the main service pages, a completed test call, a completed quote-form test, and current mobile status from Google Search Console or PageSpeed Insights.

Pass or fail condition: Pass when the navigation, service details, phone action, and quote action render correctly and complete without hidden fields, blocked controls, or incorrect routing. Fail when a driver cannot reach the intended contact step on a representative mobile device.

Severity: Critical. Owner: Web developer with the marketing owner. Corrective action: repair responsive layout, button behavior, form validation, phone links, and any script or consent layer that blocks the primary action. Validation step: repeat the full contact journey on the live page and archive the result with device and page details.

Business structured data accuracy Evidence required: the live JSON-LD output, the shop's verified name, address, phone, hours, location type, and service details, plus a validation report from Schema.org or Validator.schema.org.

Pass or fail condition: Pass when the markup validates and every declared fact matches the visible page and real operation. Fail when a physical location, service area, service, review, or business detail is inaccurate, unsupported, duplicated, or hidden from users.

Severity: High. Owner: SEO lead and web developer. Corrective action: remove unsupported properties, use only relevant supported types, and align the markup with visible business information. Do not treat structured data as a guaranteed ranking factor or as a special requirement for Google AI features.

Validation step: inspect the rendered source, rerun the validator, and compare each property with the live page and verified business record.

Core Web Vitals and layout stability Evidence required: current field data where available, Lighthouse traces for representative service pages, and a screen recording of the mobile page loading around the phone and quote controls.

Pass or fail condition: Pass when no unresolved poor field status or reproducible layout shift interferes with reading, navigation, or contact actions. Fail when page movement, delayed controls, or heavy media repeatedly disrupts the task.

Severity: High. Owner: Performance developer. Corrective action: reduce blocking resources, reserve space for media and interface elements, compress required assets, and remove nonessential scripts from the service journey.

Validation step: rerun the same page tests under the same conditions and confirm that the prior failure cannot be reproduced.

HTTPS and sensitive form handling Evidence required: a current certificate check, a crawl for insecure resources, and a documented test of any form that collects a vehicle identification number, insurance detail, or contact information.

Pass or fail condition: Pass when all public pages and form submissions use a valid secure connection with no mixed content or insecure endpoint. Fail when any request, asset, redirect, or submission drops to an insecure connection.

Severity: Critical. Owner: Hosting administrator and web developer. Corrective action: renew or replace the certificate, correct redirects and asset references, and secure every submission endpoint. Validation step: confirm the live certificate path, rerun the mixed-content check, and submit a controlled test record through the live form.

Local search controls should represent the business that a driver can actually contact or visit. Profile completeness, categories, reviews, and location content are operating inputs, but this checklist does not treat posting cadence, map embeds, review-response rates, or profile activity as guaranteed ranking factors.

Google Business Profile identity and category fit Evidence required: an exported or screen-captured profile showing the verified business name, primary category, secondary categories, phone, hours, website, address or service-area setup, and listed services.

Pass or fail condition: Pass when the primary category accurately describes the core operation and Auto Glass Shop is selected when it is available and appropriate, with secondary categories limited to services the business actually provides.

Fail when categories, naming, hours, phone routing, or service details are inaccurate or added only to target keywords. Severity: Critical. Owner: Location manager and local SEO owner. Corrective action: correct the profile to match real operations, remove keyword additions from the business name, and document why each category and service is appropriate.

Validation step: compare the live profile with the website, signage or business records, call routing, and current service menu.

Mobile service coverage accuracy Evidence required: the dispatch team's current coverage list, accepted travel limits, excluded areas, mobile service conditions, and the service areas shown in the profile and website.

Pass or fail condition: Pass when every stated city, postal area, or service zone is regularly served under the published conditions. Fail when the profile or page claims areas the team does not serve or presents a service area as a staffed location.

Severity: High. Owner: Dispatch manager and local SEO owner. Corrective action: align profile and website coverage with operational reality, remove unsupported areas, and explain mobile availability and limits in user-facing language.

Validation step: sample stated areas against current dispatch records and confirm that staff give the same answer by phone.

Honest review request process Evidence required: the request message, eligibility rule, send trigger, opt-out handling, staff instructions, and a sample showing that all eligible customers receive the same request regardless of expected sentiment.

Pass or fail condition: Pass when the process asks consistently for honest feedback without incentives, review gating, discouraging negative feedback, or selecting only satisfied customers. Fail when staff or software filters recipients, offers a benefit, or redirects criticism away from the public option.

Severity: High. Owner: Customer operations manager. Corrective action: replace selective or incentivized flows with a neutral request sent after the documented service-completion event, and train staff on the same rule.

Validation step: review a recent request sample and confirm that eligibility, wording, timing, and destination match the documented process.

Genuine location and service-area pages Evidence required: proof of a staffed customer-facing location or a content brief containing useful local service information, coverage conditions, contact routing, relevant examples, and unique operational details.

Pass or fail condition: Pass when a location page represents a genuine location or gives drivers substantial, accurate location-specific information. Fail when a page exists only because a market name was swapped into a duplicated template, when a map implies a location that does not exist, or when the same content is repeated across nominal service areas.

Severity: High. Owner: Content lead and location operations manager. Corrective action: consolidate thin pages, rewrite useful pages from verified local evidence, and keep only markets that the business can substantively describe and serve.

Validation step: compare the live page with operational records and another location page to confirm that the information is accurate, useful, and materially distinct.

Service content should help a driver choose the correct next step without overstating technical capability, safety, insurance coverage, or search performance. Each page must be reviewed against the services the shop actually performs.

ADAS calibration service resource Evidence required: the current service menu, equipment and procedure documentation, technician or service-manager review, supported vehicle or job conditions, and the handoff used when calibration is not performed in-house.

Pass or fail condition: Pass when the page accurately explains the shop's real static or dynamic calibration process, prerequisites, limitations, and customer next step. Fail when it implies every vehicle requires the same process, claims unsupported capability, or promises a safety or search outcome.

Severity: Critical. Owner: ADAS service lead and content editor. Corrective action: replace generic claims with reviewed service details, disclose limitations, and remove any calibration statement the operator cannot evidence.

Validation step: have the service lead compare the live page with the current workflow and approve a dated record of the review.

OEM and aftermarket glass comparison Evidence required: the shop's actual sourcing options, terminology used by suppliers, customer decision factors, warranty terms, and technical review of any safety or compatibility statement.

Pass or fail condition: Pass when the guide presents accurate distinctions, tradeoffs, questions to ask, and shop-specific availability without declaring one option universally superior. Fail when it uses unsupported performance claims, vague authority language, or product terms the shop cannot explain.

Severity: High. Owner: Procurement or service manager with the content editor. Corrective action: rewrite the comparison around verifiable choices, availability, documentation, and customer questions, and remove unsupported claims.

Validation step: compare the published guide with current supplier and service information and test whether staff give a consistent explanation.

Insurance assistance information Evidence required: the real intake process, information requested from customers, insurer communication steps, billing responsibility, exclusions, and approved language for coverage uncertainty.

Pass or fail condition: Pass when the page explains what the shop can assist with and clearly states that coverage, approval, reimbursement, and customer responsibility depend on the applicable policy and process.

Fail when it promises acceptance, payment, waiver, or a guaranteed claim result. Severity: Critical. Owner: Insurance coordinator and content owner. Corrective action: replace outcome claims with a step-by-step description of assistance, required documents, decision points, and limits.

Validation step: run the page through a current intake scenario and confirm that each published step matches staff practice.

Pages for distinct glass services Evidence required: a service inventory for windshield repair, full replacement, back glass, side windows, sunroofs, mobile service, and any other published offering, plus the correct contact or quote path for each.

Pass or fail condition: Pass when each page has a distinct user purpose, accurate eligibility and limitations, useful process detail, and a matching next action. Fail when multiple services are merged into a vague page or when separate pages repeat the same content without service-specific value.

Severity: High. Owner: Service manager and content lead. Corrective action: separate materially different services, consolidate duplicates, and rewrite each retained page from verified operational information.

Validation step: map every page to the service inventory and have staff confirm that the page can be used to answer a real customer inquiry.

Sticky mobile contact control Evidence required: a live mobile page showing the contact control, a completed call test, and a check that the control does not cover required content or consent choices.

Pass or fail condition: Pass when the control remains usable on representative pages and routes to the correct number or quote step. Fail when it obscures content, breaks navigation, or sends the user to an incorrect destination.

Severity: High. Estimated effort: 1 hour. Owner: Web developer. Corrective action: add or repair a restrained mobile contact control tied to the correct action. Validation step: test the live control across representative mobile pages and record the completed action.

Current real-business photo set Evidence required: a reviewed inventory containing 10+ current, accurate images of the shop, mobile units, technicians where permitted, work environment, or service process, with no misleading location or capability claim.

Pass or fail condition: Pass when the selected images are real, current, relevant, and correctly associated with the business. Fail when the set relies mainly on stock imagery, outdated branding, or images that imply services or locations the operator does not provide.

Severity: Medium. Estimated effort: 2 hours. Owner: Location manager and marketing owner. Corrective action: capture, approve, and publish an accurate photo set with descriptive file and display context where useful. Validation step: compare every published image with the current business and remove any image staff cannot verify.

Industry directory record check Evidence required: the live directory record, ownership or verification status, business details, destination URL, and confirmation that the organization is relevant to the shop.

Pass or fail condition: Pass when the listing is legitimate, accurate, verified where available, and consistent with the website and profile. Fail when the record is duplicated, inaccurate, irrelevant, or created only to manufacture authority.

Severity: Medium. Estimated effort: 3 hours. Owner: Local SEO owner. Corrective action: correct or claim the legitimate record, remove duplicate submissions where possible, and document unresolved discrepancies.

Validation step: open the public record, compare all details with the verified business information, and save the review date.

• Repair and replacement intent combined. Evidence required: the service inventory, search landing pages, and contact paths. Pass or fail condition: Pass when windshield repair and windshield replacement each have a clear, accurate purpose or are intentionally consolidated with distinct sections; fail when users cannot tell which service applies. Severity: High. Owner: Service manager and content lead. Corrective action: separate or restructure the content around real eligibility, process, limitations, and next steps. Validation step: test each page against a representative repair and replacement inquiry.
• Customer questions left unmanaged or answered inaccurately. Evidence required: the current Google Business Profile questions and answers, ownership access, and approved factual responses. Pass or fail condition: Pass when material questions have accurate, current answers and unsupported answers are reported or corrected where possible; fail when incorrect service, hour, insurance, or calibration information remains unaddressed. Severity: Medium. Owner: Location manager. Corrective action: answer from verified operating information without treating question activity as a guaranteed ranking factor. Validation step: review the public profile and compare answers with the website and staff process.
• ADAS capability implied without evidence. Evidence required: the live service pages, calibration workflow, equipment or partner documentation, and service-lead approval. Pass or fail condition: Pass when every calibration statement can be substantiated and limitations are visible; fail when the page uses generic ADAS language to imply unavailable work or guaranteed safety outcomes. Severity: Critical. Owner: ADAS service lead. Corrective action: remove unsupported claims and publish the real workflow, prerequisites, and handoff. Validation step: obtain a dated service-lead review of the live page.
• Real-business evidence replaced by generic imagery. Evidence required: the image source record and confirmation of the depicted location, vehicle, technician, or process. Pass or fail condition: Pass when imagery is authentic or clearly illustrative and does not misrepresent the operator; fail when stock images imply facilities, staff, equipment, or work the shop cannot verify. Severity: Medium. Owner: Marketing owner. Corrective action: replace misleading imagery with approved real-business evidence. A previously published internal observation cited a 20-30% conversion-rate difference, but that figure requires source reconciliation and must not be treated as causal proof. Validation step: audit each image against the source record and live business.
• Insurance assistance presented as an outcome promise. Evidence required: intake scripts, billing steps, policy disclaimers, and the published insurance page. Pass or fail condition: Pass when the page distinguishes shop assistance from insurer decisions and customer responsibility; fail when it promises coverage, approval, payment, or waiver. Severity: Critical. Owner: Insurance coordinator. Corrective action: rewrite the page around verified steps, documents, limits, and decision ownership. Validation step: compare the live copy with a current intake case and staff explanation.
• Nominal city pages created without local value. Evidence required: proof of a genuine location or a brief containing useful local coverage, access, contact, and service information. Pass or fail condition: Pass when each retained page is accurate, materially distinct, and useful to drivers in that area; fail when only the place name changes or a map implies a location that does not exist. Severity: High. Owner: Content lead and operations manager. Corrective action: consolidate thin pages and retain only genuine locations or service-area pages supported by substantive local information. Validation step: compare the page with operating records and another market page for duplication.