Start with a free account to prove the crawler path before paying or changing production traffic. Free includes 500 fresh browser renders/month for one registered domain.

1. Create account and verify your email.
2. Open the dashboard after sign-in.
3. Keep this page open while you add the domain and first key.

Register the production hostname of your SPA, for example app.example.com. Requests for unregistered hostnames are rejected before the browser starts.

1. Open Dashboard - Domains.
2. Enter the hostname without protocol or path.
3. Save the returned domain ID if you plan to automate sitemap warming or push refresh.

example.com
www.example.com
docs.example.com

Create one key per integration. For production crawler middleware, use a domain-scoped key and store it only on the server.

1. Open Dashboard - API keys.
2. Name the key after the integration, such as production middleware.
3. Select a domain scope, then copy the key once and store it as a server-side secret.

PAGEFLASH_KEY=pk_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Use the render endpoint to confirm the key, domain scope, and first fresh render all pass before adding middleware.

curl -H "Authorization: Bearer $PAGEFLASH_KEY" \
  "https://pageflash.io/render?url=https://example.com/pricing"

A successful response returns the rendered HTML crawlers will see. If monthly quota is exhausted on a cache miss, PageFlash returnsMONTHLY_QUOTA_EXCEEDED before the browser starts.

Choose the path closest to your goal after the first render works. Most SPA visibility work uses crawler middleware; direct API calls are best for generated outputs and internal workflows.

Keep normal users on your SPA. Send crawler user-agents to PageFlash so they receive complete cached HTML. Pick the layer closest to your traffic; Cloudflare Worker is usually the fastest low-risk path.

// Bind PAGEFLASH_KEY as a Cloudflare secret, then deploy.
const BOT_REGEX = /(googlebot|google-inspectiontool|googleother|bingbot|bingpreview|slurp|yandex|baiduspider|sogou|applebot|duckduckbot|duckassistbot|twitterbot|facebookexternalhit|facebookbot|facebot|meta-externalagent|rogerbot|linkedinbot|embedly|quora|showyoubot|outbrain|pinterestbot|pinterest|slackbot|discordbot|vkShare|W3C_Validator|whatsapp|telegrambot|zalobot|zalo\/|zaloapp|zaloweb|linespider|Chrome-Lighthouse|gptbot|chatgpt-user|oai-searchbot|perplexitybot|perplexity-user|claudebot|claude-user|anthropic-ai|ccbot|bytespider|phindbot|redditbot|petalbot|semrushbot|ahrefsbot|mj12bot|dotbot)/i

export default {
  async fetch(request, env) {
    const ua = request.headers.get('user-agent') || ''
    if (!BOT_REGEX.test(ua)) return fetch(request)

    const renderUrl = 'https://pageflash.io/render?url=' + encodeURIComponent(request.url)
    return fetch(renderUrl, {
      headers: { Authorization: `Bearer ${env.PAGEFLASH_KEY}` },
    })
  },
}

Use the same endpoint for HTML, screenshots, PDF, and Markdown. Direct API calls should come from your backend, job queue, or internal tool.

# HTML for SEO bots
curl -H "Authorization: Bearer YOUR_KEY" \
  "https://pageflash.io/render?url=https://your-app.com"

# Full-page PNG screenshot
curl -H "Authorization: Bearer YOUR_KEY" \
  "https://pageflash.io/render?url=https://your-app.com&renderType=png&fullpage=true" \
  --output snap.png

# PDF
curl -H "Authorization: Bearer YOUR_KEY" \
  "https://pageflash.io/render?url=https://your-app.com&renderType=pdf" \
  --output report.pdf

# Markdown for AI agents
curl -H "Authorization: Bearer YOUR_KEY" \
  -H "Accept: text/markdown" \
  "https://pageflash.io/render?url=https://your-app.com"

Test the exact request path your middleware will use. Confirm status, title, canonical, Open Graph tags, body content, and cache headers before production bot traffic moves.

curl -A "Googlebot/2.1 (+http://www.google.com/bot.html)" \
  -H "Authorization: Bearer $PAGEFLASH_KEY" \
  "https://pageflash.io/render?url=https://example.com/pricing" | head

• Look for the rendered <title>, one <h1>, canonical URL, and social meta tags.
• Open the dashboard Activity view to confirm the request is attributed to the expected domain.
• Repeat with a social bot user-agent if link previews are important.

Sitemap warming turns crawler rendering from reactive to proactive. PageFlash reads sitemap URLs, renders them ahead of time, and refreshes cache before bots arrive.

curl -X POST "https://pageflash.io/api/sitemaps" \
  -H "Authorization: Bearer YOUR_DASHBOARD_JWT" \
  -H "Content-Type: application/json" \
  --data '{"domainId":"YOUR_DOMAIN_ID","url":"https://example.com/sitemap.xml"}'

Pro and Enterprise teams can tell PageFlash exactly which paths changed. PageFlash renders the fresh version in the background, then swaps cached HTML when it is ready.

curl -X POST "https://pageflash.io/api/domains/YOUR_DOMAIN_ID/invalidate" \
  -H "Authorization: Bearer YOUR_PAGEFLASH_API_KEY" \
  -H "Content-Type: application/json" \
  --data '{"paths":["/blog/your-post","/pricing"]}'

• paths must start with / and must not include protocol or hostname.
• Use a domain-scoped API key when the CMS only publishes one site.
• The endpoint accepts up to 100 paths per request and is limited to 100 requests per minute.

await fetch(
  `https://pageflash.io/api/domains/${process.env.PAGEFLASH_DOMAIN_ID}/invalidate`,
  {
    method: 'POST',
    headers: {
      Authorization: `Bearer ${process.env.PAGEFLASH_API_KEY}`,
      'Content-Type': 'application/json',
    },
    body: JSON.stringify({ paths: ['/blog/your-post'] }),
  },
)

Need the domain ID? It is returned by GET /api/domains and when you add a domain from the dashboard.

Use SEO audit to see what crawlers receive after rendering. Pro and Enterprise unlock override workflows for titles, descriptions, Open Graph tags, canonical URLs, JSON-LD, AI copy, and llms.txt.

• Free, Starter, and Growth can inspect SEO audit signals.
• Pro adds overrides, AI copy generation, llms.txt, webhooks, and 30d activity history.
• Enterprise adds 200 AI generations/day, unlimited patterns, SLA, SSO, DPA, and private support.

HTML and Markdown renders use the cache when possible. A cache hit does not consume monthly render quota. Cold renders and forced refreshes count as fresh browser renders.

• Starter uses 1d default freshness.
• Growth uses 6h default freshness, custom TTL down to 1h.
• Pro uses 1h default freshness, custom TTL down to 10m.
• Enterprise uses 30m default freshness, custom TTL down to 5m.

PageFlash enforces the monthly render quota before a fresh browser render starts. Cache hits stay free. When a plan runs out on a cache miss, the response code is MONTHLY_QUOTA_EXCEEDED.