SEO Project Manager: The Role, the Artefacts and How to Run an SEO Project
What an SEO project manager owns, the four documents the job runs on, a working sprint cadence, and how to get technical fixes through a development queue.
Published by AI Knows Us · Updated 12 October 2026
An SEO project manager turns a list of search recommendations into work that actually ships. The role owns scope, sequence, dependencies and delivery: it decides what order the fixes happen in, gets them into the queues of the developers, writers and designers who will do them, removes whatever is blocking them, and reports on what moved. The specialist decides what should be done and why. The project manager makes sure it happens, on a date, with the right people booked.
Search work needs this role more than most marketing disciplines, because almost nothing in SEO can be delivered by the SEO team alone. A title tag change needs a content system. A speed fix needs an engineer. A new page set needs writers, legal review and design. Recommendations that sit in a spreadsheet for six months are the normal failure mode, and a project manager is the cure for it.
What the role owns
- The roadmap. One view of everything agreed, sequenced by impact and effort, with named owners and dates.
- The backlog. Everything not yet scheduled, scored consistently so the next decision is quick.
- Dependencies. Knowing that the hreflang work cannot start until the new URL structure ships, and saying so before anybody promises a date.
- Tickets. Writing them so a developer who knows nothing about SEO can implement without a meeting.
- Stakeholders. Keeping product, engineering, content and leadership aligned on what is happening and why.
- Reporting. What shipped, what it was expected to do, and what the data shows since.
The four artefacts the job runs on
| Artefact | Contents | Updated |
|---|---|---|
| Scored backlog | Item, type, expected impact, effort, dependency, owner, score | Weekly |
| Quarterly roadmap | Committed items by sprint or month, with dates and owners | Monthly |
| Ticket template | Problem, affected URLs, exact change, acceptance criteria, test plan | Per item |
| Responsibility matrix | Who is responsible, accountable, consulted and informed per work type | Quarterly |
Scoring keeps prioritisation out of the realm of opinion. Any consistent model works. Score expected impact, confidence in that estimate, and effort, then sort. The value is not precision, it is that two people looking at the same list reach the same conclusion.
The ticket is the real deliverable
Most SEO recommendations are rejected or mangled because the ticket was written for an SEO audience. A ticket a developer will accept has five parts: what is wrong now, which URLs or templates are affected, the exact change in technical terms, how to tell it worked, and what must not break. Attach a screenshot of the current state and the expected state. Say which template rather than which page, because engineers work in templates.
Title: Add self referencing canonical to product template
Problem: Product URLs with tracking parameters are being indexed
separately, splitting signals across duplicates.
Scope: product detail template only, all locales.
Change: output <link rel="canonical"> with the absolute parameter
free URL of the current product on every product page.
Acceptance: view source on three sample URLs with parameters
appended, canonical shows the clean URL in all three.
Do not change: pagination, filtered category URLs.A cadence that works alongside an engineering team
- Weekly, thirty minutes. What shipped, what is blocked, what goes into the next sprint. Attendance limited to people who can decide something.
- Sprint planning. Bring two or three fully written tickets rather than ten half written ones. A small reliable ask gets accepted repeatedly.
- Monthly, one page. Shipped, in progress, blocked, and the trend lines for the metrics you agreed at the start.
- Quarterly. Re score the backlog, retire what no longer matters, and reset the roadmap with the stakeholders who own the resource.
Reserve a standing slice of engineering capacity rather than negotiating each item. A fixed allocation, even a small one, delivers far more over a year than repeated requests for exceptions.
Running the three common SEO project types
| Project | The thing that sinks it | The control |
|---|---|---|
| Site migration or redesign | SEO consulted after the URL structure is decided | A pre launch checklist signed off before the staging freeze, with redirect mapping complete and tested |
| Content programme | Briefs outpace writer and review capacity | Work backwards from how many pieces legal and editorial can genuinely clear per month |
| Technical remediation | Fifty low priority items crowd out the three that matter | Group items by template and ship by template, highest traffic first |
For a migration specifically, the project manager's job is to be in the room early. The decisions that cost the most to reverse, URL structure, navigation, rendering approach, are all made in the first two weeks of a redesign.
The skills that distinguish a good one
Technical literacy is the entry requirement: status codes, canonicals, rendering, sitemaps, structured data, enough to write a ticket and to judge whether an engineer's objection is real. Beyond that, the job rewards three things. Writing clearly, because the ticket and the one page report are the products. Saying no with a reason, because the backlog is always longer than the capacity. And persistence that does not become friction, since every win depends on somebody else's team.
This page covers managing search work as a project. For what the SEO practitioner role itself involves, see a page on the SEO specialist role, which is a different job.
Where people get stuck on SEO Project Manager
Is an SEO project manager the same as an SEO manager?
No. An SEO manager owns strategy and results for the channel and usually manages people. An SEO project manager owns delivery: sequence, dependencies and shipping. In small teams one person holds both, and the project half is the half that gets dropped when things get busy.
What qualifications help?
Standard project management training such as Scrum or PRINCE2 gives you the vocabulary your engineering counterparts already use, and free SEO certifications from Google and the main tool vendors cover the technical ground. Neither is required. Evidence of work you got shipped carries more weight.
How do you scope an SEO project?
Start from the outcome, then list every team whose work is on the path to it. Scope is whatever those teams will commit capacity for in the period. Anything beyond that is backlog, stated as such, so nobody is surprised later.
How do you prioritise when everything looks urgent?
Score every item the same way on expected impact, confidence and effort, then publish the sorted list. Arguments then happen about the scores, which is a productive conversation, rather than about whose request matters more, which is not.
Which tools does the role use?
Whatever your engineering team already uses, usually Jira, Linear or Asana, plus a shared document for the roadmap and Search Console and your analytics platform for the reporting. Adding a separate SEO specific project tool mainly adds a place for work to hide.
One work type worth adding to the backlog
A new category of item has started appearing on search roadmaps over the past two years. Buyers now ask an assistant the question they used to type into a search box, and the assistant replies with a short list of named companies. That answer is built from sources across the web, it frequently differs from the Google results for the same query, and no rank tracker reports on it, so it never reaches a backlog. AI Knows Us tests what ChatGPT, Gemini, Perplexity and Claude say for a set of buyer questions and shows which sources produced each answer, which turns the subject into tickets a team can actually schedule.