degema.pt is partly visible to agents.
Listed by OpenStreetMap · Overture Maps.
Book directly: degema.pt/reservas/ on the business's own site · Order directly: degema.pt/takeaway/ on the business's own site · Menu: degema.pt/menu/
See what an AI agent reads on this site →
37 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.
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
Live fetches as GPTBot (http_406), ClaudeBot (http_406), PerplexityBot (http_406) 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
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 Porto. List your agency or yourself: free, reviewed by hand.
Builder: wordpress · Front: cloudflare · contact page /about/: nothing new; menu page /menu/: 70 prices; booking page /reservas/: nothing new; 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.
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": "DeGema Hamburgueria",
"url": "http://www.degema.pt",
"telephone": "+351 223 227 432",
"address": {
"@type": "PostalAddress",
"streetAddress": "Rua do Almada 249",
"postalCode": "4050-038",
"addressLocality": "Porto"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": 41.1488303,
"longitude": -8.6122052
},
"servesCuisine": [
"burger"
],
"acceptsReservations": "https://degema.pt/reservas/",
"hasMenu": "https://degema.pt/menu/",
"potentialAction": [
{
"@type": "ReserveAction",
"target": {
"@type": "EntryPoint",
"urlTemplate": "https://degema.pt/reservas/",
"actionPlatform": [
"http://schema.org/DesktopWebPlatform",
"http://schema.org/MobileWebPlatform"
]
},
"result": {
"@type": "Reservation",
"name": "Reservation"
}
},
{
"@type": "OrderAction",
"target": {
"@type": "EntryPoint",
"urlTemplate": "https://degema.pt/takeaway/",
"actionPlatform": [
"http://schema.org/DesktopWebPlatform",
"http://schema.org/MobileWebPlatform"
]
}
}
]
}
</script>
Save as /llms.txt at the root of the site. Guide.
# DeGema Hamburgueria > restaurant (burger) in Rua do Almada 249 4050-038 Porto, Porto. Phone +351 223 227 432. ## Book or order directly - Book: https://degema.pt/reservas/ (on the business's own site) - Order: https://degema.pt/takeaway/ (on the business's own site) - Menu: https://degema.pt/menu/ ## About - Website: http://www.degema.pt - This file follows llms.txt (https://llmstxt.org): a short plain-text description for language models.
Top 42% of the sites scanned in this index. Just above: Vicios de Mesa (Maus Hábitos) C, Deli Deli C. Just below: Domo Domo C, LI JIN C.
| What the top tenth of the index does | Top 10% | This site |
|---|---|---|
| Take bookings or orders on their own domain | 98% | yes |
| Publish the menu or price list as HTML | 86% | yes |
| Let AI crawlers in (no edge block, no robots.txt block) | 88% | no |
| Structured data with address, phone and hours | 28% | no |
| Have an llms.txt | 36% | no |
The top tenth is the 50 best-scoring reachable sites of the index at the last refresh.
| Average score | A or B | This site | |
|---|---|---|---|
| Sites built with WordPress 36,926 sites | 58% | 29% | 56.9% |
| Place | Distance | Grade | Direct booking or ordering |
|---|---|---|---|
| Burger King burger | 251 m | F | no |
| Noshi breakfast, regional, burger, asian | 431 m | D | no |
| MBH burger | 452 m | C | no |
| Brusco burger | 494 m | C | no |
| BAO'S burger | 558 m | F | no |
| Tio Fafá Hamburgueria burger | 716 m | C | yes |
| Curb burger | 766 m | F | no |
| Real Hamburgueria Portuguesa burger | 774 m | C | yes |
| Holy Sandwich Shop burger | 781 m | B | yes |
| Boulevard Burger House burger, fast_food | 890 m | F | yes |
| Group | Sites | Avg score | A or B | This site |
|---|---|---|---|---|
| Same kind in Porto | 492 | 50% | 26% | 56.9% |
| Built with WordPress in Porto | 187 | 63% | 42% | 56.9% |
Taberna Asiática A 100% · Gastro by Elemento A 95.4% · Ristorante Toscano A 95.4% · O Gaveto A 91% · Restaurante Churrasqueira A Brasa A 91%
With the two fixes above (No structured data for the business; The server turns AI crawlers away at the door) the score would be about 95.4%: 5th of 492 in Porto, up from 205th.
Peers are the businesses of the same index with a reachable site, latest scan of each; the rank uses the index's current ranking.
Each assistant was asked the way people ask, with web search on, for up to three places in Porto and a link to each one's own site. This business was named in one answer, by 1 of the 3 assistants asked.
| Question | Named by | Asked |
|---|---|---|
| Best burger in town, and I want to order online. | Gemini with a link to this site | 2026-10-14 |
Every place named in Porto, question by question.
The badge says how many of the assistants asked named this business, with the month; it updates with every round.
<a href="https://directindex.org/r/degema.pt"><img src="https://directindex.org/badge/named/degema.pt.svg" alt="Named by 1 of 3 assistants, Direct Index" width="300" height="40"></a>
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.
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.
The direct record an agent is served for this business, the rails it could transact through, and the agent standards the site publishes.
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/degema.pt, through the MCP tool direct_record and in the city feed /city/porto/direct.json.
| Path | Link | Status |
|---|---|---|
| Book | degema.pt/reservas/ own site | found by the scan of 2026-10-15, not yet tested |
| Order | degema.pt/takeaway/ own site | found by the scan of 2026-10-15, not yet tested |
| Menu | degema.pt/menu/ html_page | from the scan |
| Hours | none on record | |
| Phone | +351 223 227 432 |
Stable links that count: /go/degema.pt/book, /go/degema.pt/order, /go/degema.pt/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.
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 |
Found one hop past the home page: menu page /menu/: 70 prices.
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 | no |