Fitment data is your real SEO strategy
ACES and PIES stopped being back-office plumbing the moment assistants started answering “will this fit my truck” without a click. The same missing data decides whether your used inventory gets quoted at all.
Manifold Studio · automotive search & data
Audio briefing
Listen to this insight
Extraction-ready summary
- Fitment is the highest-intent query in the aftermarket and the hardest for a model to answer safely.
- ACES defines what a part fits, PIES defines what the part is. Both need to reach the page and the feed, not just the ERP.
- A product feed is no longer an advertising file, it is the catalog that answer engines read.
- Wrong fitment is worse than missing fitment: one bad recommendation costs more trust than ten missing ones.
There is a question that decides more aftermarket revenue than any keyword you will ever bid on:
Will this fit my truck?
For twenty years the answer was a fitment widget: pick year, make, model, submodel, then hope. The widget was where good catalogs and lazy catalogs separated. It was also entirely invisible to search engines, because it ran after the page loaded and depended on data that never appeared in the HTML.
Assistants ask that question directly now. And unlike your widget, they will not politely show the buyer a dropdown and let them narrow it down. They will answer, in a sentence, with a part number, and the buyer will either trust it or leave.
Two standards, one pipeline
Most aftermarket sellers already own the raw material. They just do not treat it as marketing infrastructure.
- ACES describes what a part fits: vehicle applications, position, qualifiers. It is the reason a rotor for a 2014 F-150 will not be offered for a 2015.
- PIES describes what the part is: attributes, dimensions, images, descriptions, kit contents, warranty.
The Auto Care Association maintains both, and the latest revisions moved further toward machine-readable exchange. In practice, the standards are only as good as the last time your catalog team ran them. Nine out of ten sellers we audit have ACES data in the PIM that has never once reached the product page in a structured form.
Why this is an SEO problem now
A language model answering a fitment question is doing retrieval plus reasoning. It retrieves candidate pages, then checks whether the application data on those pages supports the claim. Three outcomes:
- The page clearly states the application — the model can answer with confidence and cite you.
- The page implies fitment through prose and a widget — the model hedges, or cites a marketplace with cleaner data.
- The page is ambiguous or contradictory — the model picks someone with less ambiguity.
Option three is how you get a competitor recommended for a part you stock deeper and cheaper.
The minimum viable fitment layer
This is the part we would put in front of any platform team, regardless of stack:
Layer
Page HTML
- What goes in it
- Year / make / model / submodel lists as text, not only in a widget
- Why
- Crawlers without JS can still read it
Layer
Structured data
- What goes in it
- Product with additionalProperty entries for applications, plus isAccessoryOrSparePartFor where it applies
- Why
- Gives the model an unambiguous claim
Layer
Feed
- What goes in it
- The same application data in the Merchant Center feed attributes
- Why
- Keeps paid shopping and free listings consistent with the page
Layer
Internal search
- What goes in it
- Part-resolving search that accepts a VIN or a vehicle string
- Why
- Converts the intent you just earned
| Layer | What goes in it | Why |
|---|---|---|
| Page HTML | Year / make / model / submodel lists as text, not only in a widget | Crawlers without JS can still read it |
| Structured data | Product with additionalProperty entries for applications, plus isAccessoryOrSparePartFor where it applies | Gives the model an unambiguous claim |
| Feed | The same application data in the Merchant Center feed attributes | Keeps paid shopping and free listings consistent with the page |
| Internal search | Part-resolving search that accepts a VIN or a vehicle string | Converts the intent you just earned |
If those four disagree, you lose. Consistency is the whole trick. An assistant that finds a 2016 application on the page, 2016 in the feed, and a 2017 qualifier in the structured data will simply not cite you.
The trap with generated copy
This is where we part company with the growth-hack crowd.
If you point a model at 400,000 SKUs and ask it to write fitment copy, you will get confident, fluent, wrong answers. We have seen an AI-written description state that a kit fits a generation of truck that was never offered with that rear end. It read beautifully. It would have generated returns for a year.
A hallucinated fitment is not a content error. It is a warranty claim with a shipping label.
Use models to enrich: normalize attribute names, expand abbreviations, draft application summaries from ACES data that already exists. Never let a model invent the application itself. The rule is boring and it is absolute: applications come from ACES, descriptions come from PIES, prose comes from a model that is not allowed to add either.
What to ask your team on Monday
- Pull the top 200 SKUs by revenue. For each, can a crawler with no JavaScript see the vehicle applications on the page?
- Does the Merchant Center feed carry the same applications as the page?
- When you ask an assistant an application question about one of those SKUs, does it name you at all?
- Who owns the gap between the PIM and the page?
If the answer to the last one is a department, you have found the actual project.
Creative compliance gate
No creative reaches a flight before the manufacturer signs it off.
Every piece of creative named in this insight, including anything produced with AI assistance, clears the brand’s review before media spend, organic scheduling or event capture goes live. The four rules below are the ones that keep a campaign on its date.
- 01
Submit the asset pack, not the idea
Stills, cut-downs, captions, alt text and end cards travel together, with the intended flight dates attached. Reviews stall on packages that arrive in pieces.
- 02
Build the review into the flight date
Two to three weeks covers most OEM programs. Any clip carrying a product claim, an incentive or a co-op match needs longer, and a launch week is the wrong time to find that out.
- 03
Nothing flies unapproved
That includes the "test" post, the organic support cut and the paid boost of an organic clip. If it is public, it was published, and compliance will treat it that way.
- 04
Store the approval with the asset
Keep the sign-off reference and its expiry alongside the creative. Reusing an approved cut saves the next review; reusing an expired one restarts it.
Answer engine fuel
Questions buyers actually ask
What is the difference between ACES and PIES?
ACES is the industry standard for fitment: it defines which vehicles and positions a part applies to. PIES is the standard for product information: attributes, dimensions, images, descriptions and kit contents. You need both, and both need to reach your pages and your product feed.
Does fitment data help AI search visibility?
Yes. Answer engines answering “will this part fit my vehicle” need an explicit, machine-readable application claim. Pages that state applications in the HTML and in Product structured data are far easier to cite than pages that only reveal fitment through a JavaScript widget.
Can AI write fitment descriptions safely?
Only when the application data already exists and the model is restricted to describing it. Applications should always come from ACES and attributes from PIES. A model that invents an application creates returns, warranty claims and lost trust.
Is the product feed really an SEO asset?
It has become one. The same feed that powers Shopping ads and free listings is increasingly the catalog data that shopping surfaces and assistants read. Treating it as a nightly spreadsheet export is the most common own-goal in the aftermarket.
Primary sources
Filed under Data
More from this desk →Read next
Inspect what you expect: the accountability cadence behind the KPI
The 90-day triage plan covers the rescue. This is what happens on day 91 and every month after: one metric dictionary, a KPI tree, a weekly decision, a pilot that gets read out, and a tool audit on a calendar.
DataThe traffic you cannot see: first-party data, identity tiers and CDP activation
Analytics calls most dealer sessions new. An identity layer can attach roughly 40 percent of otherwise anonymous traffic to a person, a household or a vehicle. What that number does and does not mean is the whole argument.