Product evaluation

Write agent readiness as a product requirement people can test

Define agent-friendly website requirements, release criteria, ownership and measurement with a worked product brief and staged implementation plan.

AI Product Manager guide: A release decision with evidence. Illustrated example, not a measured result.
Original explanatory graphic. The worked scenario is fictional; it is not a client result or performance claim.

“Support AI agents” is not a requirement a team can estimate or accept. It leaves the user, task, interface and definition of success unspecified. A product manager can make the work concrete by naming one delegated journey and the evidence that will justify shipping it.

The practical answer

Write the requirement around an outcome: a user’s assistant can compare two plans using current public facts, identify an unsupported need and hand the person to the correct page. The technical approach follows from that requirement. A static page may solve the first version; an API may be needed when the underlying data changes frequently.

What to build—and what each layer does

LayerUseful jobWhat it does not establish
Readable, accessible pagesExplain the offer and make the next action understandable.That an agent will interpret every detail correctly.
A short llms.txtProvide a concise map for clients that use it.Permission, universal adoption or a search ranking boost.
Documented read-only dataReturn structured facts for a defined task.That those facts are fresh or safe without maintenance.
Optional MCP integrationExpose capabilities to compatible clients.Automatic discovery, authorization or reliable outcomes.

Choose the layer that solves the observed problem. llms.txt proposal and format describes the file convention; OpenAPI specification describes HTTP API contracts; Model Context Protocol architecture explains MCP’s client/server architecture. These are different responsibilities.

A one-page product brief

Specify the user and delegated task, the authoritative data, what may be read, what may be changed, required approvals, failure states and success evidence. Include excluded capabilities. Assign owners for content, API behavior, security review and ongoing evaluation. Make the review frequency proportional to how often the source information changes.

Worked example: a plan recommendation

Illustrative Team Notes offers individual and team plans. The acceptance set includes a solo user, a team with a supported need and a team requiring an unavailable feature. Passing means the first two receive grounded guidance and the third receives an honest limit. Add a stale-price case and a missing-policy case. An answer that sounds persuasive but invents a capability is a failed test.

Release in stages with explicit gates

Stage one improves the public information and labelled links. Stage two adds a short map and measures discovery. Stage three exposes a read-only interface if the task needs one. Later stages may introduce actions, but only with authorization, review states, recovery and observability. Define proposed thresholds before testing and label them as your team’s decision rules, not an industry standard. Keep a rollback plan for an incorrect source release.

The six-step implementation

Six steps: Name the delegated job: User, need and boundary.; Define the source of truth: Facts and accountable owner.; Write acceptance cases: Include unsupported needs.; Select the smallest interface: Page, API or compatible tool.; Review release evidence: Quality and guardrails.; Maintain the contract: Version and retest changes.
Use the sequence as a working checklist. Each step produces something you can inspect.
  1. Name the delegated job. User, need and boundary.
  2. Define the source of truth. Facts and accountable owner.
  3. Write acceptance cases. Include unsupported needs.
  4. Select the smallest interface. Page, API or compatible tool.
  5. Review release evidence. Quality and guardrails.
  6. Maintain the contract. Version and retest changes.

A short llms.txt you can adapt

This is an illustrative template. Replace every example.com URL with an existing public page on your own domain. Check the content, not just the link. If your site has no public API, leave API instructions out. Do not publish placeholder endpoints, private URLs, access tokens or customer information.

# Team Notes

> Select the appropriate product plan for a stated team need, explain exclusions and identify the next step.

