Install

Verifying the domain

Prove you own the site's domain with the tag, a token your server answers, or a DNS record.

Verifying a site proves that you control its domain. Collection does not wait for it: Parlox accepts beacons from the site's own domain from the first visit. Verification turns on the parts that read your site or act on it: the weekly checks of the pages agents reach, and the control map. Until a site is verified, those stay off, and someone else could register the same domain.

Any one of three proofs is enough. The dashboard's verification panel shows yours, runs the check when you open it, and again when you press Check now.

The tag in your homepage

If your homepage's HTML carries the pinned tag with your site's key, the site is verified with nothing else to do. Parlox fetches https://<your domain>/ and looks for a <script> whose src is on gateway.parlox.io (/sdk/parlox.js or a pinned release) and whose data-key is your public key.

It does not count when:

  • the homepage redirects to another domain (a marketplace profile, a link page);
  • the tag is added by Google Tag Manager or another script, since it is then not in the HTML your server sends;
  • the key travels only in the tag's URL (?key=), not in data-key.

A token your server answers

Your server answers GET https://<your domain>/.well-known/parlox-verify with the site's verification token, or with parlox-verify=<token>. Spaces around it are ignored, and redirects are followed.

  • With @parlox/server: set PARLOX_VERIFY_TOKEN and the middleware answers it.
  • On a static site: put the token in a file at public/.well-known/parlox-verify (Vite and most static builds copy public/ into the output).

A DNS record

Add a TXT record, either on _parlox.<your domain> or on the domain itself:

Text
_parlox.example.com.   TXT   "parlox-verify=<token>"

A new record can take a few minutes to appear. It works before your site changes at all, which makes it the right proof for a site you cannot deploy to yet, or one served by a platform.

Which proof to use

InstallSimplest proof
The pinned tag in your HTMLThe tag itself
@parlox/browser from npm, with @parlox/serverPARLOX_VERIFY_TOKEN
@parlox/browser only, on a static hostThe file in public/.well-known/, or DNS
Google Tag ManagerDNS
A platform you cannot change (or nginx denying dot-paths)DNS

The install wizard writes the token where your app loads one, or the file for a static Vite site, and its report says whether ownership will be confirmed after you deploy.