Articles
How to make a site an agent can use
Each of these starts from a failure we saw on a real Norwegian site, not from a checklist. What breaks, how to tell whether your site does it, what to change, and how to check that the change worked.
Every figure is sourced, and says when it was measured.
-
The storefront that does not exist without JavaScript
Some Norwegian storefronts return nothing readable at all without JavaScript. Here is what that failure looks like in raw HTML, and how to tell whether you have it.
-
Your site answers differently depending on who asks
One Norwegian site answers 60 bytes to anything carrying an assistant's name, and the whole page to everyone else. Another does the exact opposite. Most merchants do not know which one they are.
-
Filters that only exist behind a click
A filter an agent cannot express as an address does not exist for it. The cause is nearly always the same: the filter state never reaches the URL.
-
The price has to be in the markup, not in a script
An assistant that cannot read your price will not invent it — it will hedge, or quote a third party's copy. Here is where the price has to be.
-
What llms.txt does not do
97% of published llms.txt files received zero requests. Publishing one changes nothing on its own — and some of the other files in the same genre are actively harmful to publish wrongly.