Navattic AI Visibility: Making Embedded Demos Readable (2026)
Vorec Team · 2026-10-17 · About 8 min read
An interactive product demo is often the most detailed description of your product on your website. It walks through screens, names the buttons and shows what happens next. It usually sits inside an iframe, built from captured screens and script. Whether a search engine or an AI system can read any of that is a fair question.
Navattic, an interactive demo platform, shipped a direct answer in its September 2026 product updates. The feature is called AI visibility. When you turn it on, Navattic's Copilot writes a plain-text walkthrough of the demo and puts it in the embed code. Visitors don't see it, but the text sits in the page's raw HTML.
This post covers what Navattic documents, what Google's own policies say about text that visitors don't see, and the practical questions to check before you rely on the feature. We have not tested it. Where something is our reading rather than a vendor's statement, we say so.
Checked on 17 October 2026. Sources: Navattic's product updates (September 2026 section) and its embed documentation, Google's spam policies (page last updated 28 August 2026) and Google's robots meta tag documentation. Vendor features change, so re-check them before you decide.
What Navattic says the feature does
From Navattic's changelog and embed docs:
- The problem it targets. Navattic says demo content inside an iframe is normally invisible to AI crawlers and search engines. That is Navattic's framing. We come back to it below.
- What it generates. With AI visibility on, Copilot generates a plain-text walkthrough of the demo and includes it in the embed code. According to the docs, visitors don't see the text, but AI crawlers and search engines can read it.
- What the text is built from. The demo's step content, such as step names, dialog text and button labels.
- How you turn it on. In the embed modal, select the AI visibility toggle under Customizations, wait for Copilot to generate the walkthrough (the copy buttons stay disabled until then), then copy the embed code.
- A prerequisite. Publish the demo before turning the toggle on. The walkthrough is generated from published step content.
- It does not update itself. The docs say the text is fixed into the snippet when you copy it. If you change and republish the demo, copies already embedded on your pages keep the old text.
The changelog adds that this lets crawlers which don't run JavaScript read what the demo shows. Navattic's materials we read don't say which plans include AI visibility, so check that with Navattic.
Is the premise right? What the documentation supports
Two separate claims sit underneath the feature. They have different evidence.
"Iframe content is invisible to search engines." For Google, the documentation is more nuanced. Google's robots meta tag documentation describes an `indexifembedded` rule that allows Google to index a page's content when it is embedded in another page through iframes, even if that page has a `noindex` rule. That rule only makes sense if Google can index embedded content at all. Our reading: "invisible" is too strong as a statement about Google. Whether embedded content is credited to your page in a way that helps you is a separate question, and the Google documentation we read doesn't promise it.
"AI crawlers don't run JavaScript." We looked into this in September, in Do AI crawlers run JavaScript?. On the crawler documentation pages we checked from OpenAI, Perplexity and Anthropic, we found no statement either way. Navattic's framing may well be right for some crawlers. It is a reasonable precaution. It is not a documented fact about every AI crawler.
What both claims point to is simpler: text in the raw HTML of your own page doesn't depend on whether a crawler runs JavaScript or follows an iframe. Navattic's feature is one way to get it there.
The question to ask: hidden text and Google's spam policies
Google's spam policies have a section on hidden text and link abuse. They describe it as placing content on a page only to manipulate search engines, in a way human visitors can't easily see. Examples include white text on a white background, text positioned off-screen with CSS, and font size or opacity set to 0.
The same section lists hidden content that does not violate the policies, including accordion or tabbed content, sliders, tooltips, and text meant only for screen readers to improve the experience of people who use them.
Navattic's docs say the walkthrough is hidden from visitors. They don't say how it is hidden. What follows is our reading, not Google's or Navattic's:
- Intent and accuracy matter. The policy targets text whose sole purpose is to manipulate search engines. A walkthrough generated from the demo's own steps describes content that visitors do see when they open the demo, which is different from keyword-stuffed filler.
- Staleness is the practical risk. Because the text is baked in at copy time, a demo that changes after you embed it can leave a walkthrough describing steps that no longer exist. Hidden text that doesn't match what visitors see is exactly the kind of mismatch to avoid.
- We can't rule on it. Only Google decides how its policies apply to a specific page. If you're cautious, the conservative alternative is visible text: a short written summary or step list next to the demo, which every visitor and every crawler can read.
A checklist before you turn it on
- Publish the final version first. The walkthrough comes from published steps, and it won't update itself later.
- Read the generated text. Check that it describes the demo accurately: the right product names, the right order, no claims the demo doesn't make.
- Re-copy the embed after every demo change. Add it to your demo update routine, or the hidden text will drift away from the demo.
- Inspect the live page. View the page source and confirm the walkthrough text is in the HTML your server sends.
- Consider a visible summary too. A short paragraph or numbered step list next to the demo helps visitors who won't click through, and it isn't hidden at all.
- Confirm plan availability with Navattic. The pages we read don't state it.
What this says about demo and tutorial content generally
Navattic's feature is a sign of a wider point, and this part is our reading. Product content that lives only inside an interactive or video player depends on how each crawler handles that player, while plain text on the page does not. Interactive demos, videos and screen recordings are good at showing. Text is good at being found and quoted.
The durable fix is to publish both: the experience, and a written version of the same steps. For video tutorials, that means a transcript or a step-by-step written guide on the same page. For interactive demos, it means a visible summary or step list. If you are choosing between demo formats, our comparison of Storylane and Navattic and our roundup of product demo video software cover the trade-offs.
Where Vorec fits
Vorec focuses on narrated tutorials and written guides rather than interactive click-through demos. It records your screen, with its own macOS recorder or from a recording you upload, and drafts narration matched to the workflow it captured, then generates the voiceover, so nothing is spoken into a microphone. In the editor you can add smooth cursor motion, cursor-follow zoom and click-based auto-zoom, and freeze-sync can hold a frame to give an explanation time to finish.
The same capture can also produce a written step-by-step guide, with annotatable screenshots. That gives you the plain-text version of the walkthrough as ordinary visible content you can publish beside the video. An AI agent can drive the recording too: Vorec's `record-tutorial` skill lets Claude Code or Codex plan a walkthrough and drive the recorder through the CLI, with the capture kept local for you to review before anything is uploaded.
Plans are listed on the Vorec pricing page. Trial includes up to 3 projects; exports carry a watermark.
FAQ
What is Navattic AI visibility?
An embed setting, announced in Navattic's September 2026 product updates. When it's on, Navattic's Copilot writes a plain-text walkthrough of an interactive demo and includes it in the embed code. The text is hidden from visitors but present in the page's raw HTML.
Does the AI visibility text update when I edit the demo?
No, according to Navattic's embed documentation. The text is baked into the snippet when you copy the embed code, so you need to re-copy and replace the embed after changes.
Is hidden text against Google's guidelines?
Google's spam policies prohibit hidden text placed solely to manipulate search engines, and list accepted cases such as tabs, accordions, tooltips and screen-reader-only text. How the policy applies to a specific implementation is Google's call. Keeping the text accurate, or adding a visible summary, is the conservative approach.
Can Google index content inside an iframe?
Google's robots meta tag documentation describes an `indexifembedded` rule that lets Google index a page's content when it is embedded through iframes, which indicates Google can index embedded content. It doesn't promise that the content is credited to the page that embeds it.
Do AI crawlers run JavaScript?
The crawler documentation we checked from OpenAI, Perplexity and Anthropic doesn't say either way. Putting important content in the page's HTML avoids depending on the answer.
Want the recording to narrate itself? Record with Vorec, or upload one you already have, and get a narrated tutorial plus a written guide. Start free. 7-day trial, 100 credits, no credit card required. Trial includes up to 3 projects; exports carry a watermark.