Industries

A dealership website built around the inventory decision

A dealership website has to help someone find a vehicle before it can help the sales team start a conversation. Attractive photography and clear branding matter, but the decisive questions are practical: What is available? Can I narrow the selection? Does this vehicle fit my needs? What happens when I ask about it? Those questions should shape the website brief, the inventory architecture, and the connection between browsing and inquiry.

If search work is part of the scope, our website rule applies. We only do SEO on a site we built.

Ninetyfifth Marketing approaches car dealership website design as an inventory-led product decision. The central challenge is to make a changing selection easy to explore while keeping the underlying page structure deliberate. A shopper needs flexible search controls; the website needs a clear distinction between permanent destinations and temporary browsing states. Those needs belong in the same design conversation.

Documented work: a custom app with live inventory

For Arizona Elite Motors, the documented scope includes a custom dealer web app with live inventory, search and filtering, vehicle detail pages, SEO and AI-search work, a chatbot, trade-in capture, and review automation.

That scope gives this service a concrete foundation: a dealer website is an application with connected inventory and contact functions. The documented work supports a discussion of those components and their relationship. It does not establish a ranking result, an increase in inquiries, or a measured change in sales. A buyer evaluating a similar project should examine the proposed architecture and acceptance criteria directly.

Make inventory discovery the organizing principle

Start with the decisions people make while shopping. Someone looking for a work truck may begin with body style and budget. Someone replacing a family vehicle may start with seating needs and compare several makes. The interface should help each person narrow the available selection without requiring knowledge of the dealership's internal stock categories. Navigation labels should reflect recognizable shopping choices.

Give the homepage a useful handoff

A homepage should establish who the dealership is and provide an obvious route into current inventory. A proposed design might include an inventory search entry point, selected vehicle categories, and a clear explanation of how to contact the store. Each element should have a purpose. A promotional section that pushes inventory access far down the page deserves scrutiny, especially on a phone.

Keep the shopper's context intact

Consider a shopper who selects a price range, opens a vehicle, and then returns to compare another option. The project brief should specify whether the selected filters, sorting choice, and list position remain available. These small behaviors affect the continuity of the shopping task. They should be reviewed in a working prototype, alongside the visual design, so everyone can evaluate the actual browsing sequence.

Useful filters do not require an indexable URL for every choice

A filter is an interface control. A search landing page is a publishing decision. Treating every combination of make, model, price, mileage, and sort order as a separate search destination can produce a website structure that is difficult to explain and maintain. The proposal should distinguish between shopper-facing flexibility and the smaller set of destinations the dealership deliberately wants to publish.

For example, a shopper might narrow the inventory to a particular make within a budget and then change the sort order. That interaction needs a reliable state, but it does not automatically need a new indexable page. Depending on the architecture, browsing state could be preserved through interface state or carefully controlled parameters. The important requirement is explicit handling of filters, internal links, crawl behavior, and permanent page destinations.

• Define which inventory categories deserve stable navigation and editorial attention.
• Specify how selected filters persist when shoppers open vehicles and return.
• Document how temporary states behave when copied, refreshed, or opened on another device.
• Review which destinations appear in internal links and search-facing page structures.

Connect vehicle information to a specific next step

A vehicle page should carry the information needed to decide whether a conversation is worthwhile. In a proposed engagement, the content model would identify the vehicle fields, photography requirements, availability language, and inquiry options. The design should make the relationship between the vehicle and the inquiry explicit. A general contact form leaves the sales team with a different starting point than a question attached to a particular vehicle.

Trade-in capture and a chatbot also need defined roles. A trade-in flow could collect the information needed for a follow-up discussion, while clearly explaining the next step. A chatbot should have boundaries around what it can answer and when it should hand off. Neither component should obscure essential vehicle information or make basic contact details difficult to reach.

Scope the operating work before choosing the visual treatment

The inventory source, update responsibilities, and exception handling should be established early. Ask what happens when a record arrives without photographs, when a price is missing, or when a vehicle becomes unavailable. These are design inputs as well as technical questions. An elegant template cannot resolve an undefined availability policy, and a live connection still needs understandable behavior when information is incomplete.

A useful proposal should identify who supplies inventory data, who approves page content, who receives inquiries, and who reviews automated messages. SEO, AI-search work, and review automation should have their own defined tasks and dependencies. This makes it possible to assess the engagement as a set of reviewable deliverables, with responsibility assigned to the dealership or agency at each handoff.

Review a working shopping journey

Before approving a build, ask to walk through a complete example using representative inventory: enter the site on a phone, narrow the selection, inspect a vehicle, return to the results, and submit a question. Include an unavailable vehicle and a record with missing information. This review exposes decisions that static page mockups leave unresolved and gives the dealership a concrete basis for accepting the work.