{"id":104059,"plugin_id":"plugin_asdk_app_6a6d31df2f848191acf2daa68c6ab8fb","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-18T18:11:13.692Z","digest":"388b39c36f2faabea7089c7fc29212957476559b92c99aa880f1282b59715a31","against":null,"payload":{"description":"Explain and help complete Sitelemetry ownership verification when an audit result says \"Audit not started\" because the target hostname is not verified, the verification has expired, or it does not cover host-level checks. Covers the DNS TXT record, HTTP file and Google Search Console methods, then retries the same audit. Use when an audit asks for verification or the user asks how to verify their site for Sitelemetry.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":341},{"relative_path":"assets/icon-large.png","size_in_bytes":33181},{"relative_path":"assets/icon-small.png","size_in_bytes":7770}],"name":"domain-verification","skill_md_contents":"---\nname: domain-verification\ndescription: Explain and help complete Sitelemetry ownership verification when an audit result says \"Audit not started\" because the target hostname is not verified, the verification has expired, or it does not cover host-level checks. Covers the DNS TXT record, HTTP file and Google Search Console methods, then retries the same audit. Use when an audit asks for verification or the user asks how to verify their site for Sitelemetry.\n---\n\n# Domain verification\n\n## Ground rules\n\n- Follow the user's explicit instructions over the defaults in this skill. These rules always apply, even when the user asks otherwise: help only with sites the user owns or administers; never ask for passwords, API tokens or other credentials; never recommend a different account level, mention costs or suggest changing the account; never invent a verification status, scores, findings or other results.\n- Reply in the user's language.\n- Verification shows that the user controls the site. Help only with sites the user owns or administers, and never suggest ways around verification.\n- Verification is completed in the user's Sitelemetry account on the web, not through the audit tools: the user signs in at https://sitelemetry.com and opens the dashboard's Verified Domains section. Give the user https://sitelemetry.com/access-information#verifiedDomains for the steps. Do not guess other account URLs.\n- When a tool asks for verification, no audit ran and no audit allowance was used.\n- Never ask for passwords, API tokens or DNS, hosting or Google account credentials. The user makes the change, or you edit project files with their approval.\n\n## 1. Read the reason\n\nThe result text begins \"Audit not started. No audit quota was used.\" Read `reason` in `structuredContent` when present; otherwise match the sentence in the text.\n\n| `reason` | Text says | Meaning | What to do |\n|---|---|---|---|\n| `target_verification_required` | Verify ownership of this target | No current verification for this hostname | Choose a method (section 2) |\n| `target_reverification_required` | Renew ownership verification | The verification was last checked more than 30 days ago | Keep the DNS record or file in place and run the check again in the dashboard, or sync Google Search Console again |\n| `verification_scope_required` | The current verification does not cover the requested host-level checks | A URL-prefix verification covers only a few protected checks under that prefix, such as `sql-injection`; the other protected checks need verification of the whole hostname | Verify the whole hostname or the domain, or run only checks that the verified prefix covers |\n\nVerification covers a hostname. `example.com` and `www.example.com` are different hostnames and each needs its own verification; paths and ports under a verified hostname are covered. Verify the hostname the user wants to audit.\n\n## 2. Verification methods\n\nThe dashboard issues a token that starts with `sitelemetry-` and shows the exact record name and file URL for the hostname. Always use the values it shows.\n\n### DNS TXT record\n\n- Name: `_sitelemetry-challenge.<hostname>`, for example `_sitelemetry-challenge.example.com`, or `_sitelemetry-challenge.www.example.com` for the `www` host.\n- Value: the token, exactly.\n- Many DNS panels add the domain automatically; then enter only `_sitelemetry-challenge` (or `_sitelemetry-challenge.www`) in the name field.\n- New records can take from minutes to hours to become visible, depending on TTL. Check with `nslookup -type=TXT _sitelemetry-challenge.example.com` or `dig +short TXT _sitelemetry-challenge.example.com`.\n\n### HTTP file\n\n- URL: `https://<host>/.well-known/sitelemetry-verification.txt`\n- Content: only the token, as plain text. Surrounding whitespace is ignored. The file must be smaller than 2 KB.\n- The URL must answer with a success status over HTTPS with a valid certificate. A redirect to another host, protocol or port fails the check.\n- Where the file usually goes:\n  - Next.js, Vercel and most static site generators: `public/.well-known/sitelemetry-verification.txt`\n  - Netlify: `.well-known/sitelemetry-verification.txt` inside the publish directory\n  - nginx or Apache: the `.well-known` folder in the document root. Make sure rules that hide dot-folders do not block it; in nginx, a `location ^~ /.well-known/ { }` block takes precedence over regex rules that deny dot-folders.\n  - WordPress: the `.well-known` folder in the site's root directory, uploaded with the host's file manager or SFTP\n- Check it with `curl -s https://example.com/.well-known/sitelemetry-verification.txt`; the output must be the token.\n\n### Google Search Console\n\nAvailable when the user connects a Google account that is a verified owner of the property, then syncs properties in the dashboard.\n\n- A Domain property (`sc-domain:example.com`) covers the domain and its subdomains, including host-wide checks.\n- A URL-prefix property covers only that prefix. It authorizes host-wide checks only when it is the root URL of the hostname, such as `https://example.com/`.\n\nAfter publishing the record or file, the user runs the matching verification check in the dashboard. Generating a new code does not verify the site by itself.\n\n## 3. What verification covers\n\n- On an account with security-only access, a default `audit_security` call (or a default `audit_full`, which on such an account runs security only) runs seven public checks without verification: DNS, email DNS, RDAP, TLS, HTTP headers, MITM posture and technology fingerprint. Verification adds checks for HTTP methods, exposed files and paths, and API exposure.\n- On other accounts, the default security scope and `audit_full` need current verification of the hostname. The SEO, AI visibility, integrations, accessibility and performance audits run on public targets without verification.\n- An explicit `modules` list runs without verification only when every module is a public check (`dns`, `dns-email`, `rdap`, `tls`, `http-headers`, `mitm-posture` or `tech-fingerprint`, and `transport-delivery` on accounts that include it). Any other module needs current verification: a few of them, such as `sql-injection`, also accept a URL-prefix verification that covers the target, and the others need verification of the whole hostname.\n- A verification stays current for 30 days after it was last checked. Keep the DNS record or file in place so it can be checked again.\n\n## 4. Retry\n\nRetry only after the user confirms that the dashboard shows the hostname as verified.\n\n- Call the same tool with the same `target` spelling and the same arguments as the rejected call.\n- If the result is again a verification reason, check that the hostname (with or without `www`) matches the verified one and that the verification is current. Do not retry in a loop.\n- Then continue with the `website-audit` skill to present the results.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}