Alli AI SEO: what the snippet changes, how it serves pages to AI crawlers, and what to check before you buy

Alli AI is SEO automation software that works through a code snippet on your site. It does two things. It writes and deploys on-page changes such as titles, meta descriptions, schema and internal links across many pages and sites at once. And it serves a pre-rendered HTML version of your pages to AI crawlers such as GPTBot, ClaudeBot and PerplexityBot, so a site built with JavaScript can be read by assistants that do not run JavaScript. Alli's homepage, read on 22 October 2026, calls the product an "AI Search Visibility Platform" for AEO, GEO and SEO automation. This page explains how each half works, what Google says about the method, and what to check before you buy.

Everything about Alli here comes from alliai.com pages we read on 22 October 2026: the homepage, the FAQ, the AI crawler page, the WordPress plugin page and Alli's own comparison with Peec AI. We do not restate its prices.

Half one: the SEO Automation Engine

Alli's FAQ describes the workflow in three steps. Install the code snippet. Review the Recommendations Alli writes, editing any suggested title tags or meta descriptions you want to change. Click Approve, and the changes go live. Alli says no automated code change goes live until you approve it, and that it recrawls your site and refreshes its Recommendations every week.

The features Alli lists for this half are:

• Bulk on-page SEO automation, where one rule (for example, "add product schema to every page under /products/") is applied across every site you manage
• A visual SEO editor for changing page elements from the front end
• An AI schema markup generator and AI internal linking automation
• Keyword rank tracking, which you can set to daily, weekly or monthly
• SEO A/B testing, a site speed optimiser and white label reports

Alli markets this half to agencies running many sites, and the FAQ says its entry plan covers up to five websites. It also says Alli does not support domains in non-Roman alphabets, such as Cyrillic or Chinese domain endings, so check that if you run international sites. The FAQ offers a 10-day free trial.

Half two: the AI Search Visibility Engine

This is the part that puts Alli in the AI visibility category. Alli's case is simple: many modern sites build their content with JavaScript in the browser, and AI crawlers that do not run JavaScript receive an almost empty page. Alli says its engine detects more than 50 search and AI crawlers at request time and sends them fully rendered HTML, while human visitors keep getting your normal site.

Alli says this installs in under an hour through the snippet, a WordPress plugin or a tag manager, with no rebuild. It also says that if Alli is ever unreachable, requests pass through to your site normally. Its crawler page adds that it configures Cloudflare and similar security tools so legitimate AI crawlers are let through while bad bots stay blocked, and it shows crawler visits on a live dashboard.

Alli published research in May 2026, its Fortune 100 AI Accessibility Report, which it says found 46% of Fortune 100 corporate sites return blank pages to ChatGPT's crawler. That is Alli's own figure from its own crawl. Run the test below on your own site rather than relying on any average.

What Google says about serving crawlers a different version

Sending crawlers a pre-rendered page while people get the JavaScript version is what Google calls dynamic rendering. Google's documentation, read on 22 October 2026, says three things about it:

• It "is a workaround and not a recommended solution, because it creates additional complexities and resource requirements."
• Googlebot "generally doesn't consider dynamic rendering as cloaking", as long as the rendered version has similar content to what people see.
• For a long-term fix, Google points to server-side rendering, static rendering or hydration, which give every visitor and every crawler the same HTML.

So the rule is parity. If the version Alli serves to crawlers says the same thing as your real page, you are inside Google's description. If you can rebuild your templates to render on the server, that removes the need for the workaround. Our comparison of JavaScript rendering and server-side rendering for AI crawlers shows what the first response looks like in each case.

Check your own site first

You can see what an AI crawler receives in two minutes with curl. Ask for a page with a GPTBot user agent and count the words in the reply:

curl -s -A "GPTBot" https://www.example.com/your-page | sed -e 's/<[^>]*>//g' | wc -w

If the number is close to what a person reads on the page, crawlers already get your content and a rendering fix adds little. If it is close to zero, your content is built in the browser, and either a rendering service like Alli or a move to server-side rendering will change what AI crawlers can read. Repeat it for your main templates: home, a service or product page, and a blog post.

Questions to ask before you buy

1. What does a crawler get, compared with a person? Ask for a sample of the pre-rendered HTML for three of your pages and compare it with the live page.
2. What stays if you cancel? Changes deployed through a snippet are served by that snippet. Ask which changes remain on your site if it is removed, and export your approved titles, descriptions and schema so you can move them into your CMS.
3. Which crawlers are on the list? Alli names more than 50. Check that the search crawlers of the assistants your buyers use are among them.
4. Who approves changes? On a client site, agree who clicks Approve, since that is the step that publishes.

Readable is the start, not the result

Alli is clear about its own scope. On its comparison page with Peec AI, it lists brand mention tracking across assistants as "Not the product", and describes its job as making your content readable so an assistant can cite it. That is a useful split. Being readable lets an engine use your page. It does not tell you whether ChatGPT, Gemini, Perplexity, Claude or Google AI Overviews actually name you when a buyer asks who to choose.

That second question is the one AI Knows Us answers. We ask your buyers' questions in all five, record who gets named and which sources each answer leans on, then write the pages and earn the mentions that move the answer. After a rendering fix, a free scan at aiknowsus.com shows whether the assistants have started to name you, which is the result the fix was for.

Questions about Alli AI

What is Alli AI used for?

Two jobs: bulk on-page SEO changes deployed through a code snippet, and serving pre-rendered HTML to AI and search crawlers so JavaScript-built pages can be read. Its site markets it to agencies, enterprises and ecommerce stores.

Is Alli AI's pre-rendering cloaking?

Google says dynamic rendering is generally not cloaking as long as crawlers get content similar to what people see. Google also calls it a workaround and recommends server-side or static rendering as the lasting fix.

Does Alli AI work with WordPress?

Yes. Alli publishes a WordPress plugin, the Alli AI Visibility Engine, which serves pre-rendered HTML to GPTBot, ClaudeBot, PerplexityBot and other AI crawlers. It also installs through a snippet or a tag manager on other platforms.

Does Alli AI track whether ChatGPT mentions my brand?

Not as its main product. Alli's comparison with Peec AI lists brand mention tracking as not its product, and points to crawler-traffic monitoring and readability checks instead.

Do changes go live without my approval?

Alli's FAQ says no automated code change goes live on your site until you approve it, and that approved changes go live within seconds.