SEO SOP: the eight standard operating procedures an SEO team needs, and a template for writing each one

An SEO SOP (standard operating procedure) is a short written document that tells anyone on your team exactly how to do one recurring SEO task: who does it, what starts it, which steps to follow in order, what to check before calling it done, and where the result is recorded. Most teams need about eight of them: publishing a new page, updating an old page, changing a URL, the weekly Search Console check, the monthly technical check, investigating a traffic drop, giving access to an outside supplier, and reporting. Write each one on a single page, test it by having someone new follow it, and review it every quarter.

Why an SEO team needs SOPs at all

Most SEO damage is not caused by a bad strategy. It is caused by a routine task done differently each time. A developer changes a URL without a redirect. A writer publishes a page with no internal links. A freelancer gets owner access to Search Console and keeps it after the contract ends. Each of these is a process gap, and a written procedure closes it.

SOPs also make the work transferable and checkable: when the person who "knows how we do it" is away, the work carries on, and a manager can compare what was done with what the procedure says.

The template: nine fields per SOP

Keep every SOP in the same shape so people can scan them quickly.

Field	What to write
Name	A verb and an object, for example "Publish a new page".
Purpose	One sentence on what goes wrong if this is skipped.
Owner	One named role that is accountable, not a team.
Trigger	The event or date that starts it.
Inputs	What must exist first: a brief, access, a URL list.
Steps	Numbered, each one an action a person can tick.
Done check	How you prove it worked, with the tool you use to check.
Record	Where the result is logged, such as a change log or ticket.
Review date	When the SOP itself is next read and updated.

The "done check" field matters most. A step list without a check tells people what to do but not how to know they did it right.

The eight SEO SOPs most sites need

1. Publish a new page

Trigger: a page is approved for publishing. Steps: confirm the target query is not already the target of another page on your site, so two pages do not compete; write a unique title and meta description; use one main heading; add at least two internal links from relevant existing pages; add the page to the sitemap if your platform does not do it automatically; publish. Done check: inspect the live URL in Search Console's URL Inspection tool. Google's help page for the tool says it can "test whether a page on your site might be indexable" and lets you request indexing, with a daily limit of requests per property. For scoring the page against its query before it goes live, an on-page SEO analysis gives the checklist.

2. Update an existing page

Trigger: the page has lost clicks for three months in a row, or the facts on it have changed. Steps: compare the page's queries in the Search Console Performance report before and after the drop; update facts, dates and examples; keep the URL the same; note the change and date in your change log. Done check: the live page shows the new content and the URL has not changed.

3. Change or remove a URL

This is the SOP that prevents the most expensive mistakes. Trigger: any request to rename, move, merge or delete a page. Steps: list every old URL; map each one to its closest new URL; set up a permanent server-side redirect (Google's redirect documentation lists HTTP 301 and 308 as permanent); update internal links so they point straight at the new URL instead of through the redirect; update the sitemap. Google's site move guidance says to "keep the redirects for as long as possible, generally at least 1 year". Done check: request each old URL and confirm it returns a single redirect to the right page, not a chain. For a full platform move, use a site migration checklist rather than this SOP.

4. The weekly Search Console check

Trigger: the same day every week. Steps: open the Performance report and compare clicks and impressions with the previous period; check for messages about security issues or manual actions; check the Page indexing report for a sudden rise in pages that are not indexed. Google's own help says sites with fewer than 500 pages probably do not need the Page indexing report and can use site: searches instead, so write the version that fits your site's size. Done check: a three-line note in the log, even when nothing changed.

5. The monthly technical check

Trigger: first working day of the month. Steps: crawl the site with your crawler of choice; list new broken links, redirect chains, pages blocked by robots.txt, missing titles and duplicate titles; check page speed on your main templates. Done check: each issue has an owner and a date in your ticket system.

6. Investigate a traffic drop

Trigger: organic clicks fall noticeably more than normal week-to-week movement. Google's guide to debugging traffic drops names the main causes to check: an algorithmic update, a site-wide security or spam issue, a technical issue, changing search interest and seasonality, and reporting glitches. Steps, in that spirit: check the Google Search Status Dashboard for incidents; compare the dates of the drop with the record of Google algorithm updates; check Search Console for manual actions and security issues; check whether a release went out that week; compare the same weeks last year for seasonality. Done check: a written cause, or a written "cause not found yet" with the next date to look again.

7. Give or remove access for an outside supplier

Trigger: a new agency, freelancer or tool is hired, or a contract ends. Search Console has owners, full users and restricted users. Owners can add and remove other users and use all tools; full users can view all data and take some actions; restricted users have simple view rights on most data. Google's "Do you need an SEO?" page advises giving an auditor read access to Search Console and not write access at the audit stage. Steps: give the lowest role that lets the supplier do the job; record who has access and why; remove access on the day the contract ends. Done check: the user list in Search Console matches your access record.

8. Monthly reporting

Trigger: a fixed date each month. Steps: pull clicks, impressions and conversions from organic search; list the work done that month against the SOPs above; list what is planned next. Done check: the report answers "what changed, why, and what are we doing about it" on one page.

How to write and roll out SEO SOPs

• Start from what you already do. Ask the person who does the task to talk through the last time they did it, and write that down. Then fix it.
• One page per SOP. If it runs longer, it is two procedures.
• Write steps as actions. "Add two internal links" can be ticked. "Consider internal linking" cannot.
• Link to the source rule. Where a step comes from Google's documentation, link to it, so people can check it has not changed.
• Test with a new person. If someone new cannot follow it without asking questions, rewrite the steps they asked about.

Keep them in one shared place with the review date visible, and review each one quarterly so the steps match the tools you actually use.

Questions about writing an SEO SOP

What does SOP mean in SEO?

SOP stands for standard operating procedure. In SEO it is a written, step-by-step process for a recurring task, such as publishing a page or redirecting a URL, so it is done the same way every time.

How many SEO SOPs does a small business need?

Start with three: publish a new page, change or remove a URL, and the weekly Search Console check. Add the others as your site and team grow.

Is an SEO SOP the same as an SEO checklist?

No. A checklist lists what to check. An SOP also names the owner, the trigger, the order of steps and where the result is recorded. A checklist is often one part of an SOP.

Who should own SEO SOPs?

The person accountable for organic search results owns the set. Each individual SOP names the role that runs it, which may be a writer, a developer or an outside agency.

How often should SEO SOPs be updated?

Review each one at least every quarter, and straight away after any change to your platform, your tools or the Google documentation a step relies on.

A procedure for the answers people read instead of your page

Every SOP above measures how your site appears in Google's results. A growing share of buyers now ask ChatGPT, Gemini or Perplexity instead, and those answers name businesses based on what the engines read about you across the web. That is worth its own monthly procedure: the same ten buyer questions, asked the same way, with the named businesses and cited sources written into the log, so you can see whether a change on your site moved the answer. AI Knows Us was built to run that kind of repeatable check across the main assistants.