Finalizing the report
Preparing the stored Is Agentic score
Essential—
Recommended—
Bonus signals—
Preparing the stored Is Agentic score
ladykosha.ru
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.
Ready with gaps
Weighted across 15 applicable checks
Critical access gaps come first, followed by other applicable readiness gaps.
Verify that major agent User-Agents can reach the homepage. If your WAF or bot rules block them, remove or narrow the blocking rule. Add an allow rule only when your security setup denies them by default.
Make sure a clean search for your brand name returns your own domain in the top results. If it does not, your brand may be too generic, conflict with a more established term, or not yet indexed. Strengthen brand-name search by claiming consistent NAP across listings, earning press mentions that link to the canonical domain, and avoiding redirect chains that mask the apex domain in search results.
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.
Add JSON-LD structured data to your homepage using the identity type that matches your site - SoftwareApplication for products, Organization or LocalBusiness for companies, Person for personal sites, Article for blogs - with name, description, url, and type-appropriate fields (offers, sameAs, author) so AI can parse your identity programmatically.
Checks are grouped by relevance for Docs & content sites.
3769 chars, semantic headings (1 H1 + 30 H2s), 24.2% content ratio
Some AI crawlers are blocked - ChatGPT-User: unknown, ClaudeBot: reachable, Google-Extended: reachable, ora-agent: reachable, DeepSeekBot: reachable
How to pass
Verify that major agent User-Agents can reach the homepage. If your WAF or bot rules block them, remove or narrow the blocking rule. Add an allow rule only when your security setup denies them by default.
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
"ladykosha" search returned 9 results but domain did not appear - brand may be too generic or not indexed
How to pass
Make sure a clean search for your brand name returns your own domain in the top results. If it does not, your brand may be too generic, conflict with a more established term, or not yet indexed. Strengthen brand-name search by claiming consistent NAP across listings, earning press mentions that link to the canonical domain, and avoiding redirect chains that mask the apex domain in search results.
Valid sitemap found at https://ladykosha.ru/sitemap.xml with 625 entries
JSON-LD has Article type but missing key fields (name, description)
How to pass
Add JSON-LD structured data to your homepage using the identity type that matches your site - SoftwareApplication for products, Organization or LocalBusiness for companies, Person for personal sites, Article for blogs - with name, description, url, and type-appropriate fields (offers, sameAs, author) so AI can parse your identity programmatically.
When-to-use guidance found in llms.txt
All metadata signals present: canonical URL, lang="ru", og:image, og:type
Organization schema complete with contactPoint and address
No trust anchor pages found with sufficient content (About, Contact, Privacy)
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 ~4K tokens)
Code fences balanced across 1 markdown document
Homepage markdown fallback works (https://ladykosha.ru/index.md). No additional same-host content pages were discovered to sample.
Found the llms.txt at https://ladykosha.ru/llms.txt.
The llms.txt is well-formatted: 20 lines with markdown links, 1,641 characters in total.
All 5 probed llms.txt links resolve to real content
Path-suffix markdown docs served with text/markdown content-type: /index.md
86 native controls, 0 non-native div-soup affordances (100% native).
85/85 interactive elements have a computable accessible name (100%).
1/1 form controls have an associated label (100%).
No hidden instruction text detected in accessibility-tree attributes or off-screen content.
What does ladykosha.ru 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 ladykosha.ru do and who is it for? Explain it back to me.
7 steps3 reasoning steps
The agent partially satisfied the task by assembling a coherent explanation of ladykosha.ru from three fetches of the actual site. It successfully identified the site as a personal digital garden by Agnessa Bukowska containing reflective essays, but encountered truncated HTML responses that prevented access to the full page content, pricing information, and competitive differentiation — forcing reliance on prior knowledge and inference rather than direct evidence from the site.