On August 20, Ora announced a partnership with Vercel to launch is-agentic.com, a scanner that scores whether AI agents can discover, access, read, and use a website. MarkTechPost covered the launch on August 23 as a free public audit tool.
An agent asked to compare vendors may need to collect capabilities, pricing, customer evidence, and contact details before a person reviews the options. That makes the accessibility and clarity of those pages worth testing alongside their appearance in a browser.
Use the scanner as a diagnostic
Ora says its ranker runs 127 checks across four layers: discovery, access, usability, and payments. The Vercel version is narrower, aimed at websites whose job is making content easy for agents to find, read, and use. A scan can identify candidate problems; its score does not establish that an agent can complete your particular task.
Search visibility and task completion require separate checks. A page may be crawlable while leaving pricing in a modal, spreading capabilities across six vague pages, or making the contact path hard to interpret. Test the agent’s attempt to find an answer and inspect the page or interaction where it failed.
A failed attempt may reveal missing information, an access restriction, or a tool limitation. The result needs investigation before anyone attributes it to the copy or assumes how an agent will rank the business.
Review the pages a buyer uses
Ora’s launch post describes the tool’s question as “is my site agentic and what do I fix first.” Begin with that diagnostic approach before deciding whether the site needs a 90-day replatforming project or a custom agent interface.
Start with five pages: homepage, product or service page, pricing or engagement page, case study page, and contact page. Check whether each gives its main answer in the first 150 words. Record any missing capabilities, integration details, implementation requirements, limitations, or starting instructions. Where the page makes an outcome claim, check the supporting evidence and its scope.
Then ask an agent to perform a concrete task, such as comparing the service with a stated requirement or finding the next step for an inquiry. Review the answer against the pages, including its sources and any invented details. Fix a specific failure and repeat the task so that the team can see whether the change helped.
Give factual corrections an owner
A website used by external agents still needs the same coordination as other customer-facing material. Marketing may own the message while product, sales, support, legal, and operations supply facts about what the company offers and how an engagement works.
When the site, sales deck, help documents, and pricing page disagree, assign someone to resolve the discrepancy. Keep the limits of the offering visible as well as its capabilities. An agent’s failed attempt to use the site can help locate the problem, but a person needs to decide which statement is correct.
Use the scan and the task test together. Keep a record of the failure, the page changed, and the result of the next attempt. That gives the team a manageable way to improve readability without treating a scanner score as proof of sales performance.