The One Person Agency

Website

Quality Audit

Feed it a crawl. Get back a project plan and a content calendar, with a reason attached to every line.

White: Claude carries the load

Mint: stays human

SEO Sprints (AI WORKFLOW)

Sprint 1

Onboarding

Client setup

Kickoff call

Project plan build

Reporting setup

Sprint 3

Local

Local Audit

Google Business Profile Optimization

Citations + Profile Optimizations

Review system

Sprint 4

Content

Content execution

Content writing

Content editing

Add media

Content publishing

Sprint 5

Links

Link execution

Manual links

Paid links

Sprint 6

Reporting & Comms

Weekly / Monthly Calls

Target pages

Technical implementations

Sprint 2

Foundational

Website Quality Audit

Technical review

Content review

What It Is

The Swiss Army Knife OF SEO AuditS*

Technical

01 Find every technical issue on the site

02 Push each fix straight into the project plan

03 An AI agent or a team member executes it

Content

01 Scrape the content already on the site

02 Generate new content topic ideas

03 Build a strategic roadmap into the project plan

The output

An actionable project plan inside Agency OS, ready for execution the same day.

*Website only. Local and off-site factors are not part of this audit. That's why it's called the Website Quality Audit. Local and links run in their own sprints of the campaign.

Tools · Website Quality Audit

Section One

Audit DEEP DIVE

The Process

Step by step audit process

1 Set up the audit

• Connect Ahrefs, Search Console, GA4

• Screaming Frog crawl: Internal HTML + All Inlinks

• Optional: Redirects, Structured Data, Hreflang

2 Confirm page types

• Correct the pages it was unsure about

• Every rule after this is judged against the page type

3 Technical review

• Approve or reject each finding

• Drop one wrong page, not the whole finding

• Send approved fixes to the plan

4 Content review

• Existing content: one decision per page

• New content: context, universe, competitors, gaps, decide, push

• Finalize the audit

5 View final reporting

• Summary report

• Actions split into technical and content

• The content map

6 Project plans

• Fixes and content land as tasks

• Executed by an AI agent or the team

Tools · Website Quality Audit

Six steps as a flow: left to right across the top row, then left to right across the bottom. ONE, SET UP THE AUDIT. Connect the tools it needs: Ahrefs, plus Search Console and GA4 through Windsor. Then add the manual crawl from Screaming Frog. Two exports are required: Internal filtered to HTML, and Bulk Export, Links, All Inlinks. That second one is the export people get wrong. It is the top menu, not the Inlinks pane at the bottom of the Internal tab, which is one page at a time. All Redirects, Structured Data and Hreflang are optional, and each one lets more rules fire. TWO, CONFIRM PAGE TYPES. Correct anything it was unsure about. This is the cheapest ten minutes in the whole audit, because every rule after it is judged against the type: a service page and a blog post are held to different standards. Get it right here and the findings list is short and correct. THREE, TECHNICAL REVIEW. Approve or reject each finding, then send it to the plan. A finding is one rule across many pages, so if it is right about forty pages and wrong about one, drop that page rather than rejecting the whole thing. Every rejection is remembered against the client, and a rule you overrule repeatedly surfaces so you can turn it off for good. FOUR, CONTENT REVIEW. The big one, which is why it is the dark card. Existing content first: one row per page, not per finding, and one decision each: rewrite, add depth, update for relevancy, retarget, merge, redirect, delete, or leave it alone. Then new content, in order: set the context (the services they sell, the markets they serve, the competitors they actually have, typed as domains); build the universe, which expands every service into the whole search around it as a hub with its supporting pages and questions underneath; review what competitors earn from and the gaps in their own shelf; decide each page, roadmap or ignore; and push what you agreed to. Then finalize the audit. The order inside step four matters in one place: the context comes before the universe, because the universe is built by expanding the services you type in. Skip it and the tool guesses the practice areas off the pages that already exist, which can never find a service they sell and have no page for. That is the most valuable gap on most sites. FIVE, VIEW THE FINAL REPORTING. The summary report, the actions split into technical and content, and the content map. SIX, PROJECT PLANS. The work leaves the tool and becomes somebody's week, executed by an AI agent or a team member. Everything before step four is getting the audit honest. Everything after it is the work leaving the tool.

Technical Review

What it flags and how you decide

The goal: a site Google can crawl, index and trust, with no page leaking the traffic, links or relevance it has earned.

