← Plugin catalog
Developer Tools

Sitelemetry

Egenil Teleferik v2.5.1

Audit and improve websites

Create a free account to save this plugin.

From the developer

Declared capabilities

  • Audit security headers, TLS, DNS and email authentication
  • Audit technical SEO: crawlability, indexation, metadata and structured data
  • Add Search Console evidence from the account's existing Google connection

Cost & access

This plugin does not sell products or services and does not process payments. When an audit is not included in the connected account, it states that fact neutrally.

Not specified in the available declarations: limitations.

Onboarding example

Audit my website's security and rank the most urgent fixes.

View onboarding source →

Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 20, 2026. Package observed Nov 20, 2026.

View package source →

Description

From the marketplace listing

Sitelemetry audits websites you own or are authorized to test across six areas: security, technical SEO, AI visibility, analytics and tracking integrations, accessibility and performance. Each audit returns findings with severity, evidence, impact and a concrete fix, so you can see what to change first. A full audit runs every area included in the connected account and returns a combined score across the measured areas. Optional settings: the number of pages to crawl for the SEO and AI visibility audits; whether the SEO audit adds Search Console evidence from the account's existing Google connection, and over how many days; a brand name and competitor names you provide for the AI visibility audit's comparison content; and mobile or desktop measurement for the performance and full audits. Page and question counts are capped by the account's maximum and remaining allowance. Included skills: - Website audit: picks the narrowest audit for your question, explains the result and ranks the top fixes. - Fix and re-test: turns findings into changes for nginx, Apache, Cloudflare, Vercel or Next.js, Netlify and WordPress, then re-runs the same audit and reports what is resolved, still open or not measured. - Pre-launch check: runs the relevant audits one at a time and separates launch blockers from warnings. - AI visibility: proposes robots.txt rules for AI crawlers, schema.org JSON-LD, llms.txt and content edits, each backed by a finding. - Domain verification: explains ownership verification by DNS TXT record, HTTP file or Google Search Console. Who it is for: site owners, developers, agencies working on sites they are authorized to test, and SEO and accessibility practitioners. Limitations: A Sitelemetry account is required; available audits and usage limits reflect the access already assigned to the connected account. Some accounts include security audits only; on those, the other audit areas are not run and the result says so. A completed audit uses the account's audit allowance, and repeating a call can run another audit. Protected security checks require ownership verification of the target hostname; without it, security and full audits run only public checks or return a not-started notice that uses no allowance. Depending on the account, security and full audits of a verified target can include active checks such as port and injection probes; built-in checks send read-style requests and benign probes that are not meant to change the site but can appear in its logs or alerts. Localhost and private-network targets are blocked. Accessibility results come from static WCAG 2.2 checks, and the AI visibility audit checks questions against the site's own content without querying any AI provider. The performance audit sends the target URL to Google PageSpeed Insights. Audits are automated checks, not a manual security or accessibility review. Connections use OAuth.

Language: English · Automatically detected from descriptions.

What changed

· 3 observations

Capabilities & instructions

App-6a6d31df2f848191acf2daa68c6ab8fb updated; open the comparison for details. Sitelemetry updated; open the comparison for details. Full description changed from “Sitelemetry audits websites across security, technical SEO, AI visibility, analytics and tracking integrations, accessibility, and performance. It...

View comparison →
Capabilities & instructions

App-6a6d31df2f848191acf2daa68c6ab8fb updated; open the comparison for details. Sitelemetry updated; open the comparison for details. Full description changed from “Sitelemetry audits websites across security, technical SEO, AI visibility, analytics and tracking integrations, accessibility, and performance. It...

View comparison →

Technical updates · 1

Package or technical metadata updated

View technical comparison →

Similar plugins

Finding similar plugins… Results will appear here automatically.

Browse plugins →

Keywords

Files & skills

File archives

Plugin package33 files · 441 KBBrowse files →
Skill instructions
ai-visibility6.48 KB

View saved version →

---
name: ai-visibility
description: Use the Sitelemetry AI visibility (GEO/AEO) audit, and the technical SEO audit when it is relevant, on a site the user owns to propose evidence-backed changes such as robots.txt rules for AI crawlers, schema.org JSON-LD structured data, an llms.txt file and content edits, each only where the findings support it. Use when the user asks how AI assistants and AI search can crawl, understand or cite their site, or wants to improve GEO, AEO or structured data.
---

# AI visibility

## Ground rules

