Find Your Origin URL

Managed setup needs a current website location, also called the origin URL.

The origin is where Prerender Buddy sends normal human visitors after your public domain points to Prerender Buddy.

The simple rule

Use the URL where the website loads today without using the custom domain you are protecting.

Public domain:

1www.example.com

Good origin:

1https://project-name.netlify.app
2https://project-name.vercel.app
3https://project-name.lovable.app
4https://project-name.pages.dev
5https://project-name.up.railway.app

Bad origin:

1https://www.example.com

If the origin is the same as the public domain, the proxy can loop back to itself.

Lovable

Use the Lovable-hosted published URL, not the custom domain.

Usually this looks like:

1https://your-project.lovable.app

Where to look:

1. Open the project in Lovable.
2. Open the publish, share, or domain area.
3. Copy the default Lovable app URL.
4. Use that as the Current website location in Prerender Buddy.

If you only see the custom domain, open the site from Lovable's own preview or published URL and copy that address.

Bolt

Bolt projects are often deployed through a connected host such as Netlify, StackBlitz, or another deployment provider.

Use the generated deployment URL from that host.

Common examples:

1https://your-project.netlify.app
2https://your-project.stackblitz.io
3https://your-project.vercel.app

Where to look:

1. Open the Bolt project.
2. Find the deployment or published site link.
3. Copy the provider URL that is not your custom domain.
4. Use that as the origin.

v0, Vercel, and Next.js apps

For Vercel-hosted projects, use the Vercel deployment domain.

Usually this looks like:

1https://your-project.vercel.app

Where to look:

1. Open the project in Vercel.
2. Go to the project domains or deployments area.
3. Copy the default .vercel.app domain.
4. Use that as the origin.

If the app can run middleware, developer setup may be better because DNS can stay unchanged.

Netlify

Use the Netlify site subdomain.

Usually this looks like:

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

Where to look:

1. Open the site in Netlify.
2. Open the domains area.
3. Copy the default Netlify subdomain.
4. Use that as the origin.

Do not use the custom domain you are pointing to Prerender Buddy.

Railway

Use the Railway-generated service domain.

Usually this looks like:

1https://your-service.up.railway.app

Where to look:

1. Open the service in Railway.
2. Open networking or domains.
3. Copy the generated Railway public domain.
4. Use that as the origin.

If the app is a server app and can run middleware, developer setup may be an option too.

Cloudflare Pages

Use the Cloudflare Pages project domain.

Usually this looks like:

1https://your-project.pages.dev

Where to look:

1. Open the Pages project in Cloudflare.
2. Open custom domains or deployments.
3. Copy the .pages.dev URL.
4. Use that as the origin.

Replit, Render, Fly, and other hosts

Use the provider's generated public URL.

Examples:

1https://your-app.replit.app
2https://your-app.onrender.com
3https://your-app.fly.dev

The exact domain depends on the provider. The important part is that it must still load the normal website after your public domain points to Prerender Buddy.

If you cannot find a separate origin URL

You have three options.

Option 1: create an origin subdomain

Create a separate hostname that points directly to the original host.

1origin.example.com -> original website host
2www.example.com -> Prerender Buddy

Then use:

1https://origin.example.com

as the Current website location.

Option 2: keep the platform default URL

Many hosts keep a default provider URL even after a custom domain is added. Use that provider URL as the origin.

Option 3: use developer setup

If there is no separate origin and you control server middleware, use developer setup instead of managed DNS setup.

Quick checklist

Before saving the origin URL, confirm:

• It starts with https://.
• It loads the normal website in a browser.
• It is not the public domain being protected.
• It does not redirect back to the public domain.
• It remains reachable after DNS is changed.

If any of those fail, do not use that URL as the origin.