SEO Agency SOPs: Which Ones You Need and What Goes in Them

SEO agency SOPs are the written procedures that tell your team how recurring delivery work gets done, who owns it, and how you know it was done correctly. An agency needs about eight of them to run SEO without the founder checking every account. The rest are optional. This post lists the eight, defines what every SOP must contain, and writes three of them out in full.

SOPs are the cheapest fix for a common failure: the process lives in one senior person's head, so it breaks when that person is not the one running it. Writing the procedure down is how you find out whether the process exists. The operating model these SOPs plug into is in SEO agency operations.

The SEO agency SOPs worth writing first

An SEO agency needs one SOP per recurring task where a mistake is costly or the handoff changes hands. Start with these.

1. Client intake and access. What you collect and verify before work starts.
2. Scope and backlog setup. How a diagnostic becomes a prioritized, bounded task list.
3. Technical audit. The checks run, in what order, and how findings are rated.
4. Content brief. What a brief must specify before a writer starts.
5. Pre-publish QA. The checks a second person runs before changes go live.
6. Post-release verification. The checks run after changes go live.
7. Monthly reporting. How the report is assembled, reviewed and sent.
8. Scope change and offboarding. How out-of-scope requests and ended contracts are handled.

Do not start by writing all eight. Write the one where your last client problem began.

What every SOP must contain

Every SOP needs the same seven fields, so a new team member can read any of them the same way. If a field is blank, the SOP is not finished.

Two rules keep SOPs honest. First, checks must be checkable. Make sure the page is optimized is not a check. Confirm the title is under the agreed length and unique within the site is. Second, someone other than the author runs the SOP once before it is published. They will find the step the author skipped without noticing.

Worked SOP 1: Client access intake

Trigger: contract signed. Owner: account manager. Inputs: signed scope, client contact list. Output: completed access record filed in the client folder.

1. Send the access request as one message listing every item below, with the client's technical owner copied.
2. Request search console ownership or full-user access for every property variant the site uses.
3. Request analytics access at the level needed to view and, where required, configure goals.
4. Request CMS access with a role that can edit content and metadata, and note whether code changes need a developer.
5. Request hosting, CDN or tag manager access only if the scope includes changes there.
6. Ask who approves content and who can deploy technical changes, and record both names.
7. Ask what SEO work has been done before, and by whom. Request any prior audit or report.
8. Log in to each system yourself and record the date access was confirmed.
9. Chase unconfirmed items on a set day, then escalate to the client sponsor.
10. File the access record and mark intake complete in the project tracker.

Checks: the account manager confirms every item was tested by logging in, not just granted. A second team member confirms the record is filed before delivery starts.

Worked SOP 2: Pre-publish QA

Trigger: a page or change is marked ready for review. Owner: QA reviewer, never the author. Inputs: the brief, the staging or draft link, the page type checklist. Output: signed-off QA record.

1. Open the brief and the draft side by side. Confirm the page targets the intent the brief names.
2. Check the title and meta description against agreed length and uniqueness within the site.
3. Check one h1, a logical heading order, and that headings describe the content beneath them.
4. Check every internal link resolves, uses descriptive anchor text and points to the intended page.
5. Check images have meaningful alt text and sensible file sizes.
6. Check indexing directives: no noindex, correct canonical, correct robots handling for the page type.
7. For template or site-wide changes, test a sample of pages across each template, not just one.
8. Check structured data, if specified, validates without errors.
9. Record pass or fail for each line. Return failures to the author with the exact item.
10. After fixes, re-run only the failed lines, then sign off.

Checks: the reviewer signs the record with name and date. No change goes live without it.

Worked SOP 3: Monthly report preparation

Trigger: reporting day, set per client. Owner: analyst, reviewed by the account manager. Inputs: automated data pull, the month's shipped-work log. Output: report sent, copy filed.

1. Refresh the data pull. Do not retype numbers between tools.
2. List what shipped this month from the work log, one line each.
3. Note any change in search performance for the pages and areas affected by that work.
4. Flag anything that moved without explanation and write what you will check next.
5. Write three to five plain sentences: what we did, what moved, what we do next and why.
6. List blocked items and who each is waiting on.
7. Account manager reads the report as the client would and removes anything the client cannot act on.
8. Send, file a copy, and schedule the next month's priorities in the backlog.

Checks: the account manager confirms every figure in the text matches the data pull, and that each next step maps to a backlog item.

How do you roll SOPs out so they get used?

• Pilot on one account. Run the SOP on one live client before it becomes policy.
• Keep one location. Store every SOP where the team already works, with a single current version.
• Tie checks to release. A change that has no QA record does not ship.
• Review on a date. Compare the SOP with the way work is really done and edit the SOP or the habit.
• Retire dead steps. If a step is skipped by everyone, remove it or find out why it is skipped.

When utilization looks fine but margin is falling, missing or unused SOPs are usually why, as I describe in the post on utilization and margin drift. For help mapping which SOPs you are missing, my agency utilization consulting starts with a workflow audit. AI-search SOPs differ in kind, and I cover them in AEO agency SOPs and GEO agency SOPs.

FAQ

What SOPs does an SEO agency need?

At minimum: client intake and access, scope and backlog setup, technical audit, content brief, pre-publish QA, post-release verification, monthly reporting, and scope change with offboarding. Start with the one where your most recent client problem began, and write the others as each task becomes a costly handoff.

What should an SEO SOP include?

Every SOP should state its purpose and trigger, a single owner, required inputs, numbered steps, checks with a named verifier, the output and where it is filed, and a review date. If any field is blank, the procedure is incomplete and will be followed inconsistently.

How long should an SEO agency SOP be?

As long as one person needs to complete the task without asking questions, and no longer. Most run from eight to fifteen numbered steps. If a procedure needs far more, split it into two. Test length by having someone who has never done the task run it once.

How do you get a team to follow SOPs?

Make the check part of release, so work without a completed record does not ship. Pilot each SOP on one live account, keep a single current version where the team already works, and review it on a date against how work is really done.