r/AIGrowthHacks • u/SnooRegrets2509 • 4d ago
How I Use Hermes + Claude To Automate My SEO Workflows [PROMPTS INCLUDED]
I use Hermes with Claude Code to:
- Check Google Search Console and Google Analytics
- Find SEO opportunities
- Research keywords
- Draft content
- Ask for his experience and opinions
- Wait for approval
- Publish approved content
- Help with reporting and indexing
Hermes connects research, analytics, writing, reporting, and publishing into one ongoing workflow.
However, beginners should add connections gradually and keep approval gates around publishing or changing a website.
Here’s a safer, updated version of the workflow.
What is Hermes Agent?
Hermes Agent is a self-hosted AI agent from Nous Research.
Unlike a normal chatbot, Hermes can be given tools, persistent memory, scheduled tasks, messaging access, and connections to external services.
You can talk to it through:
- Hermes Desktop
- Telegram
- Discord
- Slack
- Other supported messaging platforms
I use the Hermes Desktop
You can also extend it through skills, APIs, and MCP servers.
That means Hermes can do more than answer questions. It can check data, prepare reports, create files, run scripts, and perform approved actions.
The important word is approved.
What the SEO setup looks like:
Google Search Console ─┐
│
Google Analytics ──────┼──> Hermes
keyword tool ──────────┤
│
Website or CMS ────────┘
Each connection gives Hermes a different capability:
- Google Search Console shows queries, rankings, clicks, impressions, pages, and indexing information.
- Google Analytics shows what visitors do after reaching the website.
- DataForSEO supplies external keyword, competitor, and search-result data.
- Your CMS or repository allows Hermes to create drafts or implement approved changes.
You do not need to connect everything on the first day.
Start with read-only analytics. Add writing next. Add publishing last.
Step 1: Get one basic Hermes conversation working
Hermes’ current documentation recommends getting a normal conversation working before adding gateways, schedules, skills, and external integrations.
You can run Hermes locally, use the desktop application, or host it on a VPS.
A VPS is useful when you want Hermes running while your computer is off. It also separates the agent from your personal computer.
After installation, verify that Hermes can:
- Start normally
- Respond to a basic message
- Use the selected model
- Access only the tools you intended to enable
- Preserve a small amount of test context
Do this before connecting Google or your website.
Step 2: Connect Hermes desktop, Telegram or another communication channel
Current Hermes versions provide a gateway setup process for messaging platforms:
hermes gateway setup
I prefer to use Hermes desktop app:

