Reporting template

SEO Daily Report Template

Copy this Search Console daily report format when you need a compact operating note for wins, drops, low CTR rows, striking-distance queries, internal links, and safe next actions.

Copyable Daily Report Markdown

Paste this markdown into a site operations note, Hermes thread, GitHub issue, or daily standup document. Fill only fields supported by Search Console exports, manual SERP review, or published site changes.

# SEO Daily Report

Date:
Site:
Reporter:
Search Console range:
Comparison range:

## 1. Executive Summary
- Clicks:
- Impressions:
- Average CTR:
- Average position:
- Biggest win:
- Biggest risk:
- Priority action today:

## 2. Wins To Preserve
| Query | Page | Change | Why it matters | Preserve action |
| --- | --- | --- | --- | --- |
|  |  |  |  |  |

## 3. Drops To Review
| Query | Page | Click loss | Position change | Review note |
| --- | --- | --- | --- | --- |
|  |  |  |  |  |

## 4. Low CTR Opportunities
| Query | Page | Position | CTR | Snippet test |
| --- | --- | --- | --- | --- |
|  |  |  |  |  |

## 5. Striking Distance Queries
| Query | Page | Position | Recommended update |
| --- | --- | --- | --- |
|  |  |  |  |

## 6. Internal Link Actions
| Source page | Target page | Anchor idea | Reason |
| --- | --- | --- | --- |
|  |  |  |  |

## 7. Content Updates
- Pages that need factual refresh:
- Pages that need a clearer answer block:
- Pages that need examples, screenshots, tools, or templates:

## 8. Safe Action Log
- Actions approved for today:
- Actions blocked for policy or quality risk:
- Owner:
- Due date:

## 9. Notes For Weekly Review
- Pattern to watch:
- Question for manual SERP review:
- Candidate GitHub issues:

CSV Column Checklist

The daily report works best when the export keeps query and page together. Add comparison-period columns when you want the report to separate wins from drops instead of only listing current performance.

Query

The exact search query. Keep casing as exported.

Page

The landing page URL tied to the query row.

Clicks

Current-period clicks from Search Console.

Impressions

Current-period impressions from Search Console.

CTR

Current-period click-through rate. Percent or decimal is fine.

Position

Current-period average position.

Previous Clicks

Comparison-period clicks for wins and drops.

Previous Impressions

Comparison-period impressions for demand changes.

Previous CTR

Comparison-period CTR for snippet review.

Previous Position

Comparison-period position for ranking movement.

Country and Device

Optional segments when a change may be market or device specific.

Date Range

Optional but recommended when reports are saved outside GSC.

Review Cadence

Daily: scan for sharp drops, unusual impression changes, new low CTR rows, and issues that need evidence preserved.
Twice weekly: choose a small batch of title, meta description, content refresh, and internal link tests.
Weekly: compare completed actions with Search Console movement, SERP notes, and publication dates before deciding what worked.
Monthly: group repeated issues into templates, tooling gaps, content refresh queues, or broader site architecture work.

Safe Action Boundaries

A daily report should create review queues, not traffic shortcuts. Keep the work tied to real user value, measured changes, and manual approval before anything is published.

Allowed

Refresh stale facts, improve headings, clarify titles, add original examples, strengthen internal links, and create issues with evidence, owner, and due date.

Needs review

Major rewrites, page merges, canonical changes, template changes, monetization changes, and anything that could affect rankings or ad policy at scale.

Blocked

Fake pageviews, ad clicks, click requests, misleading snippets, copied content, blind AI publishing, and automated account actions without a human decision.

Related Tools

Generate a first draft with the Search Console Daily Report Generator, find more query candidates with the GSC Query Opportunity Finder, and test snippet ideas in the CTR Rewrite Lab.

FAQ

What should a daily SEO report include?

A useful daily SEO report should include total clicks, impressions, CTR, average position, wins, drops, low CTR opportunities, striking-distance queries, internal link actions, and a short safe action log.

Can I use this template without Search Console access?

You can use the structure for manual notes, but the query, page, click, impression, CTR, and position sections are most useful with a Google Search Console export.

How often should I change titles or content from a daily report?

Use daily reports for triage and weekly reports for decisions. Make small, evidence-backed changes, record the publish date, and wait for recrawl and enough data before judging results.

What actions are out of bounds?

Do not create fake pageviews, click ads, ask for ad clicks, publish unreviewed AI copy, use misleading titles, or make automated changes without a human review step.

Last updated: May 19, 2026.