A “Potential quick win” label can help you decide which search observation to inspect next. Before it becomes a content assignment, you need to know what triggered it. In Shane’s Gap Analyzer, the label comes from a small rule applied to the records you enter. It is not a forecast of rankings, traffic or revenue.
This guide explains the current rule, shows where incomplete inputs can mislead you, and gives you a short review process for turning a flagged record into a useful decision. For the broader research-to-brief workflow, start with the Gap Analyzer content planning guide.
1. Understand the three conditions behind the label
In the SERP opportunities tab, a record receives the “Potential quick win” label when all three conditions are met:
- The saved Your position text contains the letters “not,” ignoring capitalization.
- Your authority score and the competitor’s authority value are both greater than zero.
- The competitor’s authority value is lower than your authority score.
There is no minimum difference between the two authority values. Your score of 41 and a competitor value of 40 satisfy the comparison just as 60 and 20 do. The tool does not calculate a confidence level or a numeric opportunity score.
For example, suppose your authority score is 40. A saved query with Your position set to “Not ranking” and competitor authority of 25 is flagged. Change the competitor value to 40 or 55, and the same record becomes “Review opportunity.” Give the record a numeric position such as 18, and it is not flagged even if the competitor value is 25.
These labels describe whether the record matches the rule. A query already ranking at position 18 might still deserve attention. A flagged query might be irrelevant to your customers. Use both groups in your review.
2. Keep an unknown position separate from a checked absence
The position field is free text. When you save a manual search opportunity with that field blank, the current tool stores “Not ranking.” The CSV import uses the same default for an empty position. That can make an unchecked query look like a checked absence if the authority conditions also match.
Use a deliberate recording convention:
- Observed numeric position: enter the position you actually recorded, then add the source and check context in the notes.
- Checked but not found: use “Not ranking” only when you completed a defined check. Record the depth of the results reviewed, date and market so the phrase has a clear meaning.
- Unknown or unchecked: enter “Unverified” rather than leaving the field empty.
Avoid “Not checked” for an unknown position. It contains “not,” so the current text-matching rule can flag it. The tool cannot distinguish the meaning of those phrases. Before importing a file, scan for blank positions and replace them with an accurate label.
Likewise, a zero or blank authority value does not satisfy the rule. Do not invent a positive value to make the label appear. Leave the observation available for a manual review until you have comparable information.
3. Make the authority comparison meaningful
Use the same provider, metric and measurement scope for your own value and the competitor’s value. Record that context with the observation. Comparing a domain-level metric on one side with a page-level metric on the other gives the software two numbers, but does not give your team a useful comparison.
A compact note might read: “Checked 4 Nov 2026; UK desktop; reviewed first 30 organic results; both authority values from the same provider and domain metric; competing page answers pricing questions.” This is a suggested note format, not a claim that the tool collects any of those details automatically.
Your authority score is a shared workspace setting. Changing it changes the rule applied to every saved search record. If the number of flagged records rises after an edit to that setting, do not describe the increase as a change in the search results. It may simply reflect the new comparison value.
The “Largest authority gap” sort orders records by competitor authority from low to high. Blank and zero values fall toward the end. It is not a ranking based on customer value, likely traffic or effort. Look at the underlying records rather than treating the first item as an automatic assignment.
4. Read the quick-win panel as a record count
The Quick-win signal panel displays flagged records divided by all saved search records. With three flagged records out of ten, it shows 3 / 10 and fills 30% of the bar.
That 30% is the share of your saved records that match the rule. It is not a 30% chance of ranking, a share of the search market, or an estimate of the work already completed. If you add another unflagged record, the fraction changes even when the original ten observations have not changed.
Repeated entries also count separately. Importing the same rows again adds records rather than merging them. Review the saved list for duplicate queries and competing pages before using the count in an update. If you intentionally keep repeated observations, include their check dates and explain that the total represents observations rather than unique opportunities.
5. Review the evidence that the rule leaves out
Missing title terms, content notes and the competitor’s last-updated date are useful context, but they do not affect this flag. The tool does not apply a freshness cutoff or decide that an old page is easy to outrank.
For each candidate, answer four questions before assigning work:
- Does the query matter to our customer? State the decision or problem the searcher is trying to solve.
- Does our intended page match that need? Open the competing result and compare the actual topic, format and level of detail.
- What can we substantiate? Identify a real example, original explanation, documented process or other evidence your team can provide.
- What is the next bounded task? Name a specific page improvement and the evidence needed to complete it.
A useful outcome might be: “Add a clearly scoped pricing example to our comparison page, confirm the assumptions with the product owner, and repeat the same search check after publication.” Avoid turning the label itself into a promise of traffic or an expected completion date.
6. Keep the decision with the research
Use Content / technical gap notes for the reason you selected an opportunity, including the observation date and important limits. The field is short, so keep a concise summary and a reference to any fuller evidence you maintain elsewhere.
Export workspace downloads a JSON record of the local workspace, including saved research, briefs and settings. Keep that export with your reporting notes before clearing browser data or moving to another device. The current interface imports SERP CSV files; it does not offer a full-workspace JSON restore control.
Shane’s Gap Analyzer analyzes observations you enter or paste. This version does not query search engines, retrieve live rankings, or independently verify AI citations. A strong workflow combines its simple flag with a careful human check, then records why a particular page deserves the next hour of work.