Store SEO audit Audit your store's SEO with Antigravity
Auditing your store's SEO with Antigravity means asking Google's agent in the IDE side panel which products, collections, pages and posts score worst in StoreSEO, and approving the read calls in Ask mode as they come.
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 are in the Antigravity IDE with a project open and the agent panel at the side. Once storeseo is in mcp_config.json with serverUrl and you have clicked Authenticate under Customizations and pasted the authorization code back, you ask which fifteen products score worst and what is failing on each. The agent calls storeseo_start first, because every other StoreSEO tool needs the conversation id it returns, then storeseo_list_resources sorted by score, lowest first, and storeseo_get_resource_seo for each candidate. All three only read. Because MCP tools you have not configured run in Ask mode, each call waits for your approval in the panel before it executes.
The reply names failing criteria by their visible titles, and separates what a StoreSEO tool can fix from what only you can change in the app, such as the focus keyword. Products carry a GEO score for AI readiness as well, so the same pass shows which listings AI shopping agents will struggle to understand. With a project open, you can have the agent save the worklist as a Markdown file in the workspace, or check failing product handles against your theme's templates before deciding what to fix first.
Ask mode makes an audit slightly slower but easy to follow, since you see each call before it runs. If you want it quicker, Antigravity's policy patterns of the form mcp(server/tool) let you allow specific tools, so you can allow the three read tools and leave everything else on Ask. That keeps the audit smooth and leaves any later apply or generate step stopping for you, in addition to the confirmation StoreSEO tells the agent to request.
-
You: Audit my store and show the fifteen worst products.
- storeseo_start read-only
- storeseo_list_resources read-only
- storeseo_get_resource_seo read-only
-
Antigravity: The fifteen lowest score between 14 and 32. Most lack a meta description and image alt text, and four need a focus keyword, which you set in the StoreSEO app.
-
You: Save that to seo-audit.md.
-
Antigravity: Saved to seo-audit.md in the workspace, with the app-only fixes listed separately.
What to ask Antigravity
Use StoreSEO to list my fifteen lowest-scoring products and the main failing criterion on each. Read only.
Audit my collections and pages, worst first, and save the list to seo-audit.md in this workspace.
Which products have the weakest GEO score for AI shopping agents, and which fixes can StoreSEO make?
- Show me my ten lowest-scoring products and the top issue on each.
- Which collections are not optimized yet, and what is failing on them?
- Give me an SEO audit of my blog posts, worst first.
- Which products have the weakest GEO score for AI shopping agents, and why?
- Summarize my store's SEO: how many products, collections, pages and posts are optimized?
- For the product Linen Shirt, list every failing SEO criterion and say which ones StoreSEO can fix.
What StoreSEO does: store seo audit
StoreSEO scores every product, collection, page and blog post against its SEO checklist, and scores products for AI readiness (GEO) as well. An agent opens a session, lists the weakest resources first and reads the per-criterion analysis for each, so you get a ranked worklist instead of a dashboard to click through.
- 1
Open a StoreSEO session
The agent calls the start tool first. It returns a conversation id every later call needs, plus a snapshot of your store: how many resources are optimized, need improvement or are not optimized, image status, rank tracking and which features are set up.
- 2
List the weakest resources
It lists products, collections, pages or articles sorted by score, lowest first, or filtered to the ones marked not optimized. Products also carry a GEO score and their AI-readiness issues.
- 3
Read the checklist for each one
For each candidate it reads the full SEO record: current meta fields, focus keyword, score, every criterion that passes or fails, image status, FAQs and AI snippet.
- 4
Sort fixes by who can make them
It separates what a StoreSEO tool can fix (meta, handle, FAQs, AI snippet, image alt text, schema) from what only you can change in the app or in Shopify admin (the focus keyword, the product title, category, inventory).
- 5
Report a worklist
You get the resources in order, with the failing criteria in plain words and one suggested next fix. Nothing is written during an audit.
Store SEO audit reference
| Resource types | Products, collections, pages and blog articles |
|---|---|
| Scores | An SEO score for every resource, plus a GEO (AI readiness) score for products |
| Status labels | Optimized, needs improvement, not optimized; GEO adds not analysed |
| Sorting | By score, lowest first, or filtered to not optimized |
| Session | Every call carries the conversation id from the start tool; calls without it fail |
| What it writes | Nothing. Every audit tool is read-only |
| Fixed only in the app | Focus keyword choice, product title wording, Shopify category, product type, inventory, variant data |
| Plan | Any active StoreSEO plan, including the free plan |
Rules Antigravity follows
- Every audit call is a read and runs straight away; nothing in this job changes your store.
- The agent describes criteria by their visible title, never by internal identifiers or raw status values.
- Criteria no tool can fix, such as choosing the focus keyword, are handed to you with a link into the StoreSEO app rather than guessed.
- The agent should offer one next fix at a time, tied to what it just found, instead of dumping the whole list as a checklist.
In Antigravity
Antigravity runs MCP tools you have not configured in Ask mode, so even the read-only audit tools wait for your approval and a long audit means several clicks. A policy that allows mcp(storeseo/*) would end the prompts, but it would also cover the apply and generate tools, leaving StoreSEO's own confirmation as the only check, so allow the three read tools individually. If the server will not connect, check that the entry uses serverUrl: the documentation says legacy fields such as url or httpUrl are not supported. The sign-in ends with a code you paste into Agent settings, so finish it in the window where you started.
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
Why does Antigravity ask before each StoreSEO audit call?
MCP tools you have not configured run in Ask mode, which requires approval before execution. Add policy patterns for the three read tools if you want the audit to run without prompts.
Why will Antigravity not connect to StoreSEO from my copied config?
Antigravity uses the serverUrl field for remote servers and does not support url or httpUrl. Rename the field in mcp_config.json, then authenticate again under Customizations in Agent settings.
Does an SEO audit change anything in my store?
No. The audit uses read-only tools: the session start, the resource list and the per-resource SEO record. Your store is only changed later, by a separate step you agree to.
What is the difference between the SEO score and the GEO score?
The SEO score measures a resource against StoreSEO's on-page checklist for search engines. The GEO score applies to products only and measures how ready the product is for AI shopping agents and generative search, using criteria such as FAQs, an AI snippet, alt text and product schema.
Can the agent choose my focus keyword?
No tool can set the focus keyword. The agent can tell you when the keyword is missing or looks wrong and give you a link to set it in the StoreSEO app, and several fixes such as keyword clusters and description writing need it set first.
How many products can the agent audit at once?
The listing is paginated, so the agent can walk your whole catalog page by page. In practice it is more useful to ask for the lowest scores first and work down from there.
Keep going
Store SEO audit with other agents
More Antigravity guides