Find SEO quick wins worth your next hour
Start with an existing page that matters to your business, has enough search data to investigate, and has a specific improvement you can verify. Search Console helps you find candidates; a low CTR or average position near page one does not by itself establish an easy win.
On this page
An hour spent improving the wrong page is still an hour lost. Before opening a list of SEO tactics, choose the page whose improvement would matter: a service page, a product explanation, or a guide that helps a potential customer take the next step.
This is the workflow we recommend for choosing that work. You can do it manually in Google Search Console or use the prepared research prompt below with Percy.
1. Build a shortlist from your own data
Open Performance → Search results, select Web search, and compare two equal, complete periods. Twenty-eight days against the preceding twenty-eight is a useful starting point when you have sufficient traffic; a seasonal business also needs a relevant seasonal comparison. Keep country and device filters consistent.
Start in Pages. Investigate pages that lost meaningful clicks, already receive relevant impressions, or support an important customer decision. Select a candidate page and inspect its Queries. You are looking for a connection between the searches, what the page promises, and what you sell. Google's Performance report documentation explains its reporting controls and metrics.
Use this shortlist before deciding on a tactic:
| Candidate | Evidence to collect | Reason to pause |
|---|---|---|
| An important page losing clicks | Losing queries and an equal-period comparison | The decline is tiny or seasonal |
| A page with relevant impressions but few clicks | Query, device, country, current results | The impressions are for the wrong audience |
| A page near the visible results | Intent match and the competing pages | Ranking would require a different kind of page |
| A useful page with weak discovery | Existing related pages that could link to it | There is no helpful editorial connection |
Do not multiply all impressions by a generic CTR benchmark and label the difference “available traffic.” That assumes away the query mix and the actual results page.
2. Decide whether the opportunity matters commercially
Imagine two candidates. A developer utility gets many impressions from people who need a one-off answer. A smaller guide attracts founders looking for the exact service you provide. The second can be more valuable even when its traffic ceiling is lower.
For each page, write down the visitor's likely task and the next step your product can actually help with. Then score the candidate in plain language:
- Business relevance: would a satisfied visitor plausibly become a customer?
- Evidence: can you point to a specific problem in the data and the page?
- Effort: can you complete and review the edit with the time available?
- Risk: could the change remove useful content or disturb existing intent?
A candidate with a clear missing explanation and a natural product connection usually deserves attention before an unrelated page with a superficially attractive impression count. This is a prioritization judgment, not a revenue forecast.
3. Choose one small, defensible change
Correct a misleading or incomplete title
Compare the title with the page's actual purpose. A page titled “Pricing” may need the product name and context; a guide about installation costs should not imply it contains a quote calculator if it does not.
Draft a title that accurately describes the page and remains useful if Google chooses different wording. Google generates title links using several sources, so changing the HTML title does not guarantee the displayed title or a CTR increase. See Google's title-link guidance.
Add a genuinely useful internal link
Find an existing page where readers would benefit from the candidate page. Add the link in the relevant explanation with descriptive anchor text. Review the destination and make sure the link is a normal crawlable link. Google's link guidance covers these basics.
For example, our traffic-drop investigation links to specific indexing explanations at the point where the reader needs to inspect an affected URL. The relationship is useful to a reader, not just a keyword connection.
Fill one missing answer on the page
Use the relevant queries and the live page to identify a question a reader would reasonably expect answered. Add a concise explanation based on your actual product, service, or expertise. Do not insert FAQs simply to repeat keyword variants.
An illustrative example: a service page mentions “maintenance included” but never explains the scope. A short, accurate scope section could help both visitors and the sales team. Whether it changes search traffic remains something to measure.
Fix an accidental technical block
If a valuable page has an unintended indexing problem, resolve the cause before rewriting the copy. Use the appropriate guide for noindex exclusions, robots.txt blocks, or canonical selection.
A status is not automatically an error: some pages are deliberately excluded or consolidated. Confirm the intended behavior first.
4. Keep a record you can evaluate later
Before publishing, save the URL, your observation, the exact edit, the date, and the metric you expect to change. Check the rendered page immediately after release.
For a title edit, compare the same page and relevant queries over comparable windows. For a product explanation, examine downstream engagement and conversions as well as search clicks. For a technical fix, confirm the live response and then check Google's later inspection state.
If several things changed at once, report the outcome as an observation. You cannot isolate the effect of one edit from an uncontrolled before-and-after comparison.
Run this investigation with Percy
Connect your Search Console site, then use this prompt. Percy can research the candidates and help draft a change; you review and publish it. A useful answer should also say when there is not enough evidence for a quick win.
Find up to three SEO quick wins on this site. Compare the last 28 complete days with the previous 28, then inspect the relevant queries and pages. Prioritize business relevance and implementation effort, not average position alone. Give me the evidence, one next action per page, and any important uncertainty. If the data is too sparse, say so rather than inventing click forecasts.
If the investigation finds several URLs sharing a query, continue with the Search Console cannibalization check before consolidating anything. If most of the site is declining, start with traffic-drop diagnosis instead of a list of isolated edits.