Optimize meta tags and content with OpenClaw
Optimizing meta tags and on-page content with OpenClaw means messaging your own agent runtime from a chat app so it has StoreSEO generate meta, tags, a URL handle, FAQs and an AI snippet for one Shopify resource, then applies the draft you approve in the thread.
Last updated: October 2026
Set up OpenClaw for StoreSEO
Skip this if OpenClaw is already connected. The full guide, with the alternatives, is on the OpenClaw page.
- 1
Add StoreSEO to OpenClaw
Run this on the installation that owns the connector. The --auth oauth flag marks the server as an OAuth server, which is what openclaw mcp login needs.
Terminalopenclaw mcp add storeseo \ --url https://mcp.storeseo.com/mcp \ --transport streamable-http \ --auth oauth
- 2
Sign in to your store
The login prints an authorization URL. Open it in a browser, pick your Shopify store and approve access. OpenClaw captures the redirect and saves the credentials.
Terminalopenclaw mcp login storeseo
- 3
Check the connection
The probe opens a live connection and reports the tools the server offers. A saved server entry proves nothing until the probe passes.
Terminalopenclaw mcp doctor storeseo --probe
How does this work in OpenClaw?
OpenClaw runs on your machine or server, and you talk to it from WhatsApp, Telegram, Slack, Discord or its Control UI. After openclaw mcp doctor shows the storeseo server healthy, you message it something like preview the meta for my three lowest-scoring products. The agent calls storeseo_start, reads each resource with storeseo_get_resource_seo, and calls storeseo_preview_resource_optimization once per resource. Each preview spends AI Content Optimizer credit, so when you ask for three, expect three previews to be charged whether or not you apply them, and say so in your message if you want the agent to repeat the cost back to you first.
The drafts come back as chat messages with the projected scores, which suits a phone: you read them on the move and reply apply the first two and skip the FAQ on the third. The agent then calls storeseo_apply_resource_optimization with the axes you chose and any skipped fields, and the draft stays usable for one hour, so a reply later in the afternoon can still apply the remainder. OpenClaw can also read what StoreSEO does automatically for new products through storeseo_get_ai_optimization_settings, which helps when you are deciding whether a one-off preview or an auto setting fits.
Writes are where OpenClaw differs from a desktop client. Its mcp configure command has a per-server approval setting with approve, prompt and auto modes, and that is the hard stop if you want the client to check before StoreSEO writes. The automations scheduler runs agents in an isolated session with nobody present to answer, so use it for reads such as listing the lowest scores each Monday, and ask for previews and applies in a message you can reply to.
-
You: Preview the meta for my lowest-scoring product and send me the draft.
- storeseo_start read-only
- storeseo_get_resource_seo read-only
- storeseo_preview_resource_optimization preview
-
OpenClaw: The draft for Linen Throw Blanket is ready: new meta title and description, three tags and two FAQs, with the score going from 31 to 78. The handle is unchanged. Shall I apply it?
-
You: Yes, apply it.
- storeseo_apply_resource_optimization needs approval
What to ask OpenClaw
Preview StoreSEO meta for my three lowest-scoring products and send me each draft with its score change. Do not apply anything yet.
Apply the first draft, skip the URL handle on the second, and leave the third alone.
Every Monday, report which products have no meta description. Read only, no previews and no applies.
- 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 OpenClaw 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 OpenClaw
A scheduled OpenClaw automation cannot wait for a yes, so keep any cron job for this job to reads and reports. Do not tell a scheduled run to preview or apply: previews spend credit unattended, and an apply has no one to approve it. Also check the per-server approval mode with openclaw mcp configure storeseo, because a mode that skips the check removes OpenClaw's own stop on storeseo_apply_resource_optimization, leaving only the confirmation StoreSEO asks the agent for in the chat.
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 an OpenClaw automation optimize my meta tags on a schedule?
It can read and report on a schedule, but it should not preview or apply. Nobody is present to say yes, and a preview spends AI Content Optimizer credit. Ask for previews in a chat message you can answer, and use automations for score reports.
How long can I wait before applying a preview from my phone?
A StoreSEO draft expires one hour after the preview. Within that hour you can apply part of it now and the rest in a follow-up message. After that the agent has to generate a new preview, which spends credit again.
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 OpenClaw guides