Web 101Agents on the Web

Make your site easier to use.

Clear facts. Clear actions. Confirmed results.

Example · Booking a class

“Find a 7am class in SoHo.”

The person approves the booking.

studio.example/classesDemo

FORM STUDIOSoHo · Tomorrow

Find your next class.

7:00 amStrength · 45 min

Select class ↗

6:00 pmStrength · 45 min

Select class ↗

Demo only. No booking is made.

Three things your site needs

Information

Answers people can find.

Publish prices, availability, delivery times, and product details as readable text.

Actions

Buttons that say what they do.

“Book the 7am class” is clearer than an unlabeled icon.

Confirmation

A visible result.

After an action, show what changed and whether it succeeded.

A small detail can change the answer.

“Does this lamp come in warm white?”

Table lamp

The photo doesn’t tell you the light temperature.

Missing product detail

Product facts

Answer the shopper’s real question.

“A backpack for cycling to work in the rain?”

Give useful facts.

Capacity, laptop size, weight, strap stability, water resistance, and what the warranty covers.

Be clear about limits.

Water-resistant is not waterproof. Describe tested conditions; link the evidence.

Keep the page easy to read.

Put a short summary first. Keep exact specs and use cases in clearly labeled details.

Share the same facts with agents.

Use product structured data or a current catalog feed. APIs and connectors can expose facts and authorized actions without navigating every screen.

Example facts to publish

{
  "name": "Commuter backpack",
  "capacity_liters": 20,
  "laptop_max_inches": 15,
  "water_resistance": "Splash-resistant; not submersible",
  "rain_test_source": "https://brand.example/testing",
  "recommended_use": ["Urban commuting", "Light rain"],
  "availability": "in_stock",
  "updated_at": "2026-10-11T09:00:00Z"
}

Fictional example, not a standard schema. Use a supported product schema for discovery and document any custom feed fields.

SEO & agent access

Good pages help. Integrations add another route.

Clear descriptions, accurate specs and availability help people, search engines and agents. A structured feed can make those facts easier to retrieve. An MCP or API only helps agents that support and discover it; it does not guarantee a recommendation.

See retailer agent-access rankings ↗ · Deep Agentic Rubric ↗

About the benchmark & further reading

The basic score checks public HTML across at least five pages. It doesn’t run the browser task shown here or verify checkout.

How browser agents use screenshots and page structure ↗