- Follow the user's explicit instructions over the defaults in this skill. These rules always apply, even when the user asks otherwise: audit only sites the user owns or is authorized to test; never ask for passwords, API tokens or other credentials; never recommend a different account level, mention costs or suggest changing the account; never invent scores, findings or other results.
- Only audit sites the user owns or is authorized to test. If that is not clear, ask first.
- Reply in the user's language. For the audit tools, set `lang` as described in the `website-audit` skill. `lang` changes the report wording, not the measurement criteria.
- Be precise about what is measured. `audit_ai_visibility` checks entity clarity, answerability, source signals and AI-crawler policy on the site's own pages. Questions are checked against the site's own content; no AI assistant or AI search provider is queried. Nothing here measures or predicts whether an AI assistant mentions or cites the site. Say this when you present results.

## 1. Run the audits

1. `audit_ai_visibility` with `target` and, if needed, `lang`. Optional arguments, only as described here:
   - `brand`: when the user names their brand, pass it (1-200 characters). Otherwise leave it out; the tool infers the brand from the site.
   - `competitors`: only names that the user supplies in this conversation for comparison content, at most 8, in the user's order. Never suggest, look up or add competitor names yourself, and leave the argument out when the user gives none. The names are used to assess the site's own comparison content; they are names, not audit targets.
   - `maxPages` (1-30) and `promptLimit` (1-24): only when the user asks for a smaller or larger audit. Omitted, they use the account's maximum; default and explicit values are capped by the account's maximum and remaining allowance.
   - The tool has no argument for the user's own questions. Use questions the user gives only when drafting content proposals in the conversation.
2. `audit_seo` on the same target only when the user explicitly asks for a technical SEO or search-engine indexing audit. Questions about AI search or AI crawlers are covered by the first audit. When structured data, crawlability or metadata matter to the request, offer `audit_seo` as a follow-up and say that it is a separate audit that uses the account's allowance. Start it only after the first audit has returned.

Handle errors, "Audit not started" prerequisites and slow audits as in the `website-audit` skill: one audit at a time, repeat the identical call once if a call times out, and relay access or allowance messages neutrally. If the result covers fewer pages or questions than were requested, say so.

## 2. Map findings to changes

Propose a change only when a returned finding, or its evidence, supports it. Cite the finding next to each proposal.

| Finding area | Change to propose |
|---|---|
| AI-crawler policy: crawlers blocked, rules unclear or inconsistent | robots.txt rules per crawler |
| Structured data missing, invalid or not describing the main entity | schema.org JSON-LD for the real organization, site and page types |
| Entity clarity | clear statements of who the organization is, what it offers and where, on the home and about pages |
| Answerability | answer-first sections and FAQs based on real customer questions |
| Source signals | author and date information, about and contact pages, refer

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 4 — file references are metadata, not package contents.

domain-verification6.75 KB

View saved version →

---
name: domain-verification
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.
---

# Domain verification

## Ground rules

- 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.
- Reply in the user's language.
- Verification shows that the user controls the site. Help only with sites the user owns or administers, and never suggest ways around verification.
- 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.
- When a tool asks for verification, no audit ran and no audit allowance was used.
- 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.

## 1. Read the reason

The result text begins "Audit not started. No audit quota was used." Read `reason` in `structuredContent` when present; otherwise match the sentence in the text.

| `reason` | Text says | Meaning | What to do |
|---|---|---|---|
| `target_verification_required` | Verify ownership of this target | No current verification for this hostname | Choose a method (section 2) |
| `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 |
| `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 |

Verification 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.

## 2. Verification methods

The 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.

### DNS TXT record

- Name: `_sitelemetry-challenge.<hostname>`, for example `_sitelemetry-challenge.example.com`, or `_sitelemetry-challenge.www.example.com` for the `www` host.
- Value: the token, exactly.
- Many DNS panels add the domain automatically; then enter only `_sitelemetry-challenge` (or `_sitelemetry-challenge.www`) in the name field.
- 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`.

### HTTP file

- URL: `https://<host>/.well-known/sitelemetry-verification.txt`
- Content: only the token, as plain text. Surrounding whitespace is ignored. The file must be smaller than 2 KB.
- 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.
- Where the file 

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 3 — file references are metadata, not package contents.

fix-and-retest6.12 KB

View saved version →

---
name: fix-and-retest
description: Turn Sitelemetry audit findings into concrete fixes for the user's stack (nginx, Apache, Cloudflare, Vercel or Next.js, Netlify, WordPress), apply them with the user's approval or hand them over ready to use, then re-run the same audit on the same target and report honestly what is resolved, still open or not measured. Use after an audit when the user asks how to fix the findings, wants the changes made, or wants to confirm that a fix worked.
---

