Prerender Alternatives: the simpler, cheaper choice

No - it's three steps: add a CNAME record in your DNS provider, remove the Prerender.io middleware package from your codebase, deploy. Most teams switch in under 10 minutes of actual work. Because PageGlass operates at the DNS layer rather than as middleware in your application, there's nothing to install, configure, or maintain in your code. You can also run both services in parallel during the cutover - point your DNS at PageGlass, leave the Prerender middleware in place, verify everything works, then remove the middleware in a follow-up deploy. There's no risk of an SEO interruption because the change is instant and we serve rendered HTML to bots from the moment your CNAME propagates. If you discover an issue, reverting is just rolling back the DNS record - no code changes required.

Yes. PageGlass is framework-agnostic by design because it works at the DNS layer, before traffic ever reaches your server. React, Vue, Angular, Svelte, Next.js (CSR mode), Nuxt, Gatsby, Astro, SvelteKit, Solid, Qwik - if it serves HTML over a domain, PageGlass can detect bot requests and serve them pre-rendered HTML. The same applies to no-code and AI-builder platforms like Lovable, Bolt, v0, Replit, Bubble, and Webflow - these are exactly the cases where Prerender.io's middleware approach falls down because you don't have access to the underlying server stack. There's no SDK to install, no package to maintain, no framework adapter that needs updating when your dependencies change. If your hosting provider lets you set a CNAME record, PageGlass works.

No. Google explicitly distinguishes between legitimate dynamic rendering (serving pre-rendered HTML to bots through a recognised CDN) and cloaking (deceptive content swapping designed to mislead crawlers). PageGlass runs on Cloudflare's edge network, which Google recognises as one of the major legitimate CDNs - the same infrastructure used by millions of websites for caching and performance. The content we serve to bots is the same content human users see, just rendered server-side instead of in the browser. This is exactly what Google's documentation says is allowed under the dynamic rendering policy. Customers running Google Ads have specifically cited this as a reason to switch from prerender services that use custom reverse proxies, which have triggered cloaking warnings in some accounts.

Your origin server continues to serve content normally - PageGlass is not a single point of failure. If you cancel, bots simply see the raw HTML response from your origin instead of the rendered version. For a static site or one that uses SSR, this means nothing changes. For a client-side rendered SPA, this means bots will see the empty shell again until you set up an alternative rendering solution. We don't lock you in: your DNS record stays under your control, your domain stays yours, and you can revert by removing the CNAME in seconds. We also keep your content cached for 24 hours after cancellation as a grace period, so even if you cancel mid-month there's no immediate cliff. The 30-day money-back guarantee on paid months means you can also try us on real production traffic and get refunded if it doesn't work for you.

It scales down, not up. PageGlass is $29/month for one site, regardless of how many pages you publish or how much bot traffic you serve - if you publish 10 pages or 10,000, the price is the same. For multiple sites, the Agency plan covers 5 sites for $99/month, and every additional site after that is $9.99. So a 10-site agency pays $148.95 in total, a 20-site agency pays $248.85, a 50-site agency pays $548.55. There are no render quotas, no page caps, no overage bills, no usage tier upgrades. Compare this to Prerender.io's tiered model which charges by page count and renders served, with overage fees when you exceed your tier - and reports of significant renewal price increases. The price you sign up at is the price you pay for the lifetime of your account.