Find pages with high impressions and low clicks, then get rewritten titles and meta descriptions ranked by opportunity size and ready to implement.
Connect Google Search Console and let Juma find the trapped value. You get back an Excel tracker ranking every page by estimated click gap, with rewritten titles and metas ready to ship and a status column for tracking what's been implemented.
_01.webp)
The team gets a ranked list of every page where clicks are being left on the table. Each page is scored by its click gap: the difference between what the position should earn and what it actually gets, multiplied by impressions. A page with 800,000 impressions at 0.05% CTR when the benchmark for its position is 2.5% represents roughly 19,000 trapped clicks per quarter. That is real traffic the site is already earning the right to have but losing at the SERP.
For the top 10-15 pages, the actual current title and meta description get scraped (no guessing from the URL pattern), the SERP gets checked for AI Overviews and People Also Ask boxes, and each rewrite comes with character counts and a one-line explanation of why the new version should perform better. The whole thing lands in an Excel file the team can sort, filter, and work through page by page.
A 2% CTR at position 3 is a problem. A 2% CTR at position 8 is normal. Without adjusting for position, a CTR audit flags pages that are performing fine and misses pages that are significantly underperforming for where they rank. The flow uses position-adjusted benchmarks (from Backlinko and FirstPageSage aggregate studies) and shows the math: "This page has 67,000 impressions at position 7.8. Benchmark CTR for that position is 3.0%. Current CTR is 0.05%. That is a gap of 1,977 clicks per quarter." The formula is shown once so every subsequent number is verifiable.
Some pages have low CTR not because of a bad title but because an AI Overview or featured snippet answers the query before anyone reaches the organic results. This prompt separates fixable CTR problems from structural ones.
For the pages where you recommended title rewrites, check which ones have AI Overviews or featured snippets on the SERP. For those, tell us whether a title rewrite will actually help or if we need a different strategy (like targeting the featured snippet or adding FAQ schema).
The team shipped the title and meta rewrites. This prompt checks GSC data 2-4 weeks later to measure the impact: did CTR improve, by how much, and which rewrites worked best.
We implemented the title and meta rewrites 3 weeks ago. Pull the latest GSC data and compare against the pre-rewrite baseline. Show us which pages improved, which didn't move, and whether the overall CTR gap closed. Recommend next steps for the pages that didn't respond.
A Juma Project is a shared space where the team stores everything Juma needs to know about a client. Create one project per client, add context as you go, and Juma will use what's relevant every time the team runs a flow. If the project already exists from other work, just add the SEO-specific items below.
Target Keywords
The keywords the client cares about most. Juma prioritizes CTR opportunities on these terms first, so the team fixes the pages that matter to the business before working through the full list.
Past CTR Baselines
Previous CTR reports or title rewrite tracking sheets. Juma compares current performance against the baseline to show progress: "CTR on this page improved from 0.14% to 1.8% since the last rewrite."
Competitor URLs
The 3-5 domains the client competes with. For each CTR opportunity, Juma checks what the competing SERP results look like so the rewritten title differentiates rather than blending in.
Add a short description in the project's info field that tells Juma what each file contains and when to use it. For example: "Target Keywords: priority terms for Q2. Past CTR Baselines: March 2026 CTR report, use as comparison baseline. Competitor URLs: top 5 organic competitors."
