godaddy.com
The website's grade
Some AI assistants are turned away by godaddy.com's website. It can't find a menu or price list, so it answers from other sites. It can't find a link to book or order online.
23 of 65 points available
agent-readiness level, Not Ready
things to fix
Provisional, with the action test and the assistant citation check still to come. The hatched part of the bar isn't measured yet.
What assistants answer
Each assistant gets three questions about this business: the official website, where to book and where to order. Each cell shows where the answer sent people.
The assistants haven't been asked about this business yet. They're asked about the top-ranked businesses in each city index, and about any business as soon as it's claimed. Claim this page to be included.
How godaddy.com compares
What to fix first
- No booking or ordering link on the website +15 points
There's no link on the site for an agent to follow. If you take bookings or orders through a platform, link to it from the site so agents can find it. Add a booking or ordering page on your own domain. How to fix it
- The server turns AI crawlers away at the door +10 points
Requests as GPTBot (challenge:access denied), ClaudeBot (challenge:access denied), PerplexityBot (challenge:access denied) were refused, but a normal browser got the page. That's usually a bot list at the host or in a firewall that the owner never chose. Ask the host to allow these user agents. How to fix it
- Structured data is incomplete +7 points
Missing: address, telephone, opening hours. How to fix it
- No menu or price list found +7 points
Agents answer 'what do they offer?' from marketplaces instead. Add a page with the menu or price list and link to it from the homepage. How to fix it
- No llms.txt no points, but worth doing
Optional for now and cheap to add. It's a short text file that describes the business for language models. How to fix it
Already right
- robots.txt lets AI crawlers in No rule blocks the main AI user agents.
- Structured data found (Organization) no address, phone or hours in it
Builder: godaddy · Front: cloudflare · Cloudflare in front; AI crawlers blocked at the edge
What to paste
Filled in from the business's own record and this scan. Check every line before it goes live. The guides show where it goes on godaddy.
Show the code to paste
Structured data (JSON-LD)
Paste it as one block in the page's head, or in the builder's custom code box. Change anything that's wrong. Guide.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "GoDaddy",
"url": "http://www.restaurantmediterrani.com/"
}
</script>
llms.txt
Save as /llms.txt at the root of the site. Guide.
# GoDaddy > organization. ## About - Website: http://www.restaurantmediterrani.com/ - This file follows llms.txt (https://llmstxt.org): a short plain-text description for language models.
Own this business?
If you fixed something or think a check is wrong, rescan. Rescans are free. Claiming takes one email to confirm. After that, the three assistants are asked about the business right away and the site is rescanned every week. You get a message only when the score changes.
What agents get, and what the site publishes
The direct record agents get for this business, the rails an agent could transact through, and the agent standards the site publishes.
Show the details
What agents get for GoDaddy
No direct path on record: the scan of 2026-10-20 found no booking or ordering link on godaddy.com or on a vendor's site. The same record is served as JSON at /api/direct/godaddy.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 | none on record |
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 | no |
| ACP discovery document /.well-known/acp.json, OpenAI and Stripe's Agentic Commerce Protocol | no |
| 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 | no |
Level 0 of 5, Not Ready
These are the standards an agent looks for before it reads a page, checked the same way as Cloudflare's Agent Readiness scan. They don't count toward 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 | no how |
| 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 |