← ClaudeAtlas

citability-auditlisted

Audit a page for citability — AI-crawler access, llms.txt, answer-shaped headings, structured data, classic on-page SEO — then apply the ordered fix list in the codebase and re-audit. $0.01 per audit.
zaialamm/seo-ai-visibility-skills · ★ 0 · AI & Automation · score 70
Install: claude install-skill zaialamm/seo-ai-visibility-skills
# Citability audit ## Goal Find out why a page is or isn't citable by search and AI answer engines, fix it, and prove the fix with a second audit. The audit returns an ordered work list; your job is to work through it, not to summarise it. ## Required inputs - An absolute `http(s)` URL of one page. Ask if the user gave only a domain — audit the homepage first unless they name a page. - Whether the site's source is in the working directory. If it is, you apply fixes; if not, you hand the user a fix list they can give to whoever owns the site. ## Before spending - Call `citable_prices` (free) once per session. It returns the wallet, network, per-call prices and the spend cap (`CITABLE_MAX_PRICE`). - One audit is $0.01. Ask before auditing more than 5 pages in one go. - Failed calls are never charged. A paid result carries `_payment.transaction`, the settlement signature. ## Tools - `citable_onpage_audit(url)` — $0.01. Returns `score` (0–100), `checks[]` (each with `id`, `status`, `weight`, `current`, `fix`) and `topFixes[]`, an ordered list of what to change first. ## Workflow 1. Run `citable_onpage_audit` on the URL. Read `score` and `topFixes[]`. 2. Report the score in one line, then the top fixes as a numbered list in the order the audit gives them — that order is by weight, so it is the order to work in. 3. If the source is available, apply fixes in that order. Typical mappings: | Check | Where it lives | Fix | |---|---|---| | `ai-crawler-access` | `robo