What we can do about it

Do what the report says

The steps in a plan are written for a developer to follow, and most of them are an afternoon each. If you have the afternoon, take them: the report is yours and there is nothing held back in it.

If you would rather it were done, we work from what the report already found: nothing is diagnosed twice.

Keep it standing when the agents arrive

This is the one that is not about the score, and it is usually the one that is already hurting. Agent traffic is a load problem before it is a readiness problem, and it arrives before anybody has decided to care about it.

It has its own page, because it deserves an explanation rather than a bullet point.

Build it so this never comes up

The cheapest version of every fix in this census is the one that was never needed: real landmarks, named controls, labelled fields, an llms.txt written when the site was, and a robots.txt that decided something on purpose.

None of that costs anything extra at build time. It costs a great deal to retrofit, which is what the census measures across the whole web every month.

And everything else

This census is published by a development company that does a good deal more than agent readiness. That work is on its own site, in its own words, and it is one link away rather than restated here.