Custom Domains
Serve public landing pages from contractor-owned domains while preserving landing paths and supported query parameters.
How routing works
A connected custom domain maps the contractor domain to the workspace public visualizer. The domain root opens the primary landing, and /l/[slug] opens a specific landing.
| Custom-domain path | Platform equivalent |
|---|---|
| / | /v/[rooferId] |
| /l/[slug] | /v/[rooferId]/l/[slug] |
| /v/[rooferId] | Allowed to avoid rewrite loops and support platform links. |
Query preservation
Supported marketing attribution and deep-link params should be preserved when moving between platform URLs and custom-domain URLs.
https://visualizer.contractor.example/l/storm-damage?brand=westlake&material=lib-tiles&shape=high_barrel&color=westlake-fn-barcelona-900-avalonbeachblend