Write SEO blog post drafts with NanoClaw
Drafting blog posts with NanoClaw means messaging your self-hosted agent a topic, letting StoreSEO write a complete draft article in one of your Shopify blogs in the background, and getting a chat message when the draft is ready to review.
Last updated: October 2026
Set up NanoClaw for StoreSEO
Skip this if NanoClaw is already connected. The full guide, with the alternatives, is on the NanoClaw page.
- 1
Create a StoreSEO access token
In the StoreSEO app open Settings, AI Toolkit and generate a personal access token. Keep it out of chat messages and out of Git.
new message to NanoClawSettings → AI Toolkit → create a token
- 2
Add StoreSEO to your agent's container
Run this on the machine that hosts NanoClaw, using your agent group's ID from ncl groups list. The header goes in as a JSON object. NanoClaw may ask an admin to approve the change.
terminalncl groups config add-mcp-server --id <group-id> --name storeseo \ --url https://mcp.storeseo.com/mcp \ --headers '{"Authorization":"Bearer YOUR_TOKEN"}' - 3
Restart the agent's container
The new server takes effect after a restart. Then message your agent with its trigger word, @Andy by default, and ask for your store's SEO score.
terminalncl groups restart --id <group-id>
Step-by-step guide in the docs: How to connect StoreSEO MCP to NanoClaw
How does this work in NanoClaw?
A post takes StoreSEO a few minutes to write, which suits an agent that keeps running in its container after you put your phone down. In your chat app you message @Andy with a brief: the topic, the audience, a target word count and whether you want a featured image. The agent calls storeseo_start, then storeseo_list_blogs to find the numeric id of the blog, since only blogs synced in the StoreSEO app are listed. It tells you the credit cost, which grows with word count and a featured image, and waits for your reply before storeseo_generate_blog_post.
After the call the agent polls storeseo_get_blog_post_job until the status is completed, failed or cancelled, and reports progress as steps completed out of total. The draft article exists from the start of the run, so it should not call the post finished while the job is still going. When it completes, ask the agent to call storeseo_get_resource_seo with the article's Shopify id and send you the draft's score and failing checks in the same thread.
The result is a draft only. You review it and publish it in Shopify admin, a step the agent cannot take. Keep generation out of scheduled tasks, because each run spends credit and would produce drafts you never asked for. A better scheduled task is a monthly message suggesting three topics from your Search Console queries, worded as suggest only. Then you pick one in a chat and approve the cost there, where your yes is part of the thread.
-
You: @Andy use StoreSEO to write a post about caring for linen bedding.
- storeseo_start read-only
- storeseo_list_blogs read-only
-
NanoClaw: I found a blog called News. A post with a featured image spends AI Content Optimizer credit, more for a longer post, and it is saved as a draft only. Should I start it?
-
You: Yes, start it.
- storeseo_generate_blog_post needs approval
- storeseo_get_blog_post_job read-only
-
NanoClaw: Still running, step 3 of 6. I will check again and message you when the draft is ready to review.
What to ask NanoClaw
Tap a prompt to copy it, then paste it into NanoClaw.
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 NanoClaw 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 NanoClaw
Polling depends on your NanoClaw container staying up. If the host restarts or you run ncl groups restart while a post is generating, the StoreSEO job carries on, but the agent may lose track of the job id. Ask it to start from storeseo_list_resources for articles, or give it the job id from the thread, and treat the draft as unfinished until the job reports completed.
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 NanoClaw publish the blog post for me?
No. StoreSEO saves the post as a draft in your Shopify blog and does not publish it live. You review the draft and publish it from Shopify admin.
What if I stop chatting while the post is generating?
The job runs in the background on StoreSEO's side, and your agent keeps running in its container, so it can keep polling. When you return, ask for the job status and wait for completed before judging the draft.
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 NanoClaw guides