Quick Wins
Find and prioritize Screpy's actionable organic-search and crawl opportunities.
Quick Wins turns Screpy data into focused opportunities. It combines organic-search movement with project data so you can choose the next investigation instead of starting from an unfiltered crawl report. It is not a substitute for judgment: confirm the affected URLs and the likely cause before assigning a fix.
Choose an opportunity type
Use the Quick Wins menu to switch between these views:
| View | Best for |
|---|---|
| Striking Distance Pages | Pages close enough to stronger rankings to merit an on-page or internal-linking review. |
| CTR Opportunities | Queries or pages with visibility where a better result presentation may earn more clicks. |
| New Content Opportunities | Search demand that may justify a new page or a meaningful content expansion. |
| Second Page Keywords | Keywords near the first page of results that need closer competitive and intent analysis. |
| Lost, Rising, and Falling Queries | Changes in the queries that bring visibility to the project. |
| Rising and Falling Pages | URL-level movement worth investigating after a content, technical, or ranking change. |
Choose the date range before making a decision. The same page can look different over a short window and a longer period, especially around launches, seasonal demand, or search-result changes.
Work from impact to implementation
Start with findings that affect important, indexable pages or repeat across a template. A small issue on a high-value page can matter more than a larger count on low-value or intentionally excluded URLs. The opportunity tables expose signals such as impressions, clicks, CTR, position, and visibility. Use Queries to see the search context behind a page before deciding what to change.
Group related work into one change when the root cause is shared. For example, a repeated metadata or linking issue should usually be fixed in the relevant template rather than in dozens of individual records. Keep a short note of the baseline count, the change made, and the crawl that verifies it.
A practical review workflow
- Select one opportunity view and a meaningful date range.
- Sort or scan for high-value URLs and queries rather than chasing the largest raw count.
- Open the affected page in Pages and inspect its crawl data, links, title, content, and indexability.
- Use SERP analysis when you need to compare the current result set and search intent.
- Make one explainable change, then review the next completed crawl and the later search data.
The table can be exported as CSV or Excel when you need to share the opportunity list or combine it with an editorial backlog.
Avoid false priorities
Do not optimize a warning without understanding its purpose. A noindex directive can be intentional. A redirect can be a valid migration control. A missing image alt text can be correct for a decorative asset. The useful question is: does this finding prevent the intended visitor or search outcome?
After the fix
Publish the change, run a new crawl, and compare completed results. If the count does not change, inspect one affected URL again; a cached page, a different template, or an incomplete crawl scope may explain the result.