notionally.com

The fix, as a brief for a coding agent

Goal: Serve AI agents the same page a browser gets
Site: https://www.notionally.com/ (notionally.com)
Issue: Crawlers blocked: GPTBot, ClaudeBot, PerplexityBot
Fix: Compare the homepage as fetched with a browser user agent and with the GPTBot, ClaudeBot and PerplexityBot user agents. Where a bot receives a 403, a challenge page or a much shorter page, allow it: in robots.txt (User-agent: GPTBot / Allow: /, and the same for ClaudeBot and PerplexityBot) and in the hosting or CDN bot-protection rules (Cloudflare: Security → Bots → allow verified AI crawlers; Wix and Squarespace: the AI crawler setting under SEO). Blocked this time: GPTBot, ClaudeBot, PerplexityBot. Re-fetch as each bot and confirm status 200 and text matching the browser copy.
Evidence:
  bots: {"bot":"GPTBot","status":403,"ratio":0,"robots":"allowed"}, {"bot":"ClaudeBot","status":403,"ratio":0,"robots":"allowed"}, {"bot":"PerplexityBot","status":403,"ratio":0,"robots":"allowed"}
  blocked: GPTBot, ClaudeBot, PerplexityBot
Docs: https://platform.openai.com/docs/bots, https://support.anthropic.com/en/articles/8896518, https://docs.perplexity.ai/guides/bots

The fix, as a brief for a coding agent

Goal: Put the content in the HTML, not only behind scripts
Site: https://www.notionally.com/ (notionally.com)
Issue: Only 0 characters without scripts
Fix: Fetch the homepage without executing JavaScript and confirm the response body contains the business name, a description and contact details as text, with at least one heading. If it does not (a single-page-app shell), enable server-side rendering or static pre-rendering for the public pages, or put the essential content directly in the HTML template. This time the plain HTML carried 0 characters of text. Re-fetch and check for at least 500 characters and an <h1>.
Evidence:
  chars: 0
  headings: 0
  bytes: 114
Docs: https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics

The fix, as a brief for a coding agent

Goal: Publish schema.org JSON-LD that matches the listing
Site: https://www.notionally.com/ (notionally.com)
Issue: No structured data
Fix: Add a <script type="application/ld+json"> block to the homepage describing the business: @type LocalBusiness or the closest subtype (Plumber, Restaurant, Hotel…; Organization or SoftwareApplication for a software company), with name, url, telephone in E.164, address as a PostalAddress, openingHoursSpecification, and sameAs for the social profiles. Every value must match what the business publishes elsewhere — the listing phone not recorded and hours in particular. Validate at validator.schema.org and re-fetch.
Evidence:
  hasHours: false
  mismatch: false
Docs: https://schema.org/LocalBusiness, https://validator.schema.org/, https://developers.google.com/search/docs/appearance/structured-data/local-business

The fix, as a brief for a coding agent

Goal: Complete the six head signals agents read first
Site: https://www.notionally.com/ (notionally.com)
Issue: Metadata missing lang, title, description, canonical, h1, ogTitle
Fix: On the homepage ensure: <html lang="…">; a <title> under 60 characters naming the business and what it does; <meta name="description"> of 50–160 characters; <link rel="canonical"> pointing at the preferred address; exactly one <h1>; and <meta property="og:title">. Missing on this page: lang, title, description, canonical, h1, ogTitle. Re-fetch and confirm all six are present.
Evidence:
  missing: lang, title, description, canonical, h1, ogTitle
Docs: https://developers.google.com/search/docs/appearance/title-link, https://ogp.me/

The fix, as a brief for a coding agent

Goal: Return 404 for missing .well-known paths
Site: https://www.notionally.com/ (notionally.com)
Issue: Missing path returned 200 text/html
Fix: Requests for unknown paths under /.well-known/ currently return 200 with text/html — usually a login redirect or a catch-all route. Make unknown paths return 404 with a short plain-text or JSON body, and never redirect a JSON-accepting request to an HTML page. Test with GET /.well-known/does-not-exist.json and confirm a 404.
Evidence:
  status: 200
  contentType: text/html
  finalUrl: https://www.notionally.com/.well-known/ai3-probe-129rl3yf.json
Docs: https://www.rfc-editor.org/rfc/rfc8615

The fix, as a brief for a coding agent

Goal: Offer Markdown to agents that ask for it
Site: https://www.notionally.com/ (notionally.com)
Issue: No Markdown for agents
Fix: Support content negotiation on public pages: when a request carries Accept: text/markdown, respond with Content-Type: text/markdown and a Markdown rendering of the page (headings, paragraphs, links), keeping HTML the default for browsers. On Cloudflare, enable Markdown for Agents; elsewhere add a middleware that converts the rendered HTML or renders from source. Confirm with curl -H "Accept: text/markdown".
Evidence:
  contentType: text/html
Docs: https://developers.cloudflare.com/fundamentals/reference/markdown-for-agents/

The fix, as a brief for a coding agent

Goal: Publish a machine-readable API description where agents look
Site: https://www.notionally.com/ (notionally.com)
Issue: No API description found
Fix: Publish an OpenAPI 3.x document at /openapi.json (and/or /openapi.yaml); add a Link response header on the homepage — Link: </openapi.json>; rel="service-desc" — and publish /.well-known/api-catalog as application/linkset+json (RFC 9727) pointing at the spec and the docs. Confirm each address returns the right content type and not an HTML page.
Docs: https://www.rfc-editor.org/rfc/rfc9727, https://spec.openapis.org/oas/latest.html, https://www.rfc-editor.org/rfc/rfc8288

The fix, as a brief for a coding agent

