Aizii Learn · AI Search
← Back to Learn

How to launch a new product so AI picks it up

A new product is invisible to AI search until the indexes have it, the crawlers can read it, and the facts about it are complete and in agreement. A launch that only announces the product has done one third of the job. A launch that also makes the product readable has done the whole job. This guide works through the launch in the order the systems need it: the page first, then the facts, then the index, then the measurement.

Google's AI guide says its systems retrieve relevant, up-to-date pages from the Search index and review the specific information on those pages to generate an answer. A new product page that is not in the index cannot be retrieved, and a page in the index with incomplete facts cannot be reviewed properly. The launch has to satisfy both steps.

1. Build the page before the announcement

  • Create the product page before the launch announcement goes out, not after. An announcement that links to a page that does not exist yet is a link to a dead end, and a dead end teaches a system not to trust the next link from the same brand.
  • Give the product a page of its own, with its own URL, not a section on a category page. A product that lives only as a row in a grid has no page for an assistant to cite, and no page for a shopper to land on.
  • Write the product description before launch, with the facts a buyer asks about: materials, size, fit, compatibility, care, and what is in the box. A description written after launch is a description the first wave of crawlers never saw.
  • Name the price, the availability, and the shipping and returns terms on the page, in words a shopper can read. A price hidden behind a click, or a shipping cost that only appears at checkout, is a fact the system cannot read.
  • Add the product to the category page it belongs to, and link from the category page to the product page. A product page with no links pointing to it is a page a crawler has to find on its own, and a crawler that has to find it on its own may not find it at all.

2. Make the facts complete and in agreement

  • Add Product structured data to the new page, with the same price and availability the page shows. Google's Product structured data docs say that when you add structured data to product pages, users can see price, availability, review ratings, shipping information, and more right in search results.
  • Check the new page with the Rich Results Test before it goes live. It reads the live page or a pasted code snippet and lists the structured data it finds, with errors and warnings. A pass means the markup is eligible for Google's rich results. It does not mean Google will show a rich result.
  • Check the same page with the Schema Markup Validator. It checks the markup against the full schema.org vocabulary, not just the types Google supports for rich results.
  • Add the product to the product feed, with the same price and availability as the page and the markup. A feed that still shows the old product list while the page shows the new product is a mismatch, and a mismatch is a product that gets disapproved or a recommendation that ends in a sold-out page.
  • If the product has variants, mark availability per variant. If one size is out of stock and the others are not, mark that size as out of stock and leave the rest alone. A product-level status that hides a variant-level shortage sends shoppers to a size that does not exist.
  • Add the product to the llms.txt file, if the store serves one, so the file lists the new page among the pages worth citing. Google says it does not use llms.txt for Google Search, and its AI guide lists llms.txt files as one of the things you do not need for Google Search. Other assistants may read the file, so add the product there, and do not treat the file as a requirement for Google.

3. Put the product in the indexes

  • Confirm the product page is in the sitemap. On Shopify, the sitemap is generated automatically and updates when you add a product. On other platforms, check that the sitemap includes the new page, and submit the sitemap again if the platform needs it. Shopify's own help page says to submit the sitemap to Google Search Console so Google can find and index the pages.
  • Submit the sitemap in Bing Webmaster Tools as well. Copilot retrieves from Bing, and a product that is only in Google's index is invisible to Copilot.
  • Ask for a recrawl of the new page in Search Console, rather than waiting for Google to find it on its own. Check the vendor docs in Sources for the current path to the recrawl request.
  • Check that robots.txt does not disallow the new page. A new collection built from a template can carry a staging block, and a broad rule can catch the new product's path by accident. Open [yourdomain.com]/robots.txt, replacing yourdomain.com with your actual domain, and read it before launch, not after.
  • Confirm the store is not password protected and the new page is not behind a bot wall. A launch page that a crawler cannot reach is a launch that only humans can see.

4. Announce it where the systems can read it

  • Announce the product on the store's own site first, on the product page and in a short post or guide that explains what the product is for and who it is for. An announcement on the store's own site is a page the indexes can read. An announcement only on social media is a post the indexes may never see.
  • Write the announcement for buyers, not for AI systems. Google's AI guide says not to rewrite copy just for AI systems, because AI systems can understand synonyms and general meanings, and not to create separate content for every possible variation of how people might search. A clear announcement that says what the product does, who it is for, and how it differs from what the store already sells is the announcement that gets cited.
  • Link the announcement to the product page, and link the product page to the announcement or guide. Links are how a crawler finds the new page, and how a system learns the new page matters.
  • Do not seek inauthentic mentions for the launch. Google's AI guide says seeking inauthentic mentions across the web is not as helpful as it might seem, because its core ranking systems focus on high quality content while other systems block spam, and its generative AI features depend on both.

5. Measure the launch, then wait

  • Run the fixed prompt set, with prompts for the new product added, and log whether the assistants name the new product, whether they recommend it, which pages they cite, and whether the facts they state are right or wrong. Run the same prompts again after the fix has been recrawled, and compare the two runs.
  • Check the Generative AI performance report in Search Console for the new page. The report shows impressions only, by page, country, device, and date, and it has no clicks or queries. A new page with no impressions yet is a page that has not been shown, not a page that has failed.
  • Do not judge the launch from one run. Answers change from run to run, and crawling can take anywhere from several days to several months depending on how often Google's systems decide a page needs refreshing. A product that is not cited in the first week is a product that has not been indexed or recrawled yet, not a product that will never be cited.
  • When a wrong fact appears, trace it to the source: the page, the markup, or the feed. Fix the source, ask for a recrawl, and retest with the same prompts after the recrawl. A wrong price in the first week usually comes from a stale feed or a cached markup block, not from the assistant inventing it.

The fundamentals

These mechanics are shared across every engine and covered in full in their own guides:

Say you run a coffee roaster

Say you sell coffee, and you launch a new single origin bean. You build the product page a week before launch, with the origin, the roast level, the tasting notes, the brew methods it suits, the price, and the shipping terms in plain words. You add Product markup with the same price and availability, check it with the Rich Results Test, and add the bean to the feed with the same values. You confirm the page is in the sitemap, submit the sitemap to Google and to Bing, and ask for a recrawl. You announce it on your own site with a short post about where the bean comes from and who it is for, linking to the product page. In the first week, the assistants do not name it. In the second week, Perplexity cites the post. In the third week, ChatGPT names the bean in two prompts, with the right price. The launch did not make the product famous. It made the product readable, indexed, and citable, and the citations followed the reading.

What this guide does not cover

This guide covers how to launch a new product so AI picks it up. It does not cover how to write the product description in full, which is our guide to writing product descriptions that AI cites, or how to measure visibility in full, which is our guide to measuring your brand's AI visibility, or the transaction layer that turns a recommendation into a sale. A launch gets the product readable and indexed. The rest of the system has to be ready when the shopper arrives.

Check your own brand now

Run the free scan. It takes seconds, no signup, and shows whether AI crawlers can read your pages today: aizii.ai/aeo-scan

Run the free scan

Sources

Note: links marked specific point to the page that supports the claim in this guide. Links marked general docs point to the vendor's general docs section for that topic, not to a page that proves every step. Check the vendor docs for the current path before relying on a menu name or click path in this guide.