Meta tags and on-page content Optimize meta tags and content with Claude
Optimizing meta tags and on-page content with Claude means asking the assistant in your chat tab to have StoreSEO draft a meta title, description, tags, URL handle, FAQs and AI snippet for a product, then reading the draft and the score change before you let it save anything.
Last updated: October 2026
Set up Claude for StoreSEO
Skip this if Claude is already connected. The full guide, with the alternatives, is on the Claude page.
- 1
Add StoreSEO as a custom connector
In Claude, open Customize, then Connectors, choose + Add and then Add custom connector. Name it StoreSEO and paste this URL as the remote MCP server URL.
URLhttps://mcp.storeseo.com/mcp
- 2
Approve your store
Claude opens the StoreSEO sign-in in your browser. Pick your Shopify store and approve access. Then start a new chat and ask this to confirm the connection works.
PromptUse StoreSEO to show me my store's SEO score breakdown.
How does this work in Claude?
You work in a Claude chat at claude.ai or in Claude Desktop, with the StoreSEO connector switched on for the conversation. You name a product or ask for the worst few, and Claude calls storeseo_start, then storeseo_get_resource_seo to read what the resource already has: its current meta, whether FAQs and an AI snippet exist, and which criteria fail. That read tells it what a preview would add, so the reply can say up front that the meta is too long and the FAQs are missing before any credit is spent.
Then comes storeseo_preview_resource_optimization. StoreSEO writes the copy on its own servers, so the text you read in the chat is StoreSEO's draft, not something Claude composed. Claude shows the new meta title and description, the tags, the FAQs and the AI snippet next to the projected score, and if the URL handle would change it lays out the old URL and the new one and tells you a redirect will be created. You answer in the same chat: apply all of it, apply the meta and skip the FAQs, or leave the handle alone. Claude then calls storeseo_apply_resource_optimization with only the parts you named, and the reply carries the recomputed score and what still needs a manual fix, such as the focus keyword.
Because the draft lives for an hour, a chat is a comfortable place to take your time. You can read the preview, ask Claude to compare it with the current copy, go and check the product page, and come back to say apply it. The preview itself spent AI Content Optimizer credit whether or not you apply, so batch requests like my five worst products mean five previews, and a good habit is to ask Claude for the credit cost of the whole batch before you say go. Applying is free.
-
You: Preview better meta for my Linen Throw Blanket. I know a preview spends credit, go ahead.
- storeseo_start read-only
- storeseo_get_resource_seo read-only
- storeseo_preview_resource_optimization preview
-
Claude: The draft raises the score from 41 to 78. New meta title and description, three tags, two FAQs, and the handle changes from /blanket-1 to /linen-throw-blanket with a redirect from the old URL. Apply all of it?
-
You: Yes, but skip the FAQs.
- storeseo_apply_resource_optimization needs approval
-
Claude: Applied the meta, tags and handle. The score is now 74. The FAQs stay in the draft for about an hour if you change your mind.
What to ask Claude
Use StoreSEO to preview a new meta title, description and FAQ for my Linen Throw Blanket product. Show me the draft and the score change before you apply anything.
Preview optimized meta for my three lowest-scoring products, one at a time. Tell me what the previews will spend first, then wait for my yes.
Apply the meta description and title from that preview, but skip the URL handle and the FAQs.
- 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 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
Claude shows its own permission prompt for each tool that writes, and the preview tool is not marked read-only, so expect a prompt for the preview as well as for the apply. Choosing Allow always on the preview is reasonable once you trust the credit cost, but keep the apply tool on ask, because Claude's prompt is the hard stop and StoreSEO's request for your yes is only an instruction the assistant follows. Also check that the StoreSEO connector is toggled on in the Search and Tools menu for the chat, or Claude will answer from general knowledge instead of reading your store.
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
Does Claude write the meta description itself?
No. Claude asks StoreSEO to generate the content on its servers and shows you the result. That keeps the copy tied to your store data and the SEO criteria, and it means the score change you see is projected by StoreSEO, not guessed by the assistant.
What if I close the Claude chat after seeing the preview?
The draft stays available for one hour. If you open a new chat in that time, ask Claude to apply the draft for that product. After an hour you need a new preview, which spends AI Content Optimizer 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 Claude guides