Is this an autonomous shopping or crawling agent?

Visually.io says a real authenticated human drives the editor and navigates the store inside the iframe. The identity is classified as user initiated, and it is not documented as a bulk web crawler.

Can robots.txt target the Visually.io Shopify Editor?

Not reliably. No stable user-agent token is published, the bot record leaves robots behavior unknown, and Cloudflare's bot directory marks the agent as not following robots.txt. Use signature-aware edge controls instead.

Does blocking the editor change AI search or training use?

No documented AI search or model-training system depends on this agent. A block affects the Visually.io editing workflow, especially page loading and design previews, rather than a store's eligibility for generated answers.

Visually.io Shopify Editor AI Crawler Guide

Q: How can I authenticate the editor traffic?

Check the Web Bot Auth HTTP message signature with the public keys at https://visually.io/.well-known/http-message-signatures-directory. This gives you an identity signal even though the agent has no stable user-agent token.

What is Visually.io Shopify Editor?

Visually.io Shopify Editor is the network identity used by Visually.io's live theme editor for Shopify stores. It is a user-initiated editing tool, not a crawler sent out to discover arbitrary websites. A store owner opens the editor and remains in control of the session.

The editor loads the merchant's Shopify theme inside an iframe. Visually.io routes the browser requests through a controlled proxy so it can temporarily adjust the theme's HTML, JavaScript, and CSS for preview and editing. The merchant can select an element in the rendered store and apply widgets or other design changes.

Because the proxy handles the browser session, it also handles requests to Shopify and to third parties used by the storefront. Those requests may appear as automated traffic at an edge or origin even though an authenticated person is navigating the pages inside the editor. Visually.io describes the human user as the party driving each session.

This traffic has no documented role in AI search, citation retrieval, or model training. Allowing it will not improve a store's presence in generated answers. Blocking it can instead prevent a merchant from loading pages or previewing changes in the Visually.io editor.

There is no stable user-agent token for this agent. Cloudflare's bot directory lists it as a signed agent and points to Visually.io's explanation of the iframe and proxy workflow. Since there is no identifying token, an agent-specific robots.txt group cannot reliably match it.

Visually.io publishes Web Bot Auth keys at https://visually.io/.well-known/http-message-signatures-directory. Verify the HTTP message signature at the CDN or edge when you need to distinguish the editor from ordinary storefront traffic. Robots.txt behavior is unknown in this bot, and Cloudflare's bot directory marks the agent as not following robots.txt.

Relevant for AI search

Is Visually.io Shopify Editor relevant for AI search?

Yes. Visually.io Shopify Editor collects pages for an AI product, so what it can crawl influences how AI systems describe your brand.

Visually.io Shopify Editor crawls and indexes pages so the AI search or assistant behind it can retrieve them at answer time. A page it has never fetched cannot be quoted, summarized, or linked in that product's answers, so most sites keep it allowed to stay citable. Blocking it removes your pages from that AI surface and hands those citations to competitors.

How to handle Visually.io Shopify Editor

Shopify merchants using Visually.io should allow correctly signed editor traffic to the storefront resources needed for previewing and editing. If the store does not use Visually.io, or policy forbids this proxy workflow, reject it at the edge.

Do not add a guessed robots.txt user agent. The agent has no stable token, its robots behavior is unconfirmed, and Cloudflare's bot directory records it as not following robots.txt. A generic rule could block unrelated clients without reliably stopping the editor.

Instead, validate Web Bot Auth HTTP message signatures against https://visually.io/.well-known/http-message-signatures-directory, then make the allow or block decision on that verified identity. Keep normal authentication and authorization checks in place for every store action.

Examples

A Shopify merchant opens a product page inside Visually.io, selects the announcement bar, and previews a replacement while the controlled proxy loads the theme in an iframe.
A CDN rule validates the editor's Web Bot Auth signature before allowing proxied JavaScript and CSS requests to reach the storefront.
A store that has never installed Visually.io blocks the signed agent identity without changing rules for shoppers or search crawlers.

Frequently asked questions about Visually.io Shopify Editor

Learn about AI visibility monitoring and how Promptwatch helps your brand succeed in AI search.

It loads the Shopify theme in an iframe so an authenticated store owner can navigate the live design and preview edits. A controlled proxy temporarily adjusts the returned HTML, JavaScript, and CSS for the editing session.

Related bots

Amazon Kendra

Amazon Kendra is a managed information retrieval and intelligent search service that uses natural language processing and advanced deep learning model.

AI Assistant