For public SPA routes with a crawler-readability gap

Verify crawler HTML for your SPA.

Render registered public routes into complete HTML for the crawler user-agents you choose. Your visitors stay on the normal React, Vue, or Svelte path when your edge, server, or proxy routes only crawler traffic through PageFlash.

Start free See the proof path

No credit card500 free fresh rendersCache hits stay free

Render receipt

200 HIT

Bot gets crawler-ready HTML

Title: <title>Pricing</title>
OG image: <meta property="og:image">
Status: Rendered & cached
Bot: Googlebot

Inspect crawler HTML after you configure routing.

Live proof

Run a crawler check against this site.

This page is wired through PageFlash. Switch crawler user-agents, inspect the response, then copy the request when you are ready.

# Request this site as Googlebot

Googlebot -> rendered HTML

curl -A "Googlebot/2.1 (+http://www.google.com/bot.html)" "https://pageflash.io"

Expected evidence

Rendered title
One H1
Canonical URL
Cache header

Registered-domain keys reject arbitrary third-party renders before a browser starts.

Start free Verify first renderPreview HTML

How it fits

Prove the crawler path before you commit to a frontend migration.

Use PageFlash for registered public SPA routes that need inspectable crawler HTML, cache state, and render evidence. Use SSR or SSG when the user experience itself needs server rendering. The same API can also produce screenshots, PDF, and Markdown for backend or internal workflows.

Register the host

Add the SPA hostname bots should see. Domain scoping rejects arbitrary third-party renders before a browser starts.

Keep the key server-side

Create a scoped key for edge, server, proxy, or job code. Do not ship PageFlash credentials in browser bundles.

Route the crawler user-agents you choose

Use your edge, server, or proxy integration to send selected crawler traffic through PageFlash. Normal visitors stay on your regular SPA route when that rule is in place.

Prewarm public URLs, then refresh

Eligible plans can queue sitemap URLs for warming. Pro and Enterprise can request background refreshes for changed paths after a publish or deploy.

Crawler-only middleware path

if (isCrawler(req.headers['user-agent'])) {
  return fetch('https://pageflash.io/render?url=' + encodeURIComponent(url), {
    headers: { Authorization: 'Bearer PAGEFLASH_KEY' }
  })
}

return serveYourSpa(req)

Proof + pricing

Prove the crawler response first. Pay for capacity and freshness only when the job is real.

The decision stays grounded in what you can inspect: rendered HTML, cache state, scoped keys, and render activity. It does not depend on a ranking or traffic promise.

Runs on pageflash.io

This marketing site uses the same crawler path you can inspect before routing your own bots.

Domain-scoped keys

Registered domains reject arbitrary third-party renders before a browser starts.

Render activity

Status, cache state, latency, and history make crawler rendering observable after launch.

Verify the first render See bot verification

Pricing path

Start with proof. Choose a plan when the operating limits matter.

Compare plans by the public routes you operate, how fresh crawler output must be, and whether your team needs sitemap warming, push refresh, or SEO operations.

Free to inspect one public crawler path

Starter to warm the first production site

Growth for more domains, URLs, and freshness control

Pro for push refresh and SEO operations

Start free Compare plans

FAQ