SEO project Gantt chart template: audit, fixes, content, links
An editable SEO project Gantt chart: audit, keyword research, technical fixes, content, publication, outreach and a measurement wait, with dependencies and milestones. Durations are illustrative.
What the SEO project gantt chart template: audit, fixes, content, links process is
An SEO project is several streams of work that look independent and are not. Technical fixes, new pages, refreshed pages and outreach can all be done by different people at the same time, but a new page published onto a site with unresolved crawling problems, or outreach started before there is anything to link to, wastes the effort. The useful question for the plan is what each stream waits for. A task list sorted by owner cannot answer it, and a timeline with dependencies can.
This template has five groups: Audit and plan, Technical fixes, Content, Links and outreach, and Measure. "Set goals and scope" is the only starting task. "Set up search and analytics tracking", "Technical and content audit" and "Keyword and search intent research" then run side by side, and the "Priorities agreed" milestone waits for all three, so nothing is fixed or written before the team has agreed what matters most. Technical work and content both start from that milestone.
In the technical group, "Fix crawl and indexing issues" (5 working days) and "Page speed and mobile fixes" (8) run together, and "Structured data and internal links" starts two working days after the crawl fixes start. In the content group, "Content briefs" lead to "Write new pages" (12), while "Refresh existing pages" (10) starts two working days after the briefs start. "Pages published" waits for "Edit and approve content" and for "Technical fixes live". With these illustrative durations the technical fixes are done 12 working days before the content is, so the content chain sets the publication date.
After publication, "Outreach and link building" (15 working days) starts, having been planned earlier in "Plan outreach and partnerships". "Wait for recrawl and indexing" is 10 working days of waiting, not work: it is the time you allow before you look at the data. "Review search and traffic data" and "Report and choose the next round" follow. How long search engines take to recrawl and how pages perform are outside your control, so the chart schedules the work and the waiting, and promises no ranking or traffic result. All durations are illustrative; set your own from your site.
If the site itself is being rebuilt, start from the website plan at /templates/website-project-gantt-chart, which has its own redirects and SEO checks. For a regular publishing rhythm rather than a one-off project, see /templates/content-calendar-gantt-chart, and for a time-boxed promotion see /templates/marketing-campaign-gantt-chart. For the approval step in content, the document approval workflow at /templates/document-approval-workflow and the change request process at /templates/project-change-request-process show the process side. For how dependencies and the critical path work, see /guides/gantt-chart-dependencies and /guides/gantt-chart-critical-path.
What this flowchart covers
In this template
- Five groups, Audit and plan, Technical fixes, Content, Links and outreach and Measure, with 19 tasks and three milestones: "Priorities agreed", "Technical fixes live" and "Pages published".
- An audit that runs in parallel: "Technical and content audit" (6 working days), "Keyword and search intent research" (5) and "Set up search and analytics tracking" (2) all follow "Set goals and scope" and all must finish before "Priorities agreed".
- A start-to-start overlap in each stream: "Structured data and internal links" starts two working days after "Fix crawl and indexing issues" starts, and "Refresh existing pages" starts two working days after "Content briefs" starts.
- A publication gate: "Pages published" waits for "Edit and approve content" and for "Technical fixes live", and "Outreach and link building" waits for it as well.
- A waiting period that is part of the plan: "Wait for recrawl and indexing" (10 working days), then "Review search and traffic data" and "Report and choose the next round".
When to use this template
- You are planning a site-wide SEO project with technical, content and link work that must be ordered and shared between people.
- You need to show a stakeholder when fixes go live, when pages are published and when results can first be reviewed.
- You want to see which stream sets the publication date, and how much slack the other one has.
- You repeat the project each quarter or for each client and want a standard plan to edit.
The plan, task by task
Every task in the chart with its length in working days and what it waits for. A dependency is a step number; SS is start-to-start, FF is finish-to-finish, and +n is a lag in working days.
| # | Task | Group | Working days | Depends on |
|---|---|---|---|---|
| 1 | Set goals and scope | Audit and plan | 2 | |
| 2 | Set up search and analytics tracking | Audit and plan | 2 | 1 |
| 3 | Technical and content audit | Audit and plan | 6 | 1 |
| 4 | Keyword and search intent research | Audit and plan | 5 | 1 |
| 5 | Priorities agreed | Audit and plan | Milestone | 2, 3, 4 |
| 6 | Fix crawl and indexing issues | Technical fixes | 5 | 5 |
| 7 | Page speed and mobile fixes | Technical fixes | 8 | 5 |
| 8 | Structured data and internal links | Technical fixes | 4 | 6SS+2 |
| 9 | Technical fixes live | Technical fixes | Milestone | 7, 8 |
| 10 | Content briefs | Content | 4 | 5 |
| 11 | Write new pages | Content | 12 | 10 |
| 12 | Refresh existing pages | Content | 10 | 10SS+2 |
| 13 | Edit and approve content | Content | 4 | 11, 12 |
| 14 | Pages published | Content | Milestone | 9, 13 |
| 15 | Plan outreach and partnerships | Links and outreach | 3 | 5 |
| 16 | Outreach and link building | Links and outreach | 15 | 14, 15 |
| 17 | Wait for recrawl and indexing | Measure | 10 | 14 |
| 18 | Review search and traffic data | Measure | 3 | 17 |
| 19 | Report and choose the next round | Measure | 2 | 18 |
How it works
Agree priorities before any work starts
Keep the audit, the keyword research and the tracking set-up as three tasks that all lead to "Priorities agreed". Technical and content work then start from one shared decision.
Run technical fixes and content side by side
Give each stream its own tasks and durations. Use start-to-start links with a small lag, as in "Structured data and internal links", where work can begin before the previous task is finished.
Decide what publication waits for
"Pages published" depends on "Edit and approve content" and on "Technical fixes live". Remove the second link if your fixes never need to come first, or add the dependency your site needs.
Plan the outreach after the pages exist
Do the planning early and the outreach itself after publication. Replace the 15-day estimate with your own.
Size the waiting period and write down what you will look at
Set the duration of "Wait for recrawl and indexing" from how often your site is crawled, and put the pages and measures you will review in the task notes before the wait begins.
Add owners, share and export
Put the person in People, record progress as work is done, and share the chart or export a PDF for a client or a manager.
Frequently asked questions
How long does an SEO project take?
It depends on the size of the site, the amount of content and how quickly changes can be released. The durations here are illustrations that add up to about nine weeks. Replace them with estimates from your own team.
Does this chart predict rankings or traffic?
No. It schedules the work and the waiting. How search engines treat the changes, and when, is outside your control, so the chart reserves a period and a review and makes no promise about the result.
Why does publication wait for the technical fixes?
So that new and refreshed pages go live on a site that can be crawled and loads properly. If your fixes can safely follow the pages, delete the link from "Technical fixes live" to "Pages published" and the chart shows the shorter plan.
Can I use this for a single page or a small site?
Yes. Delete the tasks you do not need, keep the audit, the content and the review, and use the simple version of the method in /guides/simple-gantt-chart-for-small-teams.
