Thai Corner
thaicorner.no is hard for agents to use.
See what an AI agent reads on this site →
34 of 65 points available
agent-readiness level, Not Ready
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.
What to fix first
- No structured data for the business +14 points
Add schema.org JSON-LD for the business (Restaurant, LocalBusiness or the closest type, with name, address, telephone and openingHoursSpecification, plus servesCuisine and acceptsReservations). It is the one block every assistant reads first; the fix kit below has it filled in. How to fix it
- Ordering through an unrecognised third party +9 points
Check that the provider keeps you as the merchant of record. How to fix it
- Menu or price list lives on another site +5 points
The link points to ordera.no, so the credit and the traffic go there. How to fix it
- No llms.txt no points, still worth doing
Optional today, cheap to add: a short text file describing the business for language models. How to fix it
No one is listed yet to fix this in Oslo. List your agency or yourself: free, reviewed by hand.
Already right
- robots.txt lets AI crawlers in No rule blocks the key AI user agents.
- AI crawlers get the page GPTBot, ClaudeBot and PerplexityBot all received a normal response.
Builder: unknown · Front: cloudflare
What to paste
Filled from the business's own record and this scan. Check every line before it goes live; where it goes on your builder is in the guides.
Show the code to paste
Structured data (JSON-LD)
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": "Restaurant",
"name": "Thai Corner",
"url": "https://thaicorner.no/",
"telephone": "+47 979 59 311",
"geo": {
"@type": "GeoCoordinates",
"latitude": 59.9254107,
"longitude": 10.775141
},
"openingHours": "Mo-Fr 14:00-21:00; Su 14:00-21:00",
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": [
"Monday",
"Tuesday",
"Wednesday",
"Thursday",
"Friday"
],
"opens": "14:00",
"closes": "21:00"
},
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": [
"Sunday"
],
"opens": "14:00",
"closes": "21:00"
}
],
"servesCuisine": [
"thai"
],
"hasMenu": "https://thaicorner.ordera.no/"
}
</script>
llms.txt
Save as /llms.txt at the root of the site. Guide.
# Thai Corner > restaurant (thai) in Oslo. Phone +47 979 59 311. ## Book or order directly - Menu: https://thaicorner.ordera.no/ ## Opening hours Mo-Fr 14:00-21:00; Su 14:00-21:00 ## About - Website: https://thaicorner.no/ - This file follows llms.txt (https://llmstxt.org): a short plain-text description for language models.
How Thai Corner compares
245 of 436 in Oslo
Top 56% of the sites scanned in this index. Just above: Anatolia D, Koi Sushi D. Just below: Café Sara D, Hells Kitchen D.
| What the top tenth of the index does | Top 10% | This site |
|---|---|---|
| Take bookings or orders on their own domain | 89% | no |
| Publish the menu or price list as HTML | 51% | no |
| Let AI crawlers in (no edge block, no robots.txt block) | 91% | yes |
| Structured data with address, phone and hours | 38% | no |
| Have an llms.txt | 13% | no |
The top tenth is the 45 best-scoring reachable sites of the index at the last refresh.
Nearest places with a similar menu
| Place | Distance | Grade | Direct booking or ordering |
|---|---|---|---|
| Pao Bar & BBQ thai | 1.1 km | B | yes |
| Apsorn Thai Restaurant thai | 1.3 km | C | yes |
| Tuk Tuk Thai thai | 2.0 km | D | no |
| Risbolle thai | 2.3 km | D | no |
| Kinnara thai | 2.4 km | B | yes |
| Sukhumvit Soup&Grill thai | 3.1 km | D | no |
| Yaya’s thai | 3.3 km | B | no |
Businesses like Thai Corner in Oslo
| Group | Sites | Avg score | A or B | This site |
|---|---|---|---|---|
| Same kind in Oslo | 436 | 53% | 17% | 52.3% |
The best of Same kind in Oslo
Ugly Duckling A 100% · BA3 A 93.8% · Jaipur A 90% · Yo! Sushi A 90% · Curry & Ketchup A 88.8%
The climb
With the three fixes above (No structured data for the business; Ordering through an unrecognised third party; Menu or price list lives on another site) the score would be about 95.4%: 2nd of 436 in Oslo, up from 245th.
Peers are the businesses of the same index with a reachable site, latest scan of each; the rank uses the index's current ranking.
What assistants answer
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.
Own this business?
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.
Rescan now · Markdown · Dispute a check
Deep report Ten questions the way people ask, each assistant's full answer, the eight nearest similar places, the fix plan and a PDF: 19 EUR, one-off.
Send the fixes to your web person
Show the score
Owners who score well embed the badge; it links back here and updates with every scan.
<a href="https://directindex.org/r/thaicorner.no"><img src="https://directindex.org/badge/thaicorner.no.svg" alt="Agent-Direct Score D" width="236" height="40"></a>
What agents get, and what the site publishes
The direct record an agent is served for this business, the rails it could transact through, and the agent standards the site publishes.
Show the details
What agents get for Thai Corner
The links an assistant is sent when it books, orders or reads the menu for this business, where each leads, and when a browser last checked it. The same record is served as JSON at /api/direct/thaicorner.no, through the MCP tool direct_record and in the city feed /city/oslo/direct.json.
| Path | Link | Status |
|---|---|---|
| Book | none on record | |
| Order | none on record | |
| Menu | thaicorner.ordera.no/ external | from the scan |
| Hours | Mo-Fr 14:00-21:00; Su 14:00-21:00 (closed now) | from OpenStreetMap |
| Phone | +47 979 59 311 |
Stable links that count: /go/thaicorner.no/menu answer 302 to the links above; the count is the line "followed N direct links" on this page.
Owners: claim the business below to correct this record; the claim email carries the link.
Can an agent transact?
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.
Level 0 of 5, Not Ready
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 | no how |
| 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 | no |