Meta tags and on-page content Optimize meta tags and content with Claude Code
Optimizing meta tags and on-page content with Claude Code means working from your terminal or editor, asking it to have StoreSEO preview generated meta for the products you pick, reading the draft in the session, and applying only the pieces you approve.
Last updated: October 2026
Set up Claude Code for StoreSEO
Skip this if Claude Code is already connected. The full guide, with the alternatives, is on the Claude Code page.
- 1
Add StoreSEO to Claude Code
Run this in any terminal. The user scope makes StoreSEO available in every project on your machine.
Terminalclaude mcp add --transport http --scope user storeseo https://mcp.storeseo.com/mcp
- 2
Sign in to your store
Start Claude Code, run /mcp, choose storeseo and follow the browser window: pick your Shopify store and approve access.
Prompt/mcp
How does this work in Claude Code?
You are in the terminal, often inside the Shopify theme repository, with the storeseo server added at user scope. You type a request such as optimize the meta for the three lowest-scoring products and show me the previews first. Claude Code calls storeseo_start, then storeseo_get_resource_seo for each product, and then storeseo_preview_resource_optimization one product at a time. Each call is printed in the session as it runs, so you see the tool name and, if you have not allowed it, a permission prompt before it executes.
StoreSEO generates the meta title, description, tags, handle, FAQs and AI snippet on its own servers, so Claude Code does not author any of it. What it adds is the working context around the draft. Because it can read the theme, it can check whether the product template already renders FAQs or whether a Liquid snippet hard-codes a title tag that would override the meta you are about to apply, and tell you before you spend the credit. When a handle would change it prints the old and new URL, and since you are in a repository you can ask it to grep the theme and content for hard-coded links to the old path.
After your yes it calls storeseo_apply_resource_optimization with the parts you chose, and the response gives the recomputed score. For a batch you can have Claude Code write a short table to a file in the working folder: product, score before, projected score, what you applied, what you skipped. Remember that every preview spends AI Content Optimizer credit even if you never apply it, so ask it to state the number of previews it is about to run before it starts the loop.
-
You: Preview better meta for the product with handle trail-socks. I accept the credit for the preview.
- storeseo_start read-only
- storeseo_get_resource_seo read-only
- storeseo_preview_resource_optimization preview
-
Claude Code: The draft lifts the score from 29 to 66. The handle would change from /trail-socks to /merino-trail-socks, and grep finds no hard-coded links to the old path in this theme. Apply everything?
-
You: Yes, apply everything.
- storeseo_apply_resource_optimization needs approval
-
Claude Code: Applied. The score is now 63, and the redirect from the old URL was created. I added the result to meta-changes.md.
What to ask Claude Code
Use StoreSEO to preview optimized meta for the three lowest-scoring products, one at a time. Tell me how many previews that is before you start and wait for my yes between products.
Preview meta, FAQs and an AI snippet for the product with handle merino-beanie. If the URL handle changes, grep this theme for links to the old path before I decide.
Apply the meta title and description from the last preview, skip the handle, and write a before and after score table to meta-changes.md.
- 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 Code 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 Code
Claude Code runs a tool without asking only if you have allowed it, and the allow rule matches by tool name, so allowing the preview and apply tools to cut down on prompts removes the editor-side stop for writes. Keep storeseo_apply_resource_optimization and storeseo_update_ai_optimization_settings on ask, because the confirmation StoreSEO asks for in the chat is an instruction to the agent, not a lock on the server. If you run a loop over many products, the previews can also pile up credit quickly, so cap the batch in the prompt.
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 Claude Code optimize meta for many products in one run?
It can run previews one product after another, but each preview spends AI Content Optimizer credit and each draft expires after an hour. Ask for a small batch, review each draft, and apply before moving on rather than previewing the whole catalog first.
Does Claude Code edit my theme files when it applies meta?
No. The apply tool writes the SEO fields to your Shopify store through StoreSEO. Claude Code only edits theme files if you separately ask it to, for example to remove a hard-coded title tag.
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 Code guides