Summary & Logs
KPIs, trend sparklines, biggest movers, and the run history behind every fetch.
Both sheets are generated automatically from the same date-sheet data the Dashboard uses. You never fill either one in by hand, and edits to them are overwritten the next time they're rebuilt.
The Summary sheet
Rebuilt automatically after every completed fetch, and on demand from the menu → Build Summary.
| Row | Contents |
|---|---|
| 1 | Title + last-updated timestamp |
| 2 | Tracked · Average position · In top 10 |
| 3 | Improved · Dropped · Lost · New (compared against the previous date) |
| 4 | Biggest movers: the single largest ▲ improvement and ▼ drop, with keyword, location, and size |
| 6+ (table) | One row per tracked pair: Keyword, Location, Now, Δ vs prev, Best, Worst, Avg, and a Trend sparkline |
- Improved / Dropped: the pair had a numeric rank on both the latest and previous date, and it moved.
- Lost: ranked on the previous date, but not ranked (or no data) on the latest one.
- New: ranked on the latest date, but wasn't ranked (or wasn't tracked yet) on the previous one.
- A pair whose latest fetch failed (
F) is deliberately left out of all four counts, since a failure isn't a ranking change, so it's not counted as "Lost."
All three are computed only from days within the Summary window that actually have a numeric rank. Days with no data or a failed fetch are skipped, not treated as zero.
The sparkline plots the negative of each day's rank, so an improving position (a lower rank number) always reads as an upward line, matching how the rest of the Dashboard uses green-up / red-down. The window length is Summary window (days) in Settings (30 by default).
A number if the pair is ranked, - if it was checked and genuinely not ranked, F if the latest fetch for it failed, or blank if it hasn't been checked yet today. The Δ vs prev column shows a plain — character (not a ranking change) whenever the latest result is a failure or there's nothing to compare it to.
The Summary sheet has a "warn before editing" protection, like every other generated sheet. It's a guardrail against accidental typing, not a hard lock: the script itself can always write to it, and only a human editor sees the warning.
The Logs sheet
Created automatically the first time a fetch runs, as long as Enable logging is on in Settings (it is, by default).
| Column | Contents |
|---|---|
| Run time | Timestamp the run finished (or paused/stopped) |
| Date | The date sheet the run was writing to |
| Status | Completed, Paused (time limit), Stopped (by user), or Aborted. See Fetching Rankings |
| Found | Pairs successfully ranked this run |
| Not ranked | Pairs checked but not found within your Search depth |
| Failed | Pairs that ended the run marked F |
| Details | The specific failure messages (or abort reason), truncated |
Tip
The Logs sheet is the fastest way to spot a pattern in failures. A string
of Aborted runs with the same message usually points to an expired API
key or an exhausted credit balance, both worth checking in Credits &
Pricing.
Only the most recent 500 runs are kept. Older rows are trimmed automatically so the sheet never grows unbounded. Turning Enable logging off stops new rows from being added; it doesn't delete what's already there.
Related
Last updated on
How is this guide?