What the audit checks on its own

Broken pages

404s that still carry impressions, backlinks or sessions

Redirects

301s dumping relevance on the homepage

Indexability

Tags, feeds and archives indexed with no content

Canonicals, robots, sitemap

The signals telling Google which page counts

Schema

Structured data missing on the pages that need it

Crawl depth + internal links

Money pages buried or barely linked to

How you decide

Follow the signal. A broken page with traffic or links is P1. One with nothing is a monitor.

Check the page type. Every rule is judged against it.

Drop the page, not the finding. Right about 40 pages, wrong about one? Cut the one.

Working as intended? Leave it as is.

Every call is remembered against the client.

Tools · Website Quality Audit

This is step three of the process, opened up. The goal of the technical review is simple: a site Google can crawl, index and trust, where no page is leaking the traffic, links or relevance it has already earned. The audit does the finding for you. It reads the Screaming Frog crawl alongside Search Console, GA4 and Ahrefs and flags six things on its own. Broken pages, specifically 404s that still have impressions, backlinks or sessions behind them. Redirects, especially 301s sending everything to the homepage, which throws away the relevance of the old page. Indexability, meaning tag pages, feeds and archives sitting in the index with nothing on them. Canonicals, robots and the sitemap, the signals that tell Google which version of a page counts. Schema missing on the pages that need it. And crawl depth and internal links, where money pages are buried too deep or barely linked to. Your job is the decision. Follow the signal: a broken page with traffic or links is a P1 fix, one with no signal at all is something to monitor. Check the page type, because every rule is judged against it. A finding is one rule across many pages, so if it is right about forty pages and wrong about one, drop that page and keep the finding. If a redirect is doing exactly what it should, leave it as is. Every approval and rejection is remembered against the client, so the next audit starts smarter. What you approve goes straight to the plan as tasks.

Content Review

What it flags and how you decide

The goal: every page earns its place, and every service the client sells has a page built to rank for it.

What the audit checks on its own

Missing basics

No title, meta description or H1

Thin pages

Under 618 words, judged by page type

Depth gaps

Too short for a keyword with 500+ searches

Low click-through

1,000+ impressions, under 2% clicks

Striking distance

Ranking 4 to 15 with real impressions

Missing pages

Services and searches competitors win and you don't cover

How you decide

Money pages first. A thin money page is a P1 rewrite.

One call per page. Rewrite, expand, refresh, merge, redirect or leave it.

Context before universe. Type the services they sell, or it can't find what's missing.

Roadmap or ignore. Every new page idea gets a yes or a no.

What you approve lands on the content roadmap.

Tools · Website Quality Audit

This is step four of the process, opened up. The goal of the content review: every page on the site earns its place, and every service the client sells has a page built to rank for it. The audit does the finding. On the existing site it flags six things. Missing basics: no title, no meta description, no H1. Thin pages under 618 words, judged by page type, so a thin money page is treated very differently from a thin blog post. Depth gaps: pages between 618 and 1,499 words that target a keyword with 500 or more searches, too short to compete. Low click-through: pages with over 1,000 impressions and under 2% CTR, which usually means the title and meta are not doing their job. Striking distance: pages ranking 4 to 15 with real impressions, where an on-page update can move them onto page one. And on the new content side, missing pages: the services and searches competitors earn traffic from that the client has no page for. Your job is the decision. Money pages first: a thin money page is a P1 rewrite. Every existing page gets one call: rewrite, expand, refresh, merge, redirect, or leave it alone. Set the context before you build the universe, because the universe is built by expanding the services you type in. Skip it and the tool can only guess from the pages that already exist, so it will never find a service they sell and have no page for, which is the most valuable gap on most sites. Then every new page idea gets roadmap or ignore. What you approve lands on the content roadmap and in the client's project plan.

Outputs

THE FINAL OUTPUTS

Technical matrix

Every technical finding you approved, with the pages behind it, its severity and who it is for. The list a developer works from.

Content roadmap

Every page to write or rewrite, with its keyword, its volume and the brief. It becomes cards on the client’s own content board.

Completed project plans

One Website Quality Audit task on the client’s plan, a subtask per finding. Tick a subtask there and the finding closes in the audit.

Nothing reaches the client until you push it. Approving stages the work; the push happens once, from the Plan tab, where both halves are listed together and you can see what the audit is about to commit somebody to.

Summary · Plan