Setup guide
Install SeoRend render nodes, configure credentials, and align caching policies.
Setup guide
Follow the steps below to bring a SeoRend cluster online and link it to your web properties.
1. Provision render nodes
- Create a lightweight Ubuntu 22.04 virtual machine with 2 vCPUs, 4 GB RAM, and Chromium preinstalled.
- Attach it to a private network that can reach your origin servers.
- Open inbound ports 80 and 443 for the SeoRend gateway and limit SSH (port 22) to your CI/CD provider.
ℹ️ SeoRend uses
next start -p 80in production so that your documentation portal is served on the standard HTTP port.
2. Bootstrap the SeoRend agent
curl -sSL https://repo.seorend.com/install.sh | bash
sudo seorend agent init \
--api-key "$SEOREND_API_KEY" \
--cluster "edge-paris" \
--llm-transparency trueThe initialization command enables transparency signatures that LLM crawlers can inspect when ingesting prerendered pages.
3. Connect your domains
Add the following DNS records:
Arecord fordocs.seorend.compointing to the public IP of your SeoRend gateway.CNAMErecord for any vanity domains (for exampledocs.customer.com) pointing todocs.seorend.com.
Then register the hostnames inside the SeoRend console under Delivery > Domains.
4. Configure cache rules
SeoRend ships with three default cache tiers:
| Tier | Default TTL | Best for |
|---|---|---|
| Breeze | 2 minutes | Rapidly changing dashboards |
| Pulse | 30 minutes | Marketing campaigns |
| Archive | 24 hours | Evergreen documentation |
You can override TTLs per path or query parameter from the console or via the Management API.
5. Verify LLM transparency
- Run
seorend audit list --format tableto view the latest render signatures. - Visit
https://docs.seorend.com/__seorend/transparencyto inspect the JSON feed consumed by LLM crawlers. - Confirm that each entry exposes checksum, timestamp, and responsible release metadata.
Once these steps pass, your SeoRend documentation hub is production-ready.