ajaydandge.dev
Finalizing the report
Preparing the stored Is Agentic score
ajaydandge.dev
Preparing the stored Is Agentic score
ajaydandge.dev
These checks describe whether an ordinary agent can enter, read, and operate the public site.
Agents can reach the site
Crawler access and bot defenses.
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.
No material issues were found in the applicable checks.
Checks are grouped by relevance for Docs & content sites.
Homepage: 1238 chars, semantic headings (1 H1 + 3 H2s + 4 H3s), 10.9% content ratio. 3 of 3 sampled inner pages have text without JavaScript (2 skipped).
Site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot).
No meta-refresh or JavaScript-redirect stubs across 7 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
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://ajaydandge.dev/sitemap.xml with 50 entries
Rich JSON-LD identity: Person with name, description, url, and sameAs/jobTitle (1 block)
All metadata signals present: canonical URL, lang="en", og:image, og:type
All trust anchor pages verified: About, Contact, Privacy
All 7 measured pages fit an agent context budget (largest ~2K tokens)
ajaydandge.dev ranks #6 for "Ajay Dandge" (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"). Ora first reads product terms from your homepage's JSON-LD keywords or knowsAbout, or its meta keywords tag. If none qualifies, it checks the main service's serviceType in JSON-LD, then a short product phrase in the page title. If those do not qualify, it checks product names in the homepage business's JSON-LD offers. Use clear product terms that also appear on the page. If no term qualifies, Ora searches your brand name alone. If your domain does not rank, 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.
RFC 8288 Link header advertises: describedby
Full markdown fallback support. Homepage (https://ajaydandge.dev/index.md) and all 3 sampled content pages return markdown: https://ajaydandge.dev/about.md, https://ajaydandge.dev/blog/local-llm-inference-benchmark-gpu-vs-cpu-only.md, https://ajaydandge.dev/blog/precision-and-recall.md
100% of 50 sampled sitemap entries carry lastmod; newest is 0 day(s) old
Found the llms.txt at https://ajaydandge.dev/llms.txt.
The llms.txt is well-formatted: 50 lines with markdown links, 7,606 characters in total.
Strong entity linking via sameAs: github.com, linkedin.com
All 5 probed llms.txt links resolve to real content
Code fences balanced across 2 markdown documents
Path-suffix markdown docs served with text/markdown content-type: /index.md
CLI tool mentioned in llms.txt
How to pass
Publish an official CLI tool on npm, PyPI, or Homebrew. A CLI lets agents and developers script interactions with your product without building API integrations from scratch.
Server HTML is a well-structured document (main=true, landmarks=3/4, h1=1, maxHeadingSkip=1).
21 native controls, 0 non-native div-soup affordances (100% native).
21/21 interactive elements have a computable accessible name (100%).
No hidden instruction text detected in accessibility-tree attributes or off-screen content.
What does ajaydandge.dev 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 ajaydandge.dev do and who is it for? Explain it back to me.
3 steps1 reasoning step
The agent fetched the homepage and /about and produced a thorough, well-grounded description of ajaydandge.dev as a personal portfolio, correctly noting the absence of pricing, stated audience, and comparative claims. The site was largely navigable, though /library was linked but never described and project details were split inconsistently across pages.