Why does AI never mention my parts department?

Because you never published anything for it to read. Almost no dealership states in plain text whether it sells OEM parts to the public, whether it ships, whether it price-matches, or what it keeps on the shelf. So when a shopper asks an AI engine where to get a factory part, the engine answers from somebody else's page.

I went looking for this at my own store about six months ago. Asked three different assistants where to buy a genuine BMW cabin filter near Bridgewater. Two named an online OEM parts reseller in another state. One named a competitor forty minutes away. Nobody named us, and we have the part on the shelf, today, eleven minutes from the person asking.

That is not a ranking problem and it is not a reputation problem. Nothing on our website said we sell parts to the public. The machine was not wrong. It was working with what we gave it, which was nothing.

Why is parts the most invisible department in the store?

Because it is the one department that never got a website. Sales got thousands of structured vehicle pages. Service got a scheduler and a coupon block. Parts got a phone number in the footer and, if it was lucky, a contact form.

Think about what that means to a machine reading your site. It can tell you sell cars because you published a thousand pages that describe cars. It can tell you have a service department because the word appears in your navigation. It cannot tell whether your parts counter serves walk-ins, because you have never said so in a sentence. Absence does not read as "no" to an engine. It reads as unknown, and unknown loses to a competitor who wrote one clear paragraph.

What do people actually ask AI about parts?

Specific, low-drama, high-frequency questions. Where can I buy a genuine part instead of aftermarket. Does the dealer sell parts to the public or only install them. Can I get an OEM part shipped. Will the dealership price-match an online parts site. Do I need a dealer part to keep my warranty intact. Does this dealer have the part in stock or do I wait a week.

None of those are glamorous. All of them are decided in one exchange with an assistant, and whoever answered them in writing gets named. These questions also repeat far more often than "which dealer should I buy a car from," which is the whole argument for treating fixed ops as the softer AI target in the first place.

What does an engine find when it looks for your parts counter?

Usually a page with a header image, the words "Parts Department," a form, and hours that may or may not match your Google profile. Sometimes an online parts catalog running on a third-party subdomain the engine does not connect to your business at all. That last one is common and quietly expensive: you are paying a vendor to host your parts catalog somewhere the machine cannot tell is you.

Meanwhile an independent shop or an online reseller published two hundred words of plain, specific text about the exact part, and gets the mention. It is the same dynamic that decides who wins the service drive question, one level deeper in the store.

Does fixing parts content help anything besides parts?

Yes, and this is the part most people miss. Every department page you publish strengthens the entity picture an engine builds of your business: what you do, where, under which hours, as one organization. A store with clear sales, service, parts, collision and fleet pages is simply easier for a machine to describe with confidence than a store with one of the five. The same gap runs through the collision center and the commercial side, and closing any one of them helps the others.

What should a parts page actually say?

Write the answers to the questions above, in sentences, on a page that is yours. At minimum:

Whether you sell to the public and to independent repair shops. Whether you ship, and where. Your return policy on parts. Whether you price-match, and against what. What you typically stock versus special-order, and the realistic wait on an order. The brands and model years you cover. Your parts hours, which are almost never the same as your service hours and are almost always published as if they were. And a plain-English answer on the warranty question, because it is the single most asked parts question there is and most dealers have never written it down.

What about schema?

Add an AutoPartsStore or a department entry on your existing AutoDealer markup, with its own hours, phone and areaServed. If your parts catalog lives on a vendor subdomain, link it from your own parts page and reference it in your schema so an engine can connect the two. Schema is the layer that tells a machine what a page means rather than what it says, and a department entry is a twenty-minute change that most dealer sites are missing entirely.

Where do I start?

Ask the engines the parts questions a customer would ask, using your actual town, in a clean session. Write down who gets named and what they get wrong about your hours and your stock. Then open your own parts page and read it as a machine would. If it does not answer the question you just typed, that is your first paragraph.

The free check on this site runs those questions across ChatGPT, Claude and Gemini and scores how your store comes back.