Meta tags and on-page content Optimize meta tags and content with Claude Cowork
Optimizing meta tags and on-page content with Claude Cowork means delegating the task in plain words, letting it run StoreSEO previews through your connector, and reviewing a finished set of drafts before anything is applied to your store.
Last updated: October 2026
Set up Claude Cowork for StoreSEO
Skip this if Claude Cowork is already connected. The full guide, with the alternatives, is on the Claude Cowork page.
- 1
Add StoreSEO as a custom connector
In Cowork, open Customize, then Connectors, choose + Add and then Add custom connector. If you already added StoreSEO to your Claude account, look for it in that list first. Use this URL.
URLhttps://mcp.storeseo.com/mcp
- 2
Approve your store and check it
Sign in when the browser opens: pick your Shopify store and approve access. Then start a task and ask this first, so you know the connector works before you delegate real work.
PromptUse StoreSEO to show me my store's SEO score breakdown.
How does this work in Claude Cowork?
In Cowork you describe the outcome rather than steer each step: improve the meta on my ten lowest-scoring products and give me the drafts to review. Cowork uses the StoreSEO custom connector you added under Customize, then Connectors. It calls storeseo_start, reads each resource with storeseo_get_resource_seo, and runs storeseo_preview_resource_optimization for the products in scope. StoreSEO writes the meta title, description, tags, FAQs, AI snippet and any handle change on its servers, and the preview projects each new score without saving anything.
Delegation changes how you spend credit, so say how many previews you will allow in the task itself. Each preview spends AI Content Optimizer credit whether or not you apply it, and a ten product task is ten previews. A good task statement caps the count, asks Cowork to stop after the drafts and to produce one review document: product, current score, projected score, the new meta, and the old and new URL for any handle change. You read that, reply with which products to apply and which fields to skip, and only then does Cowork call storeseo_apply_resource_optimization, which is free and returns the recomputed score.
Keep the approval conversation inside the task while you are present. Cowork can ask you a question and wait, which is what the preview-then-apply flow needs. Drafts last an hour, so if the review takes longer than that, expect Cowork to have to preview again, which spends credit a second time.
-
You: Use StoreSEO to preview new meta for my two lowest-scoring products. Two previews is fine, apply nothing yet.
- storeseo_start read-only
- storeseo_get_resource_seo read-only
- storeseo_preview_resource_optimization preview
-
Claude Cowork: Draft one lifts a ribbed tank top from 24 to 69, with a new handle that redirects the old URL. Draft two covers a canvas tote. The review sheet is ready. Apply either one?
-
You: Apply the tank top, but keep its current handle.
- storeseo_apply_resource_optimization needs approval
-
Claude Cowork: Applied the tank top meta and tags with the handle unchanged. The tote draft is still available for about an hour.
What to ask Claude Cowork
Use StoreSEO to preview new meta for my five lowest-scoring products. Preview no more than five, apply nothing, and give me one review sheet with the old and new URL for any handle change.
From the previews you just made, apply the meta titles and descriptions for products 1, 3 and 4 only, skip the FAQs and the handles, and report the new scores.
Draft a plan for which collections to optimize first, using StoreSEO scores, and do not run any previews until I pick.
- 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 Claude Cowork 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 Claude Cowork
Do not schedule this job as a recurring Cowork task. Scheduled tasks run on their cadence without you in the conversation, so nobody is there to say yes, and a scheduled preview would spend AI Content Optimizer credit every run while a scheduled apply would have no review at all. Schedule reads and reports instead, and keep meta optimization as a task you start and watch. The same applies to turning on automatic optimization with storeseo_update_ai_optimization_settings: do that only in a live task, after Cowork states what it will spend.
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 schedule Claude Cowork to optimize my meta every week?
It is not a good fit. A scheduled task runs without you, so there is no one to approve the apply, and each run would spend AI Content Optimizer credit on previews. Use a scheduled task to read scores and report, and run the optimization yourself when you are present.
How do I stop a Cowork task from spending too much credit?
State the maximum number of previews in the task and ask Cowork to stop after the drafts. Each preview spends credit whether or not you apply it, so a cap in the instructions is the simplest control.
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 Claude Cowork guides