lokeshwardewangan.in
Finalizing the report
Preparing the stored Is Agentic score
Essential—
Recommended—
Bonus signals—
lokeshwardewangan.in
Preparing the stored Is Agentic score
lokeshwardewangan.in
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 16 applicable checks
Critical access gaps come first, followed by other applicable readiness gaps.
Serve at least 500 characters of meaningful homepage content in raw HTML. Add a clear H1, keep deeper heading levels sequential, and remove excessive non-content markup.
Checks are grouped by relevance for Docs & content sites.
8081 chars with H1, but 3.0% content ratio is below the 5% target
How to pass
Serve at least 500 characters of meaningful homepage content in raw HTML. Add a clear H1, keep deeper heading levels sequential, and remove excessive non-content markup.
Site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot).
No meta-refresh stubs, JavaScript-redirect stubs, or cross-domain hops across 6 checked pages
All 5 sampled pages are publicly readable (4 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://lokeshwardewangan.in/sitemap.xml with 6 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
Organization schema complete with contactPoint and address
All trust anchor pages verified: About, Contact, Privacy
All 6 measured pages fit an agent context budget (largest ~2K tokens)
lokeshwardewangan.in ranks #4 for "Lokeshwar Prasad Dewangan developer portfolio"
Agent config found: github.com/lokeshwardewangan/trimly/blob/main/AGENTS.md
100% of 6 sampled sitemap entries carry lastmod; newest is 9 day(s) old
Found the llms.txt at https://lokeshwardewangan.in/llms.txt.
The llms.txt is well-formatted: 15 lines with markdown links, 1,565 characters in total.
When-to-use guidance found in llms.txt
Strong entity linking via sameAs: github.com, linkedin.com
All 5 probed llms.txt links resolve to real content
Code fences balanced across 1 markdown document
Returns markdown when requested via Accept header
Server HTML is a well-structured document (main=true, landmarks=2/4, h1=1, maxHeadingSkip=1).
90/90 interactive elements have a computable accessible name (100%).
No hidden instruction text detected in accessibility-tree attributes or off-screen content.
What does lokeshwardewangan.in 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 lokeshwardewangan.in do and who is it for? Explain it back to me.
20 steps8 reasoning steps4 searches
The agent could not fully satisfy the task due to JavaScript rendering blocking static content access. It assembled a partial understanding of lokeshwardewangan.in as a personal portfolio for a full-stack developer by relying almost entirely on web search results and GitHub repository metadata, since the site's actual pages returned only Next.js scaffolding. The site is not agent-navigable in its primary form; the agent succeeded only by pivoting to external sources.