Audit Dealership SEO With Evidence, Owners, and Validation

This checklist is for dealership owners, marketing managers, ecommerce teams, fixed-operations teams, and outside SEO partners who need a shared way to verify website and local-search work. It assumes the dealership has a website and Google Business Profile, but the same tests can identify missing foundations when either is incomplete.

Evidence required: Before marking anything, gather access to the website platform, Google Search Console, analytics, Google Business Profile, inventory feed or VDP templates, call or lead tracking, and the systems used to record appointments, repair orders, and vehicle inquiries. If you are beginning with no established SEO process, use the checklist to identify missing prerequisites. If the dealership already has visibility, use it to find gaps that competitors might be exploiting.

Pass/fail condition: Pass an item only when the evidence shows the intended page, profile, data field, or measurement is present and working. Do not pass an item because a vendor says it is included in a package.

Severity: Critical means the defect blocks or misdirects important pages or customer actions; high means it materially affects an important dealership search path; medium means it reduces clarity, completeness, or measurement; low means it is useful cleanup with limited immediate impact.

Owner: Assign each failed item to the person who can actually change it: web development, managed-platform support, ecommerce, inventory, local marketing, sales, service, analytics, or dealership leadership.

Corrective action and validation: Write the fix before implementation and state how it will be rechecked. A completed task should have a before-and-after record, not just a status change.

Use this section to verify whether important dealership pages can be securely accessed, rendered, crawled, indexed, and used on mobile. A technical item fails only when the evidence shows a real conflict with the intended page behavior.

• SSL certificate (HTTPS). Evidence required: crawl representative pages and inspect protocol redirects, certificates, mixed-content warnings, and canonical URLs. Pass/fail: pass when intended public pages resolve securely without broken certificate or mixed-content problems. Severity: critical if customers or crawlers cannot reliably access important pages. Owner: web platform or hosting owner. Corrective action: repair certificate, redirect, asset, or canonical configuration. Validation: repeat the crawl and browser checks after deployment.
• Mobile responsiveness. Evidence required: test key VDP, SRP, model, service, finance, contact, and location templates on real mobile devices and responsive tools. The source carries a previously published mobile-research figure above 60%, but no supporting source URL is present, so treat it as historical context rather than a verified dealership benchmark. Use the image and mobile optimization reference when reviewing media-heavy pages. Pass/fail: pass when text, navigation, forms, phone actions, and inventory controls remain usable without hidden or overlapping elements. Severity: high. Owner: web development or managed-platform provider. Corrective action: repair responsive templates and blocking interface defects. Validation: retest the same tasks on representative devices.
• Page performance. Evidence required: collect field data where available and lab measurements for representative dealer templates, including third-party script cost and image payload. The source uses a score above 75 as an operating example, not a guaranteed ranking threshold. Pass/fail: pass when no confirmed performance defect materially prevents page use or causes repeated technical failures. Severity: high for widespread template problems. Owner: development plus the platform or script vendor. Corrective action: reduce unnecessary scripts, optimize assets, and fix measured bottlenecks. Validation: rerun the same measurements and customer tasks.
• XML sitemap. Evidence required: compare submitted sitemap entries with pages the dealership actually intends search engines to discover and index. Pass/fail: pass when durable priority pages are represented appropriately and stale or unintended URLs are not being promoted by the sitemap. Severity: high when discovery of important static pages is impaired. Owner: technical SEO or platform owner. Corrective action: correct generation and submission rules. Validation: fetch the sitemap, resubmit if needed, and inspect Search Console processing.
• Robots.txt. Evidence required: inspect directives against representative inventory, model, location, service, and required rendering resources. Pass/fail: fail when an unintended block prevents access to a page or resource that must be crawled. Severity: critical for core-page blocks. Owner: technical SEO or platform vendor. Corrective action: change only the confirmed conflicting directive. Validation: test the affected URLs with live robots and crawl tools.
• Canonicalization. Evidence required: sample inventory filters, VDPs, model pages, paginated or parameterized URLs, and rendered canonicals. Pass/fail: pass when canonical signals match the intended indexable destination. Severity: critical when valuable pages point to the wrong canonical. Owner: technical SEO or vendor. Corrective action: correct template logic and internal references. Validation: recrawl and inspect the rendered canonical on affected URL sets.
• Site architecture. Evidence required: trace internal paths from the homepage and department hubs to inventory categories, durable vehicle or model pages, service content, finance content, and genuine locations. Pass/fail: pass when important pages are reachable through useful contextual links without relying on orphaned URLs. Severity: high for orphaned revenue-critical pages. Owner: ecommerce, content, and development. Corrective action: repair navigation and contextual links based on user tasks. Validation: recrawl and verify link paths from relevant hubs.

