Playbook
How to run an on-page SEO audit that gets fixed
From picking the pages to reporting to a client, in 8 steps (about 33 minutes to read). The guides explain each issue; this is the process around them.
- 1Pick the pages to auditMost SEO problems come from templates, so one page per template finds most of them. How to list a site's page types and choose which to audit.
- 2Run the auditOpen the page, run the Issues tab and check the links. What SEOSnip reads on each page, and when a result can't be trusted.
- 3Read the resultsErrors stop a page being indexed; warnings are improvements. The judgement calls behind SEOSnip's checks, explained so you can disagree.
- 4Triage: decide what's worth a ticketIndexing blockers first, then template-wide problems, then single pages. How to group issues, drop the ones that don't apply and avoid duplicate tickets.
- 5Write tickets developers act onWhat's wrong, the evidence, how to fix it and which pages it covers. How to turn an audit issue into a ticket a developer can fix without asking you anything.
- 6Hand off to developersShare a ticket with a link, export it to Jira, Linear, GitHub, Word or PDF, or let an AI agent work the board through MCP.
- 7Check it's fixedCheck if fixed re-runs the same check on the same page and records the result. How to verify fixes, and what to re-audit after a release.
- 8Report to the clientBuild a presentation from your tickets: what was found, what's fixed and what's next, in plain words, shared as a link or a PDF.
Find these issues on any page
SEOSnip checks the page in your browser, compares the server HTML with the rendered page, and turns each issue into a ticket with the evidence attached.