Portuk

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.

What to fix first

1. The site turns every visitor without a browser away, AI agents included +25 points

   A plain fetch was refused (http_403); only a real browser got the page. Every AI crawler and agent is turned away the same way, so Reachable scores 0 and the rest is measured on the rendered page. Ask the host to let the AI user agents through. How to fix it

2. No structured data for the business +15 points

   Add schema.org JSON-LD for the business (TouristAttraction, Museum, TravelAgency or the closest type, with name, address, telephone and openingHoursSpecification). It is the one block every assistant reads first; the fix kit below has it filled in. How to fix it

3. No tickets and prices found +7 points

   Agents answer 'what does it cost and when' from marketplaces instead. Add a page with tickets, times and prices as text and link it from the homepage. How to fix it

Send the fixes to your web person

No one is listed yet to fix this in Porto tours, attractions and museums. List your agency or yourself: free, reviewed by hand.

Already right

• robots.txt lets AI crawlers in There is no robots.txt, which allows everything.
• Tickets through bokun on your own domain No marketplace commission, and the guest stays yours.
• Bókun works with agents through its partners Bókun lists no traveller terms; its API terms have no bot clause and let developers use the API only to build applications for a vendor's use under a Bókun partner or services agreement. Read 2026-10-15: https://www.bokun.io/legal/api-terms. An assistant that is not a partner may not finish the step there; a direct path on your own domain works for all of them.

Builder: duda · Front: cloudflare · A plain fetch got http_403; a real browser got the page, so the scan continues on the rendered page.

What to paste

Filled from the business's own record and this scan. Check every line before it goes live; where it goes on duda is in the guides.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Portuk",
  "url": "http://www.portuk.pt/",
  "telephone": "+351915502100",
  "address": "Av. da França 256 Loja 17, 4050-276, Porto",
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": 41.16122755,
    "longitude": -8.62798452
  },
  "potentialAction": [
    {
      "@type": "ReserveAction",
      "target": {
        "@type": "EntryPoint",
        "urlTemplate": "https://bokun.io/terms/",
        "actionPlatform": [
          "http://schema.org/DesktopWebPlatform",
          "http://schema.org/MobileWebPlatform"
        ]
      },
      "result": {
        "@type": "Reservation",
        "name": "Reservation"
      }
    }
  ]
}
</script>