Z Store SEO audit

Audit your store's SEO with Zed

Auditing your store's SEO with Zed means asking the Agent Panel in your editor which products, collections, pages and posts score worst in StoreSEO, and approving the read calls as Zed prompts for them.

Jump to the prompts Connect Zed

Last updated: October 2026

Set up Zed for StoreSEO

Skip this if Zed is already connected. The full guide, with the alternatives, is on the Zed page.

1
Add StoreSEO as a remote server

Open Settings, then AI, then MCP Servers and add a remote server, or add this to settings.json yourself. Leave out headers so Zed can sign you in.
JSON

{ "context_servers": { "storeseo": { "url": "https://mcp.storeseo.com/mcp" } } }
2
Sign in and check the dot

Because the entry has no Authorization header, Zed prompts you to authenticate. Pick your Shopify store and approve in the browser. In Settings, AI, MCP Servers a green dot next to storeseo means the server is active. Then ask this in the Agent Panel.
Prompt

Use StoreSEO to show me my store's SEO score breakdown.

How does this work in Zed?

You are in Zed with a project open and the Agent Panel docked beside your code. With storeseo added under context_servers in settings.json and a green dot next to it in Settings, AI, MCP Servers, 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. Every one of those is a read, but Zed's default setting is confirm, so the panel stops and asks you to approve each tool action before it runs.

The answer comes back in the panel: failing criteria named by their visible titles, and a split between what a StoreSEO tool can fix and what you must change in the app, such as the focus keyword. Products carry a GEO score for AI readiness too, so the same audit shows which listings AI shopping agents will struggle with. Because the agent is working inside your project, you can have it write the worklist to a Markdown file next to your theme code or compare product handles against the templates you are editing.

The prompts are the practical difference in Zed. An audit of fifteen products can mean a dozen approvals, which is tedious but gives you a visible record of every call. If that gets in the way, Zed's per-tool keys let you allow the read tools by name and leave the write tools on confirm, so the audit runs quickly while a later apply still stops for you.

Zed + StoreSEO Illustrative session

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
Zed: The fifteen lowest score between 13 and 31. Most lack a meta description and image alt text, and four need a focus keyword, which you set in the StoreSEO app.
You: Which of those can StoreSEO fix?
Zed: Meta, FAQs, AI snippet and alt text on all fifteen. Want me to preview the meta for the eleven that have a focus keyword?

What to ask Zed

Prompt 1

Use StoreSEO to list my fifteen lowest-scoring products and the main failing criterion on each. Read only.

Prompt 2

Audit my pages and blog posts, worst first, and write the list to seo-audit.md in this project.

Prompt 3

Which products have the weakest GEO score for AI shopping agents, and what is missing on each?

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.

storeseo_startstoreseo_list_resourcesstoreseo_get_resource_seo

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 Zed 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 Zed

Zed's agent.tool_permissions.default is confirm unless you change it, so even the read-only audit tools prompt before they run and a catalog audit means several approvals. To speed that up, allow only the read tools with per-tool keys such as mcp:storeseo:storeseo_list_resources and keep the write tools on confirm. Setting the default to allow removes Zed's check entirely, and then the confirmation StoreSEO asks the agent for is the only one, so use it sparingly. The per-tool keys need Zed v0.224.0 or later.

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 Zed ask me to approve every StoreSEO read?

Zed's tool permission default is confirm, which prompts before any tool action, reads included. Allow specific read tools with mcp:storeseo keys if you want the audit to run without prompts.

How do I know the StoreSEO server is ready in Zed?

Open Settings, AI, MCP Servers. A green dot next to storeseo means the server is active. If it is not, complete the sign-in that Zed prompts for, then ask the audit question in the Agent Panel.

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.