Build-to-Order Listings in Google Merchant Center: Step-by-Step

Why Google Merchant Center Now Indexes Trims, Not Just VINs

For most of the last decade, Google's vehicle inventory surfaces only showed units physically on a dealer's lot—matched to a VIN, priced, and available today. That constraint quietly ended when Google added `build_to_order` as a supported availability value in the GMC vehicle feed spec. Dealers can now list configurable trims—spec'd to a specific package, engine, color combination, and MSRP—even when zero examples exist in current stock.

The practical implication: if a buyer searches "2026 Ford F-150 Tremor with 402A package" and you have a BTO listing for that exact trim, you compete for that click. Without a BTO listing, Google routes the buyer to Ford's OEM find-a-dealer page instead.

This is still an under-indexed channel. As of mid-2026, most dealer website platforms have not turned on native support for BTO feed entries. The dealers who set this up now own the SERP position before competitors catch up.

OEM-Fed BTO vs. Dealer-Stocked BTO: The Critical Distinction

These are two different things and they're often confused:

OEM dealer-locator BTO — When a buyer configures a vehicle on Ford.com or GMC.com and clicks "Find a Dealer," they're routed through OEM infrastructure. The OEM controls the listing, the lead, and the routing. The dealer gets a notification, not ownership of the discovery moment.

Dealer-stocked BTO in GMC — When a dealer publishes their own `build_to_order` feed entries in Google Merchant Center, they own the Google surface. The listing shows the dealer's name, the dealer's price, and the dealer's "Order this build" CTA. The lead comes to you directly. This is what this guide covers.

The two can coexist. Your OEM program continues running. Your dealer GMC BTO listing is incremental shelf space on top of it—for searches that happen inside Google's surfaces before the buyer ever reaches the OEM site.

What Google Actually Requires

Google's official spec is specific. A BTO listing that fails validation gets disapproved; a disapproved listing earns zero impressions. Here's what must be correct:

In your feed:

• `availability: build_to_order` — this is the exact attribute value; note it's `build_to_order`, not `make_to_order` (a common mistake)
• `vehicle_fulfillment: online` — required when availability is `build_to_order`. The most common disapproval error is leaving this out or setting it to `in_store`. Google requires online fulfillment for BTO offers because no physical unit exists to pick up.
• `availability_date` — estimated delivery date in ISO 8601 format (e.g., `2026-09-15`). Required for BTO.
• Standard vehicle attributes: year, make, model, trim, body style, mileage (0 for new), VIN or a stable identifier
• Configured options: engine, drivetrain, exterior color, interior, packages
• Price: MSRP for the configured spec, not the base trim MSRP
• Image: OEM configurator renders are accepted; minimum 800×600px

On your landing page (schema):

Google's Rich Results validator must find a `Product` + `Offer` block with `PreOrder` availability. `schema.org/PreOrder` is the correct mapped value for `build_to_order` in GMC—they're not the same string but they're equivalent in Google's processing:

```

{

"@context": "https://schema.org",

"@type": "Product",

"name": "2026 Ford F-150 Tremor — 402A Package, Carbonized Gray",

"offers": {

"@type": "Offer",

"availability": "https://schema.org/PreOrder",

"priceCurrency": "USD",

"price": "67490",

"priceValidUntil": "2026-12-31",

"seller": { "@type": "AutoDealer", "name": "Your Dealership Name" }

}

}

```

A missing `priceValidUntil` field will sometimes cause a Google Rich Results warning even when it doesn't trigger a hard disapproval. Include it.

How AI Overview and AI Mode Treat BTO Listings

Google's AI Mode (the successor to AI Overview in the shopping context) treats BTO listings differently from in-stock listings in one important way: it looks for narrative content on the landing page, not just the schema and feed data, before citing a BTO listing in a conversational answer.

For in-stock inventory, a clean feed entry plus basic schema is often enough for inclusion. For BTO listings, AI Mode wants to see a landing page that explains *why* a buyer should order this specific configuration—what the 402A package actually adds, what the Tremor's suspension tuning does on pavement vs. trail, what the lead time looks like. Generic spec tables without prose do not get cited.

This is the same principle that drives AI search visibility on standard VDPs—structured data plus narrative beats structured data alone. For BTO pages, the narrative is even more important because the buyer is making a longer-horizon decision and is actively seeking to validate their choice.

Aim for 300–500 words of original descriptive prose per BTO landing page. The page should answer:

• What distinguishes this trim or package from the base model
• Who this configuration is built for (towing, daily commute, off-road, etc.)
• What the estimated delivery window means practically (production slot, transport, prep)
• What a buyer needs to do to secure the build (deposit, order form, CRM inquiry)

Step-by-Step Setup for a Single Franchise Store

Step 1: Get OEM configurator data

Most Ford, GM, Stellantis, Toyota, and Honda franchises have a configurator export or API that produces a JSON or XML file of buildable specs by model and year. Contact your OEM's digital program rep. Without this, you're hand-keying trim data, which isn't scalable past 10–15 entries.

Step 2: Choose your starting trim set

Don't start with every possible configuration—start with your 10–20 highest-search-volume specs. For truck franchises: the Tremor, the Raptor, the AT4X, the TRD Pro, the Power Wagon. For SUV franchises: the RST, the TrailBlazer RS, the Grand Cherokee 4xe. These trims pull the most "near me" AI queries and earn the fastest citation lift.

Step 3: Build one landing page per spec

URL structure: `/order/2026-ford-f150-tremor-402a-carbonized-gray/`

Page must include:

• 300–500 words of original narrative (see above)
• Full spec breakdown as structured text (not an image)
• Configurator render image with descriptive alt text
• Pricing table: base MSRP, package cost, destination, total MSRP
• Estimated order-to-delivery window
• "Order this build" CTA connected to your CRM with source tagging
• Vehicle + Offer + FAQPage schema blocks
• Internal links to the model-line page, your in-stock units of the same model, and your financing page

Add every BTO URL to your XML sitemap the day it goes live. Include a callout in your `llms.txt` file so AI crawlers understand these are authoritative product pages, not placeholders.

Step 4: Wire the feed entries

In your existing GMC vehicle feed (same data source as your in-stock listings), add a new entry for each BTO spec. Key attributes that differ from in-stock entries:

• `availability: build_to_order`
• `vehicle_fulfillment: online` (required—without this you get an "Ineligible fulfillment" disapproval)
• `availability_date`: your estimated delivery date
• `link`: your per-spec landing page URL (not your homepage, not the model page)

Submit the updated feed and monitor the Issues tab in Merchant Center for 48–72 hours. The most common disapproval reasons are missing `vehicle_fulfillment: online` and landing page schema mismatches.

Step 5: Cross-link from your model-line page

Your `/f-150/` or `/sierra-1500/` model page should have a "Build & Order" section listing your published BTO specs. This internal linking builds entity authority for the model in Google's Knowledge Graph and makes the BTO pages discoverable to crawlers via the main site hierarchy—not just through the sitemap.

Step 6: Measure what matters

Track these metrics weekly for the first 90 days:

• Impressions per BTO URL in Google Search Console
• Leads per URL in your CRM (use UTM parameters on the CTA)
• AI citation checks: search "2026 [Model] [Trim] near [Your City]" in AI Mode weekly
• Days-to-delivery vs. same-model lot unit close rate

Within 60–90 days you'll have a clear signal on which trim-and-package combinations pull AI citations and direct leads. Double the BTO page depth (more narrative, more FAQs) on those winners.

The Channel Economics

A typical truck or SUV franchise with 15–25 BTO listings properly wired generates 10–30 incremental leads per month from buyers searching for trims that don't exist on any regional lot. These are high-intent buyers—they've already spec'd the vehicle, they know what they want, and they're looking for a dealer to execute the order. Gross margins on custom-order units are typically higher than lot units because there's no carrying cost and the buyer is buying to spec, not negotiating from a position of "take it or leave it."

The paid advertising corollary is also worth noting: running Google Vehicle Ads against BTO feed entries costs roughly the same per-click as in-stock inventory ads, but the competition density is far lower—most dealers aren't running BTO ads yet. Early movers in this format are seeing CPCs 30–50% below comparable in-stock inventory campaigns.

For how AI search surfaces generally index dealer inventory, and how structured data ties into Google AI Overview citations, see those guides for the broader context. The BTO play extends naturally from a strong VDP build standard and a working AEO content strategy. The InventoryPilot AI engine handles BTO listings the same way it handles in-stock units — see features for the full description workflow, or book a demo. The BTO play is the leading edge of a shift toward trim-level rather than VIN-level search — dealers who build that infrastructure now will have compounding advantages as AI Mode continues expanding its vehicle shopping surfaces.