The source calls these seven checks the technical foundation. Use that wording as a grouping convention, not as proof that passing them alone produces rankings. Close the section only when each failed item has evidence, an owner, a documented correction, and a reproducible validation result.

Local checks should determine whether the dealership's real-world identity, eligible profiles, genuine locations, and important third-party records are accurate and useful for customers. Do not convert posting frequency, service-area settings, citation volume, or profile completeness into undocumented ranking guarantees.

• Google Business Profile. Evidence required: verify ownership, business name, address, phone, website destination, hours, departments, and current customer-facing information. Pass/fail: pass when the profile accurately represents the eligible dealership or department. Severity: critical for wrong locations or contact routes. Owner: local marketing with operations review. Corrective action: fix inaccurate or ineligible profile data. Validation: confirm live fields and test contact destinations.
• GBP categories. Evidence required: compare primary and secondary categories with the dealership's real operation and current platform eligibility. Pass/fail: pass when categories describe genuine business functions rather than keyword targets. Severity: high. Owner: local SEO or marketing. Corrective action: remove irrelevant categories and select the most accurate eligible ones. Validation: confirm the live profile and record the final category set.
• GBP posts. Evidence required: review whether posts contain accurate, current customer information. The source suggests at least two posts per month, but no supporting source URL proves that cadence is an official ranking factor. Pass/fail: pass when posts are used when there is a legitimate customer update; do not fail solely for missing a schedule. Severity: low. Owner: local marketing. Corrective action: publish useful updates when appropriate. Validation: verify accuracy, destination links, and customer relevance.
• Service-area settings. Evidence required: compare profile settings with where the dealership genuinely serves customers. Pass/fail: fail when settings misrepresent the business or are used to imply locations that do not exist. Severity: medium. Owner: local marketing. Corrective action: align settings with real operations. Validation: confirm the live configuration and website location statements.
• Local citations. Evidence required: reconcile name, address, phone, website, and brand or department information on Cars.com, Edmunds, Kelley Blue Book, Apple Maps, and other important platforms the dealership actually uses. Pass/fail: pass when material business data is current and conflicts are resolved. Severity: high for obsolete locations or phone numbers. Owner: local marketing or data-management owner. Corrective action: update priority records rather than mass-submitting to low-value directories. Validation: recheck the corrected listings after publication.
• Location pages. Evidence required: inspect every genuine rooftop page for accurate address, contact details, departments, relevant inventory or service paths, and useful local information. Pass/fail: pass when each real location has a distinct, accurate page; do not create a page for a nominal market without useful location-specific information. Severity: high for missing real-location destinations. Owner: content, local marketing, and development. Corrective action: build or repair genuine location pages. Validation: test page accuracy, indexability, internal links, and customer actions.

The source previously cited an industry comparison of 30-50% more Map Pack clicks for more complete local setups, but no supporting source URL appears in this JSON. Preserve that range as unresolved historical context rather than a verified effect. Evaluate the dealership with its own local visibility, calls, directions, website visits, appointments, and completed business outcomes.

Use these checks to verify that each important dealership page clearly describes its visible content and that structured data matches what a customer can actually see. Do not add markup merely to pursue a search feature.

