onsite-audit · git:20260718.7d82de8 · 2026-07-18 · sha256 f35569e6eaa4fa65

onsite-audit git:20260718.7d82de8A

Immutable. This exact content is served forever at /api/v1/blob/f35569e6eaa4fa65.

---
name: onsite-audit
description: Use to audit on-page SEO for a URL or a whole site section - "audit this page", "on-page check", /organic-os:onsite-audit. Read-only; needs no credentials for public checks.
---

# On-page audit (read-only)

1. Read profile if a brain repo exists (optional - this skill also works bare).
2. Public checks per URL (WebFetch): title (length, keyword presence),
   meta description, H1 count, heading structure, canonical, robots meta,
   image alts, internal links out, JSON-LD present/valid, answer-capsule
   presence in the first 200 words, server-rendered content check.
3. If CMS credentials exist: pull the post via the CMS adapter (WordPress
   today) with `get_post` + `get_rendered_head` for the rendered truth;
   list the SEO meta field values (RankMath fields on WordPress).
4. Launch technical-seo-auditor for site-level context when auditing > 3 URLs.
5. Output: per-URL scorecard table + prioritized issue list. File signals for
   P0/P1 issues if a brain repo exists. Propose nothing here; that is
   onsite-propose's job.

At each stage boundary, append a one-line progress marker with a UTC
timestamp to the run report file before starting the stage - headless runs
are watched by tailing that file, not a terminal.