Verify your domain
Confirm that you own the website you want to audit.
01Why verification comes first
Verification helps restrict scheduled crawling to projects controlled by the user. Do not request audits for a website you are not authorised to manage.
02Option one: add a DNS TXT record
Create a TXT record named _seo-workspace.example.com, replacing example.com with your project domain. Copy the exact seo-verify= value from your project. Do not use the illustrative value shown in a public guide.
03Option two: publish an HTTPS file
Place the exact token at https://example.com/.well-known/seo-workspace-verification.txt. The endpoint must return the token as plain text with a successful response and without redirecting.
04Ask the workspace to check again
Use Verify ownership in your project after saving the change. DNS propagation and server caching can delay detection. Recheck the name, value and destination before trying again.
05After a successful check
Verification expires after the configured ownership window (30 days by default) and can be renewed. Only authorised editing roles can queue a crawl or change integration settings. Clients and analysts require explicit project assignments. Verification does not certify the site as safe or free from SEO issues.
Deployment note: this public UI update does not complete outstanding billing, crawler or account-service certification.
Still need a hand?
Share the page URL, job state and the steps you tried. Do not include secrets.
Contact support