When to use this
Create your first site when you have a Pro or Growth subscription and are ready to connect a domain you control. This step registers the root domain in GDPRChecker, runs ownership verification, and creates the site record that powers your runtime script URL, consent configuration, and heartbeat telemetry. Without a verified site, the dashboard cannot show install instructions tied to your domain or advance the setup wizard.
Use the exact hostname visitors type in the browser—typically your apex domain such as example.com, not arbitrary subpaths. GDPRChecker treats the registered root as the protected property; subdomains generally inherit protection once the runtime is installed on pages that load under that site configuration. If you operate multiple unrelated brands, Growth allows up to 3 protected websites; Pro includes 1 protected website.
Ownership verification prevents third parties from claiming your domain and receiving your runtime credentials. You will be prompted to place a verification token via DNS TXT record or an HTML file on your origin. Complete verification before installing the script so diagnostics attribute heartbeats to the correct site.
Step-by-step instructions
- Sign in and open Dashboard → Setup Step 1 · Connect Site (or Sites if you already have a list view).
- Enter your root domain without protocol or path—for example example.com rather than https://www.example.com/blog.
- Choose your verification method: DNS TXT on the apex or a well-known URL path served over HTTPS.
- Add the verification record at your DNS host or upload the file to your web server, then click Verify in GDPRChecker.
- Wait for verification to succeed; failed checks usually mean DNS propagation delay or a conflicting CDN cache.
- Once verified, note your Site ID and the generated script snippet shown on the install step—you will need both for the next article.
- Confirm the site appears in your Sites list with status indicating it is ready for script installation.
- Proceed to Install the runtime script; do not skip verification even on staging—you can add staging hosts later under Growth subdomain rules.
Expected result
Your domain is registered, ownership is verified, and Step 1 · Connect Site marks complete. The dashboard unlocks Step 2 · Install Script with a personalized script tag containing your site parameter. The Sites overview shows the domain, verification timestamp, and links into consent and protection settings.
If you are on Pro and already had a different active site, you may need to archive or replace the previous site per plan limits before adding a new root domain. Growth users can add additional sites until they reach the active site cap.
Troubleshooting
Verification keeps failing
Double-check the TXT name and value copied from GDPRChecker without extra quotes. For file verification, ensure the URL returns 200 over HTTPS without authentication walls. Disable temporary maintenance modes, and purge CDN caches that might serve an old 404. DNS changes can take up to 48 hours globally; retry after 15–30 minutes if you recently edited records.
Domain already registered
Each root domain can belong to one GDPRChecker account at a time. If you migrated accounts, remove the site from the old account or contact support with proof of ownership. Typos like www.example.com vs example.com count as different host patterns—use the canonical root your marketing site uses.
Add site button is disabled
Free plans cannot create managed sites. Upgrade to Pro or Growth, then refresh. If you are at the site limit, archive an unused site on Growth or use site replace flows on Pro before adding a new root domain.