Marketing/First-party starter playbook

Weekly website quality audit

Check public pages for accessibility issues, broken links, and copy mistakes.

  • Web fetch (built in)
// what it does
  1. 01Confirm scope. Read the supplied URLs and audit goals. Plan no more than 20 total page fetches, counting audits, link inventories, target checks, and retries. Prioritize the highest-value pages or ask for a smaller batch rather than silently skipping work.
  2. 02Capture each rendered page. Call web_fetch in audit mode for every page. Use the rendered Markdown to review visible copy and the accessibility tree to inspect roles, names, states, and heading hierarchy. If a page loads incompletely, retry once with an appropriate wait_for_selector.
  3. 03Check links when requested. Call web_fetch in links mode to inventory visible or same-origin links. Flag suspicious, malformed, duplicated, or empty destinations; do not claim a link is broken unless the available evidence shows a failure.
  4. 04Analyze findings. Identify likely typos, inconsistent terminology, missing or unclear accessible names, skipped heading levels, misleading roles, and other concrete issues visible in the captured representations.
  5. 05Report. Group findings by severity and page. For every finding include the URL, the observed evidence, why it matters, and a specific recommended fix. Separate confirmed issues from items that need a visual or manual assistive-technology check.
// guardrails in the draft

Inspect only public pages the user is authorized to audit. Respect site terms and robots guidance; never try to bypass bot protection or authentication.

Treat web_fetch output as evidence, not a complete WCAG conformance test. It does not prove color contrast, keyboard behavior, focus order, target sizing, or screen-reader usability; label those as manual follow-ups.

Quote only the minimum page text needed to identify a typo or explain a finding.

Never invent content, DOM state, response status, or link behavior that the captured result did not show.

Keep one run to at most 20 page fetches; recommend another run for a larger site.

Make weekly website quality audit yours.

Request access and we'll start with a private draft. You keep control of the tools, permissions, tests, and publication decision.