🧬 Structured Data & Schema 49
JSON-LD blocks found: 4
Schema types: BreadcrumbList, Product, OnlineStore, ProductGroup
!
Only 2 GEO-critical schema type(s)
Found: Product, BreadcrumbList. Consider adding: FAQPage, HowTo, Article, BreadcrumbList
!
Schema validation: 6 issue(s)
Required properties are missing or values are invalid
  • Organization: missing url
  • Organization: missing url
  • Organization: missing url
  • Organization: missing url
  • Organization: missing url
  • Organization: missing url
!
Schema completeness: 12 recommendation(s)
Several recommended properties are missing
  • Product: consider adding review, aggregateRating
  • Organization: consider adding logo, description, sameAs, contactPoint, address
  • Organization: consider adding logo, description, sameAs, contactPoint, address
  • Person: consider adding url, sameAs, jobTitle, image
  • Person: consider adding url, sameAs, jobTitle, image
  • Person: consider adding url, sameAs, jobTitle, image
  • Product: consider adding brand, review, aggregateRating
  • Organization: consider adding logo, description, sameAs, contactPoint, address
Rich nested schema (depth: 5)
Nested entities improve LLM understanding of relationships
i
No Speakable schema
Consider adding speakable property for voice/LLM readiness
sameAs links found
Helps LLMs disambiguate entities
i
RDFa markup detected
JSON-LD is preferred for LLM consumption
🏗️ Semantic HTML 85
Single H1 tag found
"Hoya (Wasbloem) Flamingo Dream 'Star of Java'"
Heading hierarchy is logical (11 headings)
No skipped levels detected
Rich semantic HTML (5 tag types)
: 1, : 10, : 4, : 1, : 1
Single element found
Agents can identify primary content area
i
No elements
Use for publish/update dates
Text-to-HTML ratio: 0%
Very low - content may be JS-rendered or buried in markup
Word count: 441
Sufficient content depth for LLM extraction
i
Reading level: moderate (Flesch: 31)
Content may be complex - consider simplifying for broader LLM coverage
Accessibility for Agents 82
Language declared: "nl"
Agents know what language to expect
!
No skip-to-content link
Add a skip link at the top of the page for accessibility and agent navigation
All 94 images have alt attributes
94 descriptive, 0 decorative (empty alt)
Implicit landmarks via semantic HTML
Semantic elements provide landmark equivalents
!
Link text issues: 1 empty/unlabeled
Use descriptive anchor text for agent comprehension
  • /nl
!
1 unlabeled form input(s)
Add labels for agent-driven form interaction
  • quantity
