Custom Domains

Every project is reachable on a free *.sites.spideriq.ai address the moment you deploy. To serve your site on your own domain — with automatic HTTPS — connect a custom domain.

The free subdomain

When you create a project you get a free address like your-label.sites.spideriq.ai. It is verified and secured automatically, with no DNS setup. It is perfect for previews, staging, and getting started.

Connecting your own domain

  1. Add the domain in your project's domain settings (for example example.com). SpiderPublish gives you a verification record and begins provisioning.

  2. Point your DNS at SpiderPublish as instructed — typically a CNAME, plus a TXT record to prove you own the domain.

  3. Verify the domain. Once your DNS is in place, verification confirms ownership.

  4. Wait for HTTPS. A certificate is issued for your domain automatically. This is separate from ownership verification and can take a little time after your DNS resolves.

Why the padlock can lag

Ownership verification and the HTTPS certificate are two different things. Your domain can show as verified while the certificate is still being issued. SpiderPublish checks your certificate status in the background and updates it as the certificate becomes active. If you want to check immediately, use the Re-check action in your domain settings.

HTTPS is enforced

Once your domain is live, visitors are always served over HTTPS — plain HTTP requests are redirected, and a strict-transport-security policy is applied per domain. You do not have to configure anything for this.

Setting a primary domain

If you connect more than one domain, you can mark one as primary — the canonical address your site presents.

With an agent

Domains can be added, verified, and managed through the API and tooling, so an agent setting up a new site can request the domain and report back the DNS records you need to add.

Tips

  • Add the DNS records exactly as shown. A missing TXT record is the most common reason verification stalls.

  • Give HTTPS a few minutes. If the page is verified but the padlock has not appeared, use Re-check rather than re-adding the domain.

  • Deploy after connecting. If you connect a domain to a site you have never deployed, deploy it so there is something to serve.

Next steps