## Useful pages
- [Main information](https://example.com/plans/): The current offering and relevant details.
- [Conditions and process](https://example.com/docs/): Eligibility, limitations and how the process works.
- [Next step](https://example.com/support/): The official route for a person to continue.

## Boundaries
This example does not support automated purchases or bookings.
Use the linked pages for current facts; ask when information is missing.

Serve the file at your site root when your hosting setup supports it. In a typical static build, that means placing it in the directory copied to the public root. Verify the deployed URL: a local file alone is not a published file. If your platform already generates one, inspect and maintain that version instead of creating conflicting instructions.

If you need an API, start with a read

The following is a proposed contract, not an endpoint installed on this site. Choose fields that answer the task, document their types and meaning, and return only information you intend to make public. Include a source URL and an update signal where useful. A checked date records a review; it does not guarantee the underlying data is current.

GET https://example.com/api/v1/services
Accept: application/json

{
  "example": true,
  "checked_at": "2026-11-11",
  "items": [{
    "id": "intro",
    "name": "Introductory service",
    "pricing_basis": "Request a current quote",
    "source_url": "https://example.com/services/",
    "available_actions": ["read_details"]
  }]
}

Define no-result and error behavior as carefully as success. Keep private data behind proper access controls. For future actions that change records or spend money, design authentication, authorization, explicit confirmation and duplicate-action protection separately. OWASP API Security Project provides a useful security review starting point.

A better audit prompt

Use an assistant with browsing or request capabilities. If it cannot access the site, it should report the limitation; a fluent response is not proof of inspection.

Review this public website: [URL]. Task: Select the appropriate product plan for a stated team need, explain exclusions and identify the next step.

Use browsing or request tools if available; if unavailable, say what you cannot verify. Inspect the relevant public pages and /llms.txt. Record the URLs you actually fetched and the facts you found. Do not infer success from a 200 response alone. Separate observed facts, missing information and suggested changes. Do not sign in, submit forms, change data, add to a cart or purchase.

Draft a concise llms.txt using only verified public URLs. Include an API example only if a documented public endpoint exists and its read operation is appropriate to test. Do not invent endpoints. Rank the three most useful fixes by customer impact and effort. Explain how to retest each one.

Test what happened, not what the assistant says happened

TestEvidence to keepA passing result
Retrieve the mapFinal URL, status, content type and response body.The actual text file appears; no login page or application shell.
Follow its linksThe final destination and the relevant source facts.Useful pages resolve and match the stated purpose.
Try the customer taskExact prompt, tool capability, answer and cited URLs.Required facts and next step are correct.
Ask an unsupported questionThe answer and what the source actually says.The assistant names the limit rather than inventing a capability.
Repeat after a changeSource version, date and all attempted runs.Any improvement is reproducible within the tested setup.

Measure for this site’s use case: Acceptance-case pass rate, critical errors, successful handoffs and operational effort. Passing a file-presence scan is insufficient.

Run a baseline before editing. Use fresh sessions and keep the prompt and available tools comparable. Include failed attempts in your denominator. Record whether you explicitly told the agent about llms.txt; that is different from observing spontaneous discovery. A scanner is a diagnostic aid, not a certification.

Avoid the shortcuts that create new problems

  • Do not replace readable pages with machine-only content. People still need to evaluate the offer.
  • Do not treat robots.txt or llms.txt as authentication. Protect private routes with real access controls.
  • Do not tell every crawler it may access everything merely to improve a score.
  • Do not duplicate prices and policies into several files without an update process.
  • Do not claim a successful booking, lead or sale from a generated answer. Verify the actual system result.

For interface implementation, consult Google web.dev: agent-friendly website UX and W3C: labeling form controls. Preserve descriptive controls, meaningful form labels and visible state changes. Agent testing complements human usability and accessibility testing.

Questions worth answering

Will llms.txt improve Google rankings?

No ranking benefit is established by adding this file. Google’s current guidance says it does not use llms.txt for Search visibility. Treat the file as an optional usability aid for clients that consume it; keep ordinary SEO work and task testing separate.

Do I need MCP or Markdown copies of every page?

Not for every project. Start with the smallest interface the task requires. Add Markdown resources or a compatible tool integration when there is a clear consumer and maintenance plan. Check platform support rather than assuming all assistants behave the same way.

Can I use this without coding?

Yes. You can clarify public pages, check links and run the task exercise with your existing website editor and assistant. Publishing a root file depends on the host. A public API requires additional implementation; ask for help if that is outside your skills.

How often should I review it?

Review whenever an offering, policy, route or API contract changes. Assign an owner. Frequently changing prices or stock need stronger freshness controls than a static guide.

Search guidance: Google Search: optimizing for generative AI. Documentation reviewed November 11, 2026. Provider behavior can change; recheck the linked sources when implementing.

Put one improvement to work

Start with this task: Select the appropriate product plan for a stated team need, explain exclusions and identify the next step. Save the baseline, make one justified improvement and keep the retest evidence. Use the result to choose the next useful change.

Explore product decision resources →

Sources and editorial notes

This guide combines primary-source documentation with original implementation advice and a fictional worked example. It is not a report of measured client results, guaranteed traffic or earnings. The examples use reserved example.com URLs and must be adapted and verified before deployment.