# Add your first domain and verify the banner

> Add your first public hostname, configure the consent banner, install the snippet, and run or schedule the first scan.

Author: OptinStack Team  
Published: 2026-06-28  
Page: https://community.optinstack.com/articles/add-your-first-domain-and-verify-the-banner  
Markdown: https://community.optinstack.com/llms.md/articles/add-your-first-domain-and-verify-the-banner

Before OptinStack can render a banner on your site, you need a project and at least one registered hostname\. This guide covers adding the public hostname visitors use, configuring the banner, installing the snippet, and starting your first scan\.

## 1\. Add the public hostname

For a web project, open New site and enter the public URL visitors use, for example https://example\.com\. OptinStack saves that hostname as a production hostname and uses it for scans, runtime configuration, consent records, and billing\.

For Webflow and Framer projects, OptinStack shows development hostnames detected through the connected app\. Register one without DNS verification and assign Free or a paid plan\. When the custom production hostname is ready, register and verify it before using the included one\-time move\.

> **Info:** Custom hostnames remain pending until verified. Authenticated Webflow and Framer development hostnames do not require DNS verification. Registration alone does not activate runtime, publishing, or consent collection; the hostname needs Free, paid, Enterprise, or Workspace coverage.

## 2\. Configure the consent banner

After the hostname step, the onboarding wizard walks through the consent framework preset, banner design, install snippet, and first scan\. You can change the banner mode and design later from the dashboard\.

## 3\. Install, verify, and scan

Copy the install snippet from the Install step and add it to your site\. Then verify that the snippet can be detected on the registered production hostname\.

On the scan step, choose Start Scan to queue the first scan, or choose to scan later\. Scans run only on hostnames registered to the project and may take a little while to complete, especially on larger sites\.

### Should I use one project for multiple hostnames?

Use one project when the hostnames share the same configuration, branding, and consent policy. Use separate projects when different teams own different sites or each site needs its own banner rules.

### What about example.com and www.example.com?

They can share one project and one configuration, but each hostname is treated separately for billing and scanning. Add only the variant visitors actually use. If your site serves both variants and you want OptinStack active on both, register both. Path segments like example.com/en and example.com/it do not require separate hostnames.

### Can I start on a Webflow or Framer development hostname?

Yes. Assign Free or a paid plan to the registered development hostname, then move that assignment once after the verified production hostname is ready. The previous hostname becomes inactive; later changes use Request update for review.