Skip to main content

Improve SEO and AI search visibility for your AI Studio sites

Learn how Advanced SEO Support in AI Studio helps search engines, social platforms and AI crawlers read your published site, and how to set up social previews and a sitemap.

M
Written by Matt Phillips

Your AI Studio sites just got a whole lot "louder" for the rest of the internet to hear! Advanced SEO Support improves the SEO readiness of your AI Studio projects. It makes published AI Studio sites easier for search engines, social platforms and AI crawlers to read.


What is Advanced SEO Support for AI Studio?

Advanced SEO Support helps published AI Studio sites become easier for search engines, social platforms and AI crawlers to read. This matters because most AI Studio sites are Single-Page Applications (SPAs). They are fast for people, but they often look like "empty boxes" to bots because they need JavaScript to load. This meant:

  • Google took weeks to index your content.

  • Social previews (on Slack or Twitter) looked blank or generic.

  • AI search tools (ChatGPT or Perplexity) couldn't "read" your site to cite it.

With Advanced SEO Support, supported bots can receive rendered HTML instead of an empty SPA shell. This improves crawlability, supports better social link previews, and makes your published content easier for AI-powered tools to understand.

Advanced SEO Support includes:

  • Pre-render SEO: Helps supported bots receive rendered page content instead of the default SPA response.

  • Social Media & Link Previews: Helps shared links show the correct title, description and preview image.

  • Generate Sitemap: Helps search engines find the important pages on your published site more efficiently.

Together, these tools improve visibility and discoverability, while the normal visitor experience stays the same.


Key benefits of Advanced SEO for AI Studio

  • Rich social previews: When you share a link on LinkedIn, WhatsApp or X, it shows the correct title, description and Open Graph image.

  • AI search visibility: AI-powered search engines (ChatGPT, Claude, Gemini) can understand and cite your content in their answers.

  • Edge-level performance: Pre-rendered pages are served from the Cloudflare edge in under 10ms. It's lightning-fast for bots and has no impact on your actual site visitors.

  • Instant indexability: Search engines receive fully rendered HTML. No more waiting for Google's JavaScript queue; your site can be indexed on the first crawl.

  • Per-project control: You can turn pre-rendering on or off for each project from the settings panel.


Pre-render SEO

Pre-render SEO helps supported bots receive fully rendered HTML instead of the default single-page application shell.

Note: Pre-render SEO is only available for published projects with a connected custom domain.

When you turn it on through Advanced SEO Support, supported bots can access the page content, metadata, images, canonical tags and structured data already on the page. This is especially helpful for search engines and AI crawlers that delay JavaScript rendering or skip it entirely.

Instead of seeing an empty app shell, supported bots receive rendered content on the first request. This improves crawlability, makes your content easier to interpret, and helps your pages show up more accurately in search results, previews and AI-powered experiences.

Key details:

  • Automatic bot detection: Supported search engine crawlers, social media bots and AI crawlers are served rendered HTML automatically.

  • Graceful fallback: If pre-rendering isn't turned on, or a page isn't cached yet, bots receive the standard SPA (the same behaviour as before). Nothing gets worse than it is now.

  • Automatic cache refresh: Pre-rendered pages are regenerated automatically every time you publish, change the domain or update the site. You don't need to clear or rebuild anything yourself. The system handles up to 150 routes per site.

  • Edge-level serving: Pre-rendered pages are served from Cloudflare's edge network in under 10ms. There's no extra delay for bots or visitors.


How to turn on Advanced SEO Support for AI Studio

Turning on Advanced SEO Support switches on the SEO tools available for your published AI Studio project. You set this up from the SEO settings inside the project, and you need a connected custom domain.

From within your AI Studio project, follow these steps:

  1. Open the AI Studio project you want to set up.

  2. Click More at the top of the builder. In the More panel, open SEO & AI search.
    ​

  3. Make sure the project is published, a custom domain is connected, and the custom domain is set as primary.
    For more on publishing AI Studio projects, see Publishing Your AI Studio Projects.
    ​

  4. Click Enable to turn on Advanced SEO Support.
    ​

  5. Check that the toggle turns purple once it's on. Then re-publish the project so the latest rendered output is available to supported bots.
    ​


Social Media & Link Previews

With Advanced SEO Support turned on, links shared on Facebook, Twitter, LinkedIn, WhatsApp, Slack and Discord can show the correct page title, description and Open Graph image, instead of a blank or generic preview. Each page can also have its own title, description and preview image, rather than relying on one site-wide fallback.

The Improve social preview content action uses a Copy prompt workflow to add SEO metadata across the project. When Advanced SEO Support is on, supported bots receive those tags in the rendered HTML, so each page shows the right preview details.

To generate social media and link previews:

  1. Open the AI Studio project you want to update.

  2. Click More at the top of the builder, then open SEO & AI search.
    ​

  3. Find Improve social preview content and click Copy prompt.
    ​

  4. Paste the copied prompt into the AI Studio chat.
    ​

  5. Review the update summary in the builder, then publish your project to apply the changes.
    ​

  6. Use these checks to confirm it's working:

  • Share the live URL on a supported platform such as Facebook, Twitter, LinkedIn, WhatsApp, Slack or Discord. Check that the preview shows the expected title, description and Open Graph image.

  • Use the Facebook Sharing Debugger or Twitter Card Validator to confirm the Open Graph tags are being served.


Generate Sitemap

Generate Sitemap helps search engines find the important pages on your site more efficiently. In AI Studio, the Generate sitemap action uses a Copy prompt workflow to create a sitemap for the project.

Rendered output refreshes automatically when the site is published, updated or moved to a different domain. This helps keep the sitemap in line with your latest site content and structure.

To generate a sitemap:

  1. Open the AI Studio project you want to update.

  2. Click More at the top of the builder, then open SEO & AI search.
    ​

  3. Find Generate sitemap and click Copy prompt.
    ​

  4. Paste the copied prompt into the AI Studio chat.
    ​

  5. Review the update summary in the builder, then publish your project to apply the changes. Click Details to view your sitemap.
    ​

  6. Submit your sitemap to Google Search Console. This helps Google find your URLs and lets you monitor how the sitemap is processed.
    ​


Frequently Asked Questions

Q: Do I need to publish the project before turning on Advanced SEO Support?
Yes. You need to publish before you can finish the custom domain and SEO setup.

Q: Does pre-rendering change how my site looks or behaves for regular visitors?
No. Visitors still get the same fast, interactive SPA experience. Only bots and crawlers are served the pre-rendered HTML.

Q: Does Advanced SEO Support add schema markup automatically?
No. Advanced SEO Support doesn't add schema markup by itself. If you add schema through an AI Studio prompt and it's generated in the page code, supported bots can receive that schema as part of the rendered HTML when pre-rendering is on.

Q: How does the cache refresh work?
The cache refreshes automatically when you publish the project, change the connected domain, or update the site and re-publish.

Did this answer your question?