telefoonkracht.nl
Finalizing the report
Preparing the stored Is Agentic score
Essential—
Recommended—
Bonus signals—
telefoonkracht.nl
Preparing the stored Is Agentic score
telefoonkracht.nl
These checks describe whether an ordinary agent can enter, read, and operate the public site.
Core content is available
Useful content remains accessible without a fragile browser-only path.
Navigation fails safely
Redirects and missing pages give agents a recoverable path.
Controls are understandable
Forms and interactive controls expose usable names and structure.
The public website is always evaluated. Optional surfaces appear when the scan finds positive evidence that they apply.
Strong
Weighted across 15 applicable checks
Critical access gaps come first, followed by other applicable readiness gaps.
Make sure your own domain ranks in the top results when people search your brand together with your main product (for example "Acme payments API"). If it does not, your brand may be too generic, conflict with a more established term, or not yet indexed. Strengthen it by describing your main product clearly in your homepage title and headings, earning press mentions that link to your domain, and avoiding redirect chains that mask your main domain in search results.
Checks are grouped by relevance for Business sites.
8424 chars, semantic headings (1 H1 + 10 H2s + 17 H3s), 11.7% content ratio
No meta-refresh stubs, JavaScript-redirect stubs, or cross-domain hops across 6 checked pages
All 5 sampled pages are publicly readable (5 with substantive content)
Canonical URL serves text/markdown and text/html via Accept negotiation with Vary: Accept
Nonexistent paths return HTTP 404 with markdown guidance for agents - the strongest 404 contract
telefoonkracht.nl ranks #7 for "TelefoonKracht" (searched your brand name alone: no main product term from your homepage qualified)
How to pass
Make sure your own domain ranks in the top results when people search your brand together with your main product (for example "Acme payments API"). If it does not, your brand may be too generic, conflict with a more established term, or not yet indexed. Strengthen it by describing your main product clearly in your homepage title and headings, earning press mentions that link to your domain, and avoiding redirect chains that mask your main domain in search results.
No noindex on the homepage: no robots, googlebot or bingbot meta tag and no X-Robots-Tag header hides it from search.
Valid sitemap found at https://telefoonkracht.nl/sitemap-index.xml with multiple sitemaps entries
Rich JSON-LD identity: Organization with name, description, url, and sameAs/logo/address (1 block)
All metadata signals present: canonical URL, lang="nl-NL", og:image, og:type
Organization schema complete with contactPoint and address
All trust anchor pages verified: About, Contact, Privacy
All 7 measured pages fit an agent context budget (largest ~3K tokens)
Full markdown fallback support. Homepage (https://telefoonkracht.nl/index.md) and all 3 sampled content pages return markdown: https://telefoonkracht.nl/blog/index.md, https://telefoonkracht.nl/blog/soorten-telefonische-ondersteuning/index.md, https://telefoonkracht.nl/telefoonservice/amsterdam/index.md
Found the llms.txt at https://telefoonkracht.nl/llms.txt.
The llms.txt is well-formatted: 46 lines with markdown links, 4,208 characters in total.
When-to-use guidance found in llms.txt
Entity linking to linkedin.com - add more authority profiles (Wikipedia, Wikidata, LinkedIn, GitHub)
How to pass
Add sameAs links in your JSON-LD structured data pointing to your Wikipedia page, Wikidata entry, GitHub org, and social profiles. This helps AI disambiguate your brand from similarly named entities.
Some extended schema types found: BreadcrumbList, LocalBusiness - add 1 more type that matches what the homepage shows, for full coverage
How to pass
Add 1 more JSON-LD type that matches what your homepage shows. Only add a type where the page shows that content.
All 5 probed llms.txt links resolve to real content
Frontmatter with title + description on /index.md
Code fences balanced across 1 markdown document
Path-suffix markdown docs served with text/markdown content-type: /index.md
Imperative WebMCP API detected (document.modelContext.registerTool in inline script).
Server HTML is a well-structured document (main=true, landmarks=4/4, h1=1, maxHeadingSkip=1).
129 native controls, 3 non-native div-soup affordances (98% native).
125/125 interactive elements have a computable accessible name (100%).
10/10 form controls have an associated label (100%).
No hidden instruction text detected in accessibility-tree attributes or off-screen content.
What does telefoonkracht.nl do and who is it for? Explain it back to me.
Sign me up for Vercel product updates and marketing emails.
Unsubscribe anytime. Privacy Notice
Source: Ora API
What does telefoonkracht.nl do and who is it for? Explain it back to me.
6 steps1 reasoning step1 search
The agent could not access the site directly (HTTP 429 on all fetches) and relied entirely on a single web search result, which yielded only snippets and metadata rather than full page content. The explanation is secondhand, unverified, and incomplete — pricing is internally inconsistent, service details are shallow, and no differentiation vs. alternatives is documented.