Browse inventory like a new shopper
An inventory search-results page is the place to reduce a large choice to a useful shortlist. Relevant filters and consistent vehicle cards matter more than the number of controls on the screen. Filters should reflect the stock and information the dealership can actually maintain.
Inspect it: choose a common body style, combine filters, and deliberately select an unlikely combination. Check that the result count updates, the empty state makes sense, and resetting is obvious. Return from a vehicle page and see whether your browsing context is preserved.
Ask your provider: which system supplies each filter value, how missing fields are handled, and what happens to sold vehicles? Confirm update expectations rather than assuming every destination synchronizes immediately.
Read the vehicle information closely
A vehicle-detail page should help a shopper understand the specific vehicle, not simply repeat a generic sales message. Photography, specifications, condition information, supplied pricing, and relevant conditions need a coherent order.
Inspect it: open a listing with a complete photo set and another with missing information. Check image sharpness, gallery controls, text size, and whether price-related conditions sit close to the price. Confirm that a shopper cannot mistake a placeholder for a verified specification.
Ask your provider: who owns accuracy, which fields are required, and how edits are reviewed? An attractive template cannot verify the information supplied to it.
Follow the inquiry path
Choose a vehicle and look for a sensible next action. The inquiry should retain the relevant context and make clear what happens next. A form should not promise an appointment just because someone entered a preferred time.
Inspect it: with permission in a test environment, submit an empty form and try an invalid email address. Check that errors explain the problem, entered values are retained, and a keyboard user can reach the fields that need attention. Avoid sending test leads into a real sales queue without agreement.
Ask your provider: where is an accepted request recorded, who receives it, and how is failed delivery detected? A success message in the browser is not evidence that the team received the inquiry.
Check access beyond the mouse
Readable contrast, meaningful labels, logical headings, and keyboard access are practical foundations. Accessibility is not a badge earned by installing an overlay or receiving a single automated score.
Inspect it: use Tab and Shift+Tab, activate controls with the keyboard, and check for a visible focus indicator. Zoom the page and inspect a narrow viewport. Forms need persistent labels, errors that do not rely only on color, and controls large enough to use comfortably.
Ask your provider: what manual and assistive-technology testing is included, who reviews issues, and how fixes are tracked? Use the W3C WCAG 2.2 quick reference to understand the relevant criteria. An automated scan does not certify conformance.
Measure the experience, not just a score
A large vehicle image or an unnecessary third-party script can shape the loading experience. A useful performance discussion starts with actual pages and representative conditions, not only the lightest page in a test.
Inspect it: test the homepage, inventory results, and a vehicle detail on mobile. Note when the main content appears, whether the page shifts as images load, and how quickly controls respond. Repeat cold-load lab tests so a single unusually good run does not become the whole story.
Ask your provider: which images and scripts load initially, how image dimensions are reserved, and which field data is available? Core Web Vitals measure loading, responsiveness, and visual stability. Lighthouse lab results do not establish a field INP result or guarantee rankings.
Define what an inquiry means
A click, a sent request, an accepted lead, and an attended appointment are different events. A useful measurement plan distinguishes them and connects website observations with the dealership's actual process.
Inspect it: review the proposed event names and the data attached to them before enabling tracking. Typed names, emails, phone numbers, messages, and URLs should not be casually included in analytics payloads.
Ask your provider: who owns the analytics account, what requires consent, and how accepted requests are verified? Decide how your team will assess qualified inquiries rather than treating every interaction as a sale.
Plan the move before changing the site
Keep a record of useful existing pages, their URLs, and the access needed for the domain, hosting, content, and analytics. A redesign is not a reason to send every old page to the new homepage.
Inspect it: map each important existing URL to a relevant new destination. Identify pages that should stay, pages that need a permanent redirect, and pages that should genuinely return not found. Check that application and login routes remain separate from the marketing work.
Ask your provider: who implements redirects, validates response codes, checks canonicals, and monitors the change? Review Google's site-migration guidance. Preserve access and a rollback plan, and keep staging pages out of search until the approved site is ready.
Bring your observations to the conversation.
A useful review leaves you with a short, prioritized list: what stops a shopper, what confuses your team, and what needs verification. It does not need a made-up score to be useful.
Related: SEO & marketing. Technical sources are linked in the relevant sections. No product capability or business result is guaranteed by this guide.