Overview
Search Console Review is the skill of turning impressions, clicks, CTR, and query patterns into page decisions. For a one-person company, Search Console is one of the fastest ways to stop guessing. It tells you where demand already exists, where pages are underperforming, and where refresh work will likely pay off.
When to Use This Skill
Use this weekly when traffic matters, after publishing a new cluster, when rankings drift, or when you need to decide whether to refresh, rewrite, merge, or leave a page alone.
What This Skill Does
This skill helps you find query-page mismatches, low-CTR opportunities, near-page-two wins, cannibalization risks, and dead pages that no longer deserve attention.
How to Use
Step 1: Pull the last 28 and 90 days side by side. Weekly snapshots matter, but direction matters more.
Step 2: Sort pages into four buckets: high impressions low CTR, strong CTR low impressions, declining clicks, and rising impressions.
Step 3: Look at the actual queries for each page. Ask whether the current headline, description, opening paragraph, and CTA fit the query set.
Step 4: Prioritize pages that are close to breaking out. A page sitting in positions 5 to 15 with the right intent often beats creating a new page from scratch.
Step 5: Flag cannibalization. If two pages both attract the same query family and neither wins cleanly, choose one primary page and reposition the other.
Step 6: Turn findings into explicit actions. Every review should end with refresh, title/meta update, internal linking, merge, or no-change.
Copy-Paste Weekly Search Console Review Prompt
Use this prompt to convert raw Search Console data into a prioritized weekly action list:
Act as my SEO operator.
Input: top pages from Search Console with impressions, clicks, CTR, avg position (last 28 days vs previous 28 days), plus top queries per page.
Task:
1) Rank pages by click upside and intent mismatch.
2) For each top page, decide one action: title/meta rewrite, intro refresh, internal link pass, merge, or no-change.
3) Return a weekly queue with owner and ship date.
Constraints:
- Prioritize only 3-5 pages this week.
- Prefer updates likely to increase CTR within 14 days.
- Flag cannibalization where two URLs compete for the same query family.Output
The output should include:
- Top high-impression low-CTR pages
- Pages with rising demand
- Pages losing clicks or position
- The action for each page
Evidence and Sources According to Google documentation, the Performance report is the primary source for query-page diagnostics, and it should be reviewed with both clicks and impressions over multiple date ranges.
- Source: Google Search Console - Performance report
- Source: Google Search Central - Analyze search performance with Search Console
- Source: Google Search Central - URL Inspection tool overview
Internal implementation links for this workflow:
FAQ
What should you check first in a weekly Search Console review?
Start with pages that have high impressions and low CTR in the last 28 days, then compare against the prior 28 days before you edit title and meta copy.
How many pages should a solopreneur prioritize each week?
Prioritize the top 3 to 5 pages with the largest click upside and clear intent mismatch so updates can ship in one focused session.
When should you refresh content instead of only updating snippet copy?
Refresh on-page sections when query intent has shifted or when CTR and average position both decline, because snippet copy alone will not fix weak relevance.
How do you handle query cannibalization in Search Console review?
Pick one primary URL per query family, tighten internal links toward that URL, and reposition overlapping pages to distinct secondary intents.
What output should every Search Console review produce?
A prioritized action list with page URL, target query family, action type, owner, and ship date for title/meta updates, content refreshes, and link fixes.
Common Mistakes
Do not obsess over average position without looking at query mix. Do not refresh pages with no business value just because they moved a little. Do not create new pages before checking whether an existing page already has traction. Do not end the review without a concrete next move.
SKILL.md file
Preview raw SKILL.md. Open the full source below. Scroll, inspect, then download the exact SKILL.md file if you want the original.
# search-console-review
Search Console Review
Overview
Search Console Review is the skill of turning impressions, clicks, CTR, and query patterns into page decisions. For a one-person company, Search Console is one of the fastest ways to stop guessing. It tells you where demand already exists, where pages are underperforming, and where refresh work will likely pay off.
When to Use This Skill
Use this weekly when traffic matters, after publishing a new cluster, when rankings drift, or when you need to decide whether to refresh, rewrite, merge, or leave a page alone.
What This Skill Does
This skill helps you find query-page mismatches, low-CTR opportunities, near-page-two wins, cannibalization risks, and dead pages that no longer deserve attention.
How to Use
Step 1: Pull the last 28 and 90 days side by side. Weekly snapshots matter, but direction matters more.
Step 2: Sort pages into four buckets: high impressions low CTR, strong CTR low impressions, declining clicks, and rising impressions.
Step 3: Look at the actual queries for each page. Ask whether the current headline, description, opening paragraph, and CTA fit the query set.
Step 4: Prioritize pages that are close to breaking out. A page sitting in positions 5 to 15 with the right intent often beats creating a new page from scratch.
Step 5: Flag cannibalization. If two pages both attract the same query family and neither wins cleanly, choose one primary page and reposition the other.
Step 6: Turn findings into explicit actions. Every review should end with refresh, title/meta update, internal linking, merge, or no-change.
Output
The output should include:
Top high-impression low-CTR pages
Pages with rising demand
Pages losing clicks or position
The action for each page
Evidence and Sources
According to Google documentation, the Performance report is the primary source for query-page diagnostics, and it should be reviewed with both clicks and impressions over multiple date ranges.
- Source: [Google Search Console - Performance report](https://support.google.com/webmasters/answer/7576553)
- Source: [Google Search Central - Analyze search performance with Search Console](https://developers.google.com/search/docs/monitor-debug/search-console-performance-report)
- Source: [Google Search Central - URL Inspection tool overview](https://support.google.com/webmasters/answer/9012289)
Common Mistakes
Do not obsess over average position without looking at query mix.
Do not refresh pages with no business value just because they moved a little.
Do not create new pages before checking whether an existing page already has traction.
Do not end the review without a concrete next move.
Preview raw SKILL.md. Open the full source below. Scroll, inspect, then download the exact SKILL.md file if you want the original.
# search-console-review
Search Console Review
Overview
Search Console Review is the skill of turning impressions, clicks, CTR, and query patterns into page decisions. For a one-person company, Search Console is one of the fastest ways to stop guessing. It tells you where demand already exists, where pages are underperforming, and where refresh work will likely pay off.
When to Use This Skill
Use this weekly when traffic matters, after publishing a new cluster, when rankings drift, or when you need to decide whether to refresh, rewrite, merge, or leave a page alone.
What This Skill Does
This skill helps you find query-page mismatches, low-CTR opportunities, near-page-two wins, cannibalization risks, and dead pages that no longer deserve attention.
How to Use
Step 1: Pull the last 28 and 90 days side by side. Weekly snapshots matter, but direction matters more.
Step 2: Sort pages into four buckets: high impressions low CTR, strong CTR low impressions, declining clicks, and rising impressions.
Step 3: Look at the actual queries for each page. Ask whether the current headline, description, opening paragraph, and CTA fit the query set.
Step 4: Prioritize pages that are close to breaking out. A page sitting in positions 5 to 15 with the right intent often beats creating a new page from scratch.
Step 5: Flag cannibalization. If two pages both attract the same query family and neither wins cleanly, choose one primary page and reposition the other.
Step 6: Turn findings into explicit actions. Every review should end with refresh, title/meta update, internal linking, merge, or no-change.
Output
The output should include:
Top high-impression low-CTR pages
Pages with rising demand
Pages losing clicks or position
The action for each page
Evidence and Sources
According to Google documentation, the Performance report is the primary source for query-page diagnostics, and it should be reviewed with both clicks and impressions over multiple date ranges.
- Source: [Google Search Console - Performance report](https://support.google.com/webmasters/answer/7576553)
- Source: [Google Search Central - Analyze search performance with Search Console](https://developers.google.com/search/docs/monitor-debug/search-console-performance-report)
- Source: [Google Search Central - URL Inspection tool overview](https://support.google.com/webmasters/answer/9012289)
Common Mistakes
Do not obsess over average position without looking at query mix.
Do not refresh pages with no business value just because they moved a little.
Do not create new pages before checking whether an existing page already has traction.
Do not end the review without a concrete next move.
Comments & Discussion
Add a comment