Which Pages Should I Work On?

Free, no signup. Build a modeled to-do list for pages with high-impression queries just outside the top results, CTR gaps, or stable-ranking decay.

Website properties only: do not paste an Instagram, TikTok, X, or YouTube platform-property export. The prioritization model is calibrated for pages on a website, not social posts.

Optional shortcut

Load directly from Search Console

Connect for this browser session, choose a property, and load two comparable 28-day periods. You will still choose Analyze below.

Privacy, dates, and data limits

Google's read-only access token exists only in page memory. It is not stored, sent to this site, used by telemetry, or transferred to Traverse. Ending the session clears the token and loaded analyzer data without revoking your Google grant.

This shortcut supports website properties only. Search Console platform properties for Instagram, TikTok, X, and YouTube are excluded because this analyzer's URL cohorts, page priorities, and cannibalization checks are designed for pages on a website, not social posts.

Dates use Search Console's Pacific-time calendar: 28 complete days ending two days ago, compared with the immediately preceding 28 days. Search Console returns top rows rather than a guaranteed exhaustive export; this shortcut also stops at 10,000 top rows per table to match the analyzer's safety limit. Upload an export when you need different filters or a separately preserved source file.

Optional value context

Add a one-session GA4 value overlay

Connect GA4 separately to identify scored pages with supplied key-event or revenue evidence. This does not change the GSC score.

Privacy and interpretation

GA4 is a separate analytics.readonly grant and token from Search Console. The token stays only in page memory, and requests go directly from this browser to Google's Analytics APIs. No token or GA4 row is sent to this site, telemetry, or Traverse.

The overlay loads up to 10,000 top value-ordered landing-page rows for the same 28 complete days ending two days ago. If the property has more rows, this is a partial overlay ordered by key events, revenue, then sessions. Revenue is shown in the property's source currency; this tool does not infer or convert a currency. Ending GA4 removes only its token, input block, and value context—the GSC input remains.

Paste GSC Pages first, GSC page×query export second; an optional prior Pages period goes third. Separate data sets with a line containing ---. Files never leave your browser.

Optional context: add a prior-period GSC Pages table and/or a GA4 landing-page table with Landing Page, Sessions, Key Events, and Total Revenue. Either optional table can come third or fourth.

Search Console export limit: the UI can return only about 1,000 representative rows, and privacy-anonymized queries are omitted. Treat every analysis as a view of the exported sample, not the complete query set.

Local data

Saved targets, named lists, and recent check summaries remain only in this browser.

Feedback
Report a bug

Found something broken in Which Pages Should I Work On? Let us know what happened — this goes straight to a private triage queue, not a public list.

What will be sent
 No tool inputs, uploads, pasted source, complete results, query parameters, or URL fragments are attached automatically. You can edit or remove the selected passage above. Browser and anti-abuse metadata is processed for spam prevention. 

Runs entirely in your browser — nothing you paste is uploaded or stored. Anonymous run-level outcome counters may be used for aggregate research; URLs, domains, IPs, and identifiers are never included, and no statistic is released below 100 runs.

How to use it

  1. Paste the current GSCA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. Pages export.
  2. Add ---, then paste the current combined page-by-query export for the same scope.
  3. Optionally add another separator and an equal-length prior Pages export.
  4. Select Analyze. Review the highest scores, then use each row's reasons and query evidence to choose the actual work.

Example result Illustrative data

The values below are fictional and exist only to explain the output. Modeled upside is not a traffic forecast.

Pagehttps://example.com/technical-seo-audit/

Opportunity score48.6Modeled upside clicks36.6
  • “technical seo checklist” is in striking distance at position 7.4.
  • “website audit template” has a CTR gap against the modeled curve.
  • Clicks declined 18% while position held.

What the results mean

Score sorts the list; it is a blend of signals and has no universal good/bad threshold. Upside clicks estimates the difference between actual clicks and a modeled CTR after moving three positions. Reasons identify striking distance, a CTR gap, or stable-ranking decline. Queries contains all supplied query rows joined to that normalized page, not only the trigger queries.

How it works

The engine joins page-by-query rows to page totals using normalized URLs. For positions 4–20, it estimates CTR at a position three places better and counts only positive click difference. It flags CTR gaps when a query has at least 50 impressions and less than 70% of modeled CTR. With a prior period, it adds a decay reason when clicks fell and average position moved by less than one position.

Features

  • Sorted page backlog with query-level evidence.
  • Optional period-over-period decay signal.
  • Transparent reasons and modeled upside kept separate.
  • CSV/manual input by default, with optional separate GSC and GA4 browser-session connections when Google OAuth is configured.

Limitations

  • The model does not know business priority, page quality, SERP features, or implementation effort. An optional GA4 overlay can add observed value context, but it does not predict future value.
  • Average position and a generic CTR estimate can hide device, country, and query-mix differences.
  • Moving three positions is a scenario, not a prediction.
  • Exports must share filters and the comparison periods should be equivalent.

