Allow or block Kimi-User on Adobe Commerce (Magento): Search Engine Robots in the Admin

In the Admin open Content → Design → Configuration → Edit → Search Engine Robots, add a “User-agent: Kimi-User” group with “Disallow: /” to the custom instructions, and save the configuration.

This response

You are ClaudeBot (Anthropic). Citable recognised you as an AI agent, so this is https://getcitable.in/crawlers/kimi-user/magento with the UI removed — the content only. A browser asking for the same address gets the full designed page.

Kimi-User, and where Adobe Commerce (Magento) keeps the rule

Kimi-User is a crawler run by Moonshot AI. It reads pages at the moment a person asks a question, to answer it.

Adobe Commerce and Magento Open Source generate robots.txt from the Search Engine Robots section of the design configuration.

Step by step

What to paste

A group that names a crawler replaces the * group for that crawler; it does not add to it. Paths the * group closes are open to a crawler with its own group unless they are repeated there.

Refuse Kimi-User:

User-agent: Kimi-User
Disallow: /

Allow Kimi-User:

User-agent: Kimi-User
Allow: /

What trips people up

On Adobe Commerce cloud projects, robots.txt keeps showing the default content until indexing by search engines is enabled for the environment. A saved rule that never appears is usually this.

Asked, or actually refused?

The Admin offers robots.txt only. A refusal that is enforced is made by the web server in front of the store; see Kimi-User on Nginx or on Apache.

Check it yourself

A 200 means the name is let through; a 403 means something in front of the page refuses it. This tests the name from your own address. A platform that checks a crawler’s address as well may treat the real Kimi-User differently.

The request:

curl -I -A "Kimi-User" https://your-site.example/

Questions

How do I block Kimi-User on Adobe Commerce (Magento)?

In the Admin open Content → Design → Configuration → Edit → Search Engine Robots, add a “User-agent: Kimi-User” group with “Disallow: /” to the custom instructions, and save the configuration.

How do I allow Kimi-User on Adobe Commerce (Magento)?

A crawler that robots.txt does not name follows the * group, so Kimi-User needs no rule to be allowed. To allow it by name, add the Allow block.

Can Adobe Commerce (Magento) actually stop Kimi-User, or only ask it?

The Admin offers robots.txt only. A refusal that is enforced is made by the web server in front of the store; see Kimi-User on Nginx or on Apache.

Does a rule for Kimi-User affect Googlebot or my Google rankings?

No. Googlebot goes by its own name and follows its own rules; a group or a firewall rule for Kimi-User does not apply to it.

Checked against Adobe Commerce (Magento)'s own documentation on 1 October 2026

Related

About Citable

Citable strips the UI from a website for AI agents and serves them only the content.

When an AI agent — ChatGPT, Claude, Perplexity or any of the 81 that Citable recognises — opens a page, Citable removes the theme, scripts, navigation and layout and serves only the content: the same facts, at the same URL, on the site's own domain. People and Google still get the full designed page.

How it works: https://getcitable.in/how-it-works · Summary for AI agents: https://getcitable.in/llms.txt


Source: https://getcitable.in/crawlers/kimi-user/magento · Citable · Run the free audit · llms.txt · getcitable@gmail.com