Skip to content
Is Agentic

notion.so

Important blockers remain

69/ 100

Technical readiness score

What should the prompt cover?

19 findings · 5 selected

Failures (10)

Warnings (9)

How the score adds up

35 checks

Starting an observed agent task

This run is collected separately from the technical score and will appear here as the agent moves through the public site.

Starting the agent…

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, bot defenses, and explicit agent policy.

    3 / 3 passed

  • Core content is available

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

    0 / 1 passed

  • Navigation fails safely

    Redirects and missing pages give agents a recoverable path.

    1 / 2 passed

  • Controls are understandable

    Forms and interactive controls expose usable names and structure.

    4 / 4 passed

Advertised capabilities have material gaps

Optional surfaces appear only when the scan finds positive evidence that the site offers them.

Public website

Needs work

61%

9 of 19 mature checks passed

API

Needs work

56%

5 of 11 mature checks passed

Authentication

Strong

87%

2 of 3 mature checks passed

MCP

Blocked

42%

0 of 2 mature checks passed

Fix these gaps first

Critical access gaps come first, followed by gaps in capabilities the site advertises.

  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

    Agent-friendly 404s

    Return a real HTTP 404 (or 410) status for nonexistent paths - never a 200 with your app shell, which makes agents believe every path exists. For full credit, give the 404 response a short markdown body pointing agents at your sitemap, llms.txt, or docs index. Verify with `curl -s -o /dev/null -w "%{http_code}" https://yourdomain.com/some-path-that-does-not-exist` - it must print 404.

    Critical access
  3. 03

    JSON error responses

    Return structured JSON error responses with error codes, messages, and resolution hints. Agents can't parse HTML error pages.

    Advertised capabilities
  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.

    Advertised capabilities
  5. 05

    Scoped permissions

    Support scoped API permissions (OAuth scopes or API key roles) so agents can request only the access they need.

    Advertised capabilities

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.

Essential6 of 11 passed · 54.1 / 80 points
  • Content without JavaScriptPartial (33%)
  • Not blocked by bot detectionPassed
  • robots.txt agent-user policyPassed
  • Redirect hygienePassed
  • OpenAPI spec publishedPassed
  • Markdown content negotiation (acceptmarkdown.com)Failed
  • Agent crawler reachabilityPassed
  • OAuth 2.0 supportPassed
  • Scoped permissionsPartial (60%)
  • JSON error responsesFailed
  • Agent-friendly 404sPartial (50%)
Recommended10 of 24 passed · 11.4 / 20 points
  • Developer resource discoverabilityFailed
  • Brand name discoverabilityPartial (67%)
  • robots.txt AI crawler policyPartial (50%)
  • Sitemap existsPassed
  • Content efficiencyFailed
  • JSON-LD structured dataFailed
  • Public API/docs linked from homepagePassed
  • Agent instruction / when-to-usePassed
  • Metadata completenessPassed
  • Organization schema completenessFailed
  • Trust anchor pagesPartial (50%)
  • Page token budgetPassed
  • Code fence validityPassed
  • Developer portalPassed
  • Public API with reachable endpointsPassed
  • Agent onboarding frictionPassed
  • MCP server / manifestPartial (83%)
  • Rate limit response headersFailed
  • Idempotency-Key supportFailed
  • CLI tool availablePassed
  • Multi-language SDK packagesPartial (67%)
  • MCP Apps supportFailed
  • API schema complexity analysisFailed
  • Function calling compatibilityPartial (50%)
Bonus signals14 positive · +3.3 points
  • Wikipedia / Wikidata entity presencePartial (50%)
  • NPM/PyPI SDK packagePassed
  • Agent platform configsPassed
  • ChatGPT app listedPassed
  • llms.txt existsPassed
  • llms.txt formattingPartial (50%)
  • llms.txt links resolvePassed
  • NLWeb /ask endpointPassed
  • Sandbox / test environmentPassed
  • Accessible document structurePassed
  • Native interactive controlsPassed
  • Accessible names on controlsPassed
  • Form control labelingPassed
  • Accessibility-tree injection safety (bonus)Passed

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.

Score alerts

A weekly report with ranking changes, new agent feedback, and score alerts for notion.so.

Source: Ora API

Snapshot 2026-08-20T19-38-00-851Z