Adding Domains
Overview
Adding a domain to RndrKit tells the service which custom domain you want to pre-render and where the original application is hosted. Each domain you add creates a mapping between your public-facing URL and your origin server.
Before You Begin
Make sure you have the following information ready:
- Your domain: The domain your visitors use (e.g.,
example.com). Enter just the domain name — nohttps://and nowww.prefix. RndrKit treats the apex as canonical and automatically handles thewwwsubdomain. - Origin URL: The full URL where your application is actually hosted (e.g.,
https://your-app.lovable.app,https://my-app.vercel.app, or any other hosting provider)
Adding a Domain
- Log in to your RndrKit dashboard at rndrkit.io.
- Open the Domains page and click the Add Domain button.
- Fill in the domain details:
| Field | Example | Description |
|---|---|---|
| Your Domain | example.com | Just the domain name — no https://, no www. |
| Origin URL | https://your-app.lovable.app | The full URL where your app is hosted, including https:// |
- Click Continue to DNS Setup. RndrKit will advance to a two-step wizard (Domain → DNS Setup) and show the exact DNS records you need to add.
Domain Status
Each domain card on the Domains page shows one of two top-level states:
- Active -- The domain is enabled and serving pre-rendered content to bots.
- Inactive -- The domain has been manually deactivated from its Settings tab.
The domain's Settings tab also shows a separate SSL status, which can be:
- Active -- SSL certificate is issued and in use.
- Pending Validation -- DNS has been accepted but the certificate is still being validated.
- Pending -- SSL provisioning is queued or in progress.
- Failed -- SSL provisioning failed. Re-check your DNS records and try again.
Apex and www Domains
RndrKit serves your site on both the apex (e.g., example.com) and the www subdomain (e.g., www.example.com). Because you enter the apex when adding a domain, the DNS Setup step gives you two records to add for apex domains:
- An A record for
@pointing to35.153.65.36(covers the apex). - A CNAME record for
wwwpointing to the value shown in the dashboard (coverswww.example.com).
SSL is provisioned automatically for both records once DNS propagates. Add both records so visitors reach your site whether they type the apex or the www form.
If your DNS provider supports apex CNAME / ALIAS records (for example Cloudflare, Route 53, DNSimple, Netlify DNS, or Vercel DNS), you can use an ALIAS-style record at the apex instead of the A record. Most registrar-provided DNS (GoDaddy, Namecheap, Google Domains, Hostinger) does not support this — use the A record shown in the dashboard.
For subdomain-only setups (e.g., app.example.com), the dashboard shows a single CNAME record pointing the subdomain to the provided target.
Origin URL Format
The origin URL should be the full base URL of your hosted application, including the protocol:
Correct: https://example.lovable.app
Correct: https://my-app.vercel.app
Incorrect: example.lovable.app
Incorrect: example.lovable.app/
RndrKit will proxy human traffic to this origin URL.
Multiple Domains
You can add multiple domains to your RndrKit account. Each domain is tracked independently with its own:
- Render count and usage limits
- Cache entries
- Analytics data
- SEO tool configurations
Your plan determines how many domains you can add. See Plans and Pricing for details.
After Adding a Domain
Once your domain is added, you need to:
- Configure DNS -- Point your domain to RndrKit's servers. See DNS Configuration.
- Verify SSL -- Confirm that the SSL certificate has been provisioned. See SSL Verification.
- Test rendering -- Verify that bot requests receive pre-rendered HTML.
# Test that bot rendering is working
curl -s -A "Googlebot/2.1" "https://www.example.com/" | head -50
Removing a Domain
To remove a domain from RndrKit:
- Go to the Domains page in the dashboard.
- On the card for the domain you want to remove, click the trash (delete) icon.
- Confirm the deletion in the Delete Domain dialog.
After removing a domain, remember to update your DNS records to point back to your original hosting provider.