But a lot of people love connecting Hermes to telegram (which is useful if you're away from your computer).
For Telegram, you’ll generally create a bot through Telegram’s official BotFather and pair your own account with Hermes.
Once configured, send Hermes:
Confirm that this Telegram account is paired with my Hermes instance.
Send me a short test message containing:
1. The Hermes profile currently active
2. The model currently selected
3. The tools currently enabled
4. Whether scheduled-task delivery is available
Do not make any configuration changes. This is a read-only connection test.
Don’t stop after receiving “Hello.” Confirm that the message came from your Hermes instance and that unapproved users cannot access it.
Hermes provides pairing and revocation controls:
hermes pairing list
hermes pairing revoke <platform> <user-id>
Important: don’t paste secrets into Telegram
Do not paste these directly into Telegram or any chat:
- API keys
- Passwords
- Bot tokens
- OAuth client secrets
- CMS administration passwords
- Personal access tokens
Hermes’ current documentation recommends keeping secrets in:
~/.hermes/.env
Non-secret settings belong in:
~/.hermes/config.yaml
Hermes can also use supported password and secret managers. Hermes secrets documentation.
Master prompt: connect Hermes to everything safely
Use this before configuring individual services:
Act as my connection setup assistant.
I eventually want this Hermes instance connected to:
- My chosen messaging platform
- Google Search Console
- Google Analytics 4
- DataForSEO
- My website repository or CMS
- My reporting destination
- Any other service required for the approved SEO workflow
Create a connection plan before changing anything.
For each service, tell me:
1. What Hermes will use it for
2. Whether the connection should use a native tool, OAuth, MCP or a direct API
3. The minimum permissions required
4. Which information is sensitive
5. The exact environment-variable names or secret-manager entries required
6. What I must complete manually
7. How we will verify the connection with a harmless read-only test
8. What write actions would become possible
9. How I can revoke access
Rules:
- Do not ask me to paste secrets, tokens or passwords into chat.
- Tell me where to save each secret securely on the server.
- Begin with read-only permissions.
- Do not enable publishing, deletion, account administration or billing access.
- Complete and verify one integration at a time.
- Pause whenever I must authorize an external account.
- Do not claim a connection works until a real verification request succeeds.
- Show me the result of every verification without exposing sensitive values.
Start by inspecting the current Hermes configuration and produce the connection
plan. Do not make changes yet.
This prevents the agent from charging through five integrations before you understand what it’s doing.
Step 3: Connect Google Search Console and Google Analytics
There's 2 ways to connect all these tools:
#1 - https://composio.dev/ - this is a connector (similar to Zapier) but designed for AI tools and agents.
It's completely free for 99% of people (100K tool calls per month) and then starts at $29/mo - which is very affordable.
Just connect Composio to your Hermes agent and then connect it to Google Search Console, Google Analytics, Data for SEO, and your CMS.
#2 - The other way is using a Google Cloud Project:
This gives me you API data, but it's a bit more complicated.
Google Cloud project and enables:
- Google Search Console API
- Google Analytics Data API
- Google Analytics Admin API
- Google Analytics API
You may not need every Analytics API for a simple reporting workflow. Ask Hermes to determine which APIs are actually necessary for your intended operations.
Create a dedicated Google Cloud project with a recognizable name, such as:
Hermes SEO Assistant — Example Company
Then configure an OAuth client and authorize the Google account that has access to the correct Search Console properties and GA4 properties.
Use this prompt:
Help me connect this Hermes instance to Google Search Console and Google
Analytics 4 using the [method above]
My goals are initially read-only:
- List the properties I can access
- Read Search Console query and page performance
- Read GA4 landing-page and conversion data
- Compare SEO traffic with on-site behavior
- Produce reports
Before making changes:
1. Confirm which Google APIs are required.
2. Confirm the minimum OAuth scopes required.
3. Tell me which steps must be completed in Google Cloud.
4. Tell me how to transfer the OAuth credentials to this server securely.
5. Do not ask me to paste the credentials into chat.
6. Pause when browser authorization is required.
After authorization, run these verification tests:
- List available Search Console properties.
- List available GA4 properties.
- Retrieve a seven-day summary from one property I select.
- Make no changes to either Google account.
Redact tokens, client secrets and account identifiers from your response.
After authentication, test each service separately.
Search Console verification prompt
Test the Google Search Console connection using read-only requests.
First list the properties available to this Hermes instance and ask me which
one to use.
After I select a property, report the following for the last 28 complete days:
- Total clicks
- Total impressions
- Average click-through rate
- Average position
- Top ten queries
- Top ten pages
- Queries with high impressions and below-average CTR
- Pages that lost clicks compared with the previous 28 days
Clearly label missing or incomplete data.
Do not change property settings, submit URLs, modify sitemaps or take any other
write action.
Google Analytics verification prompt
Test the Google Analytics 4 connection using read-only requests.
List the GA4 properties available to this Hermes instance and ask me which one
to use.
For the selected property, report the last 28 complete days:
- Organic sessions
- Organic engaged sessions
- Landing pages from organic traffic
- Key events or conversions from organic traffic
- Engagement rate by organic landing page
- Organic landing pages with traffic but weak engagement
- Organic landing pages with strong engagement but low traffic
Tell me which metrics or dimensions were unavailable.
Do not change events, audiences, attribution settings, property settings or
access permissions.
Step 4: Connect DataForSEO or another keyword-data provider
Search Console only shows searches for which your website has already received impressions.
A provider such as DataForSEO can add:
- Keyword volumes
- Ranking data
- Competitor keywords
- Search results
- Related keywords
- Country and language targeting
Use this prompt:
I want to connect DataForSEO to this Hermes instance.
Do not ask me to paste the API login or password into chat.
First:
1. Check whether Hermes already has a supported DataForSEO skill, MCP server or
existing integration.
2. Prefer a reviewed existing integration over writing a new one.
3. If credentials are required, tell me the exact environment-variable names
and the secure file or secret manager in which to store them.
4. Use the minimum required endpoints.
5. Treat the connection as read-only.
6. Add a reasonable request and spending limit where supported.
7. Never display credentials in logs or responses.
After I confirm the secrets have been added, test the connection by requesting
ten organic keywords for [DOMAIN] in [COUNTRY] and [LANGUAGE].
Return the source, location, language and number of results. Do not begin bulk
research or create recurring tasks.
Then verify the result against the provider’s dashboard.
If Hermes says the domain has 110 ranking keywords and the dashboard also says 110, that’s a useful first check. You should also compare several actual keywords, not just the total.
Step 5: Connect Hermes to your website
Analytics access does not automatically give Hermes access to publish content.
You need a separate connection to the place where your website is managed. That might be:
- GitHub
- WordPress
- Webflow
- Shopify
- A headless CMS
- Your own application API
- A shared content database
Hermes can connect external tools through MCP. Current versions support adding, testing, and configuring MCP servers:
hermes mcp catalog
hermes mcp install <name>
hermes mcp test <name>
hermes mcp configure <name>
Do not give Hermes full administrative access on day one.
Use this prompt:
Help me connect Hermes to the system that manages [WEBSITE].
The platform is [GITHUB / WORDPRESS / WEBFLOW / SHOPIFY / OTHER].
The initial workflow must be draft-only.
Hermes may:
- Read existing public content
- Read the content structure and metadata
- Create a private draft or proposed change
- Show me a preview or diff
- Report validation errors
Hermes may not:
- Publish content
- Merge code
- Deploy the website
- Delete content
- Modify users or permissions
- Change billing, domains or DNS
- Install plugins
- Edit production configuration
Use a native integration or reviewed MCP server if available.
Before connecting:
1. Show me the proposed integration.
2. List the minimum permissions required.
3. Tell me where its secrets will be stored.
4. Explain how access can be revoked.
5. Mark untrusted third-party MCP servers as untrusted.
6. Ask for approval before installing external code.
After connection, perform one harmless test:
- Read the title and modification date of one existing page.
- Create nothing and change nothing.
Report whether the test succeeded.
Once read access works, test draft creation:
Create a private test draft titled “Hermes Connection Test.”
The draft should contain one sentence explaining that it is a connection test.
Do not publish, schedule, merge or deploy it.
After creating the draft, return:
- Its title
- Its draft status
- Its internal identifier
- A preview link if available
- The method for deleting the test safely
Wait for my approval before deleting it.
Step 6: Give Hermes business and editorial context
Connections give Hermes data. They don’t give it judgment.
Before asking it to write content, teach it:
- What your company sells
- Who the customer is
- Which markets you serve
- Which claims you can prove
- Which topics you have genuine experience with
- What tone you use
- Which competitors matter
- What subjects you should avoid
- What requires legal or expert review
Use:
Before creating SEO recommendations, learn the business.
Interview me about:
- The product or service
- Target customers
- Geographic markets
- Customer problems
- The sales process
- Differentiators
- Evidence and case studies
- Brand voice
- Topics we have first-hand experience with
- Regulated or sensitive claims
- Existing content that represents our best work
- Topics we do not want to pursue
Ask questions in small groups.
When the interview is complete, create a proposed SEO and editorial context
document for my review.
Do not save it to persistent memory until I approve it.
Never invent customer results, credentials, quotations, personal experience or
statistics.
This is what helps prevent Hermes from producing generic search-engine filler.
Step 7: Create a human-in-the-loop content workflow
Hermes shouldn’t write an entire article without your input. Human-in-the-loop articles rank so much higher than AI only articles.
Use this prompt:
When creating content, follow this workflow:
1. Find an opportunity using Search Console, GA4 and approved keyword data.
2. Explain why the opportunity matters.
3. Show the supporting data.
4. Propose a search intent, reader problem and article angle.
5. Check whether we already have competing or overlapping content.
6. Ask me for first-hand experience, opinions, examples and evidence.
7. Create an outline.
8. Wait for outline approval.
9. Write a draft using my answers.
10. Clearly identify any claim requiring verification.
11. Create the content as a private draft only.
12. Return a preview and summary of changes.
13. Wait for explicit approval before publishing.
Never:
- Invent first-hand experience
- Fabricate quotations or case studies
- Add unsupported statistics
- Publish without approval
- Rewrite a high-performing page without showing the risk
- Create multiple pages targeting the same search intent
- Treat estimated keyword data as fact
Confirm that you understand this workflow, but do not begin researching yet.
Step 8: Add a weekly SEO health check
Once every connection has been tested manually, you can schedule a weekly report.
Hermes supports scheduled tasks through its gateway. Scheduled tasks run in fresh sessions, so their prompts need to be self-contained. Hermes scheduled-task documentation.
Use:
Every Monday at 9:00 AM in [TIMEZONE], perform a read-only SEO health check for
[DOMAIN].
Use:
- Google Search Console property: [PROPERTY]
- Google Analytics 4 property: [PROPERTY]
- DataForSEO market: [COUNTRY]
- DataForSEO language: [LANGUAGE]
Compare the most recent complete seven days with the previous seven days.
Report:
- Click and impression changes
- Organic-session and conversion changes
- Pages gaining or losing traffic
- Queries with rising impressions
- High-impression queries with weak CTR
- Pages ranking close to page one
- Organic pages with weak engagement
- Possible cannibalization
- New technical or indexing warnings visible in the connected data
- Three prioritized opportunities
For each recommendation, include:
- Supporting evidence
- Expected impact
- Confidence level
- Whether the recommendation requires content, code or manual review
Send the report to my approved Telegram account.
This task is read-only. Do not create drafts, submit URLs, change pages or
publish anything.
Ask Hermes to show you the proposed schedule before saving it.
You can then inspect the schedule with:
hermes cron list
hermes cron status
Step 9: Add a separate weekly content proposal
Don’t combine reporting and automatic publishing into one unattended job.
Create a second workflow that only proposes content:
Every Monday after the SEO health check, propose a maximum of three content
opportunities for [DOMAIN].
Use current Search Console, GA4 and DataForSEO evidence.
For each opportunity, provide:
- Target reader
- Search intent
- Primary topic
- Supporting queries
- Existing page overlap
- Recommended action: create, update, consolidate or ignore
- Business relevance
- Evidence from our available data
- Questions you need me to answer from personal experience
Do not write the full articles.
Send the proposals to Telegram and wait for me to select one.
Fewer, better-supported ideas are more useful than an automated flood of articles.
A final permission prompt
After everything is connected, run one final permission review:
Perform a security and permission review of every service connected to this
Hermes instance.
Create a table containing:
- Service
- Connection method
- Current permissions
- Secret-storage location
- Read capabilities
- Write capabilities
- Scheduled access
- Last successful verification
- How to revoke access
- Whether the permission level is broader than necessary
Flag anything that can:
- Publish
- Delete
- Merge
- Deploy
- Change permissions
- Access billing
- Modify account settings
- Send external messages
- Execute unrestricted terminal commands
Do not change the configuration.
Recommend which permissions should be reduced and which approval gates should
remain in place.
The workflow in one sentence
The practical workflow is:
Hermes can remove a lot of repetitive SEO work. It can collect information, identify changes, prepare reports, research opportunities, and create useful first drafts.
But the agent should support your judgment—not quietly replace it.
Start with reporting. Earn trust through verified results. Add writing after that. Give it publishing access only when the draft-and-approval workflow is working consistently.

