Audit a Dealership Website From Technical Evidence to Business Impact

Evidence: Start by documenting the dealership's platform, current SEO owner, recent migrations or redesigns, access to Google Search Console and analytics, inventory-feed ownership, Google Business Profile access, and which teams control sales, service, parts, and website changes. Use the Car Dealership SEO Resource Hub only for background; the audit should rely on the dealership's own systems and current configuration.

Severity: Treat missing access, unclear ownership, or an undocumented recent migration as high priority because they can prevent accurate diagnosis or block implementation even when the underlying SEO issue is understood.

Owner: Assign one audit coordinator who can obtain data from the website vendor, ecommerce team, fixed operations, local marketing, analytics, and any outside SEO provider.

Corrective action: Build an evidence inventory before making recommendations. Record the managed platform, code and template permissions, reporting access, current vendor scope, recent site changes, and the dealership queries or pages that appear to have lost visibility.

Validation: The stage is complete when the auditor can reproduce the reported problem with data, identify who controls each affected system, and distinguish a traffic issue from an access, tracking, migration, or reporting issue. This prevents a generic checklist from being applied to a dealer site whose architecture or responsibilities are still unclear.

Evidence: Check whether important dealership pages can be discovered, rendered, canonicalized, and indexed as intended. Inspect robots.txt, XML sitemaps, internal links, canonical tags, Search Console indexing reports, and rendered HTML on representative inventory, model, service, and location URLs.

Audit checks

• robots.txt: Review disallow rules that affect SRPs, VDPs, model pages, service content, assets required for rendering, or other important paths. A blocked URL may be intentional, so document the purpose before changing it.
• XML sitemap: Compare submitted sitemap URLs with the pages the dealership actually wants indexed. Remove stale or low-value entries only after confirming their role, and make sure important static landing pages are represented where appropriate.
• Indexation evidence: Use Google Search Console and URL Inspection to identify excluded, duplicate, canonicalized, or crawled-but-not-indexed pages. Do not assume a large excluded count is automatically a defect; classify the URLs first.
• JavaScript rendering: Compare visible page content with rendered HTML and inspect whether primary headings, inventory details, links, and conversion actions are available after rendering.

Severity: Critical when core dealership pages are blocked, canonicalized to the wrong destination, unavailable to rendering, or omitted from internal discovery in a way that conflicts with the intended indexation strategy.

Owner: Technical SEO or web development, with the managed-platform provider involved when robots, canonicals, rendering, or templates cannot be changed internally.

Corrective action: Fix only the confirmed defect: adjust crawl directives, sitemap membership, canonical rules, rendering dependencies, or internal links according to the intended role of each page type.

Validation: Re-crawl the affected templates, inspect live and rendered URLs, confirm the corrected directives in Search Console, and monitor whether the intended pages become discoverable and indexable without creating new duplicate paths.

Inventory and model-page checks

Evidence: Inventory duplication should be evaluated by comparing representative VDPs, SRPs, and model pages rather than assuming every feed-generated page is a problem. The source example uses a 2024 Honda CR-V to show how vehicle pages can share specifications and boilerplate while differing mainly by VIN and price.

Sample VDPs across new, used, and sold inventory. Record canonical targets, internal links, indexability, unique vehicle information, feed-supplied text, template copy, and whether the page gives a shopper useful information beyond what already appears on an SRP.

Severity: High when large groups of indexable URLs are near-identical, canonical targets conflict with the intended page, or model pages are merely filtered search results with little useful editorial context.

Owner: Inventory merchandising and technical SEO, with the feed or platform vendor included when templates, canonicals, or inventory URL behavior are vendor-controlled.

OEM content verification

Corrective action: Preserve VDPs that serve a real shopper purpose, correct self-referencing or other intended canonical behavior where misconfigured, improve internal linking to durable model and category pages, and add useful dealership-specific content only where it can be kept accurate. The source example refers to a New Ford F-150 page matching 200 other dealer pages and suggests 150-200 words of original material. Treat those values as examples of differentiation, not as minimum content requirements.

Compare quoted passages from model and trim pages with other dealer sites to identify syndicated wording. The issue is not the presence of shared OEM facts itself; the audit should determine whether the page contains enough original, useful context to serve a customer and whether the duplicate blocks are overwhelming the page.

Validate the corrected content set

Validation: Re-crawl the affected templates, compare canonical and indexation signals, review representative rendered pages, and monitor query coverage and organic entrances to the durable model or inventory pages that were intended to improve.

Evidence: Audit the dealership name, address, phone number, categories, hours, website destination, department information, and eligible profiles across the website, Google Business Profile, and important external listings. Check at least three directory records as the source suggests, but evaluate material conflicts rather than treating harmless formatting differences as a ranking diagnosis.

Local data checks

Compare the footer, contact page, profile data, major directory records, and department pages. Record old phone numbers, closed locations, duplicate or ineligible profiles, incorrect categories, mismatched URLs, and business names that do not reflect the real-world operation.

