Skip to main content

Get your product cited by ChatGPT, Claude and Perplexity

An answer-engine playbook for demos, covering which demos to make readable by AI assistants, how to write their name and description, and how to keep them fresh.

Updated Oct 15, 2026

Get your product cited by ChatGPT, Claude and Perplexity

Overview​

Buyers increasingly ask an AI assistant about a product before they ever visit its website. Walnut demos are JavaScript apps, so by default those assistants and search crawlers can't read them. With Make readable by AI and search engines, Walnut serves recognised bots a short text summary of a public demo, with a link back to the interactive player.

This playbook helps you decide which demos to open up, how to write the text an assistant will actually read, and how to keep it accurate over time.

Snapshot​

Pick the demos you want an assistant to point to​

Not every demo should be discoverable. Think about the questions a buyer types into ChatGPT, Claude or Perplexity early in their research, such as "how does this product handle approvals?" or "what does the dashboard look like?" The demos worth opening up are the ones that answer those questions well for anyone.

Good candidates:

  • Feature tours that show one capability end to end.
  • Website embeds such as the product tour on your homepage or a product page.
  • Top-of-funnel overviews that explain what your product does in a few minutes.

Keep these gated or private:

  • Lead-capture demos. If a demo has an email gate, Walnut never serves the summary, whatever the toggle says. That's by design: a demo that captures leads is never exposed to indexing.
  • Deal-specific or personalized demos. Anything built for one account belongs behind your normal sharing settings. Crawlers never see variables or recipient-specific content anyway, so a personalized demo adds nothing to an assistant's answer.
  • Demos with an access code, or ones that are expired or archived. These don't qualify either.

The setting is off by default and lives on each demo, so you opt in one demo at a time.

Example: A team has a homepage tour, three feature tours and a set of gated demos used in outbound. They turn on the toggle for the homepage tour and the three feature tours, and leave the gated demos alone.

Write a name and description an assistant can quote​

When a bot requests the demo, Walnut returns only a small page: the demo name, the demo description (if you wrote one), the first paragraph of the demo's AI-generated summary, and the canonical player URL. Screen content, guide text and narration are not included. Whatever an assistant says about your demo comes from those few lines.

Write them so they still make sense when quoted on their own:

  • Name the product and the job. "Product tour" tells an assistant nothing. A name like "Approval workflows in YourProduct: guided tour" names both the product and what the demo covers.
  • Lead the description with the outcome. One or two sentences on what the viewer will see and what problem it solves. Assume the reader has never heard of you.
  • Use the words buyers use. If prospects call it "expense approvals," don't only call it "spend governance."
  • Leave out internal jargon and campaign names.

The AI summary is generated by Walnut from the demo itself (it's the same summary used by Buyer Xpert). You don't write it directly. A demo with a clear storyline and well-written guides gives the summary better material. Until a demo has been summarised, crawlers see only the name and description, which is one more reason to write a good description.

Keep it fresh​

An assistant can only be as accurate as the text it read.

  • Update the name and description when the product changes. Changes are picked up on the next crawl.
  • Rely on re-summarising for content changes. The AI summary is rebuilt whenever Walnut re-summarises the demo.
  • Re-copy the embed code after you change the setting, name or description of an embedded demo, so the embed carries the current indexability.
  • Retire carefully. Turning the toggle off, adding an email gate, or archiving the demo stops Walnut serving the summary immediately. Assistants and search engines cache what they've already read, though, so an old answer can keep surfacing for a while. Walnut can't clear their caches.

Check what a crawler sees​

Don't guess. Fetch the Markdown version of the demo in your browser or terminal:

https://api.teamwalnut.com/public/demos/DEMO_ID.md

Replace DEMO_ID with your demo's ID. If the demo is eligible, you'll see exactly what Walnut returns to assistants. If you don't see your summary, check the eligibility list in the reference article: access must be Anyone with the link, with no email gate, no access code, and the demo not expired or archived.

Read it as a stranger would. If the name and description alone don't tell you what the product does, rewrite them.

Pair it with your website embeds​

Readable demos work alongside your website embeds, not instead of them. Your marketing page's own meta tags still control that page's indexability. The toggle governs the Walnut player URL, and the embed serves the readable summary to bots that reach the Walnut iframe directly.

A good pattern:

  1. Embed a short tour that follows the website playbook: your product's main flow, no more than 10 guide steps, with a clear call to action.
  2. Turn on Make readable by AI and search engines for that demo and give it a strong name and description.
  3. Re-copy the embed code and update it on your page.

When an assistant cites the demo, its link opens the full interactive player, and visitors get the same experience as anyone on your site.

Tips for a better result​

  • Start with your two or three most-viewed public demos rather than everything at once.
  • Make names unique. Several demos called "Overview" are hard for an assistant to tell apart.
  • Review public demos' names and descriptions as part of every launch checklist.

Key takeaways​

  • Assistants see only the name, description, first paragraph of the AI summary and the player URL, so those few lines carry all the weight.
  • Only public demos with no email gate or access code, and not expired or archived, qualify. The toggle is off by default.
  • Open up feature tours, website embeds and overviews. Keep lead-capture and deal-specific demos gated.
  • Check the Markdown URL to see what a crawler sees, and re-copy embed code after changes.
Was this helpful?