# Fix and re-test

## Ground rules

- Follow the user's explicit instructions over the defaults in this skill. These rules always apply, even when the user asks otherwise: change and re-test only sites the user owns or is authorized to test; never ask for passwords, API tokens or other credentials; never recommend a different account level, mention costs or suggest changing the account; never invent scores, findings or other results.
- Only change and re-test sites the user owns or is authorized to test.
- Reply in the user's language. For the audit tools, set `lang` as described in the `website-audit` skill.
- Base every fix on a returned finding: its evidence, impact and `remediation`. If you suggest something the audit did not report, label it as an extra suggestion.
- Never say a fix worked until a re-test has measured it.

## 1. Start from real findings

Use the findings of an audit from this conversation. If there are none, run one first with the `website-audit` skill. For every finding, note its `findingKey`, severity, title and affected location (the `Affected location:` line in `evidence`, when present). Also note the exact tool and every argument of that run (`target`, `lang`, and any of `modules`, `maxPages`, `strategy`, `includeSearchConsole`, `searchConsoleDays`, `promptLimit`, `brand` or `competitors` that were used, with `competitors` in the same order). The re-test must repeat them.

## 2. Identify the stack

Ask the user, or infer it from the project when you can read its files. If the stack is unknown, write the fixes in stack-neutral terms first, in the same answer, and ask for the stack only to give exact snippets.

| Signal | Stack |
|---|---|
| `nginx.conf`, `sites-available/`, `conf.d/` | nginx |
| `.htaccess`, `httpd.conf`, `apache2.conf` | Apache |
| Site proxied through Cloudflare, rules in the Cloudflare dashboard | Cloudflare |
| `vercel.json`, `next.config.js`, `next.config.mjs`, `next.config.ts` | Vercel or Next.js |
| `netlify.toml`, `_headers`, `_redirects` | Netlify |
| `wp-config.php`, `wp-content/` | WordPress |

When a CDN or proxy sits in front of the origin, it can add, replace or cache headers. Decide which layer owns each header and set it in one place.

## 3. Write the fixes

Work from critical to info. For each finding give:

- what changes and where (file path or dashboard location);
- the change for the user's stack, adapted to the site;
- the risk and how to roll it back;
- how to check it before re-testing, for example `curl -sI https://example.com/` for response headers.

Starting points for common findings (security headers, HTTPS redirect, HSTS, server version disclosure, caching, compression and email DNS records) are in [stack snippets](references/stack-snippets.md). Load it when you write a fix for one of these; adapt the snippets to the site and do not paste them blindly.

Safety rules:

- **Content-Security-Policy**: start with `Content-Security-Policy-Report-Only`, check the browser console for violations, then enforce. A strict policy copied without testing breaks sites.
- **HSTS**: start with a short `max-age`. Add `includeSubDomains` only when every subdomain serves HTTPS, and `preload` only when the owner decides to submit the domain to browser preload lists.
- **DNS and email records** (SPF, DKIM, DMARC, CAA): the user changes these at their DNS provider. Start DMARC at `p=none` with reports before moving to `quarantine` or `reject`.
- Never ask for or handle passwords, API tokens or hos

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 4 — file references are metadata, not package contents.

pre-launch-check6 KB

View saved version →

---
name: pre-launch-check
description: Run a pre-release check of a website the user owns with Sitelemetry security, performance and accessibility audits, plus technical SEO when the site is meant to be indexed, then summarise launch blockers versus warnings using only measured results. Use when the user is about to launch, deploy, go live, migrate or redesign a site and wants to know what must be fixed first.
---

# Pre-launch check

## Ground rules

- Follow the user's explicit instructions over the defaults in this skill, including which audits to run. These rules always apply, even when the user asks otherwise: check only sites the user owns or is authorized to test; never ask for passwords, API tokens or other credentials; never recommend a different account level, mention costs or suggest changing the account; never invent scores, findings or other results.
- Only check sites the user owns or is authorized to test. If that is not clear, ask first.
- Reply in the user's language. For the audit tools, set `lang` as described in the `website-audit` skill.
- The security audit sends test requests to the site. Depending on the account and on ownership verification, these can include active checks such as port and injection probes. Built-in checks send read-style requests and benign probes that are not meant to change the site but can appear in its server logs or firewall alerts. Tell the user before running it on a site that has not been audited before.
- Use only the scores, severities and findings the tools return. Never invent a score, a pass or a measurement.

## 1. Confirm the scope

