---
title: "Community intent report | SEO Skill"
description: "Find Search Console queries with forum, review, comparison or discussion intent so your content can answer the format people are looking for."
canonical: "https://seoskill.dev/docs/reports/community-intent"
language: "en"
---

# Community intent report

Pull out searches that sound like people want opinions, comparisons or first-hand experience. The wording is a useful content clue, but it does not prove that a forum page must rank.

## 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 returned queries with review, forum, or comparison wording.

```
seo community-intent --project example
```

## What you get from this report

Find Search Console queries with forum, review, comparison or discussion intent so your content can answer the format people are looking for.

Best for

You need Search Console wording to review community or evidence-led content opportunities.

Needs

Returned Search Console queries

You get

Find Search Console queries with forum, review, comparison or discussion intent so your content can answer the format people are looking for.

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 queries

Provides the exact wording, impressions, clicks, and date range behind each match.

### Documented phrase categories

Defines explicit forum, review, comparison, recommendation, and experience patterns.

## Use a different report for these jobs

These jobs need a different report or a manual review.

[

### You want broader repeated query themes and content gaps, not only searches containing community or comparison wording.

Run query clusters. It groups the returned Search Console demand into repeated themes without requiring the explicit phrase patterns used here.

Search query clustering report

](https://seoskill.dev/docs/reports/query-clusters)

### You need to decide whether a page should contain first-hand experience, reviews, comparisons, or a discussion format.

No automated report can judge whether you have credible experience or which editorial format will satisfy the searcher. Review representative results, the existing page, and the evidence your business can genuinely provide. This report can still select the query wording and current ranking pages 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 community-intent --json
```

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

```
seo reports run community-intent --params '{"site":"sc-domain:example.com","days":90,"minImpressions":20,"limit":25}' --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": "community-intent"
}
```

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

```
{
  "id": "community-intent",
  "params": {
    "site": "sc-domain:example.com",
    "days": 90,
    "minImpressions": 20,
    "limit": 25
  }
}
```

### 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(
  'community-intent',
  {
  "site": "sc-domain:example.com",
  "days": 90,
  "minImpressions": 20,
  "limit": 25
},
)

console.log(result)
```

## What to do next

Review the wording of the returned queries and the result formats already serving them. Use that evidence to decide whether the page needs first-hand experience, comparison detail or a different content format.

1.  01Decide whether an existing page already answers the need with credible first-hand evidence.
2.  02Use content optimization for a supported page brief.

## 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)[

Group returned Search Console queries into repeated demand themes so content gaps, templates and competing pages are easier to inspect across the site.

Search query clustering report

](https://seoskill.dev/docs/reports/query-clusters)[

Compare one URL with its Search Console queries and live page evidence to find focused content, CTR and coverage opportunities before rewriting the page.

Page SEO opportunities

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

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