Your website. Ready for search. Readable by AI.

BetterEO is a visibility CDN. It sits in front of your website, renders your pages ahead of time in a real browser, and serves that fully rendered HTML to search engines and AI assistants, or clean Markdown to the AI assistants that ask for it. Your visitors keep going straight to your site.

Add your domain in the BetterEO console, then create two DNS records at your DNS provider: a CNAME that points your domain to edge.bettereo.com (on a root domain, use CNAME flattening, ALIAS or ANAME), and a TXT record at _bettereo-verify on your domain that proves you own it. Once both are found, BetterEO activates the domain and renders the pages in your sitemap. The console's Check DNS button shows which record is missing or wrong.

Yes. As soon as you add a domain, it gets a preview address that serves your site the way BetterEO will once your DNS points here, and Fetch as crawler shows what each crawler gets for any URL. BetterEO renders your pages once your DNS points here.

Yes. As soon as you add a domain, it gets a preview address such as www-example-com-3f9a1c2e.bettereo.com that serves your site the way BetterEO will once your DNS points here. Search engines are told not to index it. On the domain’s page, Fetch as crawler shows what Googlebot, Bingbot, GPTBot, ClaudeBot, PerplexityBot or a normal browser gets for any URL of your domain: the status, the headers, the HTML or the Markdown, and whether it came from BetterEO’s cache or from your site. BetterEO renders your pages once your DNS points here, so until then crawlers get your site’s own response. After the switch, fetch again to see what BetterEO serves on your domain. Each user can run 30 fetches per hour in a project.

Crawlers keep getting fully rendered HTML, served the way search engines already accept. What changes: setup is two DNS records instead of middleware, server rules or CDN configuration; AI assistants also get clean Markdown and a generated llms.txt; you see SEO, AEO and security scores without and with BetterEO; and you pay for render time by the second instead of a plan, with unchanged pages checked rather than rendered again. Keep your current setup until BetterEO has rendered your pages, then remove it.

Search engine crawlers such as Googlebot, Bingbot, DuckDuckBot, Applebot and YandexBot; AI crawlers and assistants such as GPTBot, ChatGPT-User, OAI-SearchBot, ClaudeBot, PerplexityBot, Amazonbot and Common Crawl; and the link-preview bots of apps such as LinkedIn, Slack and WhatsApp. Everyone else is sent to your site.

Cloaking means showing crawlers different content from what visitors see. BetterEO serves crawlers a snapshot of the same page your visitors get, rendered by a real browser, and the Markdown version is a conversion of that same content. Nothing is added or hidden, and your page's noindex, canonical and language signals are kept. Google calls this dynamic rendering: it accepts it when the content matches, but describes it as a workaround and recommends server-side rendering for the long term.

BetterEO fetches pages with three bots that name themselves in their user agent: BettereoRenderer renders the pages of the sites connected to BetterEO, BettereoAnalyzer fetches the pages you ask BetterEO to analyse, and BettereoSecurityScanner checks your site’s security headers when you run a security scan. If your site uses bot protection or a web application firewall, allow requests whose user agent contains BettereoRenderer, BettereoAnalyzer or BettereoSecurityScanner, or BetterEO may get a challenge page instead of your content. BetterEO bots describes all three.

BetterEO changes what AI assistants get, with Markdown and llms.txt, and measures the result: AEO scores without and with BetterEO, the pages AI assistants fetch to answer prompts and the visits their answers send you, all from your site's real traffic. It doesn't track how often your brand is mentioned in AI answers to prompts you choose; if you need that, an AI-visibility tool complements BetterEO.

For SEO and AEO, without BetterEO is what a crawler that doesn't run JavaScript gets from your own server, and with BetterEO is what BetterEO serves crawlers. For security, your origin is scanned directly, bypassing BetterEO, and compared with your site as visitors get it through BetterEO. The difference is what BetterEO changes; anything it can't fix is marked as needing a change on your site.

Nothing they need to notice. Visitors are always forwarded to your own server, so rendering is never in their path, and they only get the security protections you turn on. Search engines and AI assistants get the cached render.

No. Visitors are always forwarded to your own server, so rendering is never in their path. If a page hasn't been rendered yet, or its cached copy is too old or can't be read, crawlers get your server's response, just as they would without BetterEO. BetterEO's edge runs on a global CDN network, so, as with any CDN, your domain's traffic does pass through it.

They can, which is why each protection is off until you choose it and shows its risk first. Most are low risk. HSTS and anti-framing are medium risk, so HSTS moves up in stages from 5 minutes to 1 year, and anti-framing lets you list the sites that may still show your pages in a frame. A protection is never added when your site already sends it. You can turn any protection off at any time, although browsers remember HSTS until its current stage ends.

No. Every SEO, AEO and security automation, including Markdown serving and the generated llms.txt and robots.txt, is off until you turn it on for a domain, and you can turn each one off again at any time. What is always part of the service is the prerendering itself, the redirect from HTTP to HTTPS, and a generated sitemap.xml that is only served when your site has none.

Pages are checked on the schedule you set. Before a scheduled render, BetterEO checks with a single request to your site whether the page changed since its last render: an unchanged page keeps its render and only the check is billed, as render time, at 50% of the time it takes, because a check mostly waits on the network rather than using the CPU. A changed page, a sitemap lastmod that moves or a render you ask for gets a full render. Content that JavaScript loads later may not be detected, so you can re-render a page, or clear the cache for a page or the whole domain, at any time.

There are no plans and no base fee. Each month a project is billed for what it has and uses: its domains beyond the ones included, the render time of its pages (billed per second), and the analyses and llms.txt generations it runs, each at its own unit price shown in the console. Your first project starts with a 14-day trial with every feature and no card needed. If no payment method is added by the end of the trial, the project is paused: renders, analyses and llms.txt generations stop and crawlers and visitors go straight to your site, nothing is deleted, and adding a payment method resumes it. Usage limits protect every account; contact us to raise them.

Only once what you owe reaches €10. Every month still gets its invoice, but while the amount you owe is below €10 nothing is charged: it is carried over and added to the next month, so a small project may only be charged every few months. The console shows what is carried over and labels each invoice carried over or charged. When a project ends, what it still owes is charged then, even below €10; amounts under €0.50, too small for a card payment, are not charged.

robots.txt is built from a template, with your choice of which AI training and AI search crawlers may read your site, and costs nothing extra. llms.txt and llms-full.txt are written from your home, about and privacy pages, with an AI model summarising the site, when you ask for it or on a weekly or monthly schedule you choose. Each llms.txt generation is billed on its own, separate from renders. Each file is only served when your site doesn't have its own.

No. The BetterEO MCP server is read-only: each token reads one project and can’t change anything, and you can revoke it at any time. Your assistant suggests fixes, and the code changes happen in your own codebase.

Yes. BetterEO runs an MCP server at mcp.bettereo.com. Create a read-only token for a project in the console and add the server to Claude Code, Cursor, VS Code or any other MCP client. Your assistant can then read your bot analytics, SEO and AEO scores and findings, security scan results and the pages BetterEO serves crawlers, and suggest fixes in your code. Each token only reads its own project, and you can revoke it at any time.