A predictable onboarding is part of the product. This page describes the operator flow: what you prepare, what you configure, and how you validate readiness.
Prerequisites
- Domain + DNS control for @, api, admin, auth
- SSL certificates (Lets Encrypt or existing certs)
- Linux server with Docker + reverse proxy
- Outbound internet access for provider ingestion
What operators configure
- Provider affiliate IDs and outbound routing templates
- Homepage blocks and visibility rules
- SEO posture: discovery coverage + templates + sitemaps
- Compliance surfaces: age gate, legal content, consent
- Optional modules: AI enable/disable
Timeline
A realistic operator timeline
Day 0: Infrastructure
Set up DNS, SSL, and proxy routing so web and admin are reachable.
- DNS records (@/api/admin/auth)
- TLS termination
- Proxy routes
- DirectAdmin subdomain registration (if used)
Day 1: Provider revenue wiring
Configure providers and affiliate IDs, then validate outbound attribution.
- Affiliate IDs per provider
- Outbound templates
- Provider health checks
- Initial freshness posture
Day 2-7: SEO and content
Finalize discovery posture and start the content loop.
- Discovery coverage
- Sitemaps and indexing
- Blog workflows
- Optional AI for drafts
Go-live checklist
- Provider health is green and ingestion freshness is acceptable.
- Affiliate IDs and outbound routing are validated.
- Sitemaps are reachable and segmented; canonical routing is consistent.
- Age gate and legal surfaces are set for your brand.
- Admin access policies are configured (roles, lockout, optional MFA).
- Internal services remain behind the proxy (loopback-only) to stay support-eligible.
Want a guided onboarding?
We can align onboarding with your target providers and your SEO program and define the fastest safe path to go-live.