Optimize meta tags and content with Hermes Agent
Optimizing meta tags and on-page content with Hermes Agent means telling it in a terminal or chat app to have StoreSEO generate meta, tags, a URL handle, FAQs and an AI snippet for a Shopify resource, then applying the draft after you reply with a yes.
Last updated: October 2026
Set up Hermes Agent for StoreSEO
Skip this if Hermes Agent is already connected. The full guide, with the alternatives, is on the Hermes Agent page.
- 1
Add StoreSEO to config.yaml
Add this under mcp_servers in ~/.hermes/config.yaml. If the file already has an mcp_servers block, add only the storeseo entry. Then start a new Hermes session, or run /reload-mcp in the one that is open.
YAMLmcp_servers: storeseo: url: "https://mcp.storeseo.com/mcp" auth: oauth - 2
Sign in to your store
On first connect Hermes prints an authorize URL and waits for the sign-in. Run this command to start it yourself or to re-authorize later. Pick your Shopify store and approve. Hermes caches the tokens in ~/.hermes/mcp-tokens/storeseo.json.
Terminalhermes mcp login storeseo
How does this work in Hermes Agent?
Hermes Agent keeps memory across sessions and answers in whatever place you reached it, a terminal or a Telegram, Discord or Slack chat. With the storeseo entry in ~/.hermes/config.yaml and the sign-in cached, you write something like preview new meta for the collection Summer Dresses and keep its URL handle. Hermes calls storeseo_start, then storeseo_get_resource_seo for the collection, then storeseo_preview_resource_optimization. StoreSEO generates the text server-side and projects the score without saving, and the preview spends AI Content Optimizer credit whether or not you apply it.
The draft appears in the conversation with the projected score. Reply in the same place: apply the meta and skip the FAQ. Hermes passes only those axes to storeseo_apply_resource_optimization and the skipped parts stay available from the draft for an hour. Because Hermes remembers earlier sessions, it can recall which products you already optimized and which you skipped, but treat that memory as a convenience rather than a record: storeseo_get_resource_seo shows what is actually saved in the store, including whether FAQs or an AI snippet already exist.
To keep the agent to reading and previewing while you experiment, narrow its tools with the include list on the storeseo server so the apply and settings tools are not exposed, then widen it when you are ready. Hermes can also run storeseo_get_ai_optimization_settings to tell you what StoreSEO already generates for new resources. If the shop's AI model matters to you, that read also lists the model in use.
-
You: Preview new meta for the Summer Dresses collection and keep the handle.
- storeseo_start read-only
- storeseo_get_resource_seo read-only
- storeseo_preview_resource_optimization preview
-
Hermes Agent: The draft has a new meta title and description, plus two FAQs and an AI snippet. The projected score moves from 42 to 81 and the handle is unchanged. Apply the meta and the FAQs?
-
You: Apply the meta only, skip the FAQs.
- storeseo_apply_resource_optimization needs approval
What to ask Hermes Agent
Preview StoreSEO meta for my five lowest-scoring products, one at a time, and show each draft and score change. Do not apply anything.
Preview a new meta title and description for the Summer Dresses collection and keep the current URL handle.
Apply the meta from that preview and skip the FAQ, then tell me what still fails.
- Optimize the meta title and description for my five lowest-scoring products. Show me the previews before you apply anything.
- Preview a new meta title, description and FAQ for the collection Summer Dresses, and keep the current URL handle.
- Apply the meta from that preview but skip the FAQ.
- Which of my pages have no meta description? Draft one for each and wait for my approval.
- What does StoreSEO optimize automatically for new products right now?
- Turn on automatic meta and alt text for new products only. Tell me what that will spend first.
What StoreSEO does: meta tags and on-page content
StoreSEO generates the content server-side: meta title and description, tags, a keyword-led URL handle, FAQs and an AI snippet. The agent shows you the draft and the projected score change before anything is saved, then applies all of it or only the parts you approve.
Requires: Generating a preview spends AI Content Optimizer credit; applying a preview is free.
- 1
Read the current state
The agent reads the resource's SEO record so it knows which fields exist, which fail and what the preview will add.
- 2
Generate a preview
StoreSEO writes the meta title, description, tags, URL handle, FAQs and AI snippet and projects the new SEO score, plus the GEO score for products. Nothing is saved yet. Preview spends credit whether or not you apply it.
- 3
Show you the draft
The agent presents the generated text and the score change. When the handle changes it shows the old and new URL and tells you a redirect will be created.
- 4
Apply what you approve
After your yes it applies everything, or only the parts you chose, for example the meta but not the FAQs. Skipped fields stay available from the same draft for an hour.
- 5
Report the new score
The apply call returns the recomputed score and the remaining checklist, so the agent tells you what changed and offers the next most useful fix.
Meta tags and on-page content reference
| Generated fields | Meta title, meta description, tags, URL handle, FAQs, AI snippet |
|---|---|
| Resource types | Products, collections, pages and articles (collections have no meta tags or tags axis in auto settings) |
| Who writes the copy | StoreSEO, server-side. The agent never authors meta, FAQs or handles itself |
| Cost | Preview spends AI Content Optimizer credit; apply is free; a new preview spends again |
| Draft lifetime | One hour after the preview |
| URL handle | Applying a new handle changes the live URL and creates a redirect from the old one; a handle already in use is dropped automatically |
| Partial apply | Apply a subset of axes, or skip individual fields such as the handle |
| Auto optimization | Optional settings that generate content for newly synced resources; only future syncs, nothing is backfilled |
| Auto settings plan | Configurable on any plan; switching an auto toggle on needs a paid plan and no active trial |
Rules Hermes Agent follows
- The agent previews first and applies only after you confirm the previewed content.
- When a handle changes, you see the old URL and the new URL before the apply call, because applying creates a redirect.
- A request like optimize my worst five products authorizes the previews; the agent should remind you that previews spend credit even if you do not apply them.
- Turning on auto optimization spends credit on every future sync, so the agent proposes the exact sections and waits for your yes.
- Product title, focus keyword and description body are not written by this job; the description has its own tool in the AI search job.
In Hermes Agent
If you edit config.yaml to add or narrow the storeseo tools, start a new Hermes session or run /reload-mcp, otherwise the open session keeps the old tool list and may still expose, or still hide, the preview and apply tools. A hermes cron job has nobody to say yes, so give it reads only for this job: previews would spend credit unattended, and the apply is a write that needs your answer. Ask for those in a chat you can reply to.
What runs without asking. Reads such as SEO scores, store listings, settings and Google reports run straight away. Generating a preview spends AI credit but writes nothing, and StoreSEO tells the agent to say what a generation will cost before it runs one. Applying content, optimizing images, changing settings, publishing llms.txt or agents.md, writing a product description and deleting anything wait for your yes in the conversation. That yes is an instruction the agent follows, not a lock on the server, so your client's own tool-approval setting is the hard stop.
Questions
Can I restrict Hermes Agent to previews so it cannot apply anything?
Yes. Hermes lets you narrow a server's tools with include and exclude lists in config.yaml, so you can leave out storeseo_apply_resource_optimization. Previews still spend AI Content Optimizer credit, and you need to restore the tool before you can apply a draft.
Does Hermes remember which products it already optimized?
Hermes keeps memory across sessions, but the saved state in your store is the reliable record. Ask it to read the resource with StoreSEO before deciding, because storeseo_get_resource_seo shows the current fields, score and any FAQs already saved.
Does previewing an optimization change my product?
No. A preview generates the content and projects the score without saving anything. It does spend AI Content Optimizer credit, and applying the draft afterwards is free.
What happens to the old URL when the handle changes?
Applying a new URL handle updates the live URL and StoreSEO creates a redirect from the old one, so existing links keep working. The agent should show you both URLs before it applies the change.
Can I apply only part of a preview?
Yes. The apply step takes the axes you approved, and individual content fields such as the URL handle can be skipped. Skipped parts stay available from the same draft for one hour.
Does auto optimization fix my existing products?
No. Auto optimization only acts on resources synced or updated after you turn it on. Existing products are fixed with the preview and apply steps in this job.
Will StoreSEO change my product title?
No. This job writes the SEO meta title, not the storefront product title. The product title is edited in Shopify admin.
Keep going
Meta tags and on-page content with other agents
More Hermes Agent guides