Optimize meta tags and content with Muse
Optimizing meta tags with Muse means asking Meta's personal AI agent to have StoreSEO draft a meta title, description, tags and URL handle for one Shopify resource, reading the draft in your thread, and saying yes only to the parts you want applied.
Last updated: October 2026
Set up Muse for StoreSEO
Skip this if Muse is already connected. The full guide, with the alternatives, is on the Muse page.
- 1
Send this message to Muse
Paste it into a new chat with Muse in the app, on muse.ai or in WhatsApp. Muse is rolling out in the US first, so you need access to it before this works.
new message to MuseAdd a custom connector for my Shopify SEO app StoreSEO: https://mcp.storeseo.com/mcp - It is an MCP server over HTTP and it signs in with OAuth. Send me the sign-in link and I will approve it. - Once it is connected, show me my store's SEO score breakdown.
- 2
Approve the sign-in for your store
Open the sign-in link Muse sends back, pick your Shopify store in the browser and approve access. Meta does not review custom connectors, so only approve this one if you started it.
server URLhttps://mcp.storeseo.com/mcp
Step-by-step guide in the docs: How to connect StoreSEO MCP to Muse
How does this work in Muse?
Start with one resource and name it, for example write better meta for my best selling linen shirt, because every preview spends AI Content Optimizer credit. Muse calls storeseo_start, reads the current fields with storeseo_get_resource_seo and then calls storeseo_preview_resource_optimization. StoreSEO writes the copy on its own servers, so the words come from StoreSEO and not from Muse, and the response carries a draft id plus the projected score change. Muse pastes the old and new title and description into the thread, which on a phone means you read two short blocks and a score instead of opening the Shopify admin.
The apply is a separate step. storeseo_apply_resource_optimization is a write, and StoreSEO tells the agent to wait for your yes. In Muse there is a second layer: Meta says Muse asks for permission on important actions and that a Sentinel agent approves what leaves its machine, so you may be asked once by Muse in its own words and once by StoreSEO's flow. You can answer yes to the title and description and no to the handle. When a handle changes, the apply creates a redirect from the old address, so ask Muse to show old and new addresses side by side before you agree.
Previews are where the credit goes, and a thread makes it easy to lose count. A fair routine is to ask Muse for the three weakest products, preview them one at a time, and reply to each draft before the next arrives. If you dislike a draft, tell Muse what to change, but know that a new preview spends credit again. The product title and focus keyword are not written by this job, so a request to rewrite them gets a pointer to the StoreSEO app instead.
-
You: Use StoreSEO to improve the meta on my Linen Shirt product.
- storeseo_start read-only
- storeseo_get_resource_seo read-only
-
Muse: The meta description is empty. A preview uses AI Content Optimizer credit and saves nothing. Should I generate one?
-
You: Yes, go ahead.
- storeseo_preview_resource_optimization preview
-
Muse: Illustrative draft: a new title and description, with the score projected from 29 to 74. Apply the title and description only, and skip the handle?
-
You: Yes, apply those two.
- storeseo_apply_resource_optimization needs approval
What to ask Muse
Tap a prompt to copy it, then paste it into Muse.
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 Muse 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 Muse
Do not treat Muse's own permission prompt as the review of the content. Muse decides when to ask, and the question it puts to you may be about sending a call out of its machine rather than about what the draft says. Read the title and description in the thread first, then answer. Because a custom connector is not reviewed by Meta, the only brake you fully control is the wording of your request plus revoking the connection in StoreSEO under Settings, AI Toolkit.
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 Muse write the meta text itself?
No. StoreSEO generates the meta title, description, tags and handle on its own servers. Muse fetches the draft, shows it in the thread and passes along only the parts you approve.
What stops Muse from applying a draft I have not read?
StoreSEO tells the agent to wait for your yes, and Muse and its Sentinel agent ask permission on important actions. Those are instructions and client behavior, not a server lock, so tell Muse to preview and ask before it applies and read each question.
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 Muse guides