Optimize meta tags and content with Paperclip
Optimizing meta tags from Paperclip means giving an agent a ticket to have StoreSEO draft new meta titles, descriptions, handles, FAQs and AI snippets, then reviewing the previews on the task before anyone approves an apply.
Last updated: October 2026
Set up Paperclip for StoreSEO
Skip this if Paperclip is already connected. The full guide, with the alternatives, is on the Paperclip page.
- 1
Add StoreSEO to the agent Paperclip runs
Run this on the machine that hosts the agent, as the same OS user the Paperclip heartbeat runs as, from the agent's working directory. It is the claude_local adapter path, and user scope makes StoreSEO available to every Claude Code agent that user runs.
terminalclaude mcp add --transport http --scope user storeseo https://mcp.storeseo.com/mcp
- 2
Sign in once, then let Paperclip run headless
Start claude interactively as that same user, run /mcp, choose storeseo and finish the browser sign-in: pick your Shopify store and approve. Claude Code keeps the credentials, so later Paperclip runs need no browser. Check with claude mcp get storeseo.
new message to Paperclip/mcp
Step-by-step guide in the docs: How to connect StoreSEO MCP to Paperclip
How does this work in Paperclip?
The unit of work is a Paperclip task, not a chat message. You write the ticket, for instance preview better meta for the five lowest-scoring products and show me the old and new text, and assign it to an agent whose runtime has StoreSEO connected. The agent calls storeseo_get_resource_seo so it knows which fields fail, then storeseo_preview_resource_optimization for each product. StoreSEO writes the meta title, description, tags, URL handle, FAQs and AI snippet on its own servers and projects the new score; the agent only relays it. Those previews spend AI Content Optimizer credit even if you never apply them, so the ticket should name how many products you are willing to preview.
The review happens in Paperclip's comment thread. The agent posts each draft next to the current text, flags any URL handle change with the old and new address, and stops with a question. Applying is a different kind of step: storeseo_apply_resource_optimization changes the live product and, for a handle, creates a redirect. Run that step in a session you are watching, or reply on the ticket with exactly which products and which parts to apply, for example the meta but not the FAQ, and let the agent make the call.
Splitting the work this way fits how Paperclip is built. A cheaper, scheduled run can do the reading and drafting, and a supervised run does the writing, so the unattended part never holds the permission to change your store.
-
You: Ticket: preview better meta for Linen Shirt and show me old versus new.
- storeseo_get_resource_seo read-only
- storeseo_preview_resource_optimization preview
-
Paperclip: Preview posted on the ticket: new meta title and description, plus FAQs and a snippet, projected 38 to 76. It used AI credit and nothing is saved yet. Apply the meta and keep the current URL handle?
-
You: Yes, meta only. Skip the FAQs and the handle.
- storeseo_apply_resource_optimization needs approval
-
Paperclip: Applied the meta only and commented the recomputed score. The FAQs stay available from the same draft for an hour.
What to ask Paperclip
Tap a prompt to copy it, then paste it into Paperclip.
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 Paperclip 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 Paperclip
A reply on a Paperclip ticket is not a permission prompt. Under the Claude Code adapter's default of dangerouslySkipPermissions, an agent that decides to apply a preview will do so without stopping, and the Paperclip connector review queue does not sit in front of a server added with claude mcp add. If you want a real hard stop before storeseo_apply_resource_optimization, set that flag to false so the tool does not run, or attach StoreSEO as a connector and leave the apply action on Ask first.
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 a scheduled Paperclip run apply meta changes by itself?
It can if the agent is allowed to, but it should not. A routine has nobody to say yes, so keep it to reading and previewing, and run the apply in a task you start and watch. Previews still spend credit, so cap how many products the routine drafts.
How do I approve only part of a preview from Paperclip?
Say which parts in your reply, for example the meta title and description but not the FAQ or the handle. The agent passes that subset to the apply step, and skipped fields stay on the same draft for one hour.
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 Paperclip guides