- **Target**: the public `https://` URL of the site. A staging site must be reachable over public HTTPS; localhost, private addresses and hosts behind a VPN cannot be audited. A staging hostname is a separate host from the production one.
- **Verification**: the security audit's protected checks need current ownership verification of that hostname (see the `domain-verification` skill). The performance, accessibility and SEO audits do not.
- **Indexing**: ask whether the site should be indexed by search engines at launch. Include `audit_seo` only if it should. On a staging site that is deliberately `noindex`, indexation findings are expected; say so rather than listing them as blockers.
- **Runs**: state which audits you will run and that each one uses the account's audit allowance, then start them without waiting for another reply. Mention `audit_full` only if the user asks for a single run, and note that its full scope needs current ownership verification of the hostname, which the separate performance, accessibility and SEO audits do not. `audit_full` measures performance on mobile unless you send `strategy: "desktop"`.

## 2. Run the audits one at a time

When the user names the audits, run exactly those. Otherwise use this order:

1. `audit_security`
2. `audit_performance` with `strategy: "mobile"` (add a `desktop` run only if the user asks)
3. `audit_accessibility`
4. `audit_seo`, if indexing is in scope. Leave `maxPages` at its default unless the user asks. A site that is not live yet usually has no Search Console data; the audit still runs without it. Send `includeSearchConsole: false` if the user does not want Search Console data used.

For each audit:

- Wait for the result before starting the next. If a call times out, repeat the identical call once, as described in the `website-audit` skill. Never start a duplicate audit.
- Keep the same `target` and `lang` on every call.
- If the text begins "Audit not started", or `structuredContent.status` is `action_required`, no audit ran and no allowance was used:
  - A verification reason on `audit_security` (`target_verification_required`, `target_reverification_required` or `verification_scope_required`): record security as not measured, continue with the other audits, and point to the `domain-verification` skill.
  - `entitlement_required` or `usage_limit_reached`: note it neutrally wit

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 3 — file references are metadata, not package contents.

website-audit10.1 KB

View saved version →

---
name: website-audit
description: Run a Sitelemetry audit on a website the user owns or is authorized to test and present the findings ranked by severity with the top fixes. Use when the user asks to audit, scan, check or score their own site for security, technical SEO, AI visibility, analytics and tracking, accessibility (WCAG) or performance (Core Web Vitals), asks for an overall site health check, or asks what an audit result, access message or allowance message means.
---

# Website audit

Use the Sitelemetry audit tools to measure a website and explain what to fix first.

## Ground rules

- Follow the user's explicit instructions over the defaults in this skill. These rules always apply, even when the user asks otherwise: audit only sites the user owns or is authorized to test; never ask for passwords, API tokens or other credentials; never recommend a different account level, mention costs or suggest changing the account; never invent scores, findings or other results.
- Only audit sites the user owns or is authorized to test. If that is not clear, ask before calling any tool. Do not audit competitors or other third-party sites, even when a tool would accept the target.
- Reply in the user's language. Set `lang` to it when it is one of `en`, `tr`, `es`, `de`, `fr`, `pt`, `it`, `ja` or `zh`; otherwise leave `lang` out and translate your summary yourself. `lang` changes the wording of the result, not what is measured.
- The audits run from Sitelemetry's servers. A completed audit uses the connected account's audit allowance. A result that says "Audit not started" uses none, and a failed audit releases what it reserved. An identical call made while the first run is still in progress continues that run; for a short time after it finishes, it can return the same result. Any other repeated or changed call can run another audit and use more allowance.
- Security and full audits send test requests to the site. Depending on the account and on ownership verification, these can include active checks such as port and injection probes. Built-in checks send read-style requests and benign probes that are not meant to change the site but can appear in its server logs or firewall alerts. Say this before the first security or full audit of a site.
- The host may ask the user to confirm each audit call. If the user declines, do not call the tool and do not report it as a failed audit.
- Never invent scores, grades, findings, measurements or links.

## 1. Get the target and the area

- If the user's message names a site and an area, use them. If only a site is given and the area is unclear, ask, or use `audit_full` when the user wants everything.
- `target` is a public `https://` URL or a bare hostname such as `example.com`. Localhost, private addresses, credentials in the URL and `#fragment` are not accepted.
- Ownership verification covers a hostname. `example.com` and `www.example.com` are different hosts, so use the host the user verified in Sitelemetry for security and full audits.
- Keep the same `target` spelling, `lang` and other arguments on every retry and re-test.

## 2. Pick the narrowest tool