Interactive elements are keyboard-accessible
No tabindex="-1" on interactive elements, no non-focusable click handlers
🔗 Internal Linking 65
Internal links: 78
Good internal link density for crawling
Navigation elements: 4
Agents can identify site navigation
i
No breadcrumb navigation detected
Add breadcrumbs for hierarchical context (great for LLM citations)
i
No in-page anchor links
A table of contents helps agents find specific sections
i
External links: 24
External links to authoritative sources build credibility
!
2 internal link(s) with weak anchor text
Use descriptive anchor text for better agent comprehension
Page has navigation and footer links
Page is well-connected to site structure
🔍 Meta & Discoverability 88
!
Title tag: 72 chars (too long)
"Hoya Flamingo Dream 'Star of Java' M (Wasbloem) online kopen | Example.c..."
Meta description: 145 chars
"Maak kennis met onze schattige babyplantjes, exclusieve planten en mooie huiskam..."
Canonical URL set
https://example.com/nl/product/hoya-flamingo-dream-star-of-java-m
Open Graph tags: 8
og:title, og:description, og:url, og:site_name, og:locale, og:image, og:image:alt, og:type
Twitter Card tags: 5
i
No hreflang tags
Add if content is available in multiple languages/regions
Viewport meta tag set
🤖 Machine Readability 85
Substantial content in DOM (2951 chars)
Content appears server-rendered or hydrated
Robots meta: indexable
"index, follow"
No AI bot restrictions in meta
No specific bot blocking detected in page HTML
AI crawlers allowed in robots.txt
No disallow rules for GPTBot, ClaudeBot, PerplexityBot, CCBot, or Google-Extended; sitemap referenced
No X-Robots-Tag restrictions
Response headers place no noindex/noai limits on AI systems
i
No llms.txt found
Consider publishing /llms.txt to point LLM crawlers at your key pages (nice to have, not a ranking factor yet)
i
No Content-Signal directive in robots.txt
Add a Content-Signal directive to declare search / ai-input / ai-train usage preferences for AI crawlers
i
No HTTP Link discovery headers
Expose resources via the Link response header (rel="describedby", api-catalog, sitemap, mcp) so agents discover them without parsing HTML
i
No Markdown source endpoint
Advertise a .md version of the page via <link rel="alternate" type="text/markdown"> for clean agent ingestion
i
No llms-full.txt
Publish /llms-full.txt, a concatenated Markdown corpus of your llms.txt pages, for full-context AI ingestion
i
No RSS/Atom/JSON feed discovered
Expose a feed via <link rel="alternate"> as a machine-readable content stream
i
No RSL licensing manifest
Publish RSL terms via /license.xml, a robots.txt License: directive, or <link rel="license"> to set machine-readable AI license/royalty terms (Really Simple Licensing)
i
IndexNow not detected
Adopt IndexNow to instantly push new/updated URLs to Bing/Yandex/Naver; Bing's index feeds ChatGPT Search, Copilot and Perplexity (Google does not support it)
🏛️ Entity & Authority 53
i
No author information detected
Author data helps LLMs assess content credibility (E-E-A-T)
Publication date found
Schema: yes, Meta: no, Modified: no
i
Published 51 days ago
Content is relatively recent
!
Only About page linked
Link both About and Contact for full trust signals
Legal pages linked
Privacy: yes, Terms: yes
💬 Citability & Answer-Readiness 50
FAQ/Q&A content detected
19 FAQ-like elements
i
No definition lists
Use / / for term definitions - highly extractable
i
No data tables
Tables with headers are excellent for structured data extraction
Content lists: 2
Lists are easy for LLMs to cite and restructure
!
Lead paragraph is very short (30 chars)
Add a clear answer/summary as the first paragraph
!
Only 3/11 headings have IDs
Add IDs to all headings for deep linking and section references
Performance & Crawlability 60
All images have width/height attributes
Prevents layout shift (CLS) during loading
All non-hero images use loading="lazy"
Good for performance - reduces initial page weight
!
8 render-blocking script(s)
Add defer or async to scripts for faster page load
  • /_next/static/chunks/polyfills-42372ed130431b0a.js?dpl=dpl_EhJMxwCcDWpDyAw8VnH8u
  • https://eu-assets.i.posthog.com/static/surveys.js?v=1.268.9
  • https://eu-assets.i.posthog.com/array/phc_rA5g2nH52kOTkHTrRayCYx2kcqbdBAFweoyPn0
  • https://eu-assets.i.posthog.com/static/exception-autocapture.js?v=1.268.9
  • https://eu-assets.i.posthog.com/static/tracing-headers.js?v=1.268.9
i
Could not verify font-display in external stylesheets
Use font-display: swap in @font-face for faster text rendering
!
DOM size: 2663 elements (large)
Large DOM can slow crawling and parsing - consider simplifying
🔌 Agent Interactivity 18
i
No WebMCP declarative tools detected
Add toolname, tooldescription, and toolparamdescription attributes to forms to enable AI agent interaction
i
No WebMCP imperative API usage detected
Use document.modelContext.provideContext() to register tools for complex, multi-step agent workflows (WebMCP ships natively in Chrome 146+/Edge 147+; the legacy navigator.modelContext API was deprecated in Chrome 150)
i
No WebMCP SDK/polyfill detected
Consider @mcp-b/global polyfill or @mcp-b/react-webmcp for early WebMCP adoption
!
1 of 2 form(s) ready for WebMCP
Some forms need labels, names, or input types before they can be upgraded to WebMCP
  • form #2: missing input types
