Search and Organic Discovery

SERP Observation Log

Record result types, recurring questions, source patterns, freshness, localization, volatility, and unmet reader needs without copying competitors.

Free editable Markdown · SEO researchers, content strategists, and editors · Updated July 30, 2026

Download Markdown

Accessible HTML preview

Blank template

The downloaded file contains the same fields in editable Markdown.

Observation context

Query: [Exact wording]
Date and local time: [YYYY-MM-DD; time]
Country or region: [Observation scope]
Language: [Interface and query language]
Device or viewport: [Mobile, desktop, other]
Session context: [Signed out/in; relevant limitations]
Search surface: [General, images, news, video, other]
Collection method: [Manual notes, approved tool, or other]

Result patterns

Dominant page types: [Tool, guide, product, forum, video, research]
Special features: [Answer, local pack, images, discussions, other]
Source categories: [Official, publisher, marketplace, community]
Freshness pattern: [Dates and apparent sensitivity]
Recurring questions: [Natural-language themes]
Refinement suggestions: [Themes, not copied lists]
Localization signals: [Region, currency, language, local sources]
Volatility: [Stable, mixed, or changing with evidence]

Interpretation checks

Observation conditions are complete enough to reproduce approximately.
Position is not treated as permanent or universally identical.
Observations and interpretations are labeled separately.
Ranking is not presented as proof of accuracy.
Competitor wording, examples, and structures are not copied.
Proposed value is based on expertise or original evidence.
Related queries or dates were compared when needed.
Findings link to a documented content decision.

How to use this template

Define a small query set and record market, language, device, date, session, and collection method.
Note result formats, source types, dates, recurring questions, refinements, and visible special features.
Separate direct observation from hypotheses about reader intent or quality.
Identify unmet needs only where the team has expertise and original value to contribute.
Compare across queries or dates, then link decisions to the intent map and content brief.

Preserve observation conditions

Record the query exactly, date and local time, language, country or region, device, search surface, and whether the session was signed in or personalized. Note that private browsing does not eliminate all localization. Capture broad patterns rather than obsessing over one position: result types, dominant page formats, dates, source categories, special features, and recurring refinements. A screenshot may aid internal review when permitted, but structured notes are easier to compare over time and safer than storing unnecessary account context.

Interpret patterns as hypotheses

Result composition can suggest likely reader needs: tools for immediate action, guides for learning, product pages for evaluation, local results for place-based tasks, or recent reporting for changing subjects. It does not prove what every searcher wants. Separate observations from interpretations and confidence. Check whether top pages satisfy the query directly, rely on authority, offer evidence, or leave common questions unresolved. Do not equate ranking with factual quality or permission to reproduce a structure, example, or claim.

Look for useful differentiation

Identify gaps your team can responsibly address: a clearer workflow, current primary evidence, accessible format, honest limitation, localized explanation, original dataset, or tool. A missing subheading is not automatically a content opportunity. Compare observations across related queries and dates before deciding whether a pattern is stable. Link the log to the intent map and content brief, record decisions, and schedule a fresh observation when volatility or major changes make the evidence stale.

See the fields in context

Fictional example: indoor herb light guide

The query set and result observations are invented to demonstrate logging.

Context: English desktop observation for a fictional UK market on 2026-07-30.
Pattern: Invented results mix buying guides and plant-care explainers, suggesting both product and learning jobs.
Recurring need: Several fictional refinements concern measuring distance, but snippets offer inconsistent unlabeled units.
Opportunity: Publish an original, tested measurement walkthrough with units and safety boundaries, not a rewritten shopping list.
Decision: Create separate intent records for equipment comparison and care procedure before assigning any URL.

Frequently asked questions

Should exact rankings be recorded?

They can be included as a dated observation, but patterns and intent signals are often more useful. Do not treat one session as a universal ranking.

Can snippets be used as factual sources?

No. Verify a claim in the underlying primary or otherwise appropriate source; snippets can be incomplete, stale, or removed from context.

How often should observations be repeated?

Use a cadence appropriate to volatility and decision importance. Repeat after meaningful performance changes, result-format shifts, or before a major brief is approved.

Is an empty result feature a content gap?

Not by itself. A worthwhile gap combines reader need, lack of adequate coverage, and your ability to create distinctive, reliable value.