A 90-day triage plan you can run without a replatform
If the platform replacement is stuck in committee, here is the order of operations that buys you time and proves the thesis with numbers.
Manifold Studio · automotive search & data

Audio briefing
Listen to this insight
Extraction-ready summary
- Establish a manual AI-visibility baseline before buying any platform.
- Structured data and server-rendering are the two cheapest permanent wins on a legacy stack.
- Reconcile feed and page for the top 200 SKUs before touching design.
- A before-and-after table persuades a committee better than a strategy deck.
Every dealer group we audit has a platform replacement document. It has a timeline, a vendor shortlist, and a sponsor who is careful not to commit. It is three years old.
Waiting for it is a decision, and usually the wrong one. Here is the sequence we would run in parallel, in ninety days, with people you already have.
Days 1 to 14: establish an honest baseline
Before anything, measure the thing nobody measures.
- Twenty questions your buyers actually ask, written down verbatim.
- Each asked in ChatGPT, Gemini, Perplexity, and Google, once.
- Logged: mentioned? cited? which competitor? which marketplace?
This is your only real baseline, and it costs nothing. Do it again on day ninety with the same questions. Two comparable snapshots beat a subscription you cannot interpret.
Days 15 to 30: fix legibility
Server-render product and category templates. No redesign. The same page, with the facts in the HTML.
Audit crawler access. Decide deliberately which retrieval crawlers you allow, then publish the policy.
Ship Product schema. sku, brand, offers, applications. Generated from the same data that renders the page, never hand-maintained.
If you can only do one item from this entire plan, do the structured data. It is the cheapest permanent improvement available to a legacy stack.
Days 31 to 55: fix the catalog
- Reconcile the Merchant Center feed against the page for the top 200 SKUs.
- Resolve brand, part number and vehicle naming to one format everywhere.
- Pull ACES applications out of the PIM and into both the page and the feed.
- Kill any generated description that asserts fitment it cannot source.
This is the unglamorous quarter that decides whether the next three years work.
Days 56 to 75: build the answer surface
- Twenty question-answer pages, each answering one question completely in the first two sentences.
- Spec and fitment tables on the top category pages.
- FAQ blocks with
FAQPageschema where the questions are real. - An
llms.txtthat points at what matters.
Write them like a human who knows the catalog. Do not publish machine-written fitment.
Days 76 to 90: rewire the paid side
- Audit which Search campaigns were auto-migrated to AI Max.
- Check final URL expansion against your top-spend destinations.
- Write the AI Brief with fitment and brand constraints stated plainly.
- Add text disclaimers for legal copy.
- Re-run the twenty questions and compare.
What to show the committee
Not a redesign mockup. Three numbers:
- Crawlable product pages: before and after.
- Mentions in the twenty-question set: before and after.
- Paid landing page quality on the top twenty destinations: before and after.
A committee cannot argue with a before-and-after table the way it can argue with a strategy deck. That is your replatform business case, generated for free, in ninety days, on the platform they are refusing to replace.
You do not need permission to make the catalog legible. You need permission to spend money, and you mostly do not need that either.
The honest caveat
None of this fixes a platform that cannot publish structured data or server-render. If you hit that wall in week two, you have your answer about the replatform, and you have it with evidence.
Either way, you stop guessing. That is worth ninety days.
Week thirteen is the report. The report page shows the shape we hand back: paid separated from organic, every denominator stated, and campaigns ranked by booked appointments.
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
Can I improve AI search visibility without replacing my ecommerce platform?
In most cases yes. Server-rendering the existing templates, adding Product structured data, and reconciling the product feed with the page are additive changes that do not require a replatform.
What should I measure first?
A manual baseline: twenty real buyer questions asked in ChatGPT, Gemini, Perplexity and Google, logged monthly with whether you were mentioned, cited, or replaced by a competitor. It costs nothing and it makes every later claim testable.
How much of this can one person do?
The measurement, the structured data and the answer pages can be done by one competent engineer or technical marketer in three months, provided merchandising gives access to catalog data.
Primary sources
Filed under Strategy
More from this desk →Read next
Hire the designer who can code, or rent one forever
A static mockup cannot carry behavior, state or latency, so somebody guesses, and somebody reworks. The hybrid designer-developer is the cheapest form of certainty on the roster, and almost nobody is paying for it properly.
StrategyThe program, not the pep talk: internal enablement that survives a staff change
Argued already that a tool is nothing without the education to guide it. This is the build: a role map, a one-page SOP format, a 30/60/90 training ladder and the vendor support terms that make it stick.