| The user asks about | Tool | Optional arguments besides `target` and `lang` |
|---|---|---|
| Security headers, TLS, DNS, email authentication, exposed files | `audit_security` | `modules`, only when the user names specific checks |
| Crawlability, indexation, metadata, structured data, internal links | `audit_seo` | `maxPages` (1-30, default 8), `includeSearchConsole` (default `true`), `searchConsoleDays` (`7`, `28` or `90`, default `28`) |
| AI visibility, GEO, AEO, AI crawler policy | `audit_ai_visibility` | `maxPages` (1-30), `promptLimit` (1-24), `brand`, `competitors`; see the `ai-visibility` skill |
| Analytics, tags, marketing pixels, consent, site verification tags | `audit_integrations` | none |
| Accessibility, WCAG | `audit_accessibility` | none |
| Speed, PageSpeed, Core Web Vitals | `audit_performance` | `strategy`: `m

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 4 — file references are metadata, not package contents.

Release notes

Sitelemetry 2.5.1 declares the existing Sitelemetry MCP connection at https://sitelemetry.com/mcp in the package; authentication stays with the existing app connection. It includes the five skills and seven audit tools described below. The ai-visibility skill now describes a deliberate AI training opt-out in robots.txt as the info-level finding that the technical SEO audit reports, separate from the low-severity finding for blocked AI search crawlers. Sitelemetry 2.5.0 adds five skills and an updated listing. The MCP server URL (https://sitelemetry.com/mcp) and the seven audit tool names are unchanged. The audit tools already include these options, which were approved separately and are not changed by this version (new inputs are optional; existing inputs keep their types and allowed values; output schemas and the readOnlyHint, destructiveHint and openWorldHint values are unchanged): - audit_seo: new includeSearchConsole and searchConsoleDays (7, 28 or 90) inputs; the maxPages description now states that it is capped by the account's maximum and remaining allowance. - audit_ai_visibility: new maxPages, promptLimit, brand and competitors inputs. - audit_full: new strategy input (mobile or desktop) for the performance area, and the title "Full audit (all included areas, one score)". - Accurate scope wording in the audit_security, audit_seo, audit_ai_visibility and audit_full descriptions: the default security checks follow the connected account; active checks such as port and injection probes run only on a target whose host the account has verified; the AI visibility audit checks questions against the site's own content and queries no AI provider; the full audit covers the areas the account includes; a not-started notice uses no allowance; and repeating a call can run another audit. New skills: - website-audit: chooses the narrowest audit, reads results and access or allowance messages, and ranks the top fixes. - fix-and-retest: turns findings into fixes for nginx, Apache, Cloudflare, Vercel or Next.js, Netlify and WordPress, then re-runs the same audit and compares the results by finding. - pre-launch-check: runs security, performance, accessibility and SEO audits one at a time and separates launch blockers from warnings. - ai-visibility: proposes robots.txt, JSON-LD, llms.txt and content changes backed by AI visibility findings. - domain-verification: explains ownership verification by DNS TXT record, HTTP file or Google Search Console, then retries the same audit. Listing: new long description, starter prompts and capability labels, brand colors and dark-theme icons. The package now uses the Agent Plugins format with review and onboarding metadata.

Declared in the saved package. Remote tools may change independently.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package license
MIT
Package author
Egenil Teleferik
Keywords
See keywords
Listing translations
de-DE, es-ES, fr-FR, it-IT, ja-JP, pt-BR, tr-TR, zh-CN
Getting started skill
./skills/website-audit/SKILL.md
Commerce declaration
Does not support commerceThis does not establish whether access is free or paid.

Declared capabilities

  • Audit security headers, TLS, DNS and email authentication
  • Audit technical SEO: crawlability, indexation, metadata and structured data
  • Add Search Console evidence from the account's existing Google connection
  • Check AI visibility readiness and AI crawler policy on the site's own content
  • Detect analytics, tag manager, pixel and consent integrations
  • Run static WCAG 2.2 accessibility checks
  • Measure performance and Core Web Vitals on mobile or desktop
  • Run a full audit across the areas included in the account, with one combined score
  • Turn findings into stack-specific fixes and re-test them
  • Separate launch blockers from warnings before a release
  • Explain ownership verification by DNS, HTTP file or Search Console

Package observed Nov 20, 2026.

Technical details
First seen
Sep 30, 2026 · 22:02 UTC
Last seen
Nov 20, 2026 · 06:00 UTC
Latest observed change
Nov 18, 2026 · 18:11 UTC
Collection status
Collected

plugin_asdk_app_6a6d31df2f848191acf2daa68c6ab8fb

Download plugin data (JSON)

Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.