Find SEO Quick Wins

Check SEO MCP opportunities from crawl, search, and connected traffic data, then verify the evidence before planning work.

list_quick_wins surfaces bounded opportunities from available crawl, search-performance, and connected traffic data. A completed crawl is needed for crawl-derived opportunities; it is not a universal prerequisite for the tool. Check each item's source and time window before deciding what to do.

Prompt

Find SEO quick wins for [PROJECT] from the sources currently available.

For each opportunity:
- explain the detection rule
- identify the source and its time window
- show the affected count
- retrieve representative records
- estimate reach and likely effort
- identify the owning team
- define how to verify the fix

Rank by expected impact divided by implementation effort.
Do not treat a crawler recommendation as proof without checking the records.

Tool sequence

list_projects and select the project.
list_quick_wins and note the source, date range, and availability for each category.
For crawl-derived items, call list_crawls, select the relevant completed crawl, and use a matching verification tool:
- list_pages
- list_links
- list_images
- get_page_details

For connected search or traffic opportunities, use only the evidence and links actually returned by the tool. This MCP surface does not expose a general Search Console query/page export; verify a high-stakes search conclusion in the source product if the returned sample is insufficient.

A practical scoring model

Score each candidate from 1–5:

Factor	Question
Reach	How many important pages or journeys are affected?
Severity	Does it block access, create conflict, or weaken understanding?
Confidence	Is the issue verified by records and context?
Effort	Can one controlled change fix the pattern?

Use the score to guide discussion, not as a universal ranking formula.

Keep source-specific denominators separate. For example, a crawl issue count is not comparable to search impressions or tracked keyword counts without a decision about which pages and dates matter.

Avoid false efficiency

Do not prioritize an item only because its count is large. Thousands of low-value archive pages may matter less than one broken navigation target. Conversely, a template correction can resolve a large issue set with little work.

Turn findings into tickets

Ask the agent to produce one ticket per shared root cause:

Group these quick wins by likely root cause.
For each group, draft a ticket with evidence, affected URL patterns,
acceptance criteria, and the exact post-release SEO MCP validation prompt.