OrganiqSEO quick wins from your own Search Console data
· Organiq · third-party facts carry source and date in the text
SEO quick wins are queries where your site already appears and a small change (title, meta description, first paragraph, internal links) tends to bring clicks within weeks. Both signals come from Search Console: CTR below the expected for the position (CTR gap) and queries in striking distance (positions 4 to 20). Default period: 28 days.
How do I calculate the CTR gap?
For every query with at least 20 impressions, compare the observed CTR with the expected CTR at the same position. The expected value comes from the property's own CTR curve (when there are enough impressions per band) or from a generic benchmark. lostClicks = impressions × (expected CTR − observed CTR). Sort by lost clicks: in Organiq that is score_opportunities with minImpressions: 20, and the answer says whether the expected value came from the own curve or the benchmark (ctrSource).
What is striking distance?
Queries where the page sits between positions 4 and 20, where a jump to position 3 changes CTR visibly. The estimated gain is impressions × (CTR at target position − current CTR). In Organiq: find_page_poaching_opportunities with minPosition: 4, maxPosition: 20, targetPosition: 3, sorted by gain.
How do I separate brand from non-brand?
Brand queries have a high CTR and distort the curve. Set the brand terms on the property and read get_breakdown: brand share and how much traffic sits in the 4–10 and 11–20 bands. A site with 70% brand clicks needs its quick wins on the non-brand side.
What do I do with the list?
| Signal | Action | Typical horizon |
|---|---|---|
| CTR gap at positions 1–3 | Rewrite title and meta description with the short answer | 2–4 weeks |
| Striking distance 4–10 | Strengthen the first paragraph and internal links to the page | 4–8 weeks |
| Striking distance 11–20 | Expand the content and consolidate competing pages | 8–12 weeks |
Horizons are orders of magnitude observed on small and medium sites; measure with get_site_summary and query_top_queries (comparison with the previous period) before concluding.
How do I run this in a conversation?
With the connector in Claude or ChatGPT: "What are my site's quick wins: queries with CTR below the expected for their position?" The quick-wins skill chains the tools and returns a table with query, page, position, impressions, CTR, expected CTR, estimated gain and suggested action. Small sites: lower minImpressions to 5–10 and widen to 90 days.
Frequently asked questions
How many impressions does a query need?
At least 20 in 28 days for the CTR to be read with some confidence; on small sites use 5–10 impressions and 90 days, and treat the result as a list of hypotheses.
Does the CTR benchmark fit my niche?
As a starting point. When the property has enough impressions per position band, its own curve replaces the benchmark; the answer states which one was used.
Why did CTR drop without the position changing?
The SERP changed: AI Overviews, more ads or new features. Check get_annotations for a Google update on that date and compare the own CTR curve by band.
Is position 1 with a low CTR a quick win?
Usually yes, if the query is not brand and the SERP has no direct answer; rewriting the title to deliver the answer tends to recover clicks within a few weeks.