MCP Platform
Google Search Console — Content Groups
Group your pages or queries and track their Search Console numbers together, with your approval for every change.
Install only these tools
Semust-com/google-search-console-mcp has ready-to-paste Claude Desktop, Claude Code and Cursor configs that load just this family of tools, using SEMUST_MCP_TOOLSETS. The content-group tools are in the gsc family.
Product page: Google Search Console MCP
A content group is a saved set of pages or queries whose Search Console numbers are added up together, the same groups you see in Semust under Search Console → Content Groups. Claude builds a group with you in conversation: it suggests groups from your site's URL structure, previews what a group would contain and saves it once you approve. It can also read how your existing groups perform.
Tools
| Tool | What it does | Access |
|---|---|---|
content_group_list | The project's saved content groups: name, type, patterns and a link to the group in Semust | Read-only |
content_group_get | One group's clicks, impressions, CTR and position; first half vs second half of the period, the daily series and its top pages or queries | Read-only |
content_group_suggest | Page groups suggested from your site's first-level URL folders (e.g. /blog/) | Read-only |
content_group_preview | Which pages or queries a set of patterns would match, with counts per pattern and warnings. Nothing is saved | Read-only |
content_group_create | Saves a new content group | Writes |
content_group_update | Renames a group or replaces its patterns | Writes |
content_group_delete | Deletes a group; your Search Console data is not affected | Writes |
Only the four read tools should be auto-approved
content_group_list, content_group_get, content_group_suggest and content_group_preview are read-only, so you can add them to alwaysAllow. The write tools (content_group_create, content_group_update, content_group_delete) are marked as changing tools, so your client asks you before each one. Keep it that way.
How patterns match
| Type | Match | Example |
|---|---|---|
page | A URL is in the group when it contains a pattern | /blog/ → every page with /blog/ in its address. A full URL → that page |
query | A query is in the group only when it equals a pattern | lawyer does not match "lawyer near me"; list every query you want |
Patterns are lowercased. A page matched by two patterns is counted once. A group can have up to 100 patterns.
How a group gets built
Claude checks your existing groups
If a group with the same name or the same patterns exists, it shows that group or offers to update it instead of creating a duplicate.
It finds patterns in your real data
For page groups it uses your site's URL folders (
content_group_suggest) or your page list; for query groups it picks the queries from your Search Console keywords. It does not invent patterns.Preview
It shows how many pages or queries the group would contain, their total clicks and impressions, the counts per pattern and any warnings: patterns that match nothing, patterns that match the whole site, or patterns another pattern already covers.
You approve
Claude saves the group only after you clearly say yes, then gives you its link in Semust. For updates and deletes it also says what will change and waits for your yes.
What you need
- An MCP key. Create one in Semust under Settings → MCP Setup; content groups need no extra permission. Groups live only in your project and are undone by deleting them. The old account API key can read groups but not change them.
- Search Console connected. The group tools work only on projects with Search Console connected.
Example requests
- "Make a content group of my blog pages and show me how it did over the last 3 months"
- "Create a group for my brand queries"
- "Which of my content groups grew the most?"
- "Add the /guides/ pages to my blog group"
Limits
| Limit | Detail |
|---|---|
| Patterns | Up to 100 per group, each up to 200 characters |
| Type | A group's type cannot change later; delete it and create a new one |
| Speed | Search Console is asked once per pattern, so a large group can take a few seconds |
| Comparison | content_group_get compares the first and second half of the date range. Search Console data runs about two days behind |
Errors such as content_group_exists, content_group_not_found and write_scope_required are explained in Troubleshooting.