• Title tags and meta descriptions. Evidence required: crawl priority model, inventory, service, finance, and genuine location pages for missing, duplicated, misleading, or templated metadata. Pass/fail: pass when the title and description accurately distinguish the page and match its search intent. Severity: medium. Owner: content or SEO. Corrective action: rewrite only affected priority pages. Validation: recrawl and verify rendered metadata.
• Vehicle structured data. Evidence required: compare visible vehicle type, price, mileage, condition, availability, and other supported fields with the structured data actually rendered. Pass/fail: pass when markup is valid, supported, and consistent with visible page information. Severity: high when markup is misleading or materially wrong. Owner: development or platform vendor. Corrective action: repair or remove inaccurate markup. Validation: run structured-data validation and compare the rendered page.
• Organization or local business structured data. Evidence required: compare visible dealership name, address, phone, hours, and relevant profiles with the markup. Pass/fail: pass when the chosen type and properties accurately represent the visible business. Severity: medium. Owner: development or technical SEO. Corrective action: align markup with the page rather than adding unsupported fields. Validation: validate syntax and visible-content consistency.
• Review structured data. Evidence required: inspect whether any review markup follows current search-engine guidelines and reflects reviews genuinely shown on the page. Pass/fail: fail when markup is self-serving, hidden, unsupported, or inconsistent with visible content. Severity: high for misleading markup. Owner: technical SEO and development. Corrective action: remove or correct unsupported implementation. Validation: retest the markup and confirm the page remains accurate without claiming rich-result eligibility.
• H1 and header hierarchy. Evidence required: inspect headings on representative templates. The source refers to one H1 with supporting H2 and H3 structure. Pass/fail: pass when headings describe the page logically and are not used merely to repeat keywords. Severity: medium. Owner: content or template owner. Corrective action: repair confusing or missing hierarchy. Validation: inspect rendered headings after deployment.
• Keyword and topic alignment. Evidence required: compare the page's search intent with its visible copy, headings, image alternatives, inventory, and customer task. The source mentions the first 100 words as an example, not a placement rule. Pass/fail: pass when the page naturally answers the target intent without forced repetition. Severity: medium. Owner: content or SEO. Corrective action: improve clarity and topical completeness. Validation: re-read the rendered page and monitor relevant query coverage.

The source also carries a previously published 20-30% click-through comparison for correct inventory markup. No supporting source URL is included, so do not treat that range as a verified effect or reason to add unsupported schema. Validate markup for accuracy first.

Content checks should prove that the dealership has useful information for real buyer and service questions that inventory pages alone cannot answer. Publication volume is not a pass condition by itself.

• Buying guides. Evidence required: compare Search Console queries, sales questions, and inventory mix with existing guides. Pass/fail: pass when important recurring buyer questions have accurate, useful destinations tied to vehicles the dealership actually sells. Severity: medium. Owner: content with sales review. Corrective action: create or improve only evidence-backed guides. Validation: review query relevance, assisted inventory views, and qualified leads.
• Financing and trade-in content. Evidence required: identify recurring financing, trade-in, and affordability questions and check whether the website answers them without unsupported approval, rate, savings, or eligibility claims. Pass/fail: pass when customers can understand the process and reach the correct next step. Severity: high for misleading finance information. Owner: content with finance and compliance review. Corrective action: replace vague sales copy with accurate process guidance. Validation: review submitted leads and the live page for accuracy.
• FAQ content. Evidence required: collect the 10-15 recurring questions heard by sales, service, finance, or customer-care teams. Pass/fail: pass when answers are accurate, useful, and maintained. FAQ content can help readers, but do not add or promote FAQPage markup as a route to Google FAQ rich results. Severity: medium. Owner: content with department review. Corrective action: publish or update reader-focused answers. Validation: confirm factual accuracy and monitor relevant query engagement.
• Blog or resource cadence. Evidence required: compare proposed topics with real search demand and dealership expertise. The source suggests at least two posts per month, but no source URL proves that cadence influences rankings. Pass/fail: pass when resources are published because they answer useful recurring questions, not because a quota was met. Severity: low to medium. Owner: content. Corrective action: replace volume targets with an evidence-backed topic queue. Validation: measure query relevance, engagement, and assisted customer actions.
• Vehicle comparisons. Evidence required: identify comparison queries that match inventory the dealership can genuinely discuss. Pass/fail: pass when comparison pages are accurate, current, balanced, and connected to relevant inventory. Severity: medium. Owner: content with sales or product review. Corrective action: create useful comparisons without inventing superiority claims. Validation: recheck specifications and monitor qualified comparison traffic.

The source previously associated buyer-focused content with 2-3x more organic traffic in internal experience. Because no supporting source URL or methodology is present, treat that range as a historical observation rather than a forecast. Judge content by the dealership's own query coverage and customer outcomes.

