visibility

capability

payful.com

✓ verified

AI Visibility: ✓ check completed — level L1

AI Capability: ✓ check completed — level L2

Levels are cumulative — you must pass L1 before reaching L2, L2 before L3, and so on.

L1 Basic Accessibility 5/6

✓ Major AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended) are permitted to access your site. AI crawling allowed

✗ Main content is visible in the HTML source, not only rendered after JavaScript executes. Page content directly readable

✓ The page has a clear title and meta description, helping AI quickly identify the topic. Clear title and description

✓ The page responds quickly enough to avoid AI crawl failures or timeouts. Reasonable response time

✓ The site uses a valid HTTPS certificate. HTTPS secured

✓ Core content isn't blocked by login walls, membership gates, or paywalls. Content is not gated

L2 Content Comprehensibility 3/6

✓ Uses Schema.org / JSON-LD to help AI understand page content more accurately. Has structured data

✓ Open Graph tags provide supplementary title and summary information. Has social sharing info

✓ A canonical URL tells search engines and AI which version of the URL is authoritative. Clear canonical address

✗ The page has a clear H1 and uses H2/H3 headings to organize content logically. Clear heading hierarchy

✗ The HTML lang attribute is set, helping AI identify the page language. Language declared correctly

✗ The page has meaningful text content, not just a few sentences of boilerplate. Substantial content

L3 Discoverability 6/6

✓ An accessible XML sitemap helps AI and search engines discover your pages. Provides a sitemap

✓ The sitemap includes recent pages and isn't neglected over time. Sitemap stays updated

✓ Key content pages are easily reachable from the homepage and main pages. Clear internal linking

✓ Page URLs clearly reflect the content topic, rather than being cryptic parameter strings. Clean, readable URLs

✓ A /llms.txt file proactively tells LLMs which content is most worth paying attention to. Provides llms.txt

✓ The canonical tag points to the current page's standard address, avoiding duplicate page confusion. Consistent canonical setup

L4 Trust & Authority 3/6

✓ Structured data includes basic info like company/organization name, website, and logo. Organization info is clear

✓ Both users and AI can easily find your contact or about page. About and contact info visible

✗ Pages attribute content to an author, team, or organization. Content source is clear

✗ Pages include publish or update dates, helping assess content freshness. Publication dates are clear

✓ The site has essential pages like privacy policy and terms of service. Legal info is complete

✗ Basic security response headers are set, reflecting site maintenance quality. Proper security configuration

L5 AI-Optimized 0/6

✗ Page content is structured for AI to directly extract answers. Has FAQ / HowTo / Q&A structure

✗ Helps AI understand the page's position and hierarchy within the site. Has breadcrumb structure

✗ Products, services, or content include structured Review/Rating data. Has review information

✗ Multilingual pages have clear corresponding relationships, such as hreflang tags. Supports multiple languages

✗ Uses multiple effective Schema.org types, not just one. Richer structured data

✗ Pages contain FAQs, tables, lists, definitions, etc., making it easy for AI to extract and summarize. Clear content block structure

L1 Basic Accessibility 6/6

✓ Uses semantic HTML elements such as header, nav, main, article, section, and footer so agents can better understand page structure. Semantic HTML

✓ Includes essential metadata such as page title, description, and social sharing tags to improve machine interpretation. Metadata

✓ Provides JSON-LD structured data based on Schema.org to make entities and page meaning more explicit. Structured Data

✓ Public content is accessible without CAPTCHA or other anti-bot challenges that block legitimate automated access. No CAPTCHA Barriers

✓ Core content is present in the initial HTML response, rather than relying entirely on client-side JavaScript rendering. Server-Rendered Content

✓ Uses stable, human-readable URLs without excessive query parameters, session tokens, or hash-fragment routing. Clean URLs

L2 Discoverability 6/6

✓ Provides a robots.txt file that permits access for legitimate crawlers and agent systems where appropriate. robots.txt

✓ Publishes a valid XML sitemap to help agents and crawlers discover indexable pages efficiently. XML Sitemap

✓ Exposes a /llms.txt file that gives LLM-based systems guidance on important content and site structure. llms.txt

