Optimize meta tags and content with Manus
Optimizing Shopify meta tags with Manus means asking a task agent to have StoreSEO generate a meta title, description, tags, URL handle, FAQs and AI snippet for several resources, then bringing the whole batch back so you decide what gets applied.
Last updated: October 2026
Set up Manus for StoreSEO
Skip this if Manus is already connected. The full guide, with the alternatives, is on the Manus page.
- 1
Create an access token in StoreSEO
In the StoreSEO app, open Settings, then AI Toolkit, and generate a named personal access token. Copy it now and keep it out of any chat.
new message to ManusStoreSEO → Settings → AI Toolkit → generate a token
- 2
Add StoreSEO as a custom MCP server
In Manus, open Settings, then Integrations, then Custom MCP Servers, and choose Add Server. Give it a name, paste this URL as the server URL and enter your token as the authentication, as a Bearer token.
server URLhttps://mcp.storeseo.com/mcp
- 3
Check it and use it
Manus verifies it can reach the server and read its tools. Then start a task that names StoreSEO, so Manus uses the connector.
new message to ManusUse StoreSEO to show me my store's SEO score breakdown.
Step-by-step guide in the docs: How to connect StoreSEO MCP to Manus
How does this work in Manus?
The starting point is a task that names StoreSEO and the size of the job, for example use StoreSEO to preview new meta for my five lowest-scoring products. Manus calls storeseo_start, lists resources by score with storeseo_list_resources, reads each candidate with storeseo_get_resource_seo and then calls storeseo_preview_resource_optimization once per product. StoreSEO writes the copy on its own servers, so the wording comes from StoreSEO, not from Manus, and each response carries a draft id and the projected score change. Nothing is saved at this point, but every preview spends AI Content Optimizer credit, and the task should tell you that before it starts.
Manus is at its best when it can return one consolidated answer. Instead of you opening five products, you get a single summary with the old and new title, description and handle for each, ranked by projected score gain. When a handle changes it should show the old and new URL, because applying that part creates a redirect. You answer in the same task with a decision such as apply all five, apply everything except the handles, or apply only the two biggest jumps.
Only then does Manus call storeseo_apply_resource_optimization, passing the products and the fields you approved. Drafts expire after an hour, so answer while the task is still open. The apply is free because the credit went at preview time. If you also want StoreSEO to optimize future products on its own, that is a separate settings change through storeseo_update_ai_optimization_settings, and it should be proposed with the exact sections and a credit warning before it runs.
-
You: Use StoreSEO to improve the meta on my five worst products.
- storeseo_start read-only
- storeseo_list_resources read-only
-
Manus: Each preview spends AI Content Optimizer credit and saves nothing, and five previews means five generations. Should I go ahead?
-
You: Yes, preview all five.
- storeseo_preview_resource_optimization preview
-
Manus: Illustrative result: all five have drafts, with the biggest projected jump from 29 to 74 on Linen Shirt. Two drafts change the URL handle and will create redirects. Apply all five but skip the two handle changes?
-
You: Yes, do that.
- storeseo_apply_resource_optimization needs approval
What to ask Manus
Tap a prompt to copy it, then paste it into Manus.
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 Manus 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 Manus
A general agent will happily keep going, so put a number in the task. A request like optimize my store could turn into dozens of previews, and each one spends credit whether or not you apply it. Previews and applies also do not belong in a scheduled Manus task: nobody is there to approve, and the skip confirmations setting that lets a scheduled task send or publish without asking should stay off. Schedule the audit that finds weak products, then run the previews in a normal task you are watching.
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 Manus write the meta text itself?
No. StoreSEO generates the meta title, description, tags, handle, FAQs and AI snippet on its own servers. Manus fetches the draft, shows it to you and passes along only the parts you approve.
How long do I have to approve a Manus meta preview?
A draft lasts one hour after the preview. If your task sits unanswered for longer, ask Manus to preview again, 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 Manus guides