K Store SEO audit

Audit your store's SEO with Kiro

Auditing your store's SEO with Kiro means asking the agent in AWS's IDE which products, collections, pages and posts score worst in StoreSEO, with the read tools optionally listed in autoApprove so the audit runs without stopping.

Jump to the prompts Connect Kiro

Last updated: October 2026

Set up Kiro for StoreSEO

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

1
Add StoreSEO to your Kiro MCP config

Open the Command Palette (Cmd+Shift+P on Mac, Ctrl+Shift+P on Windows and Linux), search for MCP and open the workspace config (.kiro/settings/mcp.json) or the user config (~/.kiro/settings/mcp.json). Paste this and save. Kiro applies the change on save, and the first connection opens a browser sign-in: pick your Shopify store and approve.
JSON

{ "mcpServers": { "storeseo": { "url": "https://mcp.storeseo.com/mcp" } } }

How does this work in Kiro?

You are in Kiro with a project open and the agent chat beside your files. Once storeseo is in .kiro/settings/mcp.json or ~/.kiro/settings/mcp.json and the browser sign-in is done, 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 are reads. 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.

Kiro is built around planning multi-step work in a project, so an audit fits naturally as the first step of a longer job. Ask for the worklist, have the agent save it into the workspace as a Markdown file, then come back to it and decide what to fix. Products also carry a GEO score for AI readiness, which tells you which listings AI shopping agents may misread. On a large catalog, ask for pages of twenty and stop at a score threshold instead of pulling every product in one go.

The setting worth knowing is autoApprove. Each server can carry a list of tools that run without a prompt, and for an audit the right list is the three read tools: storeseo_start, storeseo_list_resources and storeseo_get_resource_seo. With that in place the audit runs without interruptions, while any write tool you ask for later still goes through Kiro's own prompt, which is a second check on top of the confirmation StoreSEO tells the agent to ask for.

Kiro + 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
Kiro: The fifteen lowest score between 12 and 30. Most lack a meta description and image alt text, and five need a focus keyword, which you set in the StoreSEO app.
You: Save that to seo-audit.md.
Kiro: Saved to seo-audit.md in the workspace, with the app-only fixes listed separately.

What to ask Kiro

Prompt 1

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

Prompt 2

Audit my collections, pages and blog posts, worst first, and save the list to seo-audit.md in this workspace.

Prompt 3

Which products have the weakest GEO score for AI shopping agents, and what would fix 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 Kiro 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 Kiro

Kiro's documentation does not state its default approval behavior when autoApprove is empty, so check what your install does before you assume reads run quietly or prompt. If you do use autoApprove, list the three read tools individually. A wildcard would also cover StoreSEO's apply and generate tools and let Kiro run them without asking, leaving StoreSEO's own confirmation as the only check. A workspace .kiro/settings/mcp.json also overrides a user-level entry with the same name, so if the sign-in points at the wrong store, check which file defines storeseo.

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

Which StoreSEO tools should I put in Kiro's autoApprove list for an audit?

The three read tools: storeseo_start, storeseo_list_resources and storeseo_get_resource_seo. List them individually rather than with a wildcard, so apply and generate tools still go through Kiro's prompt.

Can I keep an SEO audit worklist inside my Kiro project?

Yes. Ask the agent to write the results to a Markdown file in the workspace, then reopen it later to choose what to fix. The audit itself only reads from StoreSEO.

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.