Form IDs are stable (no dynamic/hashed patterns)
Stable IDs help AI agents maintain state across interactions
i
Product page: consider adding WebMCP tools
Recommended tools for this page type: addToCart, checkAvailability, selectVariant, compareProducts
i
No UCP discovery file detected
No /.well-known/ucp profile found for agent-driven commerce
i
product page: consider adding UCP
Should have checkout + fulfillment + discount capabilities
i
No MCP server card
Publish /.well-known/mcp/server-card.json so agents can discover your MCP server (name, version, transport, tools)
i
No A2A agent card
Publish /.well-known/agent-card.json to declare agent-to-agent skills (an AP2 payments extension can be added here once a card exists)
i
No Agent Skills index
Expose reusable agent skills at /.well-known/agent-skills/index.json
i
No NLWeb endpoint
Advertise a natural-language query endpoint via <link rel="nlweb"> or a Link header (conventionally /ask)
i
No schemamap
Publish /schemamap.xml listing per-resource JSON-LD (.jsonld) endpoints for agent-friendly structured data
i
No Web Bot Auth directory
Publish an Ed25519 JWKS at /.well-known/http-message-signatures-directory so verifiers (Cloudflare, Akamai, Vercel, AWS WAF) can cryptographically attest your signed agent traffic (RFC 9421)
🎯 Content Positioning 52
!
Some differentiation signals: 1 found
Add more "only/first/leading/unique" claims to stand out
  • "exclusieve planten en mooie huiskamerplanten"
!
Some specificity & proof: 2 found
Add more statistics, measurable outcomes, or case studies
  • "€24,95 inclusief 21% btw"
  • "pot van 12 cm doorsnede"
!
Partial problem-solution framing
Solution and outcome present, but no clear problem articulation
!
Some social proof: 1 type found
Add testimonials, logo walls, or "trusted by" sections
  • ratings
i
No authority/expertise signals
Mention certifications, partnerships, or research to build credibility
!
Low positioning density (7%)
Only 7% of sentences carry positioning signals - aim for 15-40%
📅 Content Freshness 70
!
Only published date found
Add dateModified to schema or meta for "last updated" signals
Content is recent (2 months old)
Within the 6-month freshness window LLMs prefer
i
No temporal language detected
Add explicit dates ("as of February 2026") to anchor recency
Copyright year is current (2026)
Footer signals an actively maintained site
i
No version/changelog signals
Not critical for product pages - more relevant for software/docs
📊 Information Density 55
!
Moderate information density (42%)
42% substantive sentences, 8% filler - aim for >60% substantive
Few self-contained sections (0/2)
Sections need 150-500 words with topic sentences and supporting data
i
No claim-evidence pairing detected
Pair statistics with explanations ("X% which means...") for stronger LLM extraction
Low semantic foam (4%)
Content stays specific - few empty marketing phrases
!
Moderate content-to-boilerplate ratio (48%)
Main content takes 48% of body - consider reducing nav/footer noise
🔬 Factual Verifiability 22
No external citation links
Link to authoritative sources (.gov/.edu/.org) to support factual claims
i
No source attribution in text
Phrases like "according to [source]" or "research from..." build credibility
i
No semantic citation elements
Use <cite>, footnotes, or a references section for verifiable claims
i
No methodology or data attribution
If you cite data, link the source or describe how it was collected
i
No authoritative outbound links
Even one .gov/.edu/.org link can boost perceived trustworthiness
📚 Content Comprehensiveness 58
!
Word count below ideal for product page (441)
Product pages perform best at ~800 words - add care details, FAQs, or shipping info
Heading coverage looks balanced (2 H2s)
Reasonable structure for the current word count
!
Some definition patterns found (1)
Add more "X is...", "X means..." patterns - LLMs love extractable definitions
i
No comparison or alternatives content
A "vs other Hoya varieties" section helps LLMs answer comparative queries
i
Weak cross-reference signals (0/3)
Add a table of contents, related products, or key takeaways block
🖼️ Multimodal Content 72
!
Image alt quality is partial (62% descriptive)
Some alt attributes are generic ("image", "photo") - rewrite as descriptive
i
No <figure>/<figcaption> usage
Wrap key images in <figure> with <figcaption> for richer caption context
i
No video/audio media on page
N/A - skipped accessibility checks for this page
!
Partial SVG accessibility
3 of 8 inline SVGs have title/desc/aria-label - add to the rest
ImageObject schema detected
Product images are described in structured data