✓ Publishes an OpenAPI or Swagger specification so agents can understand available API endpoints programmatically. OpenAPI Specification

✓ Provides comprehensive documentation in a format that is easy for machines and agents to parse and use. Machine-Readable Documentation

✓ Ensures primary content is available as text, rather than being locked inside images, videos, or non-parsable PDFs. Text-Accessible Content

L3 Structured Interaction 2/6

✗ Exposes a well-defined REST or GraphQL API for programmatic access to data and actions. Structured API

✓ Returns JSON payloads with stable and predictable schemas across endpoints. Consistent JSON Responses

✗ Supports query parameters for search, filtering, pagination, and retrieval refinement. Search and Filtering Support

✗ Provides an agent descriptor, such as an A2A agent card at /.well-known/agent.json, to advertise agent capabilities. A2A Agent Card

✗ Clearly documents rate limits and returns proper 429 Too Many Requests responses when limits are exceeded. Documented Rate Limits

✓ Returns machine-readable error responses with clear codes, messages, and actionable context. Structured Error Handling

L4 Agent Integration 0/6

✗ Provides an MCP (Model Context Protocol) server so agents can access tools, resources, and actions through a standardized interface. MCP Server

✗ Supports WebMCP or comparable browser-oriented agent interaction patterns for web-based automation. WebMCP Support

✗ Supports write operations such as POST, PUT, PATCH, and DELETE, enabling agents to create and update resources. Write-Capable API

✗ Supports automation-ready authentication methods such as API keys or OAuth client credentials flows. Agent-Friendly Authentication

✗ Supports webhooks so agents can receive event-driven updates instead of relying only on polling. Webhooks

✗ Write operations support idempotency keys or equivalent safeguards to prevent duplicate execution. Idempotent Writes

L5 Autonomous Operation 0/6

✗ Supports real-time update channels such as SSE or WebSockets for low-latency agent workflows. Event Streaming

✗ Supports agent-to-agent capability discovery or negotiation so systems can adapt to each other dynamically. Capability Negotiation

✗ Provides APIs for subscription, lifecycle management, or registration of agent integrations. Subscription and Management API

✗ Supports multi-step workflows, task coordination, and stateful execution across actions or services. Workflow Orchestration

✗ Can proactively notify agents when relevant content, state, or business events change. Proactive Notifications

✗ Supports handoff between agents or services so tasks can continue across system boundaries. Cross-Service Handoff

AI Readiness Report

download .md

Executive Summary

Payful.com has a solid foundation for AI discoverability and basic agent interaction, but lacks the advanced features needed to be highly visible or usable by modern AI systems. Its strengths are in foundational SEO and basic API documentation, while key gaps are in content structure, trust signals, and programmatic agent integration.

AI Visibility — L1

The site is technically accessible to AI crawlers and has good discoverability tools like sitemaps and llms.txt. However, poor content structure, missing language tags, and a lack of AI-optimized structured data (like FAQs and reviews) severely limit its ability to be accurately understood and recommended by AI assistants.

AI Capability — L2

AI agents can discover the site's pages and documentation, and it provides a basic OpenAPI spec and JSON responses. However, it lacks a fully functional public API, agent authentication, and any advanced integration features, preventing agents from performing meaningful automated tasks or transactions.

With these scores, the site is unlikely to be surfaced as a top recommendation by AI assistants like ChatGPT or Claude. It also misses opportunities for automation, as AI agents cannot programmatically interact with its services to perform actions on behalf of users.

Top Issues

CRITICAL Content Not Crawlable by AI visibility · L1 · developer

Why: AI crawlers like GPTBot and ClaudeBot cannot execute JavaScript. If main content is only rendered after JavaScript executes, the AI sees an empty or incomplete page, making the site invisible.

Impact: AI systems cannot discover, index, or recommend your content, services, or products. This is a foundational blocker for all AI visibility.

Fix: Implement server-side rendering (SSR) or static site generation (SSG) for core content. Ensure the HTML source served to the crawler contains the primary text, headings, and links without requiring JavaScript execution.

HIGH Poor Content Structure for AI Comprehension visibility · L2 · content

