Features
Render. Improve. Understand.
Everything you need to understand and improve how machines see your site.
Render
Deliver the complete page
Modern sites rely on JavaScript that many crawlers cannot run, or run slowly. BetterEO renders your pages ahead of time and hands crawlers a version they can read in full.
Who gets what
- Search engines get the cached render instantly, as complete HTML.
- AI assistants get a Markdown version when they ask for it.
- Visitors go straight to your site, so rendering is never in their path.
Prerendered HTML
- Fully rendered HTML for crawlers that don’t run JavaScript, served from a cache at the edge.
- Works with sites built with React, Vue, Angular and other JavaScript frameworks.
- Rendering as mobile, desktop, or both.
Render scheduling
- Pages discovered from your sitemap.
- Per-domain render schedules keep caches fresh.
- Render up to 100 pages matching a URL pattern on demand.
- Re-render a page, or clear the cache for a page or the whole domain, at any time.
Quick checks
- Before a scheduled render, a single request checks whether the page changed since its last render.
- An unchanged page keeps its render: only the check is billed, at 50% of its time.
- A changed page, a sitemap lastmod that moves or a render you ask for gets a full render.
Only good renders are cached
- A render that hits a bot check, shows only a cookie wall or comes out almost blank is never served to crawlers.
- The previous good version stays.
- Pages marked noindex aren’t cached at all.
- The console says what happened and how to fix it.
Built-in signals
- Plain HTTP is redirected to HTTPS.
- Rendered pages carry a canonical Link header.
- A sitemap.xml of your rendered pages is served when your site has none.
- Your page’s noindex, canonical and language signals are kept.
For AI assistants
- A Markdown version of each page, announced in a Link header.
- Generated llms.txt, llms-full.txt and robots.txt.
- Each file is only served when your site doesn’t have its own.
- Off until you turn them on for a domain.
Improve
Improve what matters
Improvements BetterEO applies at the edge, per domain. Each one is off until you turn it on, and you can turn it off at any time.
You stay in control
- Every SEO, AEO and security automation starts off.
- Each security protection shows its risk first.
- A protection is never added when your site already sends it.
- Turn any automation off again at any time.
SEO
- Fill a missing description, sharing tags, canonical and language from the page’s own content, never overwriting what is there.
- Add WebSite, Organization, Breadcrumb and Article structured data built from visible content.
- Notify Bing and other IndexNow search engines when your pages change.
AEO
- Serve a Markdown version of each page to AI assistants, announced in a Link header.
- Generate llms.txt and llms-full.txt from your home, about and privacy pages.
- Generate robots.txt, choosing which AI training and AI search crawlers may read your site.
Security
- Baseline headers: no file-type guessing, a stricter Referrer-Policy, a Permissions-Policy and hidden server version numbers.
- HTTPS only (HSTS), raised in stages from 5 minutes to 1 year.
- Anti-framing against clickjacking, with the sites you still allow.
- Upgrade insecure requests and Cross-Origin-Opener-Policy.
- Cookie hardening: Secure and SameSite=Lax where they are missing.
- A security.txt that is renewed automatically.
- Blocking of sensitive files such as .git and .env.
Generated files are only served when your site doesn’t have its own, and a security protection is only added when your site’s response doesn’t already send it. How the security protections work
Understand
See what changes
Every analysis compares the same page without and with BetterEO, so you see what changes for your own site rather than take our word for it.
On this site
70 → 95 The security score of bettereo.com, scanned at its origin and then with BetterEO’s protections turned on.
SEO and AEO scores
- Without BetterEO is what a crawler that doesn’t run JavaScript gets from your server.
- With BetterEO is what BetterEO serves crawlers.
- Findings are marked as fixed by BetterEO or as needing a change on your site.
AEO, explained
- 80% content, assessed by AI.
- 20% machine readability: structured data, a Markdown version, llms.txt and a robots.txt that lets AI crawlers in.
Security score
- Your origin is scanned directly, bypassing BetterEO.
- It is compared with your site as visitors get it through BetterEO.
- Ready-to-paste integrity attributes for third-party scripts.
Improvements
- A prioritised list of suggested changes for each domain.
- The expected impact and the effort involved.
- How many pages each one affects.
Site health
- Issues found in each render.
- Failed resources, JavaScript errors and insecure requests.
- Third-party scripts, page weight and possible soft 404s.
Bot analytics
- Which search engines and AI crawlers visit.
- Which pages they request.
- Which format they received.
AI interactions
- The pages AI assistants fetch to answer prompts.
- How often they use your pages in their answers.
- How many visitors their answers send you, from your site’s real traffic.
Search Console insights
- Optionally connect Google Search Console.
- Search performance and indexing data alongside your renders.
- Clicks, impressions and position before and after your domain went live on BetterEO.
Compare with competitors
- Analyse a competitor’s page next to yours.
- Compare their SEO and AEO scores and findings side by side.
Keep exploring