StoreSEO

Language

  • English
  • 日本語 Not available
  • Polski Not available
  • Italiano Not available
Claude Code Blog post drafts

Write SEO blog post drafts with Claude Code

Writing blog post drafts with Claude Code means briefing Anthropic's terminal agent from the folder you already work in, and letting StoreSEO write the post into a draft article in your Shopify blog while you keep coding.

Last updated: October 2026

01

Set up Claude Code for StoreSEO

Skip this if Claude Code is already connected. The full guide, with the alternatives, is on the Claude Code page.

  1. 1

    Add StoreSEO to Claude Code

    Run this in any terminal. The user scope makes StoreSEO available in every project on your machine.

    Terminal
    claude mcp add --transport http --scope user storeseo https://mcp.storeseo.com/mcp
  2. 2

    Sign in to your store

    Start Claude Code, run /mcp, choose storeseo and follow the browser window: pick your Shopify store and approve access.

    Prompt
    /mcp
02

How does this work in Claude Code?

You type the brief at the Claude Code prompt, for example a 1,500 word post on choosing a ring size for the Guides blog, targeting the keyword ring size guide. Claude Code calls storeseo_start, then storeseo_list_blogs to resolve the blog id, and you see each call scroll past in the terminal. Because Claude Code sits in your project folder, it can also read a content plan, a CSV of keywords or a brief written in Markdown there and turn each line into a request.

The generate call is the one to pay attention to. StoreSEO tells Claude Code to state the credit cost and wait for your yes before storeseo_generate_blog_post, and Claude Code adds its own permission prompt for the tool unless you allowed it. Generation runs in the background for a few minutes. Claude Code polls storeseo_get_blog_post_job, reports steps completed out of total, and can carry on with other work in the same session between polls. When the job completes, ask it to read the draft with storeseo_get_resource_seo and write the SEO findings, or the article id, into a file in the repository.

The post itself lands as a draft article in Shopify, never published live, so the last step is yours in Shopify admin. If you write several posts, do them one after another and agree the cost each time, so you can see the credit being spent before the next one starts.

Claude Code + StoreSEO Illustrative session
  1. You: Draft a 1,500 word post on choosing a ring size for my Guides blog, no featured image.

  2. storeseo_start read-only
  3. storeseo_list_blogs read-only
  4. Claude Code: Guides is synced. The post will spend AI credit in proportion to its length. Should I start generation now?

  5. You: Yes, start it.

  6. storeseo_generate_blog_post needs approval
  7. storeseo_get_blog_post_job read-only
  8. Claude Code: Generation is running, 1 of 5 steps done. I will poll the job and tell you once the draft article exists in Shopify.

03

What to ask Claude Code

Prompt 1
Use StoreSEO to list my blogs, then read content-plan.md in this folder and tell me which row to write first.
Prompt 2
Write a 1,500 word draft for the Guides blog targeting ring size guide, no featured image. Tell me the credit cost and wait for my yes.
Prompt 3
Check the blog post job you started, and when it completes read the draft's SEO record and save the article id to notes.md.
  • List my blogs and write a 1,200 word draft on how to care for linen shirts in the News blog. Tell me the cost first.
  • Write a draft post targeting best gifts for coffee lovers, with a featured image.
  • How far along is the blog post you started?
  • Check the SEO score of the draft you just wrote.
  • Draft three post ideas for my store and write the strongest one.
04

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. 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. 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. 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. 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.

storeseo_list_blogsstoreseo_generate_blog_poststoreseo_get_blog_post_jobstoreseo_get_resource_seo
05

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
06

Rules Claude Code 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 Claude Code

A permission rule that allows the StoreSEO tools to stop the prompts also covers storeseo_generate_blog_post, which spends credit, so scope an allow rule to the read tools and keep the generate tool on ask. Claude Code has a default tool timeout, but StoreSEO returns a job id straight away and the writing happens in the background, so the long wait is in polling, not in one blocked call. Keep polls modest in a long session instead of looping on the job as fast as possible.

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.

07

Questions

Can Claude Code write several blog posts from a content plan file?

Yes, one at a time. Claude Code can read the plan in your folder and start a post per row, but each generation spends AI credit, so agree the cost for each post before it starts.

Where does the finished post end up?

As a draft article in the Shopify blog you picked. Claude Code can read its SEO record, but you review and publish it from Shopify admin.

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.

08

Keep going

Blog post drafts with other agents

More Claude Code guides