Optimize meta tags and content with Antigravity
Optimizing meta tags and on-page content with Antigravity means asking the agent in Google's IDE side panel to have StoreSEO generate a meta title, description, tags, URL handle, FAQs and AI snippet for a Shopify resource, then applying the draft you approve.
Last updated: October 2026
Set up Antigravity for StoreSEO
Skip this if Antigravity is already connected. The full guide, with the alternatives, is on the Antigravity page.
- 1
Add StoreSEO in View raw config
In the Antigravity IDE open the menu in the agent side panel, choose MCP Servers, then Manage MCP Servers, then View raw config. Paste this into mcp_config.json and save. The field is serverUrl: Antigravity does not support url or httpUrl for remote servers.
JSON{ "mcpServers": { "storeseo": { "serverUrl": "https://mcp.storeseo.com/mcp" } } } - 2
Sign in, then check the connection
Open Agent settings (Cmd+, on Mac, Ctrl+, on Windows and Linux), go to Customizations and click Authenticate next to storeseo. Pick your Shopify store and approve in the browser, copy the authorization code it shows, paste it into the settings panel and click Submit. Then ask this in the agent panel.
PromptUse StoreSEO to show me my store's SEO score breakdown.
How does this work in Antigravity?
You open the agent side panel in Antigravity with your storefront project loaded, and once storeseo shows as authenticated under Agent settings, Customizations you type a request such as preview new meta for my lowest-scoring product. Tools you have not configured run in Ask mode by default, so the agent needs your approval before each call. It runs storeseo_start, then storeseo_get_resource_seo, then storeseo_preview_resource_optimization. StoreSEO generates the draft on its own side and projects the score without saving. The preview spends AI Content Optimizer credit, whether or not you apply it.
When the draft comes back, with a meta title, description, tags, FAQs and an AI snippet, read it against the page it will sit on. Antigravity can open the theme template in the same window, so check how the title is rendered and whether the theme adds a store-name suffix before the new meta title looks too long. If a new handle is proposed you should see the old and new URL, because applying creates a redirect. Reply apply the meta and skip the handle, and the agent calls storeseo_apply_resource_optimization with only those parts.
There are two layers of confirmation. StoreSEO tells the agent to wait for your yes in the conversation, and Antigravity's Ask mode then prompts for the call itself. The Ask mode prompt is the hard stop. If you later add a policy of the form mcp(storeseo/tool), you decide per tool whether Antigravity stops asking, and the preview and apply tools are the ones worth leaving on Ask.
-
You: Preview new meta for my lowest-scoring product.
- storeseo_start read-only
- storeseo_get_resource_seo read-only
- storeseo_preview_resource_optimization preview
-
Antigravity: The draft for Linen Throw Blanket has a new meta title and description, three tags and two FAQs, and the score would move from 31 to 78. A new handle is proposed and would create a redirect. Apply all of it?
-
You: Apply it, but skip the handle.
- storeseo_apply_resource_optimization needs approval
What to ask Antigravity
Use StoreSEO to preview new meta for my lowest-scoring product and show me the draft and projected score. Apply nothing yet.
Preview a 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 URL handle and the FAQ.
- 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 Antigravity 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 Antigravity
Antigravity reads remote servers from the serverUrl field and does not support url or httpUrl, so an entry copied from another client leaves storeseo without tools and the preview call never appears. The sign-in also ends with a code you paste back into Agent settings, so finish it in the same window. If you allow mcp(storeseo/*) in a policy, Antigravity stops asking before storeseo_apply_resource_optimization, and only the confirmation StoreSEO asks the agent for remains.
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
Will Antigravity ask before it applies a StoreSEO draft?
By default, yes. MCP tools you have not configured run in Ask mode, which requires your approval before execution. A policy that allows every StoreSEO tool at once turns that prompt off, so allow only specific read tools if you want to keep it for writes.
Does previewing meta in Antigravity change my store?
No. The preview generates a draft and a projected score without saving anything. It spends AI Content Optimizer credit, and the store changes only when the agent calls the apply tool after your yes.
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 Antigravity guides