Frequently asked questions

Which GSC exports do I need to prioritize pages?

Paste a current Pages export first and a combined page-by-query export second. You can optionally add a prior-period Pages export third to detect click decline while average position stayed stable.

What is a striking-distance query?

In this model it is a supplied query with average position from 4 through 20. The tool estimates click upside for moving it three positions, using a modeled CTR curve.

How is a CTR gap detected?

A query with at least 50 impressions is flagged when its observed CTR is below 70 percent of the model estimate for its average position.

What does the opportunity score represent?

It combines modeled upside clicks, a page-level bonus for CTR-gap evidence, and current clicks when stable-ranking decline is present. It is a prioritization heuristic, not predicted traffic.

Can I compare two periods with different lengths?

You can, but the decline reason would be misleading. Use equal-length periods with comparable filters, seasonality, and reporting completeness.

Next stepGSC Regex Builder & Tester — generate the corrected version.

Feature requests for Which Pages Should I Work On

Upvote what you want most. New ideas can be submitted from the floating Feedback menu; requests appear here once approved, and the most-wanted rise to the top.

Loading…

➕ Request a feature

New requests are reviewed before they appear here.

حول الأداة

ترتيب GSC صفحات بواسطة ضمن مسافة الوصول, CTR-gap, و تراجع الترتيب المستقر فرص.

مجاني, من دون تسجيل. بناء واحد مُمثَّل to-do قائمة من أجل صفحات مع high-impression استعلامات فقط خارج ال الأعلى نتائج, CTR فجوات, أو تراجع الترتيب المستقر.

الميزات

  • مفرز صفحة backlog مع query-level دليل.
  • اختياري period-over-period اضمحلال إشارة.
  • شفاف أسباب و الزيادة المقدّرة محتفَظ به منفصل.
  • CSV/manual إدخال بواسطة افتراضي, مع اختياري منفصل GSC و GA4 browser-session اتصالات عندما محرك Google OAuth هو مهيّأ.

كيفية العمل

ال محرك يدمج page-by-query صفوف إلى صفحة إجماليات استخدام normalized عناوين عنوان URL. من أجل مواضع 4–20, إنه تقديرات CTR في واحد موضع three places أفضل و أعداد فقط إيجابي نقرة فرق. إنه علامات CTR فجوات عندما واحد استعلام يحتوي في الأقل 50 مرات الظهور و أقل من 70% من مُمثَّل CTR. مع واحد سابق فترة, إنه يضيف واحد اضمحلال سبب عندما نقرات fell و متوسط موضع منقول بواسطة أقل من واحد موضع. ال درجة الفرصة combines الزيادة المقدّرة نقرات, واحد على مستوى الصفحة CTR-gap bonus, و حالي نقرات عندما stable-ranking انخفاض هو موجود; إنه هو واحد تحديد الأولويات استدلالي, ليس متوقَّع زيارات.

القيود

  • ال نموذج يفعل ليس يعرف نشاط تجاري أولوية, صفحة جودة, SERP ميزات, أو تنفيذ effort. واحد اختياري GA4 overlay يمكن أضف مرصود قيمة سياق, لكن إنه يفعل ليس يتنبأ مستقبل قيمة. متوسط موضع و واحد عام CTR تقدير يمكن إخفاء جهاز, country, و query-mix فروق. Moving three مواضع هو واحد سيناريو, ليس واحد تنبؤ. صادرات يجب حصة مرشحات و ال مقارنة فترات ينبغي يكون مكافئ.

الأسئلة الشائعة

ما هو واحد ضمن مسافة الوصول استعلام?

في هذا نموذج إنه هو واحد مقدّم استعلام مع متوسط موضع من 4 من خلال 20. ال الأداة تقديرات نقرة upside من أجل moving إنه three مواضع, استخدام واحد مُمثَّل CTR منحنى.

كيف هو واحد فجوة نسبة النقر مكتشف?

واحد استعلام مع في الأقل 50 مرات الظهور هو موسوم عندما الخاص به مرصود CTR هو أدناه 70 نسبة مئوية من ال نموذج تقدير من أجل الخاص به متوسط موضع.

ما يفعل ال درجة الفرصة يمثل?

إنه combines الزيادة المقدّرة نقرات, واحد على مستوى الصفحة bonus من أجل CTR-gap دليل, و حالي نقرات عندما stable-ranking انخفاض هو موجود. إنه هو واحد تحديد الأولويات استدلالي, ليس متوقَّع زيارات.

يمكن I قارن اثنان فترات مع مختلف lengths?

أنت يمكن, لكن ال انخفاض سبب سيكون يكون misleading. استخدم equal-length فترات مع comparable مرشحات, موسمية, و reporting اكتمال.