Severity: High when incorrect local data can send customers to the wrong place, when a legitimate rooftop lacks a usable destination, or when profile configuration misrepresents the actual dealership or department.

Google Business Profile review

Verify the primary category, appropriate secondary categories, real business hours, accurate website URL, current customer-facing information, and eligible department or brand profiles. Do not treat service-area fields, photo cadence, posts, Q&A activity, or other profile activity as documented ranking factors. Use them when they improve accuracy or customer usefulness.

Location-page review

If the group operates more than one genuine location, each location should have a useful page that accurately describes that rooftop, its contact details, departments, services, directions, and other location-specific information. Do not create nominal city pages merely because the dealership wants visibility in a surrounding market, and do not require a map embed as a ranking mechanism.

Owner: Local marketing or local SEO for profile governance, with dealership operations responsible for verifying real-world business information and the web team responsible for location-page implementation.

Corrective action: Correct material business-data conflicts, remove or resolve ineligible duplicates, align categories with genuine operations, and strengthen only real location pages with useful local content. For broader context, use the Car Dealership SEO Resource Hub.

Validation: Confirm the corrected data is live on the dealership website and priority listings, test phone and website destinations, review profile eligibility, and track local visibility and customer actions without attributing every movement to one profile edit.

Evidence: Determine which technical settings the dealership can change directly and which are controlled by the managed website provider. Do not assume a platform-wide defect from one site. Test the actual installation, contract permissions, template behavior, scripts, canonicals, schema, rendering, and page-speed data.

DealerSocket (now Solera)

The source associates DealerSocket with JavaScript-heavy implementations and limited template-level control in some configurations. Verify those constraints on the dealership's account rather than treating them as universal. Record whether canonical tags, schema, metadata, rendering dependencies, or Time to First Byte can be changed internally or require support.

Dealer.com (Cox Automotive)

The source describes configuration differences by contract tier. Audit the available admin controls, generated headings, title templates, CDN behavior, and third-party scripts on the actual site. A generated H1 or locked title template is a defect only when it conflicts with the page's intended content and cannot be corrected through available settings.

DealerOn

The source notes that duplicate title patterns and canonical configurations can require review. Validate the dealership's templates directly, document the affected URL sets, and separate vendor limitations from configuration choices made inside the account.

When the platform is the constraint

Severity: Critical when the platform prevents a correction that blocks, mis-canonicalizes, or materially degrades an important page type; medium when the limitation affects optimization flexibility without preventing access or indexation.

Owner: Web development or technical SEO should document the defect, while the dealership account owner manages escalation with the provider and leadership owns any contract or migration decision.

Corrective action: Submit a reproducible support request with affected URLs, expected behavior, evidence, and business impact. Continue improving elements the dealership controls while the vendor issue is unresolved, but do not assume content or link work can compensate for every technical constraint.

Validation: Re-test the exact affected URLs after the vendor change, preserve before-and-after crawl evidence, and verify that the platform modification did not introduce new rendering, canonical, tracking, or template problems elsewhere.

Evidence: Convert the audit into an issue register that records affected URLs or profiles, evidence, business consequence, technical dependency, responsible owner, corrective action, and validation method. Prioritization should reflect the size and certainty of the defect, not how easy it is to report.

High-priority work within 30 days

• Confirmed indexation or crawl defects affecting important pages
• Canonical rules sending valuable pages to unintended destinations
• Material Google Business Profile or NAP errors that misrepresent a dealership or department
• Broken or missing sitemap behavior when it affects discovery of intended static pages

Owner: Technical SEO, web development, local marketing, or the managed-platform provider depending on the defect. Validation: Re-crawl, inspect live directives, verify profile data, and confirm that the corrected destination or indexation behavior is observable.

Medium-priority work within 60-90 days

• Model or location pages that are demonstrably thin, duplicated, or poorly matched to search intent
• Measured performance problems caused by unnecessary or poorly implemented third-party scripts
• Incomplete pages for genuine dealership locations
• Schema gaps where structured data does not accurately represent the visible page content

Owner: Content, development, technical SEO, or local teams depending on the issue. Validation: Compare rendered pages, technical measurements, query coverage, and customer actions after the correction rather than assuming publication alone proves success.

Recurring controls

• Monitor model and service pages for stale or inaccurate information
• Ask eligible customers consistently for honest reviews and respond when a response is useful, without review gating or incentives
• Update Google Business Profile information and media when the customer-facing information changes; do not impose an undocumented posting cadence as a ranking requirement
• Recheck indexation and rendering after meaningful platform updates

Corrective action: Sequence work so confirmed access and indexation defects are resolved before lower-certainty optimization ideas. If the root cause is controlled by the website provider, document the constraint and escalation path. The linked professional dealership SEO audit reference can be used when outside technical review is needed.

Validation: Close an issue only when the change is live, the original defect can no longer be reproduced, and the expected technical or local signal is observable. Business outcomes may take longer to assess, so keep technical validation separate from later traffic, lead, or revenue evaluation.