foresteract.com is hard for agents to use.
Some AI assistants are turned away by the website of foresteract.com. It finds no menu or price list, so it answers from other sites. It finds no link to book or order online, only a phone number.
See what an AI agent reads on this site →
29.3 of 65 points available
agent-readiness level, Basic Web Presence
things to fix
Provisional: the action test and the assistant citation check still to come; the hatched part of the bar is not measured yet.
Each assistant is asked three questions about this business: the official website, where to book, where to order. The cell says where the answer sent people.
Not asked yet. Assistants are asked about the top-ranked businesses in each city index, and about every claimed business the moment it is claimed; claim this page to be included.
Only a phone number or WhatsApp, which agents cannot use yet. If you take bookings or orders through a platform, link to it from the site so an agent can find it. Add a booking or ordering page. How to fix it
Agents answer 'what do they offer' from marketplaces instead. Add a menu or price list page and link it from the homepage. How to fix it
Live fetches as GPTBot (http_403), ClaudeBot (http_403) were refused while a normal browser got the page. This is usually a hosting or firewall bot list the owner never chose. Ask the host to allow these user agents. How to fix it
Missing: address, telephone, opening hours. How to fix it
Optional today, cheap to add: a short text file describing the business for language models. How to fix it
Builder: wordpress · Front: cloudflare · Cloudflare in front; AI crawlers blocked at the edge
Filled from the business's own record and this scan. Check every line before it goes live; where it goes on wordpress is in the guides.
Where to paste it on WordPress: a plugin that adds code to every page's header, such as WPCode (Insert Headers and Footers), in its Header box. the official help page.
One block in the page's head, or in the builder's custom-code slot. Replace anything that is wrong. Guide.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "KOITOTO TOGEL",
"url": "https://demolehopest.com/",
"telephone": "+6221123456777"
}
</script>
Save as /llms.txt at the root of the site. Guide.
# KOITOTO TOGEL > organization. Phone +6221123456777. ## About - Website: https://demolehopest.com/ - This file follows llms.txt (https://llmstxt.org): a short plain-text description for language models.
Fixed something, or think a check is wrong? Rescans are free. Claiming takes one email to confirm; after that the three assistants are asked about the business right away, the site is rescanned weekly, and you get a message only when the score changes.
The direct record an agent is served for this business, the rails it could transact through, and the agent standards the site publishes.
No direct path on record: the scan of 2026-10-14 found no booking or ordering link on foresteract.com or on a vendor's site. The same record is served as JSON at /api/direct/foresteract.com, through the MCP tool direct_record.
| Path | Link | Status |
|---|---|---|
| Book | none on record | |
| Order | none on record | |
| Menu | none on record | |
| Hours | none on record | |
| Phone | +6221123456777 |
Owners: claim the business below to correct this record; the claim email carries the link.
Measured, not scored: the Agent-Direct Score stays at specification v1.0. This says which rails an agent could transact through today, and what the booking or ordering vendor's terms allow.
| UCP profile /.well-known/ucp, Google and Shopify's Universal Commerce Protocol | not measured |
| ACP discovery document /.well-known/acp.json, OpenAI and Stripe's Agentic Commerce Protocol | not measured |
| MCP server card /.well-known/mcp/server-card.json | no |
| Ordering vendor that takes agent orders Square, Toast, or a vendor whose terms allow agents | not measured |
Not measured at this scan; the next scan measures it.
The next scan also reads the contact, menu and booking pages one hop deeper; facts found there can change the score.
The standards an agent looks for before it reads a page, on the same criteria as Cloudflare's Agent Readiness scan. Not part of the score; each missing item links to a how-to. Cloudflare's report.
| Link headers on the homepage | no how |
| sitemap.xml | yes |
| AI bot rules in robots.txt | yes |
| Content Signals in robots.txt | no how |
| Markdown on Accept: text/markdown | no how |
| llms.txt | no how |
| API catalog (RFC 9727) | no how |
| MCP server card | no how |
| A2A agent card | no how |
| Agent Skills index | no how |
| OAuth or OIDC discovery | no how |
| OAuth protected resource metadata | no how |
| auth.md | no how |
| Web Bot Auth key directory | no how |
| ARD capability manifest | no how |
| DNS-AID records | no how |
| WebMCP tools on the page | no how |
| JSON-LD for the business | yes |