← Skills

Tailwin

SEO audit

Inspect selected pages, then use retained evidence to prioritize and verify changes.

  1. Call list_sites to establish scope. audit_url checks one canonical public HTTPS page for citability and structured data, plus homepage AI readability and robots access, without LLM spend. URLs cannot contain queries, fragments or credentials; redirects are rejected, so supply the final URL. Every response is bounded to 512 KB. Unavailable auxiliary evidence returns a null score rather than an access claim. It is not a full-site crawl.
  2. Use inspect_schema for a retained structured-data snapshot and run_pagespeed for actual Lighthouse lab and CrUX field evidence. PageSpeed requires an explicit device and quota confirmation; follow the PageSpeed guide.
  3. Retained history, comparisons and fix briefs use the audit-history workflow. Preserve observation dates, source scope and rules versions, and distinguish unavailable categories from resolved findings.
  4. These examples describe implemented tools, not a live-provider verification. A configured provider and a successful real response are still required before claiming a current measurement.

Tool call examples

These are the params for a JSON-RPC tools/call request. Replace the example site and snapshot IDs with IDs returned by this workspace, and replace example URLs and names with authorized pages and verified facts. Obtain approval before sending confirmMetered: true.

audit_url

{
  "name": "audit_url",
  "arguments": {
    "url": "https://example.com/article"
  }
}
Tailwin: be the answer, not the search result