Meta tags and on-page content Optimize meta tags and content with Grok
Optimizing meta tags and on-page content with Grok means asking it in a chat on grok.com to have the StoreSEO connector generate a meta title, description, tags, URL handle, FAQs and AI snippet for a Shopify resource, then applying the draft you say yes to.
Last updated: October 2026
Set up Grok for StoreSEO
Skip this if Grok is already connected. The full guide, with the alternatives, is on the Grok page.
- 1
Add a custom connector
Open the connectors page on grok.com, choose New Connector and then Custom. Enter this as the MCP server URL and complete the authentication when it opens.
URLhttps://mcp.storeseo.com/mcp
- 2
Approve your store and check it
Pick your Shopify store in the browser and approve access. Then start a chat with the connector available and ask this to confirm the connection works.
PromptUse StoreSEO to show me my store's SEO score breakdown.
How does this work in Grok?
You are in a normal Grok conversation with the StoreSEO custom connector available, so there is no terminal and no file to edit. You type something like rewrite the meta for my Linen Throw Blanket product and show me the draft. Grok opens a StoreSEO session with storeseo_start, reads the product with storeseo_get_resource_seo, which returns the current fields, the score and each failing criterion, and then calls storeseo_preview_resource_optimization. StoreSEO writes the copy on its own side and projects the new SEO score, plus the GEO score for products, without saving anything.
Because this is chat, the draft arrives as readable text in the thread, which makes it easy to edit by talking. You can answer make the description shorter and mention free shipping, but remember what that means in practice: Grok does not author StoreSEO's generated fields, so a changed draft means another preview, and another preview spends credit again. A cheaper path is to apply the draft as it is, or skip individual fields such as the handle, and change a single field later in the StoreSEO app. When the preview proposes a new URL handle Grok should show you the old and the new address and tell you a redirect will be created before you agree.
Applying is a separate call, storeseo_apply_resource_optimization, and StoreSEO tells the agent to wait for your yes before making it. xAI's connector documentation does not describe a per-tool approval setting, so that instruction and your own reading of the proposal are the main check in the conversation. After the apply, Grok reports the recomputed score and what still fails, and you can ask it to move on to the next product in the same thread.
-
You: Rewrite the meta for my Linen Throw Blanket and show me the draft first.
- storeseo_start read-only
- storeseo_get_resource_seo read-only
- storeseo_preview_resource_optimization preview
-
Grok: StoreSEO drafted a meta title, description, tags, two FAQs and an AI snippet, and projects the score moving from 31 to 78. The handle stays as it is. Do you want me to apply all of it?
-
You: Go ahead and apply it.
- storeseo_apply_resource_optimization needs approval
What to ask Grok
Using StoreSEO, preview new meta for my lowest-scoring product. Show the generated text and the score change before you save anything.
Draft a meta title, description and FAQ for my About Us page and wait for my go-ahead.
Apply that preview but keep the current 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 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
A preview spends AI Content Optimizer credit when it is generated, and in a chat it is tempting to keep asking for small rewrites. Each rewrite request that triggers a new preview spends again, so decide which fields you want changed before you ask, or apply the draft and tweak a single field in the app. On Grok Business and Enterprise a team admin has to provision the connector in the cloud console first, so members may see no StoreSEO tools until that is done.
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 I ask Grok to reword the generated meta description?
You can ask, but StoreSEO writes the generated fields on its own side, so the agent cannot edit the draft in place. A reworded request means a new preview, which spends AI Content Optimizer credit again. You can also apply the draft and edit one field afterwards in the StoreSEO app.
Will Grok 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.
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 guides