---
title: "SEO quick wins report | SEO Skill"
description: "Find page-one queries with useful impressions and weaker CTR evidence, then inspect the search result before changing titles, snippets or page copy."
canonical: "https://seoskill.dev/docs/reports/quick-wins"
language: "en"
---

# SEO quick wins report

Find visible queries that may have a practical CTR opportunity without rewriting the whole page. The shortlist is fast to review, but the word quick does not make the evidence certain.

## Install and run the report

Install the CLI once, then run `seo start` to connect your site and Google data. After setup you can run this report yourself or ask your agent to run it.

Install the SEO CLI globally.

```
npm i -g seo
```

Run setup after installation.

```
seo start
```

Find visible queries and pages that deserve a closer CTR review.

```
seo quick-wins --project example
```

## What you get from this report

Find page-one queries with useful impressions and weaker CTR evidence, then inspect the search result before changing titles, snippets or page copy.

Best for

You want a small queue from returned positions 4 to 10 with meaningful impressions.

Needs

Returned Search Console query and page rows

You get

Find page-one queries with useful impressions and weaker CTR evidence, then inspect the search result before changing titles, snippets or page copy.

Use next

Build a content optimization brief

Every report follows the same rules for missing data and outside estimates.[See how report data works](https://seoskill.dev/docs/reports#how-report-data-works).

## What you need before you run it

The report uses the information below. Optional sources are only used when you ask for them.

### Returned Search Console query and page rows

Provides impressions, clicks, CTR, and average position for the selected finalised window.

### Optional live-page checks

Fetches a limited number of candidate pages for title, snippet, content, and technical context.

## Use a different report for these jobs

These jobs need a different report or a manual review.

[

### You want pages averaging positions 11 to 20 rather than page-one rows with weak CTR.

Run second page. It returns a page-oriented queue with the queries, impressions, clicks, CTR, and average position behind each candidate, while keeping the position range as a review filter rather than a ranking forecast.

Second page SEO report

](https://seoskill.dev/docs/reports/second-page)

### You need to know whether changing a title or snippet will definitely increase clicks.

No automated report can decide that in advance. Review the live result page, query intent, competing snippets, and the page itself, then record the change and measure a complete later period. Quick wins can still select the strongest rows for that review.

Needs more evidence

## Use the report with an agent or in code

The command above is enough for most work. These options let an agent, script or application run the same report with explicit input and structured output.

### CLI

Use the report catalog when an agent, script or CI job needs predictable JSON instead of the normal terminal output. Check the current input first, then run the report with the validated parameters.

Check the current input before the agent or script runs the report.

```
seo reports describe quick-wins --json
```

Once the input is valid, run the report through the report catalog.

```
seo reports run quick-wins --params '{"site":"sc-domain:example.com","days":90,"limit":20,"minImpressions":100,"verifyContent":true,"verifyLimit":5}' --json
```

### MCP

An MCP agent follows the same two-step flow. It inspects the current schema, fills the required fields and only then runs the report.

Ask the MCP server for the current report input.

```
{
  "id": "quick-wins"
}
```

Run the report after the agent has checked and filled the input.

```
{
  "id": "quick-wins",
  "params": {
    "site": "sc-domain:example.com",
    "days": 90,
    "limit": 20,
    "minImpressions": 100,
    "verifyContent": true,
    "verifyLimit": 5
  }
}
```

### TypeScript

Install the package in a Node 22 project when your application needs to run the report directly. The result includes the same evidence, warnings and limits returned through the CLI and MCP server.

Add the SEO package to your project.

```
npm install seo
```

Run the report from your TypeScript application.

```
import { executeReport } from 'seo/mcp'

const result = await executeReport(
  'quick-wins',
  {
  "site": "sc-domain:example.com",
  "days": 90,
  "limit": 20,
  "minImpressions": 100,
  "verifyContent": true,
  "verifyLimit": 5
},
)

console.log(result)
```

## What to do next

Inspect the current result and page intent before changing its snippet. Record the exact title or description update and compare the same queries after a complete data window.

1.  01Inspect the SERP and live page for the best-supported rows.
2.  02Record a specific change and measure it over a complete later window.

## Related reports

[

Build a content brief from one page, its Search Console queries and the headings or topics already present. Keep every suggestion tied to demand.

Content optimization report

](https://seoskill.dev/docs/reports/content-optimization)[

Audit one URL for technical SEO, metadata, canonicals, schema, links and Search Console queries. See the live evidence before changing the page.

SEO page audit

](https://seoskill.dev/docs/reports/audit-page)[

Compare matched Search Console periods around a recorded SEO change and keep releases, demand shifts and other confounders beside the result.

SEO change measurement

](https://seoskill.dev/docs/reports/measure-change)

## Sources used by this report

These primary sources define the provider data or search controls used by the result.

-   [Search Console Search Analytics API guidance](https://developers.google.com/webmaster-tools/v1/how-tos/search_analytics)