AI readable content fixes this: your website’s server adds the widget’s content to the page as plain HTML, so these tools can read it.
More and more people ask AI tools about a business before they buy. When an AI agent visits your page, AI readable content lets it read your reviews, ratings and sources instead of an empty widget. Not every AI agent is guaranteed to use it.
Turn on AI readable content
- Open your widget and click Embed widget.
- Click AI readable content.
- Click Copy URL. Each widget has its own public URL:
https://embedsocial.com/api/widgets/{widget-ref}/fragment. It needs no API key, and the ref is the same value as data-ref in your embed code. - Add the server-side snippet to your page template, right after the widget embed code. The AI readable content window has ready-to-copy code for PHP, Node.js, Next.js and cURL.
AI readable content is available on every plan. It’s a server-side setup, so you or your developer need access to the page template.
How it works
Your server requests the widget’s fragment while it renders the page and prints it right after the embed code. The fragment is plain HTML, visually hidden with an inline style. Visitors keep seeing the regular widget, while crawlers and screen readers can read the content.
The fragment includes:
- Up to 20 items from the widget’s first page
- A summary with the total item count, average rating and source names
- For each item: author, rating, date, source, title, text and a link to the original
It adds about 10 to 20 KB of HTML and no JavaScript. A fresh request adds about 200 to 300 ms to the page response (2 seconds at most, the timeout). Pages served from your cache add nothing.
Implementation rules
- Request the fragment on your server. Don’t load it with browser JavaScript, because crawlers that skip JavaScript would never see it.
- Print the response body as-is. Don’t escape, edit or hide it with display: none or the hidden attribute.
- Print nothing when the status isn’t 200, the body is empty or the request fails. Use a 2-second timeout.
- Cache the result on your server for 5 minutes.
A 404 response means the widget is off, “Show widget on website” is disabled, the account has no active subscription or reached its view limit, or the widget has no items yet. A newly published widget can return 404 for a few minutes. New items can take up to about 10 minutes to appear.
Website builders and static sites
Hosted builders such as Shopify, Wix, Squarespace and Webflow usually can’t request a URL while a page renders, so the fragment can’t be added there directly. Use edge injection instead, for example a Cloudflare Worker or Vercel/Netlify edge middleware. On static sites, fetch the fragment at build time and rebuild regularly, or inject it at the edge.
Use it responsibly
Only add the fragment to pages where the visible widget shows the same content. Search engines can treat hidden text that differs from what visitors see as spam, so don’t edit the fragment, and don’t add rating schema for content that isn’t visible.
Optional: add Schema code for star ratings
Schema code is a separate feature. It adds review structured data to the page, which search engines can use to show star ratings in results. It doesn’t replace AI readable content.
What the Schema code includes
The Schema code includes:
- Your average star rating
- Your total number of reviews
- The individual review content included in the structured data
How to get and add your Schema code
You can copy your Schema code from inside your widget, under the 'Schema' tab, and paste it into the header/body of the page where your widget is embedded. For full step-by-step instructions, see Embed codes.
Note: Schema code is available only on certain plans, see the pricing page. AI readable content is available on every plan.
If you have any questions, click the bottom right chat icon to talk with our customer success team or send us an email at support@embedsocial.com We're here for you 🙏