Skip to content
Is Agentic

avivita.co.il

Agents are likely to struggle

What should the prompt cover?

12 findings · 5 selected

Failures (11)

Warnings (1)

Task

What does avivita.co.il do and who is it for? Explain it back to me.

Waiting for the agent’s first step…

Critical access blockers remain

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.

    0 / 2 passed

  • Core content is available

    Useful content remains accessible without a fragile browser-only path.

    0 / 1 passed

Evaluated surfaces have material gaps

The public website is always evaluated. Optional surfaces appear when the scan finds positive evidence that they apply.

Public website

Blocked

6%

0 of 12 mature checks passed

Fix these gaps first

Critical access gaps come first, followed by other applicable readiness gaps.

  1. 01

    Content without JavaScript

    Server-side render your homepage so AI crawlers see meaningful content without JavaScript. Ensure an H1 and 500+ chars of text in raw HTML.

    Critical access
  2. 02

    Not blocked by bot detection

    Allowlist known AI agent User-Agents (ChatGPT-User, ClaudeBot, Google-Extended, DeepSeekBot) in your WAF or bot-detection rules.

    Critical access
  3. 03

    Agent crawler reachability

    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.

    Critical access
  4. 04

    Markdown content negotiation (acceptmarkdown.com)

    On the responses that serve text/markdown via Accept negotiation, add Accept to the Vary header (Vary: Accept, Accept-Encoding). Without it, CDNs can serve the cached HTML variant to an agent asking for markdown (or vice versa), depending on which variant landed in cache first.

    Other readiness checks
  5. 05

    Developer resource discoverability

    Make your developer resources (API docs, OpenAPI spec, auth docs, webhooks, MCP server) discoverable by name. Publish them at predictable URLs, list them in llms.txt, and include your product name in page titles and headings so search engines surface them for name-based queries.

    Other readiness checks

Audit the checks behind the score

Applicable evidence is grouped by how it contributes to this preview model. Bonus checks appear only when they add points.

Essential0 of 4 passed · 0 / 80 points
  • Content without JavaScriptFailed

    Homepage blocked by WAF/security challenge - content not accessible to agents

    Recommendation

    Server-side render your homepage so AI crawlers see meaningful content without JavaScript. Ensure an H1 and 500+ chars of text in raw HTML.

  • Not blocked by bot detectionFailed

    Agents blocked: GPTBot, ClaudeBot, ChatGPT-User, PerplexityBot, Google-Extended, Applebot-Extended

    Recommendation

    Allowlist known AI agent User-Agents (ChatGPT-User, ClaudeBot, Google-Extended, DeepSeekBot) in your WAF or bot-detection rules.

  • Markdown content negotiation (acceptmarkdown.com)Failed

    Not acceptmarkdown.com compliant: Accept: text/markdown returned text/html; charset=utf-8; Vary header missing Accept (got "none")

    Recommendation

    On the responses that serve text/markdown via Accept negotiation, add Accept to the Vary header (Vary: Accept, Accept-Encoding). Without it, CDNs can serve the cached HTML variant to an agent asking for markdown (or vice versa), depending on which variant landed in cache first.

  • Agent crawler reachabilityFailed

    No major AI crawler can reach the homepage - ChatGPT-User: blocked, ClaudeBot: blocked, Google-Extended: blocked, ora-agent: blocked, DeepSeekBot: blocked

    Recommendation

    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.

Recommended0 of 8 passed · 1.7 / 20 points
  • Developer resource discoverabilityFailed

    Agent searched for "avivita.co.il" developer resources but found nothing relevant

    Recommendation

    Make your developer resources (API docs, OpenAPI spec, auth docs, webhooks, MCP server) discoverable by name. Publish them at predictable URLs, list them in llms.txt, and include your product name in page titles and headings so search engines surface them for name-based queries.

  • Brand name discoverabilityPartial (67%)

    avivita.co.il appears 4 times in brand-name search results for "avivita.co.il" (top position: #6)

    Recommendation

    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.

  • Sitemap existsFailed

    No sitemap found

    Recommendation

    Add a valid XML sitemap at /sitemap.xml listing all indexable URLs. Include lastmod dates and keep it under 50MB.

  • JSON-LD structured dataFailed

    Homepage blocked by WAF - cannot check structured data

    Recommendation

    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.

  • Agent instruction / when-to-useFailed

    No agent instruction file with when-to-use guidance found

    Recommendation

    Tell agents when to reach for you: add a 'when to use this' section to your llms.txt (or a dedicated agent-instructions file) that names your best-fit use cases and how an agent should call you. Be specific about the jobs you are right for - generic marketing copy does not read as guidance.

  • Metadata completenessFailed

    Homepage blocked by WAF - cannot check metadata

    Recommendation

    Add all four signals to your homepage: , , , and . Agents use these for entity resolution and attribution.

  • Organization schema completenessFailed

    Homepage blocked by WAF - cannot check Organization schema

    Recommendation

    Add Organization JSON-LD that includes both contactPoint (with email/phone and contactType) and address (PostalAddress). This lets AI verify your business legitimacy and answer contact queries.

  • Trust anchor pagesFailed

    No trust anchor pages found with sufficient content (About, Contact, Privacy)

    Recommendation

    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.

Bonus signals0 positive · +0 points

No positive signals in this group.

Inspect the underlying audit

The complete Ora audit uses evidence from the scan on . After applying changes, run another scan from the homepage to refresh these recommendations.

Sign me up for Vercel product updates and marketing emails.

Unsubscribe anytime. Privacy Notice

Source: Ora API

Snapshot 2026-08-22T23-26-15-823Z