Learning Center · Answers · Getting started
How long does it take to make a website agent-ready?
Short answer
Plan on about 90 days in three phases of roughly a month each. Spend the first month letting agents in, the second making pages readable and usable, and the third proving agents can finish your money journeys. Many access fixes are settings changes that take hours.
In more detail
Effort varies a lot by fix. AgentScore labels each check by typical effort. Bot protection, robots.txt and llms.txt fixes are usually hours. Prices in the HTML, structured data and guest checkout are usually days. Making content load without JavaScript and adding MCP or agentic commerce support are usually weeks. For stores that block assistants, the fix is usually a settings change.
Getting a baseline takes days. A scan, a look at agent traffic in your logs and one tested journey come first. By day 90, aim for no critical findings on your home page and key product pages, at least one money journey tested by a real agent on a schedule, and a monthly view leadership can read. None of these is a target score.
The work never fully ends. A new pop-up campaign, a bot protection change or a redesigned product page can undo months of work in one release. After day 90, rescan after every significant release and at least monthly, keep journey tests running, and add agent checks to your definition of done.
What to do
- Name one owner and agree what done means by day 90.
- Days 1 to 30: run a scan, connect your logs and fix Access.
- Days 31 to 60: fix Readability and Navigability findings.
- Days 61 to 90: test money journeys with real AI agents.
- After day 90: rescan after every significant release.
Read more
How does your own site do?
AgentScore checks your site in about a minute and ranks what to fix first.