Why: Headings (H1, H2, H3) provide a semantic outline of the page. Without them, AI struggles to understand the topic hierarchy, main points, and how information is organized.

Impact: AI is less likely to accurately summarize or extract key information from your pages, reducing the quality of AI-generated answers that cite your site.

Fix: Audit key pages (homepage, product pages, blog posts). Ensure each page has one clear H1 title. Use H2 for major sections and H3 for subsections to create a logical content hierarchy.

HIGH Page Language Not Declared visibility · L2 · developer

Why: The HTML `lang` attribute (e.g., `<html lang="en">`) tells AI the primary language of the page. This is crucial for language-specific search queries and for AI to process text correctly.

Impact: AI may misinterpret the language of your content, leading to poor matching for user queries and potential exclusion from language-specific AI results.

Fix: Add the `lang` attribute to the opening `<html>` tag on every page, specifying the correct language code (e.g., 'en' for English).

HIGH Insufficient Meaningful Content visibility · L2 · content

Why: AI systems evaluate the depth and substance of a page. Pages with only a few sentences or boilerplate text are considered low-value and are less likely to be surfaced as a primary source.

Impact: Your pages will be deprioritized by AI in favor of more comprehensive sources, reducing traffic and authority.

Fix: Review key landing pages. Expand content to provide substantive explanations, unique value propositions, and detailed information. Aim for several paragraphs of unique, helpful text per page.

HIGH No Structured API for Programmatic Access capability · L3 · product

Why: AI agents and other automated systems interact with services via APIs. Without a well-defined REST or GraphQL API, agents cannot directly query your data or perform actions.

Impact: You are missing the entire channel of AI-driven automation. Agents cannot look up information, make bookings, or perform tasks on behalf of users, limiting your service's integration potential.

Fix: Design and document a public API for core data and functionalities. Use OpenAPI/Swagger for REST or publish a GraphQL schema. Start with read-only endpoints for key resources.

Quick Wins

⚡

Page Language Not Declared — Add the `lang` attribute to the opening `<html>` tag on every page, specifying the correct language code (e.g., 'en' for English). (developer)

⚡

Missing Basic Security Headers — Configure your web server (e.g., Nginx, Apache) or application framework to send security headers. A minimal set includes: `X-Content-Type-Options: nosniff`, `X-Frame-Options: DENY`, and `Referrer-Policy: strict-origin-when-cross-origin`. (devops)

⚡

Content Lacks Author Attribution — Add author bylines to blog posts and articles. For company pages, use Schema.org `Organization` markup to associate the content with your brand. Include author names and, if possible, links to author bios. (content)

⚡

Content Missing Publication Dates — Add a visible publication date to all time-sensitive content (blog posts, news, documentation updates). Use the `<time>` HTML element with a `datetime` attribute and consider adding `datePublished` in Schema.org `Article` markup. (content)

30-Day Roadmap

Week 1: Quick Wins

— Add the `lang` attribute to the opening `<html>` tag on every page (e.g., lang='en').

— Configure web server to send security headers: X-Content-Type-Options: nosniff, X-Frame-Options: DENY, Referrer-Policy: strict-origin-when-cross-origin.

— Add visible author bylines to blog posts and articles, and implement Schema.org Organization markup for company pages.

— Add visible publication dates using the `<time>` element with datetime attribute to all time-sensitive content.

Visibility L1 → L2

Week 2: Foundation

— Audit key pages (homepage, product pages, blog posts) to ensure one clear H1 per page and a logical hierarchy using H2/H3 headings.

— Review and expand content on key landing pages to provide substantive explanations, unique value propositions, and several paragraphs of unique text.

Visibility L2 → L3

Weeks 3-4: Advanced

— Implement server-side rendering (SSR) or static site generation (SSG) for core content to ensure primary text, headings, and links are in the HTML source without requiring JavaScript.

— Design and document a public read-only API for core data using OpenAPI/Swagger or GraphQL schema.

Visibility L3 → L4, Capability L2 → L3

The site should achieve AI Visibility Level 4 and AI Capability Level 3 by addressing foundational crawlability, content structure, and initial programmatic access.