SEO Weekly Report Template: Shipped, Blocked, Ready to Review
A one-page weekly SEO report template that shows verified work, blockers, decisions needed, and search comparisons ready for review.
Template
SEO Weekly Report Template: Shipped, Blocked, Ready to Review
A useful weekly SEO report tells a manager where the work stands before the next meeting. It shows what reached the website, what is waiting on another person, which choice needs an answer, and which past change is finally ready for a result review.
That is more useful than a page of rankings followed by a task list. Rankings can move every week. The questions that keep SEO work moving are usually about implementation, ownership, and decisions.
TL;DR
- Get the one-page SEO weekly report template.
- List shipped work only when the live result has been checked. Label anything else as implemented and awaiting verification.
- Show each blocker with an owner, the action needed, and a date.
- Give decision makers a recommendation and a deadline, not just a question.
- Put Search Console comparisons in the report when the full review period and data are available.
- Link important lines to the URL and evidence so a reader can inspect them.
What belongs in the report
Use one report for one project and one reporting week. Keep it to four sections:
| Section | The reader needs to know |
|---|---|
| Shipped and verified | What changed on which URL, when it went live, and who checked it |
| Blocked | What cannot move, who can unblock it, and by when |
| Decisions needed | The options, your recommendation, the approver, and the decision date |
| Ready for review | Which earlier change now has a complete comparison, what the data shows, and what to do next |
Put the reporting period and update time at the top. If there is no item in a section, write "None this week." Empty space leaves people wondering whether nobody checked.
The copyable report template has fields for each section. It is a writing format; the supporting tasks, approvals, live checks, and performance data should remain in the systems where the team records them.
Shipped means the change is live and checked
For each completed item, include the affected URL, what changed, the live date, verifier, and a link to the evidence. A content brief approved on Tuesday is an approved brief. A page published on Thursday but not checked is implemented and awaiting verification. Keep those states distinct.
A concise line is enough:
/services/seo/ title updated on September 21. SEO lead checked the live HTML title on September 22. Evidence: task T-104 and live check. Recheck after the next service-page template release.This lets a manager accept the work without reopening every ticket. The separate SEO QA checklist shows how to define the live check for titles, canonicals, and indexing directives.
Do not fill this section with work that was merely started. The report should show the number of changes that reached the site and passed their agreed check. A short list of meaningful changes beats a long list of activity.
Blocked work needs a next owner
"Waiting on development" explains little. State the exact handoff: the ticket, affected URL, person or team, action required, date requested, and what slips if it does not move.
For example:
/pricing/ canonical correction is waiting for the September 29 release slot. Web lead owns deployment; SEO lead will verify the live canonical the same day. The page-level result review moves back if the release slips.Separate a true blocker from an item the SEO has not started. A blocker has a defined next action that another person or team must take. If the SEO can move the work today, put it in the plan instead.
Decisions needed should offer a choice
Ask for a decision only after showing the options, recommendation, and consequence. Name the approver and date. This keeps a weekly report from becoming an open-ended request for input.
For example:
Decision by September 28: Approve the revised /integrations/crm/ product claims or return specific corrections. Content lead recommends approving version 2 after product review. If approval moves past Monday, publication shifts into the next week. Owner: marketing director.Keep the proposed page or document linked. If the approver rejects the work, record the reason and new owner. An approval is a decision about the proposed work; it does not mean the page has been published.
Review results when the comparison is ready
Every week, look back at earlier work whose review window has finished. Include the affected URL, change date, before and after dates, filters, source, observed movement, and any other event that could affect the comparison.
Google notes that Search Console data can arrive a few days late. Do not call a comparison ready while its after period is incomplete or recent data is still preliminary. Its Performance report lets you filter by page, date, and search type. Keep the same filters on both sides.
A short result note might read:
/guides/internal-linking/ refresh, published August 20. In Google Web Search for the United States, clicks rose from 110 in July 23 to August 19 to 132 in August 21 to September 17. That is 22 additional clicks, or 20%. The page also received a homepage link during the after period, so the increase cannot be attributed to the refresh alone. Next action: review the main queries and keep the page under observation.This is an illustrative example with invented figures, not a customer result. Google's guidance on measuring page changes makes the same caution: other events can affect search performance during a comparison. Report what was observed, then say what you will investigate.
If nothing is ready, write "No completed comparison this week" and show the next scheduled review date. Avoid filling the gap with a fresh seven-day ranking chart and calling it the result of last week's work.
A filled weekly SEO report
This example is fictional. The dates, tasks, and search figures are invented to demonstrate the format.
- Project: Example Company website
- Week: September 18 to September 24, 2026
- Updated: September 25, 2026
- Owner: SEO lead
Shipped and verified
| URL and work | Evidence | Next action |
|---|---|---|
/services/seo/ title updated September 21 | SEO lead checked live title September 22; task T-104 | Recheck after next service-page template release |
Blocked
| URL and issue | Waiting on | Next action |
|---|---|---|
/pricing/ canonical still points to the old URL | Web lead; release slot September 29 | Deploy correction, then SEO lead checks production canonical |
Decisions needed
| Decision | Recommendation | Owner and deadline |
|---|---|---|
Approve version 2 of /integrations/crm/ product claims | Approve after product review so publication can proceed | Marketing director by September 28 |
Ready for review
| URL and change | Search evidence | Next action |
|---|---|---|
/guides/internal-linking/ refresh on August 20 | Google Web Search, US, all devices; July 23 to August 19: 110 clicks; August 21 to September 17: 132 clicks; +22 (+20%). Homepage link added during after period. | SEO lead reviews query mix and records a cautious outcome note |
The manager can answer the week’s operating questions from this page. They can follow the evidence links when a decision needs more detail. They do not need to infer delivery from a traffic line or chase the SEO for a verbal update.
Keep the report short enough to use
Three rules prevent the template from becoming another reporting project:
- Include the important work and exceptions. Keep routine task chatter in the task.
- Link each important line to its source instead of copying a full audit, crawl, or chat thread into the report.
- End each blocked item, decision, and comparison with one next owner and action.
If a manager wants to review the SEO's priorities, access, or decision rights, use the weekly report as evidence for that conversation. The guide to managing an SEO specialist covers those management choices in more detail.
SEO Logbook can keep URL-linked tasks, approvals, live checks, page changes, monitoring detections, and available Search Console comparisons in the project. Its reporting workflow draws from that saved history. Use the weekly format to select what your manager needs to act on now; keep the underlying record available for verification and later reporting.
The report has done its job when the next decision, owner, and check are obvious.