By industry

Car dealership website design: sold cars listed

A shopper on a Friday night wants to see a used hatchback this weekend and needs to know the car is still on the lot. Mimiq sends simulated shoppers through your inventory and test drive form and shows where each one stopped.

5 visitors try to .
First test free with an accountRun it from your coding agent

Why do car shoppers find a car on a dealer's website and still not request a test drive?

A shopper requests a test drive when the car is still for sale, the form asks only for what a stranger can answer, and the request confirms a real visit. Dealer sites often fail one of those, usually because the inventory is loaded from a stock system that updates late, or the form asks for a number printed only on the car. Check the listing of a car you know has sold, then fill in the form for a car that is still on the lot. A simulated test sends a shopper through the search, the listing and the form, and shows the screen where they stopped.

What this looks like in a report

Who
Anders, shopping for a used hatchback with a child seat already fitted
How they arrived
Opened a used car listing from a marketplace link on his phone
Where they stopped
Test drive form, at the stock number field

“The form wants a stock number, and I am not at the lot to read the sticker on the windshield. I cannot tell if the car is still there. I will try the other dealer on the list.”

The fix. Replace the stock number field with the vehicle name and a choice of day, and hide the test drive button on any car marked sold. Add a line to the confirmation that names the car and says who will reply, and by when.

An illustration. Run a test to see your own.See a real sample report

A sold car stays on the lot page, and the test drive form still accepts it

Inventory on a dealer site is often pulled from a stock system on a schedule rather than the moment a car sells. Between updates, a car that sold on Tuesday can still show as available on Thursday, with its photos, its price and a working request button. The shopper who asks for a test drive gets a confirmation, then waits for a reply about a car that is gone. The sales team sees the sold status in the back office and assumes the site is current, so the stale listing stays out of sight until a customer finds it.

  • Does a car you know has sold still show a test drive button?
  • Does a search filter return the same cars you see on the lot?
  • Does the test drive form ask for a stock number only found on the car?
  • Does the confirmation name the car and say who will reply, and when?
  • On a phone, does the request button stay visible while the shopper scrolls the photos?

The stock sync decides what a shopper can trust

Car listings on many dealer sites come from a stock system that updates on its own schedule. The website shows what it last received, so a car can be sold in the office and still sit in the search results for a while. A search filter adds to the problem. A shopper who filters for a used hatchback sees a list that does not match the lot, and opens cars that are no longer there. Compare your search results with the cars on the lot once a day, and note which ones carry no sold label.

A form that asks for a number only the lot can see

The test drive form is the step that turns interest into a visit, so every field on it should be one a stranger can answer from home. Some dealer forms ask for a stock number printed on the windshield sticker or in the back office, not on the listing. A shopper cannot fill that in without going to the lot, and cannot go to the lot to find out whether the car is there. Look at each required field and ask whether a person on a sofa can answer it. If not, make it optional, or let the shopper name the car in their own words.

The search, the listing and the car that is gone

Run the three steps in the order a shopper does: search, open a listing, request a test drive. The search can keep a sold car in the results. The listing can leave the sold label out, or put it in small type under the photos. The request can accept the form and confirm a visit for a car that no longer exists. Each step looks fine when the owner tests it with a car they know is in stock. A run that starts from the search box uses the cars a shopper actually meets, so it catches the one that is gone.

What you get with Mimiq

  1. 01

    Run it by hand, or on every pull request

    Paste a link and a task in the app and watch the visitors work. Or run them on every preview deploy: the GitHub Action comments on the pull request, any other CI can call the MCP endpoint, and your coding agent can run it too.

  2. 02

    Bugs and usability problems in one report

    The browser records errors and failed or slow requests on the step they happened. The visitors say where the wording or the steps confused them, and where they left.

  3. 03

    Visitors that behave like your audience

    Each visitor is a different profile with a reason to be there, matched to who the page is for, described by you, or built from your own customers.

  4. 04

    A prompt to fix each problem

    Every problem comes with a fix to paste into Cursor, Claude Code, Lovable or any coding agent, and one prompt hands over the top problems at once. Then send the same visitors through again.

  5. 05

    Follow every visitor

    See each visitor's whole path, step by step with screenshots, and what it was thinking at every step. Ask any visitor a question.

The browser records relevant JavaScript errors and failed or slow app requests encountered during the run, attached to the step where they occurred. The visitors are simulated: they find problems, they do not predict how many real people will convert.

A feed change from your stock system can list sold cars again

Dealer sites change when the stock system changes, when a new feed is added, or when a campaign page pulls in its own list of cars. Any of these can bring a sold car back into search, or a form field that only the lot can answer. Run the same shopper from the search box after each feed change. The run shows whether the cars a shopper finds are still for sale.

Starter

Try it on one launch

$9 once
120 credits, never expire

About 4 tests of 5 visitors

  • Visitors on your landing page, signup and checkout
  • Where they left and why, with a fix to copy for each problem
  • Run it in the app or on every pull request
  • Ask any visitor a question, included
  • Test accounts and protected previews
Buy 120 credits

Builder

Test every build

$19 a month
500 credits every month

About 20 tests of 5 visitors

  • Everything in Starter
  • Credits refill each month, and what is left rolls over once
  • Cancel anytime
Choose Builder

Pro

Test every release, as a team

$49 a month
1,500 credits every month

About 60 tests of 5 visitors

  • Everything in Starter
  • Credits refill each month, and what is left rolls over once
  • Cancel anytime
Choose Pro

Scale

Test at scale, every day

$149 a month
6,000 credits every month

About 240 tests of 5 visitors

  • Everything in Starter
  • Credits refill each month, and what is left rolls over once
  • Priority support
  • Cancel anytime
Choose Scale
$0for your first test, with a free account (Google sign-in, no card). It includes 50 credits, enough for 10 visitors. After that a visitor uses 5 credits, and packs start at $9 for 120 credits.
See a sample report

Questions

Will this tell me how many test drives I will sell?

No. It does not predict how many shoppers will request a test drive, and it cannot tell you how many requests turn into sales. It shows the screen where a simulated shopper stopped, whether the car they chose was still listed and which field they could not answer. For rates, use your sales records, not a test run.

Can a simulated shopper put down a deposit or apply for finance?

No. A deposit that takes a real card ends at the payment step, because visitors cannot pay with a real card. A run can reach a finance form and shows whether that form asks for details before it offers a test drive time, which can be where shoppers give up.

Should I give the test a real customer's name or trade-in details?

No. Use made-up names and a test email address, and do not enter a real customer's name, trade-in details or phone number into a run. A test does not check your site against privacy rules, and a shared report should not carry anyone's details.

Does the test check whether a sold car is removed from my back office?

No. It sees only what the public site shows. If a car is still listed after it sold, the run will show that listing, but the test does not look inside your stock system. Check the sold status in that system yourself, and compare it with the listing the next morning.

Keep reading

Send visitors and see what breaks first.

Your first test is free: sign in with Google and it starts right away. Last checked 2026-11-02.

5 visitors try to .