Recommended Changes

3 critical issues, 26 warnings

Priority Category Issue Recommendation
Medium Structured Data & Schema Only 2 GEO-critical schema type(s) Found: Product, BreadcrumbList. Consider adding: FAQPage, HowTo, Article, BreadcrumbList
Medium Structured Data & Schema Schema validation: 6 issue(s) Required properties are missing or values are invalid
Medium Structured Data & Schema Schema completeness: 12 recommendation(s) Several recommended properties are missing
High Semantic HTML Text-to-HTML ratio: 0% Very low - content may be JS-rendered or buried in markup
Medium Accessibility for Agents No skip-to-content link Add a skip link at the top of the page for accessibility and agent navigation
Medium Accessibility for Agents Link text issues: 1 empty/unlabeled Use descriptive anchor text for agent comprehension
Medium Accessibility for Agents 1 unlabeled form input(s) Add labels for agent-driven form interaction
Medium Internal Linking 2 internal link(s) with weak anchor text Use descriptive anchor text for better agent comprehension
Medium Meta & Discoverability Title tag: 72 chars (too long) "Hoya Flamingo Dream 'Star of Java' M (Wasbloem) online kopen | Example.c..."
Medium Entity & Authority Only About page linked Link both About and Contact for full trust signals
Medium Citability & Answer-Readiness Lead paragraph is very short (30 chars) Add a clear answer/summary as the first paragraph
Medium Citability & Answer-Readiness Only 3/11 headings have IDs Add IDs to all headings for deep linking and section references
Low Performance & Crawlability 8 render-blocking script(s) Add defer or async to scripts for faster page load
Low Performance & Crawlability DOM size: 2663 elements (large) Large DOM can slow crawling and parsing - consider simplifying
Low Agent Interactivity 1 of 2 form(s) ready for WebMCP Some forms need labels, names, or input types before they can be upgraded to WebMCP
Medium Content Positioning Some differentiation signals: 1 found Add more "only/first/leading/unique" claims to stand out
Medium Content Positioning Some specificity & proof: 2 found Add more statistics, measurable outcomes, or case studies
Medium Content Positioning Partial problem-solution framing Solution and outcome present, but no clear problem articulation
Medium Content Positioning Some social proof: 1 type found Add testimonials, logo walls, or "trusted by" sections
Medium Content Positioning Low positioning density (7%) Only 7% of sentences carry positioning signals - aim for 15-40%
Low Content Freshness Only published date found Add dateModified to schema or meta for "last updated" signals
Medium Information Density Moderate information density (42%) 42% substantive sentences, 8% filler - aim for >60% substantive
High Information Density Few self-contained sections (0/2) Sections need 150-500 words with topic sentences and supporting data
Medium Information Density Moderate content-to-boilerplate ratio (48%) Main content takes 48% of body - consider reducing nav/footer noise
High Factual Verifiability No external citation links Link to authoritative sources (.gov/.edu/.org) to support factual claims
Medium Content Comprehensiveness Word count below ideal for product page (441) Product pages perform best at ~800 words - add care details, FAQs, or shipping info
Medium Content Comprehensiveness Some definition patterns found (1) Add more "X is...", "X means..." patterns - LLMs love extractable definitions
Low Multimodal Content Image alt quality is partial (62% descriptive) Some alt attributes are generic ("image", "photo") - rewrite as descriptive
Low Multimodal Content Partial SVG accessibility 3 of 8 inline SVGs have title/desc/aria-label - add to the rest