Check

Is your site server-side rendered?

Paste any URL below for an instant verdict — or pick your framework for a check that explains the result in your stack's own terms.

Check any URL

https://

Server-rendering built in

Meta-frameworks

Frameworks that ship a server. The check confirms your routes actually use it — per-route opt-outs and client-side data fetching can quietly undo it.

App Router vs Pages Router, SSG vs SSR vs ISR, and what “use client” does and doesn't change.

Universal rendering, route rules, and how a Nuxt app drifts back to client-only without anyone noticing.

Compiler-first rendering, per-page ssr/csr/prerender flags, and what the minimal runtime means for crawlers.

Islands architecture: HTML-first by default, so the check verifies your islands are enhancements, not the content.

Loader-based SSR and what the check should show on a healthy Remix app.

Static builds, hydration, and the “my built site shows no content” problem set.

Client-rendered by default

Single-page app frameworks

These ship an empty HTML shell unless you've added a rendering layer — the highest-stakes checks on the site.

The #root shell, why create-react-app and Vite SPAs serve crawlers nothing, and the paths to fixing it.

The <app-root> empty shell, two-wave indexing, and Angular Universal / hydration as the way out.

The #app mount point, what crawlers see before Vue boots, and when the answer is Nuxt.

Everything else

Platforms & at scale

CMS platforms and bulk checking for audits.

Server-rendered by nature — until a page-builder or headless setup changes the story.

Liquid themes vs headless storefronts, and where product content actually renders.

Bulk checker

Coming soon

Check a list of URLs in one run — for audits and agency reports.

Got a red or amber verdict?

The fix guidesdiagnose the specific symptom you're seeing — from empty view-source to "Crawled — currently not indexed." And if you'd rather have it fixed than read about it, that's what we do.