Forma Studio and all results here are illustrative. Explore the findings, build a scope, and download the sample report. Changes in this preview are temporary.
Agent experience
A foundation to build on
The readiness breakdown
SampleOverview
The executive view
Clarity for your next conversation.
The core service pages are readable, with opportunities to make commercial facts and the quote journey clearer. Start with the observable content gaps, then verify the structured action in a compatible browser. This report uses illustrative data.
Request a quote
A practical next step
Start with the evidence.
Review each finding, select the work that matters, and prepare a scope your client can understand.
Review recommendationsFindings
5 recommendationsMake commercial facts easier to interpret
medium prioritymedium effortObserved evidenceIn scope
Make commercial facts easier to interpret
What we observed
No JSON-LD blocks were observed on https://example.com.
https://example.com/services: 0 JSON-LD blocks observed.
https://example.com/contact: 0 JSON-LD blocks observed.
https://example.com ↗Why it matters
Agents may need to infer the offering and its details from page text. Clear structured facts can make comparisons more consistent.
Recommended implementation
Select the schema types that match the actual page, such as Service, Product or Organization. Describe only facts present in the visible content; use explicit names, URLs and applicable offer details.
How to verify
Validate the markup, rescan the same pages, and compare extracted names and commercial details with the visible page. Presence alone does not establish correctness or ranking benefits.
Verify the detected WebMCP tools in a compatible browser
medium prioritysmall effortObserved evidence
Verify the detected WebMCP tools in a compatible browser
What we observed
https://example.com/contact: declarative annotation for “request_quote” — Prepare a project quote request using the customer’s service requirements.
https://example.com ↗Why it matters
Source annotations suggest an agent interaction surface, but this scan does not establish that tools are available or that the journey works.
Recommended implementation
Open the relevant page in a WebMCP-compatible browser and inspect document.modelContext.getTools(). Review names, descriptions and inputs. Test an agreed read-only scenario before proposing further actions.
How to verify
Record browser/API version, page state and returned tool metadata. Keep registration evidence separate from any explicit task-execution result.
Give the quote form clear field labels, required-field guidance, and a useful confirmation message.
medium prioritymedium effortModel suggestion
Give the quote form clear field labels, required-field guidance, and a useful confirmation message.
What we observed
Model-generated recommendation from the stored AX analysis. Validate on the affected page before including it in the implementation scope.
https://example.com ↗Why it matters
Review whether this recommendation addresses a real barrier to: Request a quote. Commercial impact has not been measured.
Recommended implementation
Give the quote form clear field labels, required-field guidance, and a useful confirmation message.
How to verify
Confirm the issue manually on the relevant page, capture baseline evidence, and repeat the same scenario after implementation. Record an unresolved result if the barrier remains.
Explain the service scope and quote requirements beside the primary contact action.
medium prioritymedium effortModel suggestion
Explain the service scope and quote requirements beside the primary contact action.
What we observed
Model-generated recommendation from the stored AX analysis. Validate on the affected page before including it in the implementation scope.
https://example.com ↗Why it matters
Review whether this recommendation addresses a real barrier to: Request a quote. Commercial impact has not been measured.
Recommended implementation
Explain the service scope and quote requirements beside the primary contact action.
How to verify
Confirm the issue manually on the relevant page, capture baseline evidence, and repeat the same scenario after implementation. Record an unresolved result if the barrier remains.
Evaluate a simpler representation of key content
low prioritymedium effortOpportunity
Evaluate a simpler representation of key content
What we observed
An Accept: text/markdown, text/plain request returned text/html.
https://example.com ↗Why it matters
A simpler representation may reduce parsing work for compatible agents. Semantic, accessible HTML remains useful on its own.
Recommended implementation
First review the existing HTML with the target agent. If parsing is a barrier, offer an equivalent Markdown response for content pages and preserve canonical URLs and commercial details.
How to verify
Request both HTML and Markdown, compare facts and links, and set Vary: Accept correctly if negotiation is implemented.
WebMCP
A clearer way for agents to act.
WebMCP exposes structured actions from a website to compatible browser agents. This assessment separates source evidence, registered tools, and completed tasks.
Implementation evidence
Source detected
Runtime inspection
not tested
Task execution
Not tested
WebMCP is assessed separately and does not affect the AX score. Missing support is an opportunity to evaluate, not a universal failure.
Observed tools
request_quoteForm annotationPrepare a project quote request using the customer’s service requirements.
https://example.com/contact
Coverage matters
https://example.com/contact
Initial public quote form
Illustrative form annotation. Registration and task completion have not been tested.
WebMCP is an experimental enhancement and does not affect this AX score.
Understand WebMCP and implementation optionsImplementation
A scope your client can act on. Selected work items, estimates, and implementation status.
Make commercial facts easier to interpret
Select the schema types that match the actual page, such as Service, Product or Organization. Describe only facts present in the visible content; use explicit names, URLs and applicable offer details.
Verification criteria
Validate the markup, rescan the same pages, and compare extracted names and commercial details with the visible page. Presence alone does not establish correctness or ranking benefits.
“Implemented” records your agency’s update. A fresh audit and the same agreed scenario are needed to verify improvements.
Evidence
Behind the assessment
Observed signals are evidence of individual checks. They do not establish that an agent can complete a purchase, booking, or enquiry.
Scan coverage
https://example.com
https://example.com/services
https://example.com/contact
Timestamp: 2026-09-01T10:00:00Z. Other pages, sessions, and interactive states may differ.