---
title: "SEO action plan | SEO Skill"
description: "Turn finalised monthly Search Console evidence into a limited SEO action plan with clear priorities and the follow-up report to run for each one."
canonical: "https://seoskill.dev/docs/reports/monthly-action-plan"
language: "en"
---

# SEO action plan

Build a practical monthly work list from supported Search Console findings. Every action stays linked to the report that produced it so an agent can inspect the evidence before making a change.

## 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
```

Run create a monthly seo action plan through the report catalog.

```
seo reports run monthly-action-plan --params '{"site":"sc-domain:example.com","month":"2026-05","limit":10,"includeBrand":false}' --json
```

## What you get from this report

Turn finalised monthly Search Console evidence into a limited SEO action plan with clear priorities and the follow-up report to run for each one.

Best for

A repeatable monthly review should end with a small action queue.

Needs

Finalised monthly Search Console evidence

You get

Turn finalised monthly Search Console evidence into a limited SEO action plan with clear priorities and the follow-up report to run for each one.

Use next

Monthly SEO report

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.

### Finalised monthly Search Console evidence

Provides the calendar-month report, comparison evidence, opportunities, and caveats.

### Workflow limits and brand settings

Bound the detail and keep branded searches included or excluded consistently.

## Use a different report for these jobs

These jobs need a different report or a manual review.

[

### You only need a readable monthly status report and do not want a generated follow-up queue.

Run monthly report. It returns the calendar-month comparison, opportunity evidence, what each source returned, and caveats without adding the workflow action list.

Monthly SEO report

](https://seoskill.dev/docs/reports/monthly-report)[

### You need to measure the effect of one known implementation rather than review the whole month.

Run measure change with the recorded implementation date and suitable before-and-after windows. It preserves coverage and comparison limits around that change. Neither report can prove causation when other changes overlap.

SEO change measurement

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

## 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 monthly-action-plan --json
```

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

```
seo reports run monthly-action-plan --params '{"site":"sc-domain:example.com","month":"2026-05","limit":10,"includeBrand":false}' --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": "monthly-action-plan"
}
```

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

```
{
  "id": "monthly-action-plan",
  "params": {
    "site": "sc-domain:example.com",
    "month": "2026-05",
    "limit": 10,
    "includeBrand": false
  }
}
```

### 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(
  'monthly-action-plan',
  {
  "site": "sc-domain:example.com",
  "month": "2026-05",
  "limit": 10,
  "includeBrand": false
},
)

console.log(result)
```

## What to do next

Open the supporting report behind each action before assigning the work. Carry unfinished or weakly supported items into the next month with their evidence gap stated plainly.

1.  01Run the leading focused report.
2.  02Store the output for a consistent comparison next month.

## Related reports

[

Create a monthly SEO report from finalised Search Console data with clear comparisons, page evidence, missing data and next actions for the next month.

Monthly SEO report

](https://seoskill.dev/docs/reports/monthly-report)[

Turn crawl findings into a concise narrative that explains what matters, what changed and which evidence supports the next action without hiding limits.

Narrative SEO report

](https://seoskill.dev/docs/reports/narrative-report)[

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)