Question 1

What exactly does UpRender do?

Accepted Answer

UpRender sits between your website and the automated visitors that crawl it — AI bots, search engines, social preview agents. When one of those visitors shows up, UpRender intercepts the request, renders your JavaScript app into full HTML, and serves that back. Your real users never see any difference.

Question 2

How long does setup actually take?

Accepted Answer

For most teams, under an hour. You point bot traffic to UpRender through a middleware condition, proxy rule, or CDN header — and that's it. No code changes to your app, no deploys, no downtime. We have step-by-step guides for Vercel, Cloudflare, Nginx, and most common stacks.

Question 3

Do I need to rewrite or modify my frontend?

Accepted Answer

No, and that's kind of the point. UpRender is external infrastructure — it renders your existing app on demand. React, Next.js, Vue, Angular, Nuxt, Remix — whatever you're running today keeps running exactly the same way for your users.

Question 4

Who is UpRender a good fit for?

Accepted Answer

Best fit is dev-led teams with JavaScript-heavy public routes: SaaS product pages, documentation sites, help centers, pricing pages, blog platforms. If AI bots visit your site and you want them to actually read your content rather than getting a blank page, UpRender is built for that.

Question 5

What if my site is mostly server-rendered already?

Accepted Answer

You may need UpRender less urgently, but it can still help. SSR frameworks can have hydration edge cases, partial client rendering, or inconsistent metadata delivery. AI Visibility scoring works regardless of your rendering approach.

Question 6

What is AI Visibility and why does it matter?

Accepted Answer

Rendering is the foundation — it makes your pages readable. AI Visibility is the analysis layer on top: per-page scores, metadata quality checks, schema gaps, bot traffic breakdowns, and llms.txt management. It answers 'which pages are actually AI-ready?' so you can act on real data instead of guessing.

Question 7

What's included in AI Visibility scoring?

Accepted Answer

Each page gets scored on: heading structure, title and description quality, schema markup coverage, content density, canonical setup, Open Graph completeness, and llms.txt alignment. You get an overall score plus a breakdown of specific issues — so you know exactly what to fix.

Question 8

What is llms.txt and why should I care?

Accepted Answer

llms.txt is an emerging standard (similar to robots.txt) that tells AI systems which pages are most important, what topics they cover, and how to reference your content accurately. UpRender generates and maintains yours automatically based on your rendered pages.

Question 9

Does this replace traditional SEO?

Accepted Answer

Not at all — it complements it. A lot of what makes a page AI-readable (good metadata, structured data, clear content hierarchy) also makes it better for classic search. Think of it as improving the machine-readable foundation that everything else depends on.

Question 10

How often are pages re-analyzed?

Accepted Answer

Pages are re-analyzed when they're re-rendered. You can also trigger manual re-analysis from the dashboard, or set cache TTLs that automatically refresh content on your schedule.

Question 11

Which bots and crawlers does UpRender detect?

Accepted Answer

We detect 15+ crawlers including GPTBot, OAI-SearchBot, ClaudeBot, Claude-SearchBot, Googlebot, Google-Extended, Bingbot, Applebot, Meta-ExternalAgent, DuckDuckBot, Facebook's crawler, LinkedIn's bot, and more. You can also add custom rules for any bot you want to handle differently.

Question 12

Will this slow down my site for real users?

Accepted Answer

No. UpRender only intercepts traffic from known bots — real user requests go straight to your app as normal. Bot responses are served from cache at the edge, typically under 200ms.

Question 13

What happens if UpRender has downtime?

Accepted Answer

You can configure a fallback behavior — either pass bot traffic through to your origin app or serve a cached version. Bot rendering failures don't affect your users either way.

Question 14

Can I apply UpRender to only specific routes?

Accepted Answer

Yes. You can set route-level include and exclude rules, so only the pages you care about go through the rendering pipeline. Useful for keeping private routes or high-traffic API paths out of scope.

Question 15

Do you support multi-domain or multi-site setups?

Accepted Answer

Yes. All plans support unlimited domains from a single account. Enterprise plans add workspace-level isolation, custom governance rules, and dedicated support for complex multi-site rollouts.

Question 16

Is UpRender GDPR compliant?

Accepted Answer

Yes. We don't store user data, and rendered pages are cached as static HTML snapshots. You control cache TTLs, data retention, and can configure EU-region rendering for data residency requirements.

Question 17

Can we self-host or use a private deployment?

Accepted Answer

Yes, on Enterprise plans. You can run the rendering infrastructure in your own cloud environment, keeping rendered content entirely within your security perimeter.

Question 18

What data does UpRender log?

Accepted Answer

We log bot request metadata (user agent, route, response code, cache status) for your analytics dashboard. We do not log personal user data or store any page content beyond the rendered HTML cache.

Question 19

Is there really a free plan?

Accepted Answer

Yes — 50 rendered URLs per month, forever free. It's meant for validating that rendering works on your key routes before committing to a paid plan. No credit card needed to start.

Question 20

What's the difference between Starter and Pro?

Accepted Answer

Starter gives you reliable bot delivery at scale (25,000 renders/month) with full analytics. Pro adds the AI Visibility layer: per-page scores, AI analysis, llms.txt generation, and deeper bot analytics. If you want to actively improve AI citation rates, you want Pro.

Question 21

Can we try Pro before committing?

Accepted Answer

Yes. You can start on Free or Starter and upgrade at any time. Usage rolls over month-to-month and you can downgrade if your needs change.

Question 22

What counts as a 'rendered URL'?

Accepted Answer

A rendered URL is one request from a bot that UpRender intercepts and serves a fully-rendered HTML response for. Cached responses after the first render don't count against your quota.

Question 23

Do you offer annual billing or discounts?

Accepted Answer

Yes, annual billing is available with a discount applied upfront. Enterprise plans are fully custom-priced based on volume, domains, and support requirements. Reach out and we'll put together something that fits.

Questions we get all the time

Getting Started

AI Visibility

Technical & Delivery

Privacy & Security

Pricing & Plans

Didn't find what you were looking for?