Meta tags and on-page content Optimize meta tags and content with Grok Bot
Optimizing meta tags with Grok Bot means asking a named xAI Bot to have StoreSEO generate a meta title, description, tags, URL handle, FAQs and AI snippet for one Shopify resource, then applying only the parts of the draft you say yes to.
Last updated: October 2026
Set up Grok Bot for StoreSEO
Skip this if Grok Bot is already connected. The full guide, with the alternatives, is on the Grok Bot page.
- 1
Ask your Bot to add StoreSEO
In a chat with your Bot, ask it to add a custom remote HTTPS MCP server with this URL. xAI's documentation says a plugin added from your own chat is personal and account-wide, so every Bot on your account can use it. Complete the StoreSEO sign-in when the browser opens: pick your Shopify store and approve access.
PromptAdd a custom remote HTTPS MCP server called StoreSEO with the URL https://mcp.storeseo.com/mcp and sign me in.
- 2
Attach it and check it works
In a chat, type @ to attach the StoreSEO connector to the task, then ask this to confirm the connection.
PromptUse @StoreSEO to show me my store's SEO score breakdown.
How does this work in Grok Bot?
You start in a chat with a Bot and attach the StoreSEO plugin with @. A good opening request names one resource, for example write better meta for my bestselling candle product, because each preview spends AI Content Optimizer credit. The Bot reads the current state with storeseo_get_resource_seo, then calls storeseo_preview_resource_optimization. StoreSEO writes the copy on its own servers, so the words come from StoreSEO rather than from Grok, and the response carries a draft id and the projected score change. The Bot lays the draft out in the chat so you can read the title, the description and the new URL handle next to the old one.
The apply step is where Grok Bot's own controls come in. Calling storeseo_apply_resource_optimization is a write, so the Bot should ask you in plain words, and the client can add a prompt offering Allow once, Always allow or Deny. Choose Allow once while you are learning how the drafts look. If a handle changed, applying it creates a redirect from the old address, which is why the Bot should show both URLs before that call. You can approve only the meta and skip the handle, and the Bot passes just those fields along.
The cloud computer helps with volume without changing the rules. You can ask the Bot to work through ten products in the same conversation, previewing one at a time and pausing for your yes before each apply. What it should not do is preview in a loop on a schedule: every preview spends credit whether or not you apply it, and a routine has no one to approve the result. Use a routine to find which products need meta, then do the previews in a chat.
-
You: Use @StoreSEO to improve the meta on my Soy Candle product.
- storeseo_start read-only
- storeseo_get_resource_seo read-only
-
Grok Bot: The meta description is empty. A preview spends AI Content Optimizer credit and saves nothing. Should I generate one?
-
You: Yes, go ahead.
- storeseo_preview_resource_optimization preview
-
Grok Bot: Illustrative draft: a new title and description, with the score projected from 31 to 78. Apply the title and description only, and skip the handle?
-
You: Yes, apply those two.
- storeseo_apply_resource_optimization needs approval
What to ask Grok Bot
Use @StoreSEO to preview new meta for my Soy Candle product and show me the old and new title, description and handle before anything is saved.
Preview meta for my three lowest-scoring products, one at a time, and wait for my yes after each one before you apply it.
Apply only the meta title and description from that draft and skip the URL handle.
- Optimize the meta title and description for my five lowest-scoring products. Show me the previews before you apply anything.
- Preview a new meta title, description and FAQ for the collection Summer Dresses, and keep the current URL handle.
- Apply the meta from that preview but skip the FAQ.
- Which of my pages have no meta description? Draft one for each and wait for my approval.
- What does StoreSEO optimize automatically for new products right now?
- Turn on automatic meta and alt text for new products only. Tell me what that will spend first.
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 Grok Bot 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 Grok Bot
Treat Always allow with care here. Grok Bot saves it as a rule for matching actions, so if you choose it on storeseo_apply_resource_optimization or storeseo_preview_resource_optimization, the client stops asking and only StoreSEO's own preview-first instruction remains. A Test run on a routine also performs real work, including connected tool calls, so never test a routine that contains a preview or apply. In Auto-review, an Ask first rule on the apply tool is the hard stop.
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 Grok write the meta text itself?
No. StoreSEO generates the meta title, description, tags, handle, FAQs and AI snippet on its own servers. The Bot fetches the draft, shows it to you and passes along only the parts you approve.
How do I keep a Grok Bot from applying meta without my yes?
StoreSEO tells the agent to wait for your yes, but the hard stop is your client setting. Leave the apply tool on Allow once or add an Ask first rule in Auto-review, and avoid Always allow on it.
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 Grok Bot guides