Search problem
High impressions, low CTR
Search Console shows people are seeing your page in results — but not clicking. That is usually a title, snippet, or first-viewport mismatch, not a cue to publish ten more articles.
What the problem looks like
- Impressions exist — Google is showing the URL for a query.
- Clicks lag — CTR is weak relative to position and intent.
- The SERP is the work surface — title and description compete in a list of alternatives.
This page does not invent keyword volumes. Use your own Search Console numbers as the source of truth.
What to do first
- Open the query and page in Search Console.
- Search the query and compare your title and snippet to competitors.
- Make one bounded change: title, meta description, first viewport, or an internal link that supports the intent.
- Measure impressions, clicks, CTR, and position again at 14 and 28 days.
How Search Repair Radar helps
Search Repair Radar connects to Search Console and returns one evidence-backed repair packet — not a dashboard of unresolved metrics, and not a content mill.
Search Console is required before any repair
Search Console is required before any repair. Search Repair Radar reads a connected Search Console property and looks for one non-brand query and page that already earns impressions with a weak click-through rate. Without that connection there is no owned row to repair, and the product does not invent a weaker insight, a keyword volume, or a title aimed at a query you have not been shown for.
The example card on the product page is not that connection. It is a fixture. Its claim ceiling says: EXAMPLE RESULT ONLY. Numbers are synthetic for illustration. They are not from your Search Console property and are not a customer outcome claim. It also records what the example did not do: no real site was changed, no real Search Console property was read, and the example is not a ranking or revenue guarantee. Treat every number on that card as part of the fixture. They are not your impressions, not a search volume, and not a customer outcome.
After you connect, a real run still may return no repair. Rows that miss the impression bar, that are brand queries, or that sit on a property whose non-brand demand is too thin do not get a title rewrite. Thin demand comes back as a table and a reason, not as a stuffed title. The next action in that case is to build the thing people would search for, then run again. That is a different task from repairing a page people already see and do not click.
One example of the recommended change
The fixture query is “project status update template” on https://example-site.test/templates/status-update. The opportunity class is high impressions, low CTR. Why the fixture says it matters: This example query shows high impressions with a weak click-through rate. A tighter title and meta description that match the query intent is a bounded first repair — before writing more pages.
The one recommended change is a title edit, not a new article. Current example title: Templates | Example Site. Proposed title: Project Status Update Template (Free) | Example Site. Rationale on the fixture: Put the query phrase early, state the asset type, and keep the brand last so the SERP snippet matches intent. The repair kind stays inside title, meta description, first viewport, or an internal link. Measurement on the fixture is a reread at 14 days and 28 days. Those checkpoints compare impressions, clicks, click-through rate, and position on the same query and page. They are not a promise that the numbers will move.
You apply the title or snippet in your own site. Search Repair Radar does not publish the page and does not edit Search Console for you. Connecting the property is what makes a later packet about your URLs. Until then, the only honest artifact is the labeled example.
The receipt the harness keeps
A repair is one change plus a receipt. The public sample at /receipt/sample shows the shape. Nothing runs from that page. The sample verdict is “This homepage title is leaking first-visit clicks.” The honest scope limit on the sample is “Sample shape. Not live proof. No traffic or rank guarantee.” Before: “Unclear title. Primary action buried.” After: “One title. One action. Sample shape only.” The next line is “You approve, skip, or revise.” The window says a 14-day window starts when you stamp, and that the sample itself has no traffic or rank numbers.
The boundary on the sample is no publish, no deploy, no outbound send, and approval required. Live screenshots and sign-off are unchecked. That sample is about a homepage title, not about the fixture query above. It is here so you can see a honest scope limit, one change, and a receipt in one place. Your Search Console packet, once a property is connected, is a separate object. If there is no qualifying row, you get the no-repair reason instead of a receipt that pretends a title was chosen.
How to read a real packet
Open the query and the page in Search Console first. Then search the query yourself and look at your title and snippet next to the other results. The mismatch is usually one of four things: the title does not contain the words the query used, the description promises something the page does not open with, the first viewport answers a different job than the result line, or an internal link is sending the wrong URL into the conversation. Pick one. Do not ship ten articles because one URL is seen and not clicked.
Brand queries are set aside. A row that is only your company name is not the leak this tool is built to repair. Position, when Search Console provides it, is part of the evidence, not a rank you can quote on a sales page. If position is missing, the packet does not fill one in. If impressions are real but too small to clear the bar, you see the owned rows and you do not get a rewrite.
After you change the title, snippet, first viewport, or link, wait for the 14-day and 28-day reread. Compare the same query and the same URL. A movement is a measurement, not a certificate. No movement is also a measurement. Neither one is a reason to invent a second repair on the same day from a hunch.
Where this sits in the harness
Launchfiles is the launch operator for AI-built products: it takes a product to its first paying customers and keeps them, through agents acting inside a policy you approve, with a receipt for every public act. This page is the check for a URL that is seen and not clicked. The check does not start until Search Console is connected. The harness will not publish, deploy, or spend without approval, and this repair follows that rule.
If the first screen is the problem rather than the result line, use Design UX Radar. If you need a draft that stays inside facts you already wrote down, use Page Draft. Neither of those replaces a Search Console row. Search Console is required before any repair from this product.