Make your social experience discoverable by AI assistants

Learn what AI assistants read from a hosted social experience, why embeds on your own site stay invisible to them, and which controls decide what gets cited.

AI assistants and other large language models (LLMs) answer from text they can fetch. They don't watch video, and most of them don't run JavaScript.

What they read on your hosted social experience is the HTML each video page serves before any script runs. That video page is the unit of AI discoverability, the same way it's the unit of search visibility.

Discovery by an LLM doesn't come from keyword stuffing or passive indexing. It comes from clear semantic context: communities and groups with real descriptions, captions written as sentences, and content that stays brand-safe, current, and trustworthy.

Onsite places your video on the sites and apps you own; for the whole product, see Onsite: what it does and where to start. For how crawlers reach your pages at all, see How search engines and AI crawlers index your hosted social experience.

What an AI engine reads on a video page

Every video page on your hosted social experience ships a server-rendered text block in its initial HTML. Visitors see the player, while crawlers and screen readers see the text underneath it, which mirrors what the player shows.

ElementSource
The title, as the page's only h1The video's title, or the first sentence of its caption
A descriptionThe caption, when it differs from the title
The transcript, under a "Transcript" headingThe spoken words of the video, when Genuin has them for that video
"By" and a link to the authorThe creator's profile, or your brand page for brand posts
The publication dateWhen the post was published
"From the … community" and "Posted in …", with their descriptions and linksThe community and group the video belongs to
View and like countsThe post's engagement
TagsThe video's keywords

The same facts repeat as a schema.org VideoObject in JSON-LD. It carries the name, URL, description, thumbnails, upload date, duration, and MP4 URL, plus the transcript and keywords when present.

The author is a Person or, for brand posts, an Organization with its description and logo. InteractionCounter entries give views, likes, comments, and shares. Nothing is invented: Genuin leaves out a field it doesn't have rather than filling it with a placeholder.

Every published video gets this treatment, whether it's brand-authored or curated, a member discussion, a creator or expert contribution, or shoppable or educational content.

Communities and groups work as semantic containers. Their names and descriptions set topic boundaries, editorial intent, and the areas where your brand has authority, and every video page quotes them.

Community and group pages serve their name, their description, and links to their videos. The video sitemap lists every published video with its title, description, thumbnail, MP4 URL, view count, and publication date.

What an AI engine can't read

  • Embeds on your own site. The Web SDK renders the feed in the browser after the page loads and injects no text or structured data into your page's HTML. A crawler that fetches your product page sees the empty container, so the videos become readable only on their community pages.
  • The feed itself. Contextual feeds, How Contextual Continuity embeds work, and How Generative Contextual Continuity embeds work decide what a visitor sees. They change nothing about what a crawler fetches, because page context, continuity across pages, and generated sections live in the request a browser makes.
  • Anything behind sign-in. Private communities and groups aren't crawlable.

In your Business Account, a community's Community Type is Public or Private. A group's Who can see this Group is Everyone, which includes people without an account, or Group Members only.

So the path from your website to an AI citation runs through links. A page that embeds a feed gives crawlers nothing, but a plain link to a community, a group, or a video does. The share links Genuin generates are those URLs.

Control what AI engines find

  1. Write captions as sentences. The caption is the page's description, and the headline in results when there's no title. A caption of hashtags describes nothing, so say what the video shows in a sentence or two, then add tags.
  2. Give communities and groups real descriptions. They're served on their own pages and quoted on every video page under "From the … community" and "Posted in …". A one-word description is a one-word answer.
  3. Fill in creator and brand profiles. The author's name, bio, and page go out with every video. A creator with a bio is an entity an engine can name; one without is a handle.
  4. Keep AI crawlers allowed. The robots.txt on your hosted social experience allows every crawler by default, so GPTBot, ClaudeBot, PerplexityBot, and the search crawlers can all fetch your pages. To allow search engines but block AI training crawlers, ask support@begenuin.com for per-crawler rules, because Business Account has no robots.txt editor.
  5. Link to your hosted social experience, and submit the sitemap. Link community and video URLs from your navigation, articles, and product pages. Submit https://<your-domain>/sitemap/index.xml to Google Search Console and Bing Webmaster Tools, after you move to your own domain with White-label your hosted social experience.

In your Business Account, a community's description is its Purpose of this community field, and a group's is its Description, up to 300 characters. You edit them under Manage > Communities and Manage > Groups. Your brand's Bio is under Settings > Brand Profile and takes up to 150 characters.

Fresh pages help too. Each video page's lastmod in the sitemap is its last update, and engines revisit pages that change.

Keep governance on as well. With AI moderation and editorial approval in place, every page an engine reads has passed your brand and community guidelines first. Learn more about Moderation Baselines and Queue.

Send embed visitors to your hosted social experience

Embeds don't make content readable to AI engines. Their settings decide whether visitors, and the links they share, reach the pages that are.

  1. In your Business Account, go to Grow > On Site and select Embed.
  2. Click + New to create an embed, or open one from the Embeds list.
Step 2: The Embeds list, where + New starts a new embed.
  1. Choose the Community and Group the embed draws its videos from.
Step 3: The Community and Group pickers set where the embed's videos come from.
  1. For a Standard Wall embed, under View Settings, select Show Join Community Button and Show Community Share Button so visitors can join the community and share links to it.
Step 4: View Settings for a Standard Wall embed, with the join and share buttons turned on.
  1. For a Carousel embed, select the Expand View tab, and under Engagement Details select Enable Engagement Tools to let visitors Repost, Spark, Comment, and Share.
  2. Select Enable Redirection, then select Community, Group, and User so visitors can open the community, group, or user profile page from the embed.
Step 6: Engagement Details on the Expand View tab, with redirection to community, group, and user pages.
  1. Click Generate Code or View Embed Code to copy the embed code.

Page and category context reach the feed through the Web SDK, not through these settings. Learn more in Deliver contextual feeds with page, user, and location context and Generate an embed code in your Business Account.

What this isn't

  • Contextual feeds make your embeds relevant to the page a visitor is on. They're worth doing for visitors, but they don't make content discoverable to engines.
  • Open access to your data. AI engines read only your public pages. Private communities and groups, and videos that haven't passed moderation, never reach them, and nothing moves your content to an external platform.
  • Marketplace > LLMs in your Business Account is where you add AI models for your own Supervised Intelligence capabilities. It has no effect on how outside assistants see your hosted social experience. Learn more about adding AI capabilities, tools, and models from the Marketplace.
  • A player inside the assistant. To have AI assistants render your own player inline, see Generative Player for LLM Applications.
  • llms.txt isn't served on hosted social experience domains. If you publish one for your own website, link community and video URLs from it.

Limitations

  • Transcripts aren't exposed today. The page renders a transcript whenever the feed API supplies one. The API doesn't supply transcript text, so the "Transcript" section and VideoObject.transcript are absent.
  • Embeds are invisible to crawlers. Nothing in the embed builder changes this.
  • No self-serve robots.txt. Per-crawler rules go through support.
  • Profile and brand pages aren't in the sitemap. Engines reach them through the author links on video pages.
  • No llms.txt or llms-full.txt on hosted social experience domains.

See also

TRUST AND COMPLIANCE

© 2026 Genuin Inc.

Genuin Footer