Platform setup

Netlify setup

Use Netlify origin URLs or Edge Functions without exposing API keys.

Netlify setup

Use this guide when the site is hosted on Netlify or when a Netlify-hosted client app needs crawler-readable HTML.

Netlify can host static apps, edge functions, and framework projects. Hosting on Netlify does not automatically mean the page is server-rendered.

What this guide helps with

  • choosing no-code DNS setup or Netlify Edge Function setup
  • finding the right Netlify origin URL
  • keeping API keys server-side
  • verifying crawler requests after deployment
  • avoiding common custom-domain and root-vs-www mistakes

When to use no-code DNS setup

Use no-code DNS setup when:

  • the site is a static React, Vue, Vite, Lovable, Bolt, Base44, or generated app
  • you can point the public hostname to Prerender Buddy
  • you do not want to edit Netlify Edge Function code
  • the Netlify subdomain still loads the normal site

Use the Netlify URL as the Current website location:

URL examples
1https://your-site.netlify.app

Do not use the custom domain as the origin:

URL examples
1https://www.example.com

After DNS changes, that custom domain points to Prerender Buddy. If it is also used as the origin, the request can loop.

When to use developer setup

Use developer setup when:

  • you can add a Netlify Edge Function
  • you want DNS to stay unchanged
  • you can store PRERENDER_BUDDY_API_KEY as a Netlify environment variable
  • crawler routing can happen before the app shell is returned

The Edge Function must run before Netlify returns the HTML page. Adding code inside browser React components is too late.

What to enter in Prerender Buddy

For no-code DNS setup:

Example
1Public website address: www.example.com
2Current website location: https://your-site.netlify.app

For developer setup:

Example
1Public website address: www.example.com
2Connection method: Developer/API setup
3API key: stored in Netlify environment variables

API key storage

In Netlify, add the key in:

Environment variable
1Site configuration -> Environment variables
2Name: PRERENDER_BUDDY_API_KEY
3Value: your_site_api_key

Do not expose the key in frontend variables, public files, or client bundles.

Root vs www handling

If www.example.com is protected, redirect example.com to https://www.example.com.

The redirect should preserve the path:

Request flow
1https://example.com/pricing
2  -> https://www.example.com/pricing

If root and www behave differently, Google may crawl the unprotected hostname and still see the app shell.

How to verify

  1. Deploy the Netlify change or update DNS.
  2. In Prerender Buddy, open the site.
  3. Click Refresh status for DNS setup.
  4. Click Verify Installation.
  5. Open Logs and confirm a crawler request appears.
  6. Test both root and www if both are public.

What success looks like

  • crawler checks return rendered page content
  • metadata and H1 are visible to crawler-style requests
  • render logs show recent crawler traffic
  • normal visitors still see the original Netlify site

Common mistakes

  • using the custom domain as the origin URL
  • assuming Netlify hosting means server-rendered HTML
  • adding crawler logic inside React instead of an Edge Function
  • storing the API key with a public frontend prefix
  • protecting www but leaving root unprotected
  • testing a Netlify preview URL instead of the final custom hostname

Ready to check the setup?

After DNS or middleware is deployed, use Verify Installation from the site dashboard and check the logs tab for crawler requests.

Still stuck? Email support@prerenderbuddy.com.

Open dashboard