04 / Observe demand
A trend is a question.
Keep the context.
A manual research notebook for the observations that might change what you make next.
No live feed, crawler, connector or volume estimate. Record what you actually saw, where you saw it and what you compared. Bring that bounded hypothesis into the same Lab draft.
Before you read the spike
Relative interest is not search volume.
Google Trends uses sampled data normalized to a 0–100 scale within the selected request. 100 is a relative peak, not a count of searches or a percentage of everyone. A zero may reflect insufficient data; it does not prove no interest.
Do not calculate lift across incompatible exports. Region, time window, category, term versus topic, search type and comparison set matter. A spike does not identify its cause or predict a commercial outcome.
Open the explorer only when you choose. It is an external service with its own privacy policy. This app does not fetch results or send your note or brief to Google.
Open Google Trends explorer (external, new tab)Read the source & access limitsOne active draft. Yours to keep.
Across Lab and Trends, edits stay in this tab's memory. Reload clears them. No content fetch, analytics or server submission. Save explicitly to replace the single local device copy; Load is never automatic.
JSON preserves input, edited Markdown, metric definitions, counts and notes. Imports are validated before replacement. Device storage is browser-local, not encrypted; do not include secrets or private customer records.
01 / Working notes
Write a reproducible observation.
02 / Working notes