SSRChecker

It fetches your homepage the way an AI crawler does — a plain request, without running JavaScript — and reports how much of your content is actually in the server HTML: title, meta description, H1, and visible text. If your content only appears after JS runs, most AI crawlers can't see it.

SSR means server-side rendering: your server returns the full HTML content on the first request. The opposite is client-side rendering, where the server returns a near-empty shell and JavaScript builds the page in the browser — which crawlers that don't run JS never see.

Most AI crawlers (and many search crawlers) fetch your HTML but do not execute JavaScript, or do so unreliably. If your content is injected by JS, they may index an empty page — so your content can't be found, summarized, or cited.

It measures the visible text length in the raw HTML, checks for an empty app container (like an empty root div), and looks for your title, meta description, and H1 in the server response. From that it labels your homepage server-rendered, partial, or client-rendered.

Server-render or pre-render your key content so it's in the initial HTML. Frameworks like Next.js, Nuxt, Astro, or SvelteKit support SSR or static generation. Even a hybrid where your main content and headings are in the HTML is a big improvement.

No. Being readable is necessary but not sufficient — whether AI answers actually mention and cite you depends on your content, authority, and evidence. That's what the full AEOMaster audit measures.