Personal AI agents reach websites with no name to block in robots.txt

Your website's bot filter now decides what happens to a visitor your SEO team never signed off on. Search Engine Journal reports that Meta's Muse and OpenAI's dots arrive in a cloud Chromium browser with no user agent, no referrer and no IP range anyone has published, so robots.txt has nothing to name.

The piece by machine-first consultant Slobodan Manic uses Meta's and OpenAI's own documentation plus Shopify, Amazon and WebAIM. It describes two tiers the agents arrive in.

Connector tier and browser tier

Search Engine Journal quotes Meta describing Muse as launched with "dozens of partners along with access to the entire Shopify catalogue" through APIs Meta integrated. OpenAI's dots has its own version through its plugin ecosystem, which the article says reaches more than 4,000 apps. Everyone outside that is in the browser tier, which Meta describes as "a real up-to-date Chromium-based browser" on "a dedicated secure computer".

Shopify's default setting, "Allow Shopify to manage for me", enrolls a store in those AI shopping channels automatically. A store on a custom platform is in the browser tier unless it builds a connector.

No name to put in robots.txt

Meta's own crawlers page lists five bots and Muse is not one of them. OpenAI's lists four and dots is not on that list. Meta's documentation, quoted in the piece, says Muse "will appear as your activity, so if you ask Muse to buy a shirt from a clothing designer's website, that designer might use your visit to show you an ad on Instagram". Amazon blocked Muse in September not through robots.txt but through its Conditions of Use, and told Meta the agent "doesn't identify itself when it browses" and "appears to capture and store customer credentials".

The decision therefore moves off the SEO team's desk and onto bot protection. Search Engine Journal cites HUMAN Security saying its product can identify Muse, which the piece suggests is a question to ask any bot vendor.

What the agent actually reads

Meta says Muse's browsing sub-agent reads a page through the accessibility tree "not the raw DOM" and "has no ability to run JavaScript in the page context". The piece checked a Shopify product page in Chrome and found a sizing control that showed six of seven sizes as out of stock to a human through styling alone. In the accessibility tree it saw seven identical "Select size" buttons with nothing marked unavailable, so an agent would learn which sizes a shopper sees at a glance only by trying each one. Structured data in JSON-LD is absent from the tree, while most on-page SEO work still carries over.

Why Google Analytics will miss the orders

Search Engine Journal reports that when a shopper buys through a connector, the checkout never loads the merchant's pages, so Google Analytics and pixels do not run. Shopify confirms this for stores on Meta and Google. Google Analytics 4 added an AI Assistant channel that sorts visits by referrer, so it counts a link click from the app and misses the agent sessions that have no referrer at all. The Information reported that more than three million people prompt Muse at least once a week.

The pages a person acts on, the forms, the bookings and the checkouts, are the pages an agent now has to use too, and WebAIM found 95.9 percent of the top million home pages had WCAG 2 failures in 2026.

Source

What Personal AI Agents Like Meta Muse And OpenAI Dots Mean For SEO, by Slobodan Manic, Search Engine Journal.