How Should I Describe Bundle Contents So AI Does Not Invent Products or Prices?
To stop AI inventing bundle products or prices, write the contents as a text list with quantities and full product names. State the bundle price once, clearly apart from any "worth" figure or the total of separate prices. Say what is not included, and explain the rules for choose-your-own bundles in words. Give each bundle its own URL, title and feed entry, marked as a bundle, and retire old bundles properly. Assistants invent contents when a bundle is shown only as a photo of items. They mix up prices when component prices and "worth £X" figures sit beside the bundle price. Contents that change with the season, without the page saying so, cause the rest. Clear text leaves them less to guess.
Why do assistants get bundles wrong?
- Contents shown, not listed. A photo of five items with the caption "Everything you need" gives no names to repeat. Assistants fill the gap with items from similar bundles.
- Several prices on one page. The bundle price, each component's price, the total if bought separately, and a "worth" figure. Any of them can be quoted as the price.
- Choose-your-own bundles. "Pick any 3" becomes a fixed list of three products in the answer.
- Changing contents. A seasonal gift set that changes each year, on the same URL, with older descriptions still cached or quoted elsewhere.
- Feeds that look like the main product. A bundle submitted with the main product's title and image looks like the product alone at a higher price.
- Component pages that mention the bundle without making clear that the bundle is a separate product.
What should the bundle page say?
| Element | What to write | Example |
|---|---|---|
| Title | Bundle name plus what it is | "Skincare Starter Set: cleanser, serum and moisturiser" |
| Contents | Text list with quantity, full name and size | "1 × Daily Gel Cleanser, 150 ml; 1 × Vitamin C Serum, 30 ml; 1 × Light Moisturiser, 50 ml" |
| Bundle price | One clear figure | "Set price: £45" |
| Comparison | Labelled separately, and genuine | "Bought separately: £56" |
| Not included | Items people might expect | "Does not include the sunscreen shown in some photos" |
| Rules | For flexible bundles | "Choose any 3 products from the 8 listed below. The price is £30 whichever you choose." |
| Availability | Whether contents change | "Contents of this set are fixed" or "Contents change each season; this listing describes the autumn set" |
Keep the comparison figure honest. UK pricing guidance for traders says offers that claim better value for a combination of products should only be used if the consumer genuinely gets better value. Reference prices should be genuine prices. A "worth £80" figure based on prices nobody pays is misleading to people. It is also the number most likely to be quoted as the price.
How should flexible bundles be described?
State the rules, then list the options:
- The choice: how many items, from which list.
- The price: fixed, or dependent on the choice. If it varies, give the range: "£28 to £34 depending on your choice."
- The options: every eligible product by full name, in text.
- What cannot be combined, if some items are excluded.
Avoid a page that shows only a builder tool loaded by script. Most AI crawlers do not run scripts, so they see an empty page, or only the default selection, which then appears in answers as fixed contents.
What should product feeds and markup say?
In Google Merchant Center:
- Mark retailer-created bundles with the
is_bundleattribute. Google's help describes it as a main product grouped with other, different products, sold together as one package for a single price. Do not use it for bundles the manufacturer created. - Identifiers: for a bundle you created, submit the GTIN, MPN and brand of the main product. For a manufacturer's bundle, submit the bundle's own identifiers.
- Describe the whole bundle in the title, description and image, as Google's best practice advises, rather than reusing the main product's.
- Use
multipackonly for several identical products, not mixed bundles.
In structured data on the page, give the bundle its own Product with its own Offer and price. Schema.org also has ProductCollection, and an includesObject property that lists the exact quantity of each product in an offer or collection. Google's merchant listing documentation does not list them, so treat them as an extra, and make the visible text list the main source. How product markup works more generally is covered in how to use product JSON-LD so AI can understand your products, prices and offers.
How do prices get mixed up?
Take an illustrative set with three items priced separately at £18, £22 and £16, a total of £56, sold together for £45. The page shows "Worth £56!" in large type and the £45 price below the add-to-basket button. Each component links to its own page. Assistants asked "How much is the Skincare Starter Set?" can produce three wrong answers from this page alone. "£56" comes from the worth figure. "£18" comes from the first component price they meet. "About £45 each" comes from misreading the price as applying per item. Put "Set price: £45" first, near the title, and label the £56 as "Bought separately". Then each number has a job that is hard to confuse.
How do you retire or change a bundle?
- Discontinued bundles: mark them as discontinued or remove them, and redirect the URL to the closest current bundle or category. Update feeds the same day.
- Seasonal changes: give each edition its own URL, or state the edition clearly on the page, such as "Winter 2026 edition", and update feeds and markup together.
- Component changes: update the contents list the day a component is swapped. A list that no longer matches the box leads to complaints as well as wrong answers.
How assistants handle products that are no longer available is covered in how retailers should handle AI recommendations for out-of-stock products.
How do you test what assistants say?
Ask ChatGPT, Gemini, Perplexity and Google's AI features, several times each:
- "What is in the [bundle name]?"
- "How much is the [bundle name]?"
- "Is the [bundle] cheaper than buying the items separately?"
- "Does [brand] sell a [category] gift set?"
- "Can I choose the items in [bundle]?"
Record the contents and price each answer gives, and the cited source. A wrong item usually traces to an image-only list, an old edition, or a marketplace listing. A wrong price usually traces to a "worth" figure or a component price.
What might an illustrative case look like?
Consider an illustrative tea company selling a "Discovery Box" of any six teas from a list of twenty, for £24. Assistants described it as containing six specific teas, the default selection in its builder tool, and quoted "£36", the "worth" figure. Its feed used the title "Earl Grey Loose Leaf Tea" because the builder's first item was Earl Grey. The company rewrote the page to state "Choose any 6 of the 20 teas below; £24 whatever you choose". It listed all twenty in text and labelled £36 as "if bought separately". It changed the feed title and marked the entry as a bundle. A month later, answers described the choice correctly and gave £24 as the price.
What do people ask about bundles and AI answers?
Should we remove the separate-prices figure?
Not if it is genuine and helpful. Label it clearly and place it after the bundle price.
Do we need a page for every bundle?
Yes, for any bundle sold as a product. Bundles that exist only in the basket as discounts are better described on the offer or promotion page.
How often should bundle pages be checked?
Whenever contents or prices change, and before each seasonal edition goes live.
Published by The Kovmere Team · updated Sep 29, 2026 · More resources