Review checks should evaluate whether the dealership collects honest feedback consistently, handles responses professionally, and monitors reputation across the platforms customers actually use. Review activity should not be treated as a fixed ranking formula.

• Review request process. Evidence required: inspect how sale and service customers become eligible for a request and whether the same neutral process is applied consistently. Pass/fail: pass when eligible customers can leave honest feedback without incentives, review gating, or discouragement of negative reviews. Severity: high for selective or incentivized collection. Owner: customer experience, sales, service, or marketing. Corrective action: standardize a policy-compliant request workflow. Validation: sample recent requests and confirm the process is neutral.
• Review response process. Evidence required: inspect response quality, privacy handling, unresolved complaints, and team ownership. The source uses 48 hours as an operating example, not a documented ranking threshold. Pass/fail: pass when responses are timely enough for customer care, factual, and professional. Severity: medium. Owner: reputation or dealership management. Corrective action: define escalation and response standards. Validation: review a sample of positive and negative cases after rollout.
• Review monitoring. Evidence required: identify which platforms generate meaningful dealership visibility or customer feedback, including Google, Yelp, Trustpilot, and automotive review sites where applicable. Pass/fail: pass when the team can see and route relevant feedback; do not fail merely because every possible platform is not monitored. Severity: medium. Owner: reputation or marketing. Corrective action: consolidate alerts and ownership. Validation: test that new reviews reach the responsible team.
• Reputation mentions. Evidence required: review brand and manager mentions that can materially affect customer understanding or require a response. Pass/fail: pass when relevant mentions can be identified and escalated. Severity: low to medium. Owner: PR or reputation. Corrective action: configure appropriate monitoring and response ownership. Validation: test alerts with known mentions.
• Testimonials on the website. Evidence required: verify that displayed testimonials are authentic, current, and represented accurately, and inspect any associated structured data for guideline compliance. Pass/fail: fail when testimonials are unverifiable or markup implies unsupported ratings. Severity: high for misleading claims. Owner: content and technical SEO. Corrective action: correct, remove, or document testimonials and unsupported markup. Validation: compare visible content with the underlying source and retest structured data.

The source carries a previously published comparison in which dealerships averaging 4.5+ stars were associated with 20-30% higher conversion rates than those below 4.0. No supporting source URL is present in this JSON, so preserve those values only as unresolved historical context. Use the dealership's own lead, appointment, repair-order, and vehicle-sale data when evaluating reputation impact.

Week 1-2: Confirm technical access and local accuracy. Evidence required: collect failed crawl, indexation, security, mobile, profile, citation, and genuine-location checks. Pass/fail: this stage passes when critical blockers have owners and reproducible validation tests. Severity: prioritize critical and high defects. Owner: technical, local, and platform teams. Corrective action: repair access, indexation, mobile-use, and material business-data problems before lower-dependency work. Validation: repeat the failed tests.

Week 3-4: Repair page meaning and structured data. Evidence required: review failed metadata, inventory markup, page hierarchy, model or service content, and genuine location-page checks. Pass/fail: pass when corrected pages accurately represent visible content and intended search tasks. Severity: high or medium based on affected demand. Owner: content, ecommerce, and development. Corrective action: fix priority pages first and create a 10-question FAQ only when those questions are genuinely recurring. Validation: recrawl, validate markup, and inspect rendered pages.

Week 5+: Maintain evidence-backed content and reputation work. Evidence required: review unanswered customer questions, review-process gaps, and content opportunities that remain after technical fixes. Pass/fail: pass when ongoing work has a real owner, source data, and a defined measurement method. Severity: medium or low unless compliance or reputation defects are present. Owner: content, reputation, sales, service, or analytics. Corrective action: maintain a topic and feedback queue based on evidence rather than an arbitrary quota; the source's 2 posts/month figure is an operating example only. Validation: review query relevance, lead quality, feedback coverage, and completed business outcomes.

The source uses a 2-4 week window for early ranking impact. Treat that range as a planning observation, not a guaranteed search response. Validate technical corrections immediately where possible, then evaluate visibility and business outcomes on the longer timeline appropriate to the affected search path.