Documentation / Verify your website
Verify your website
Before WebTestrunner runs browser tests, you must prove you control the site. After you add a website in the dashboard, you receive a unique token. Publish that token with one of the methods below, then click verify. Until verification succeeds, scheduled and manual runs stay blocked for that site.
The examples on this page use token 123456789. Your dashboard shows your real token—always use that value.
File method
Publish a plain text file at your site root whose name and content are your token:
- URL:
https://your-site.example/123456789.txt - Body: only the token (
123456789), no extra whitespace or HTML
We fetch that URL over HTTPS and check that the response body matches your token.
Meta tag method
Add this tag to the <head> of your homepage (or the base URL you registered):
<meta name="webtestrunner.validate" content="123456789" />
Meta name: webtestrunner.validate. Content must equal your token exactly.
DNS TXT method
Add a TXT record on the domain (or subdomain) that matches your site. Include your token in the record value. DNS propagation can take a few minutes to hours depending on your provider—retry verification after the record is visible publicly.
Tips
- Verification tokens are time-limited (about 48 hours). If yours expires, generate a new one from the dashboard and publish it again.
- The registered base URL must match how you serve the site (including
https://and any path prefix if the app lives under a subdirectory). - You only need one successful method. Keep the file, meta tag, or DNS record in place so future re-checks can succeed.
Next steps
After the site shows as verified, build a browser test, then choose a schedule. Or jump to the dashboard.