Quick Start Guide
Overview
This guide walks you through setting up RndrKit for your website. By the end, search engine bots will receive fully rendered HTML versions of your pages.
What you will need:
- A RndrKit account (sign up at rndrkit.io)
- Access to your domain's DNS settings
- Your site's origin URL (e.g.,
your-app.lovable.apporyour-app.vercel.app)
Step 1: Sign Up and Log In
Create your account at rndrkit.io. You can sign up with your email or use a social login provider. Once logged in, you will be taken to the dashboard.
Step 2: Add Your Domain
From the dashboard, click Add Domain and enter the following:
- Custom Domain: The domain where your site is live (e.g.,
www.example.com) - Origin URL: Where your application is actually hosted (e.g.,
example.lovable.app)
Custom Domain: www.example.com
Origin URL: example.lovable.app
Click Add Domain to save. Your domain will appear in the dashboard with a status of Pending until DNS is configured.
For detailed instructions, see Adding Domains.
Step 3: Configure DNS
You need to point your domain to RndrKit's servers. Go to your DNS provider and create a CNAME record:
| Type | Name | Value | TTL |
|---|---|---|---|
| CNAME | www | cname.rndrkit.io | Auto |
If you are using Cloudflare, make sure the proxy status is set to DNS only (gray cloud) so that traffic routes through RndrKit rather than Cloudflare's proxy.
DNS changes can take up to 24 hours to propagate, but typically take effect within minutes.
For provider-specific instructions, see DNS Configuration.
Step 4: Verify SSL
RndrKit automatically provisions an SSL certificate for your domain using Let's Encrypt. Once DNS propagation completes, your domain's SSL status in the dashboard will change from Pending to Active.
You can check SSL status on the domain detail page. If the certificate is not issued within 30 minutes of DNS propagation, see SSL Verification for troubleshooting.
Step 5: Test Bot Rendering
Once your domain is active, verify that pre-rendering is working by simulating a bot request:
curl -s -A "Googlebot/2.1" "https://www.example.com/" | head -100
You should see fully rendered HTML with your page content, meta tags, and structured data. Compare this with a normal request:
curl -s "https://www.example.com/" | head -100
The normal request should return your SPA shell (the origin response), while the Googlebot request returns the pre-rendered version.
Step 6: Warm Your Cache (Optional)
To ensure bots get fast responses from the start, you can pre-warm your cache for important pages. Go to Cache Management in the dashboard and use the cache warming feature to render your homepage and key landing pages.
See Cache Warming for details.
What Happens Next
With RndrKit active on your domain:
- Search engine bots visit your site and receive fully rendered HTML. Google, Bing, and others can now index all your content, meta tags, and structured data.
- Social media crawlers (Facebook, Twitter, LinkedIn) receive proper Open Graph tags, so your link previews display correctly.
- Human visitors are proxied to your origin server and experience your site exactly as before.
Verify in Google Search Console
After a few days, check Google Search Console to confirm that Google is indexing your pages correctly:
- Go to URL Inspection and enter one of your page URLs.
- Click Test Live URL to see what Google sees.
- The rendered HTML should show your full page content.
You can also use the Coverage report to monitor how many pages are being indexed over time.
Next Steps
- Dashboard Overview -- Learn your way around the dashboard
- Analytics -- Monitor which bots are visiting your site
- SEO Audit -- Check your pages for common SEO issues
- Sitemaps -- Generate and submit a sitemap for your site