GEO-Bericht: www.lloretdemar.org
Gesamt
Crawlbarkeit
Semantisches HTML
Strukturierte Daten
Aktualität
JS-Abhängigkeit
KI-Agent-Bereitschaft
Vertrauenssignale
Extrahierbarkeit
KI-Simulation
Crawlbarkeit
Robots.txt
robots.txt gefunden
Erlaubte Bots: GPTBot, Google-Extended, PerplexityBot, Amazonbot, ClaudeBot, Bytespider
Sitemap
Sitemap gefunden
URLs: 543 | Hat lastmod: Nein
Semantisches HTML
Seitensignale
https://www.lloretdemar.org/
| H1-Anzahl | 2 |
| H2-Anzahl | 39 |
| H3-Anzahl | 8 |
| Semantisches Verhältnis | 0,05 |
Landmarks
- nav: Fehlend
- main: Fehlend
- footer: Fehlend
- header: Vorhanden
- article: Fehlend
- section: Vorhanden
Multiple H1 tags found (2)
Found 2 <h1> elements on the page
Lösung: Use a single H1 per page for clear content hierarchy.
No <main> landmark
Page lacks a <main> element
Lösung: Wrap primary content in a <main> element to help AI understand page structure.
Low semantic HTML usage
Semantic ratio: 0.05 (14 semantic tags vs 280 divs)
Lösung: Replace generic <div> elements with semantic HTML5 tags (article, section, aside, etc.).
No <nav> landmark
Page lacks a <nav> element
Lösung: Use <nav> for navigation sections.
Strukturierte Daten
Erkannte Schema-Typen
https://www.lloretdemar.org/
BreadcrumbList, EntryPoint, ImageObject, ListItem, Organization, PropertyValueSpecification, ReadAction, SearchAction, WebPage, WebSite
Aktualität
Aktualitäts-Signale
https://www.lloretdemar.org/
| Last-Modified Header | — |
| Zeitangaben-Tags | 0 |
| Aktualisierungshinweise | 0 |
No freshness signals detected
No Last-Modified header, <time> tags, or date phrases found
Lösung: Add date metadata: use <time datetime=''> tags, Last-Modified headers, and sitemap <lastmod> entries.
JS-Abhängigkeit
Seitenstatus
https://www.lloretdemar.org/
JS-abhängig: Nein
KI-Agent-Bereitschaft
Endpunkt-Erkennung
| Typ | URL | Status |
|---|---|---|
| feed | https://www.lloretdemar.org/feed | 200 |
Feeds & APIs
| OpenAPI/Swagger | Nein |
| MCP-Manifest | Nein |
| OIDC-Discovery | Nein |
| RSS-/Atom-Feeds | 1 gefunden |
CTA & Bot-Zugang
| CTAs gefunden | 3 |
| Deep-linkfähig | 2 |
| Nur JS | 1 |
| Bot-Wall erkannt | Nein |
1 feed(s) detected
Feed types: feed
Lösung: Great! RSS/Atom feeds help AI systems track content updates.
Vertrauenssignale
Pflichtseiten
| About | Fehlend |
| Terms | Fehlend |
| Contact | Gefunden |
| Imprint | Gefunden |
| Privacy | Fehlend |
Kontaktinformationen
| Ja (central-turisme@lloret.cat) | |
| Telefon | Ja (17899974393493580, 17932041963353935, 17943629382252855, 18068761544709961, 18100187852587575) |
| Adresse | Nein |
Organisation-Schema
| Org-Schema vorhanden | Ja |
| Name konsistent | Nein |
| Logo lädt | Ja |
No about page found
No link to an About/Company/Team page detected
Lösung: Add an About page to establish organizational identity. AI systems use this to build entity profiles.
No privacy policy found
No link to a Privacy/Datenschutz page detected
Lösung: Add a Privacy Policy page. Required by GDPR and signals trustworthiness.
Organization name inconsistency
Organization schema name does not match title, og:site_name, or visible brand text
Lösung: Ensure the Organization schema 'name' matches your visible brand name across the site.
Inhalts-Extrahierbarkeit
Analyse pro Seite
https://www.lloretdemar.org/
| Hauptinhalt Zeichen | 8341 |
| Hauptinhalt-Anteil | 40% |
| Link-Dichte | 39% |
| Überschriften pro 1000 Wörter | 47,97 |
| Max. Überschriften-Abstand (Wörter) | 623 |
| Durchschn. Absatzlänge | 19 Wörter |
| Dünner Inhalt | Nein |
High link density in main content
Link density: 39% of main text is inside anchor tags
Lösung: Reduce excessive links within main content. High link density looks like a link farm to AI systems.
KI-Simulation
Halluzinationsrisiko
MEDIUM — Durchschnittliche Konfidenz: 35%
Fragen-Analyse
| Frage | Konfidenz | Nachweis | Fehlend |
|---|---|---|---|
| What does this company/site do? | 100% | Escull amb qui vols venir i et proposem mil opcions per gaudir a fons de … | — |
| What are the products/services? | 0% | Unknown | Product/Service schema, dedicated /products/ or /services/ page |
| How much does it cost? | 0% | No pricing found | Pricing information (currency patterns, /pricing page) |
| How to contact them? | 70% | Email address found; Phone number found | — |
| Where are they located? | 0% | No location found | Physical address or LocalBusiness schema with address |
| What are the policies? | 40% | Policy language found in page content | — |
AI cannot determine pricing
No pricing patterns found on any page
Lösung: Add a /pricing page or include pricing information in HTML (not just PDFs).
AI cannot determine your location
No physical address or LocalBusiness schema with address
Lösung: Add a physical address and LocalBusiness JSON-LD with address.