Hermes SEO

Hermes SEO is a native Hermes plugin port of SEO workflows from Claude SEO v2.4.2. It includes 25 workflow skills plus the seo router, 19 specialist role skills, 56 utility scripts, Schema.org templates, and optional integrations. Claude SEO was created by Daniel Agrici. See credits for upstream attribution and media notes.

This independent community plugin is maintained at yuzushi-dev/hermes-seo. It is listed in the Hermes plugin catalog. Release v0.1.0 remains available.

The plugin helps Hermes inspect websites, prepare SEO recommendations, validate or draft structured data, and run focused workflows for content, local search, international SEO, and AI search visibility. Its skills guide the analysis; bundled utilities handle specific checks and transformations.

The map below groups the 25 workflow skills. Provider integrations are optional, and Google OAuth workflows remain disabled because Hermes does not yet provide a profile-scoped authorization route.

Install the released commit from GitHub with Hermes' Git installer:

hermes plugins install https://github.com/yuzushi-dev/hermes-seo.git --ref 5f04951e8fddc8b869378236a7ff5b584a0d023d --yes-deps --enable
hermes plugins doctor hermes-seo --ci

The --ref value pins the install to the v0.1.0 commit. --yes-deps consents to installing the plugin's declared Python dependencies, including in non-interactive shells. The plugin registers namespaced skills such as hermes-seo:seo-audit and hermes-seo:role-seo-technical; use skills_list and skill_view to discover or load them. The hermes-seo:seo skill routes general SEO requests. The runtime commands are hermes seo setup, hermes seo doctor, and hermes seo run.

hermes seo setup creates a private virtual environment and downloads pinned Python packages. Browser setup also downloads Chromium and may use substantial disk space. Setup is user initiated. hermes seo doctor --json checks readiness without changing the system. Use hermes_seo_run for credentialed utilities and hermes seo run <script.py> for noncredentialed utilities. Both run through the isolated environment and script allowlist.

Ask Hermes in natural language, for example:

• “Run hermes-seo:seo-audit on https://example.com and give me the highest-priority findings with evidence.”
• “Use hermes-seo:seo-schema to inspect the JSON-LD on https://example.com/about and suggest a corrected block.”
• “Load hermes-seo:seo-content-brief and create a brief for a guide to accessible home renovation.”
• “Use hermes-seo:seo-technical to check the sitemap, robots.txt, canonical tags, and page status codes for https://example.com.”

The agent can also load the router with “Use hermes-seo:seo to help me investigate this site's search visibility.”

The original Claude SEO README includes this excerpt from a Schema.org audit dated 2026-02-09:

Schema types: Organization, WebSite, SoftwareApplication. Critical issues: 2; warnings: 5; passed checks: 18; overall grade: B+.

Source: upstream sample report. The excerpt is reproduced from the original Claude SEO README.

Claude SEO's ten-principle method groups its principles into four phases: perceive, analyze, validate, and act. The diagram is adapted from the upstream graphic with Hermes SEO branding.

The separate FLOW skill and its prompt materials remain attributed under CC BY 4.0. See the FLOW skill.

This upstream recording shows the Claude SEO audit workflow in the Claude Code interface.

Google Search Console growth and PageSpeed results for claude-seo.md, published by Daniel Agrici in the upstream project for March to June 2026.

The native plugin requires Hermes Agent 0.22.2 or newer and supports Linux and macOS. Windows is not declared because the registered runtime launches through Bash. Python 3.10 or newer with venv support is required for the managed SEO runtime.

The package preserves optional integrations for DataForSEO, Banana image generation, Firecrawl, Ahrefs, SE Ranking, Profound, Bing Webmaster, Matomo, and Unlighthouse. They require compatible MCP servers or individual service credentials and stay inactive unless configured in Hermes. Setup scripts that wrote Claude Code configuration were removed. See extension notes for what is retained and what remains unverified.

Do not call paid endpoints, spend API credits, or submit data to external services without the user's explicit approval for that operation. Skills request approval before external or paid operations; hermes_seo_run does not enforce an approval policy. Skills must report when a provider or credential is unavailable. CI skips the suite's explicit live-network render check and does not call provider APIs.

Google Search Console, GA4, Google Ads, and Indexing API OAuth flows remain disabled until Hermes provides a profile-scoped Google authorization route. Supported profile-vault names are GOOGLE_API_KEY, MOZ_API_KEY, BING_WEBMASTER_API_KEY, KEYWORDSEVERYWHERE_API_KEY, MATOMO_API_TOKEN or MATOMO_TOKEN, MATOMO_URL, MATOMO_SITE_ID or MATOMO_IDSITE, HERMES_SEO_LOCAL_TARGETS, DATAFORSEO_USERNAME, DATAFORSEO_PASSWORD, INDEXNOW_KEY, and Banana's GOOGLE_AI_API_KEY. IndexNow's nonsecret key-location URL stays a normal script argument. Secrets are never catalog metadata or repository files.

The runtime allowlists bundled scripts, rejects path traversal, and uses the source project's SSRF and DNS-rebinding protections. Runtime files and browser binaries use the active Hermes plugin data directory; credentials remain in the active Hermes profile vault and are injected only for an allowlisted script. No credential files belong in this repository. Schema feedback runs after Hermes file-write tools and returns findings to the model; it does not block or roll back a write.

The plugin can start local subprocesses for its managed Python runtime through hermes_seo_run. This native tool runs in the Hermes host plugin process; a Docker terminal sandbox does not contain it. Script arguments may therefore name host paths accessible to that process. hermes seo setup downloads Python packages and, unless skipped, Chromium. Audit workflows fetch user-selected websites. Optional integrations send data to their named third-party providers and may incur charges; they remain inactive until separately configured. The plugin stores its managed environment, cache, and runtime configuration in Hermes plugin data storage. It does not include telemetry or a self-updater.

The core project is MIT licensed. The FLOW framework and its prompt materials remain CC BY 4.0 with source attribution. See LICENSE, the FLOW skill, and media credits.

hermes plugins validate /path/to/hermes-seo
hermes plugins doctor /path/to/hermes-seo --ci
rtk pytest -q

The source suite covers local script behavior and security boundaries. API-backed behavior needs the corresponding service account and was not validated as part of the local port.

Catalog preparation metadata is available in docs/catalog-submission-template.yaml, the catalog entry template.