Goal: Publish an MCP server card
Site: https://www.notionally.com/ (notionally.com)
Issue: No MCP server card
Fix: Publish /.well-known/mcp/server-card.json and /.well-known/mcp.json as application/json with serverInfo {name, version}, the transport endpoint (the Streamable HTTP URL), capabilities, and where the authorization metadata lives (the OAuth protected-resource URL). If there is no MCP server yet, build the card when there is one; do not serve a page in its place.
Evidence:
  looked: /.well-known/mcp/server-card.json, /.well-known/mcp.json, POST https://mcp.notionally.com/mcp initialize, POST https://mcp.notionally.com/ initialize, POST https://www.notionally.com/mcp initialize
Docs: https://modelcontextprotocol.io/specification/latest, https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2127

The fix, as a brief for a coding agent

Goal: Publish OAuth discovery metadata that validates
Site: https://www.notionally.com/ (notionally.com)
Issue: No OAuth discovery metadata
Fix: Serve /.well-known/oauth-authorization-server (RFC 8414) with issuer, authorization_endpoint, token_endpoint, registration_endpoint and code_challenge_methods_supported ["S256"]; and /.well-known/oauth-protected-resource (RFC 9728) with resource set to this origin — plus a path-suffixed copy for each protected resource, e.g. /.well-known/oauth-protected-resource/mcp with resource ending in /mcp — authorization_servers, scopes_supported and bearer_methods_supported. Return application/json with CORS open. Found this time: authorization server no, protected resource no.
Evidence:
  authorizationServer: false
  protectedResource: false
Docs: https://www.rfc-editor.org/rfc/rfc8414, https://www.rfc-editor.org/rfc/rfc9728

The fix, as a brief for a coding agent

Goal: Publish a machine-readable price for agent access
Site: https://www.notionally.com/ (notionally.com)
Issue: No price for agent access
Fix: Publish the price of agent access where agents look: a Link header on the homepage with rel="payment" pointing at the terms, or /.well-known/x402.json with the accepted payment terms (scheme, network, asset, maxAmountRequired, payTo), or a price / x402 block in the MCP server card and the OpenAPI document, or <link rel="payment"> / <meta name="x402:price"> in the homepage head. Looked this time: Link header, /.well-known/x402.json, homepage head. Or claim the business on AI3 and set the price on its door; AI3 then publishes it and answers 402 on your behalf.
Evidence:
  looked: Link header, /.well-known/x402.json, homepage head
Docs: https://www.x402.org/, https://github.com/coinbase/x402, https://www.rfc-editor.org/rfc/rfc8288

The fix, as a brief for a coding agent

Goal: Answer an unpaid agent request with 402 and payment terms
Site: https://www.notionally.com/ (notionally.com)
Issue: Unpaid agent request answered 200
Fix: Make the agent endpoint (the MCP endpoint named in the server card, else the homepage) answer an unauthenticated request with Accept: application/json using status 402 and payment terms: an x402 body with x402Version and accepts[] carrying payTo, maxAmountRequired and network, or Cloudflare pay-per-crawl (a 402 with a crawler-price header). This time https://www.notionally.com/ answered 200. Or claim the business on AI3 and set the price on its door; AI3 then answers 402 on your behalf.
Evidence:
  endpoint: https://www.notionally.com/
  status: 200
Docs: https://www.x402.org/, https://developers.cloudflare.com/ai-crawl-control/features/pay-per-crawl/, https://www.rfc-editor.org/rfc/rfc9110#status.402

The fix, as a brief for a coding agent

Goal: Publish who to pay
Site: https://www.notionally.com/ (notionally.com)
Issue: No payee published
Fix: Publish the payee where agents look: payTo in the x402 402 body, or in /.well-known/x402.json, or a pay block in the MCP server card with the address and network. Looked this time: the 402 body, /.well-known/x402.json. Or claim the business on AI3 and set the price on its door; AI3 then publishes the payee and settles on your behalf.
Evidence:
  looked: the 402 body, /.well-known/x402.json
Docs: https://www.x402.org/, https://github.com/coinbase/x402

The fix, as a brief for a coding agent

Goal: Be listed where tool routers look
Site: https://www.notionally.com/ (notionally.com)
Issue: In no catalogue an agent searches
Fix: Publish /.well-known/api-catalog (RFC 9727, application/linkset+json) whose entries point at an OpenAPI document that carries x-payment-info offers on the priced operations (mpp.dev/advanced/discovery), then register it at mpp.dev/services and mppscan.com. Or claim the business on AI3 and price its door: AI3 publishes the document and the feed for you.
Evidence:
  entries: 0
  looked: /.well-known/api-catalog
Docs: https://mpp.dev/advanced/discovery, https://www.rfc-editor.org/rfc/rfc9727, https://tempo.xyz/developers/blog/introducing-mercator

The fix, as a brief for a coding agent

Goal: Publish robots.txt, a sitemap and llms.txt
Site: https://www.notionally.com/ (notionally.com)
Issue: Missing sitemap
Fix: Publish /robots.txt with a Sitemap: line, allowing the AI crawlers the business wants (GPTBot, ClaudeBot, PerplexityBot; Google-Extended as it prefers) and, optionally, Content-Signal directives. Publish /sitemap.xml listing the public pages. Add /llms.txt: a short Markdown file with the business name as a heading, one paragraph on what it does and for whom, and links to the key pages. Missing this time: sitemap. Confirm each answers 200 with the right content type.
Evidence:
  robots: true
  llms: true
  missing: sitemap
Docs: https://llmstxt.org/, https://www.sitemaps.org/protocol.html, https://contentsignals.org/