deepcalls.io
Finalizing the report
Preparing the stored Is Agentic score
Essential—
Recommended—
Bonus signals—
deepcalls.io
Preparing the stored Is Agentic score
deepcalls.io
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.
Publish real /about, /contact, and /privacy pages with at least 500 characters of content each. These are the pages AI agents check to verify your business is legitimate before recommending you.
Checks are grouped by relevance for Business sites.
7482 chars, semantic headings (1 H1 + 7 H2s + 18 H3s), 11.0% 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
deepcalls.io ranks #1 for "DeepCalls security assessment"
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://deepcalls.io/sitemap-index.xml with multiple sitemaps entries
Rich JSON-LD identity: Organization with name, description, url, and sameAs/logo/address (3 blocks)
All metadata signals present: canonical URL, lang="nl", og:image, og:type
Organization schema complete with contactPoint and address
Contact, Privacy pages verified - missing: About
How to pass
Publish real /about, /contact, and /privacy pages with at least 500 characters of content each. These are the pages AI agents check to verify your business is legitimate before recommending you.
All 7 measured pages fit an agent context budget (largest ~2K tokens)
Full markdown fallback support. Homepage (https://deepcalls.io/index.md) and all 3 sampled content pages return markdown: https://deepcalls.io/blog/index.md, https://deepcalls.io/de/blog/scattered-spider-servicedesk/index.md, https://deepcalls.io/diensten/aanvullend/index.md
Found the llms.txt at https://deepcalls.io/llms.txt.
The llms.txt is well-formatted: 37 lines with markdown links, 6,506 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: ProfessionalService - add 2 more types that match what the homepage shows, for full coverage
How to pass
Add 2 more JSON-LD types that match 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
Server HTML is a well-structured document (main=true, landmarks=4/4, h1=1, maxHeadingSkip=1).
71 native controls, 0 non-native div-soup affordances (100% native).
71/71 interactive elements have a computable accessible name (100%).
No hidden instruction text detected in accessibility-tree attributes or off-screen content.
What does deepcalls.io 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 deepcalls.io do and who is it for? Explain it back to me.
11 steps5 reasoning steps2 searches
The agent could not access the live site due to persistent HTTP 429 rate limiting and assembled an answer entirely from search engine snippets and summaries. The site was not navigable via direct fetch, forcing reliance on external summaries of DeepCalls' positioning, which the agent disclosed as unverified.