SEARCHTRIAGE / PAGE-CLICK REVIEW
Spot the change.
Choose what to review.
Two exports. A clear, honest review list. No account needed.
01 / ALIGN YOUR INPUTS
Same view. Two windows.
Export the Pages table from your own Search Console property for each period. CSV columns: URL, Page or Top pages, plus Clicks.
Technical limits: 10,000 rows · 5 MiB per file · 20 columns. UTF-8, comma-separated CSV. Exact URLs are matched; no URL normalization.
Equal-length, non-overlapping windows are required. Matching duration alone does not make periods equivalent; consider weekdays, seasonality, and export limits.
02 / A STARTING POINT, NOT A DIAGNOSIS
Your review list
| Page URL / status | Previous clicks | Current clicks | Click change | Change % |
|---|
No rows match this view. Change your filters to explore the comparison.
Click declines do not prove indexing loss, a technical fault, or any other cause. New / missing means absent from an export—not a newly created or deleted page. Search Console data and export limits may omit rows. Review the original data before acting.
Start with two snapshots.
We’ll keep the arithmetic simple, and the unknowns visible.
Your manual review stays yours.
How matching, privacy and exports work
Identity: exact URL strings only. Protocol, casing, trailing slashes, query strings and fragments are preserved. Duplicates block the entire import; no silent merging. URLs are plain text, never links or fetch targets. Only absolute HTTP(S) URLs without credentials or whitespace are accepted.
Arithmetic: current minus previous clicks for pages present in both exports. Percentage change is (current − previous) ÷ previous × 100. Zero baselines have no comparable percentage, even for 0 → 0. A page absent from either export has no change or percentage.
Ordering: within matched declines, the largest absolute drop comes first. All-rows view groups declines, missing, new, unchanged, then increases; ties use exact URL text. The minimum-volume filter tests the higher of the two known click counts. Export includes every filtered row, not only the displayed page.
Privacy: no OAuth, API connection, crawler, data-processing backend, app telemetry, persistent browser storage or cloud sync. Closing or reloading discards work. Downloaded reports are unencrypted and may contain sensitive URLs. CSV text cells are formula-escaped; validated numeric changes remain numbers. Keep the downloaded report private.
Limits: each file supports 10,000 data rows, 5 MiB UTF-8 text, 20 columns, URLs up to 2,048 characters, and 0–1,000,000,000 clicks per row. Only the required URL and clicks columns are used; other columns are ignored after structural validation. No daily normalization, seasonal adjustment, SEO score, indexing check or diagnosis.
Free beta: scope, privacy and limits
No account. No charge. Manual comparison of two owner-exported page/click CSVs. No Search Console connection, crawling, SEO diagnosis or traffic promise. Exact URL matching and equal-length, non-overlapping date windows are required.
Technical limits: 10,000 data rows, 5 MiB and 20 columns per CSV; up to 20,000 joined URLs; 50 displayed rows per page. Export includes all filtered rows, not just the displayed page. These are local reliability bounds, not paid quotas.
Local processing: your CSV contents stay in this tab’s memory and are not uploaded by this app. Closing or reloading loses work. No app analytics or persistent browser storage. When hosted, the hosting provider receives normal access logs for page and asset requests.
Keep exports private: CSV reports, including potentially sensitive URLs are unencrypted copies. Clearing the app does not delete downloaded files. Check that downloads saved before closing. Native browser downloads, keyboard behavior and mobile layouts still need release QA.