Hermes Agent for SEO: Connect Search Console, DataForSEO, and Build SEO Skills

Which tools does a Hermes Agent SEO setup need?

How do you connect SEO data and skills to Hermes Agent?

1. 1

   Turn on the toolsets SEO work needs

   Run hermes tools and enable web, browser, file, terminal, skills, memory, and cronjob. Leave unrelated toolsets off (Spotify, Home Assistant, Discord admin): a shorter tool list gives the model less to choose from when it decides what to call. For a one-off session you can also pass a list directly with hermes chat --toolsets.

   hermes tools
   
   # or, for a single session
   hermes chat --toolsets "web,browser,file,skills,memory"

2. 2

   Create Google Cloud credentials for Search Console

   In Google Cloud Console, create a project, enable the Search Console API, and create credentials. You have two options. An OAuth client signs in as you and sees every property your Google account can reach. A service account sees only the properties where you add its email as a user in Search Console, which the mcp-gsc README says needs full access. For an agent, the service account is the better habit: you decide exactly which sites it can read. Save the downloaded JSON somewhere permanent and outside any git repo.

3. 3

   Install mcp-gsc and register it in config.yaml

   Install uv, clone mcp-gsc, and add it under mcp_servers in ~/.hermes/config.yaml (full block in the examples below). mcp-gsc needs Python 3.11 or newer. The detail that is easy to miss: Hermes strips environment variables from MCP subprocesses and passes only safe system variables plus what you write in the server's env block, so a GSC_CREDENTIALS_PATH exported in your shell never reaches the server. Leave GSC_ALLOW_DESTRUCTIVE unset so the agent cannot run destructive Search Console operations. Then type /reload-mcp in a chat and ask the agent to list your properties.

   curl -LsSf https://astral.sh/uv/install.sh | sh
   git clone https://github.com/AminForou/mcp-gsc.git ~/mcp/mcp-gsc
   cd ~/mcp/mcp-gsc
   uv venv .venv
   uv pip install -r requirements.txt

4. 4

   Add DataForSEO for keyword and SERP data

   Create a DataForSEO account, copy your API credentials, and add the official dataforseo-mcp-server to config.yaml with DATAFORSEO_LOGIN and DATAFORSEO_PASSWORD in its env block. It runs through npx, so Node.js must be on your PATH. DataForSEO is a paid API: check its pricing before asking the agent for anything in bulk, and start with a single keyword to see what one request returns. An agent retrying in a loop can send far more requests than you expect. If you prefer not to run the server locally, DataForSEO also hosts one at https://mcp.dataforseo.com/v3/mcp with OAuth.

5. 5

   Search the skills hub before writing your own

   Search for existing SEO skills with hermes skills search seo, read a skill's SKILL.md before installing it, and install only what matches how you work. Hub skills come from the official Hermes repo, Vercel's skills.sh, GitHub repos, and sites that publish a skills index. Every hub install passes a security scanner that checks for data exfiltration, prompt injection, and destructive commands. A clean scan means the skill is not obviously malicious. It says nothing about whether its SEO advice is good. Our read: generic public checklists are a starting point, and your own skills win because they carry your site's rules.

   hermes skills search seo
   hermes skills browse
   hermes skills install <identifier>   # after reading its SKILL.md
   hermes skills list

6. 6

   Write an on-page audit skill

   Create ~/.hermes/skills/seo/page-audit/SKILL.md with YAML frontmatter (name, description, version, tags, required toolsets) and a body that spells out the procedure, the output format, and the pitfalls. Skills load on demand, so the description decides when Hermes reaches for one; write it as the task a person would actually ask for. Test with /page-audit followed by a URL. Then use it for a week and add a line to Pitfalls every time the output goes wrong. Hermes can also create and patch skills itself after complex tasks; set skills.write_approval to true if you want to review those edits before they are saved.

7. 7

   Write a weekly Search Console report skill

   Create a second skill, gsc-weekly-report, that compares the last 7 days with the previous 7 through mcp-gsc and returns a short report in a fixed format. The fixed format matters more than clever analysis: a report shaped the same every week can be scanned in two minutes and compared with last week. Tell the skill which movements count and set an impressions floor so it ignores noise from tiny queries. Keep in mind that recent Search Console data can still change. mcp-gsc's GSC_DATA_STATE defaults to all, which includes fresh data; set it to final to use finalized data only.

8. 8

   Schedule the report with hermes cron

   Create the job with hermes cron create, a schedule, a prompt, and --skill gsc-weekly-report. Hermes accepts natural schedules like "every monday 9am" as well as cron expressions like "0 9 * * 1". Each run is saved under ~/.hermes/cron/output/, and once the messaging gateway is set up, --deliver can send results to Telegram, Slack, Discord, or email. Before the first unattended run, review the approvals settings (there is a separate cron_mode) and trigger the job once by hand with hermes cron run so you read the output before anyone else does.

   hermes cron create "every monday 9am" "Run the weekly Search Console report for sc-domain:example.com and save it to ~/seo/example-com/reports/" --skill gsc-weekly-report --name gsc-weekly
   
   hermes cron list
   hermes cron run <job-id>   # test once by hand

Copy-ready config and skill files

mcp_servers:
  gsc:
    command: "/Users/you/mcp/mcp-gsc/.venv/bin/python"
    args: ["/Users/you/mcp/mcp-gsc/gsc_server.py"]
    env:
      GSC_CREDENTIALS_PATH: "/Users/you/keys/gsc-service-account.json"
      GSC_SKIP_OAUTH: "true"
      GSC_DATA_STATE: "all"

  dataforseo:
    command: "npx"
    args: ["-y", "dataforseo-mcp-server@latest"]
    env:
      DATAFORSEO_LOGIN: "your-api-login"
      DATAFORSEO_PASSWORD: "your-api-password"

---
name: page-audit
description: Audit one URL for on-page SEO issues using the live page and Search Console data
version: 1.0.0
metadata:
  hermes:
    tags: [seo, audit]
    category: seo
    requires_toolsets: [web]
---

# On-page SEO audit

## Procedure
1. Fetch the live URL. Quote title, meta description, canonical, robots meta, H1, and H2s.
2. Pull the last 28 days of queries for this URL from Search Console.
3. Check whether the top 5 queries by impressions appear in the title, H1, or first paragraph.

## Output (always this format)
| Element | Current | Issue | Fix | Evidence |

Evidence is a quoted element or a Search Console figure with its date range.

## Never
- Estimate traffic or search volume without a tool result
- Recommend changes to pages other than the given URL
- Rewrite the whole page; propose the specific edit

## Pitfalls (add a line after every bad run)
- Search Console URLs can differ from the live URL by trailing slash or locale prefix; match both
- A plain fetch can miss JavaScript-rendered content; use the browser tool if the body looks empty

---
name: gsc-weekly-report
description: Weekly Google Search Console report comparing the last 7 days with the previous 7
version: 1.0.0
metadata:
  hermes:
    tags: [seo, reporting, search-console]
    category: seo
---

# Weekly Search Console report

## Procedure
1. Compare the last 7 days with the previous 7 days for the given property.
2. Report site totals: clicks, impressions, CTR, average position, each with % change.
3. List the 5 pages with the largest click loss and the 5 with the largest gain.
4. For each page, list the queries behind the change. Skip queries under 100 impressions in both periods.

## Output
- A 5-line summary first: numbers only, no adjectives
- Then the two tables
- End with at most 3 things worth checking, each tied to a row above

## Never
- Blame a change on an algorithm update without a source
- Round or estimate figures; copy them from the tool output
- Call a single week-over-week change a trend

Frequently asked questions