Write SEO blog post drafts with Manus
Writing Shopify blog drafts with Manus means asking a task agent to have StoreSEO write a full SEO post into one of your synced blogs as a draft, then checking the finished article's score while you review and publish it yourself.
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 request carries the brief: use StoreSEO to write a 1,200 word draft on how to care for linen shirts in my News blog, with a featured image. Manus calls storeseo_start and then storeseo_list_blogs, which returns your synced blogs with their numeric ids. An empty list means your blogs have not been synced in the StoreSEO app yet, and no tool can do that. StoreSEO writes the post itself on its own servers, so the prose comes from StoreSEO, not from Manus, and Manus is the one who carries the brief, the cost and the waiting.
Generation spends AI Content Optimizer credit, and the cost grows with the word count and a featured image. Manus should say that and wait for your yes before it calls storeseo_generate_blog_post, which fails before anything is queued if your credit is short. The post then writes in the background for a few minutes. This is the part Manus handles well: it keeps polling storeseo_get_blog_post_job with the job id, reports how many steps are done, and does not call the draft finished while the job runs, until the status is completed, failed or cancelled.
When the job completes, the task can read the draft with storeseo_get_resource_seo using resource type article and the article id from the job result, and report its SEO score. Nothing is published. The article sits as a draft in Shopify admin, where you read it, fix what you want and publish it. If the job fails, the error message explains why and credits are settled automatically.
-
You: Use StoreSEO to write a draft post on linen shirt care for my News blog.
- storeseo_start read-only
- storeseo_list_blogs read-only
-
Manus: The News blog is synced. A post spends AI Content Optimizer credit, and a featured image adds to it. It saves as a draft only. Should I write it at 1,200 words with an image?
-
You: Yes, with the image.
- storeseo_generate_blog_post needs approval
- storeseo_get_blog_post_job read-only
-
Manus: Illustrative progress: the job is at step 3 of 6 and still running, so the draft is not ready to read yet.
What to ask Manus
Tap a prompt to copy it, then paste it into Manus.
What StoreSEO does: blog post drafts
StoreSEO writes a full blog post with AI and saves it as a draft article in the Shopify blog you choose, optionally with a featured image. Nothing is published: you review and publish from Shopify admin.
Requires: Spends AI Content Optimizer credit; the cost grows with word count and a featured image. Blogs must be synced in the StoreSEO app.
- 1
Pick the blog
The agent lists your synced blogs, the sections posts go into, with their ids. An empty list means the blogs need syncing in the StoreSEO app first.
- 2
Agree the brief and cost
Topic, keyword, length and whether to add a featured image. The cost grows with length and the image, so the agent tells you and waits for your yes.
- 3
Generate in the background
Writing takes a few minutes. The agent polls the job and reports progress, and does not present the post as finished while it runs.
- 4
Check the draft
When the job completes, the agent can read the draft article's SEO record. You review and publish the post from Shopify admin.
Blog post drafts reference
| Output | A draft article in the chosen Shopify blog, never published live |
|---|---|
| Featured image | Optional; uploaded with the draft and adds to the cost |
| Run time | A few minutes in the background |
| Insufficient credit | The call fails before anything is queued or spent |
| Blogs | Only blogs synced with StoreSEO are listed; syncing is done in the app |
| Failed runs | The job reports the error and credits are settled automatically |
Rules Manus follows
- The agent states the expected credit use and waits for your yes before it starts a post.
- Posts are saved as drafts only; publishing is done by you in Shopify admin.
- While the job runs, the agent reports progress and never presents the draft as finished.
In Manus
Manus can make a recurring task out of anything, but a weekly write a post task would spend credit every run with nobody to agree to the cost, and it would pile up drafts you never asked for. Keep blog generation in a task you start, and keep any scheduled task to listing drafts or reporting. Leave the skip confirmations setting off. It lets a scheduled task publish or send without asking, which is the wrong default for anything that spends credit. Whatever Manus produces, you still review and publish from Shopify admin.
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
Will Manus publish the blog post to my store?
No. StoreSEO saves the generated post as a draft in the Shopify blog you choose. You review and publish it from Shopify admin.
Can I schedule Manus to write a blog post every week?
You can schedule a task, but you should not let it generate. Each post spends credit and a scheduled run cannot wait for your yes. Schedule a report of your drafts and start the writing yourself.
Will the agent publish a blog post on my store?
No. StoreSEO saves generated posts as drafts in the Shopify blog you choose. You review and publish them from Shopify admin.
How long does a blog post take?
A few minutes. The writing runs in the background and the agent checks the job until it is completed, failed or cancelled.
What does a blog post cost?
It spends AI Content Optimizer credit, and the amount grows with the word count and with a featured image. If you do not have enough credit the call fails before anything is spent.
Why does the agent say I have no blogs?
Only blogs synced with StoreSEO are listed. Sync your blogs in the StoreSEO app, then ask again.
Keep going
Blog post drafts with other agents
More Manus guides