Frequently Asked Questions

Prerendering generates a fully rendered HTML version of your page and serves it to search engine bots and AI crawlers. Modern websites use JavaScript to load content dynamically, but bots like Googlebot, GPTBot, and ClaudeBot don't always execute JavaScript. Without prerendering, these bots may see an empty page instead of your actual content.

When a bot visits your site, Prerex detects it via user-agent analysis and DNS verification. Instead of serving the JavaScript-heavy page, Prerex delivers a clean, fully-rendered HTML version from its cloud cache. Human visitors are never affected — they see your normal site.

No. Prerex only activates for bots, never for human visitors. Bot requests are served from cache in approximately 200 milliseconds. Your site’s performance for real users is completely unchanged.

Prerex detects 29+ bot families across 4 categories: SEO bots (Googlebot, Bingbot, Yandex, Baidu), Social bots (Facebook, Twitter, LinkedIn, Pinterest), AI crawlers (GPTBot, ClaudeBot, PerplexityBot), and QA tools (Lighthouse, PageSpeed). Every bot is verified using reverse + forward DNS lookup.

Yes. Prerex works alongside WP Super Cache, WP Rocket, W3 Total Cache, LiteSpeed Cache, and any other cache plugin. It automatically handles cache bypass for bots without disrupting your existing setup.

Free includes 5,000 renders per month and supports Google and Bing bots. Pro at €19.99/month adds AI crawler support (ChatGPT, Claude, Perplexity), social bot support, Rex Sense adaptive rendering, HTML cleanup, custom bot policies, and up to 100,000 renders per month.

Prerex is built specifically for WordPress and modern JS frameworks. It offers zero-config WordPress plugin installation, built-in DNS-verified bot detection, and npm packages for Next.js, Nuxt, and Express. Prerender.io requires manual server configuration and has no native WordPress or framework integrations.

With Prerex Pro, yes. GPTBot, ClaudeBot, and PerplexityBot receive fully rendered HTML of your pages. On the Free plan, AI bot visits are logged but not served — you can see how often AI crawlers visit and upgrade when ready.

No. Cloaking means showing different content to bots vs humans to manipulate rankings. Prerex serves the exact same content — just pre-rendered so bots can actually read it. Google explicitly supports dynamic rendering as a legitimate technique.

For WordPress: install the plugin, activate it, done — zero configuration needed. For Next.js: npm install @prerex/next and add one line to middleware.ts. For Nuxt: npm install @prerex/nuxt and add to modules. Full guide at prerex.io/get-started.

Only what’s needed to render pages: URLs visited by bots, bot user-agents, and bot IPs for DNS verification. No personal visitor data, no analytics, no tracking of human users.

The first 250 users who sign up get Pro free for 6 months. After 6 months, you can continue on Pro at €19.99/month or switch to the Free plan.