A JavaScript website can need crawler-readable HTML regardless of whether it is hosted on a modern frontend platform, traditional shared hosting, or a self-managed VPS.
The hosting brand is not the main decision. The important questions are:
- Where is authoritative DNS managed?
- Does the website have a separate public origin URL?
- Can you edit server middleware or the reverse proxy?
Those answers determine the Prerender Buddy setup path.
Quick answer
If the server already sends complete HTML, you probably do not need Prerender Buddy. If visitors see a complete JavaScript page but bots receive thin HTML or an empty app shell, Prerender Buddy can help by serving rendered HTML to search engines and AI crawlers.
The short decision tree
Use managed DNS when the current website can remain available at a separate origin URL. The public www hostname points to Prerender Buddy, which serves rendered HTML to supported crawlers and forwards normal visitors to the origin.
Use a server-side integration when you control Nginx, application middleware, an edge function, or another request layer. The existing server keeps receiving traffic and sends only supported crawler page requests through the render path.
| Current setup | Practical starting point |
|---|---|
| Hostinger or GoDaddy DNS with a stable hosting URL | Managed DNS |
| cPanel shared hosting with a preview or origin hostname | Managed DNS |
| DigitalOcean App Platform with a stable app URL | Managed DNS or app middleware |
| DigitalOcean Droplet or another VPS | Server-side integration |
| Nginx in front of the application | Nginx reverse proxy integration |
DNS provider and web host may be different
A domain can be registered at GoDaddy, hosted at Hostinger, use Cloudflare nameservers, and receive email somewhere else. Edit records at the provider named by the domain's active nameservers, not automatically at the registrar or web host.
Before changing anything, record the existing DNS zone and preserve:
- MX records
- SPF, DKIM, and DMARC records
- domain and email verification TXT records
- unrelated application subdomains
Prerender Buddy website routing should not require deleting email records.
Managed DNS requires a separate origin
The origin is the address where the original website remains available after the public hostname changes.
Good origins include:
- a hosting provider URL
- a platform deployment URL
- a staging hostname
origin.example.compointing directly to the current server
The public protected hostname must not also be its own origin. If www.example.com points to Prerender Buddy and Prerender Buddy forwards visitors back to www.example.com, the requests can loop.
Read how to find the correct origin URL before making the DNS change.
Hostinger
First confirm that the active nameservers point to Hostinger. Then use hPanel's DNS zone to point www to customers.prerenderbuddy.com while keeping the original site reachable at a temporary URL or origin subdomain.
Hostinger accounts often combine website and email controls, so take extra care not to remove MX, SPF, DKIM, or DMARC records.
Follow the Hostinger setup guide.
GoDaddy
In GoDaddy's Domain Portfolio, the CNAME Name field should normally contain only www. The root domain should permanently forward to the protected www hostname, with paths preserved where possible.
If the nameservers point elsewhere, make the DNS change at that provider instead.
Follow the GoDaddy setup guide.
cPanel shared hosting
cPanel's Zone Editor is useful only when the cPanel host is authoritative for DNS. Shared hosting users often do not have the server access required for Nginx or middleware integration, so managed DNS is usually the simpler path.
Create a separate origin before replacing the existing www A or CNAME record. If the host does not expose a preview URL, ask support whether a staging hostname or direct origin hostname can be used.
Follow the cPanel setup guide.
DigitalOcean and other VPS providers
DigitalOcean can be only the DNS provider, an App Platform host, or a Droplet provider. Treat those as different setups.
- DigitalOcean DNS with a separate origin can use managed DNS.
- App Platform can use its stable app URL as origin or supported server middleware.
- A Droplet with Nginx usually fits the server-side integration path.
Follow the DigitalOcean setup guide or the broader self-hosted website guide.
Nginx reverse proxy
When Nginx already receives public traffic, it can distinguish supported crawler requests before the JavaScript app shell is returned.
Keep that routing narrow. Render only public GET page requests, and skip assets, APIs, webhooks, account pages, checkout routes, and private content. Keep the Prerender Buddy API key in restricted server configuration and use the current generated integration from the dashboard.
Follow the Nginx reverse proxy guide.
Verify the final public response
Do not stop after the DNS panel or Nginx reload reports success.
- Open the public page normally and confirm the visitor experience still works.
- Test the exact canonical hostname with a crawler-style request.
- Confirm the response contains page-specific headings, text, links, and metadata.
- Check Prerender Buddy render logs.
- Test both root and
wwwso one hostname does not bypass the setup.
Use the Bot View Checker for an individual page or the Bulk Crawler Readability Checker for a sitemap sample.
Prerendering does not guarantee rankings or AI mentions. It addresses the narrower technical problem of crawlers receiving too little readable content from a JavaScript-rendered site.
Who this is for
- SaaS founders with already-shipped JavaScript websites
- React, Vite, Vue, Lovable, Bolt, or Base44 users
- SEO freelancers checking crawler-readable HTML
- Agencies maintaining client sites without rebuilding them
You may not need Prerender Buddy if
- Server HTML is already complete.
- Static pages crawl correctly.
- You are already rebuilding with SSR or static generation.
- You only need an audit, not a rendering fix.
Check the site before changing the stack
- Bulk Crawler Readability Checker to sample important pages or sitemap URLs
- Raw HTML vs Rendered HTML to confirm whether JavaScript adds the missing content
- Bot View Checker for a deeper check of one affected page
Final recap
Prerendering on traditional hosting, cPanel, and self-hosted VPS websites comes down to what search engines and AI crawlers actually receive from your site.
Prerender Buddy does not guarantee rankings or AI citations. It helps with one specific technical problem: making sure crawlers receive readable rendered HTML instead of a thin JavaScript shell.
The first step is to check what bots see.
Check your website
Scan important pages from this site to test whether the site sends readable HTML to search engines and AI crawlers.