# Audit Linear AI crawler readiness

**Use case:** 

Inspect robots directives, headers, llms.txt and JSON-LD. Local readiness audit, not AI-answer citations. $0.02 per returned report; blocked homepage produces diagnostic OUTPUT only.

## Input

```json
{
  "domain": "linear.app",
  "competitor_domains": [],
  "category_keywords": [],
  "generate_ready_llms_txt": true
}
```

## Output

```json
{
  "domain": {
    "label": "Domain",
    "format": "string"
  },
  "brand_name": {
    "label": "Brand",
    "format": "string"
  },
  "geo_readiness_score": {
    "label": "GEO Score (0-100)",
    "format": "integer"
  },
  "geo_readiness_grade": {
    "label": "Grade",
    "format": "string"
  },
  "ai_crawler_accessibility_score": {
    "label": "Crawler Score",
    "format": "integer"
  },
  "entity_authority_score": {
    "label": "Entity Score",
    "format": "integer"
  },
  "agent_discovery_score": {
    "label": "Agent Score",
    "format": "integer"
  },
  "citation_comparison_score": {
    "label": "Citation Score",
    "format": "integer"
  },
  "gptbot_status": {
    "label": "GPTBot",
    "format": "string"
  },
  "oai_searchbot_status": {
    "label": "OAI-SearchBot",
    "format": "string"
  },
  "claude_bot_status": {
    "label": "ClaudeBot",
    "format": "string"
  },
  "perplexity_bot_status": {
    "label": "PerplexityBot",
    "format": "string"
  },
  "google_extended_status": {
    "label": "Google-Extended",
    "format": "string"
  },
  "has_llms_txt": {
    "label": "llms.txt Present",
    "format": "boolean"
  },
  "llms_txt_url": {
    "label": "llms.txt URL",
    "format": "string"
  },
  "has_llms_full_txt": {
    "label": "llms-full.txt Present",
    "format": "boolean"
  },
  "has_agent_manifests": {
    "label": "MCP/OpenAPI Manifest",
    "format": "boolean"
  },
  "json_ld_schemas_found": {
    "label": "JSON-LD Schemas",
    "format": "array"
  },
  "has_organization_schema": {
    "label": "Org Schema",
    "format": "boolean"
  },
  "has_software_schema": {
    "label": "Software Schema",
    "format": "boolean"
  },
  "same_as_links_count": {
    "label": "sameAs Authority Links",
    "format": "integer"
  },
  "comparison_pages_detected": {
    "label": "Comparison Pages",
    "format": "array"
  },
  "ai_search_queries_count": {
    "label": "AI Search Intents",
    "format": "integer"
  },
  "top_priority_fix": {
    "label": "Top Priority Action",
    "format": "string"
  },
  "audit_timestamp": {
    "label": "Audit Timestamp",
    "format": "string"
  }
}
```

## How it works

### 1. Sign up on Apify or log in

The AI Crawler Readiness Audit & llms.txt Draft Actor is ready to run with the inputs already set for "Audit Linear AI crawler readiness". [Sign up or log in](https://console.apify.com/create-task-from-example/lhOpd7UmbzLWZDQpr) and you'll land in Apify Console with a copy of this exact task.

### 2. Start the "Audit Linear AI crawler readiness" task

The AI Crawler Readiness Audit & llms.txt Draft Actor will start running based on the input automatically. You can also change all the input fields, like brand domain, competitor domains (up to 3), and more, to match your specific use case.

### 3. Receive the "Audit Linear AI crawler readiness" output

Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as domain, brand, GEO Score (0-100), and more.

### 4. Integrate into your workflow

The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also [run the "Audit Linear AI crawler readiness" task via API](https://apify.com/hirepulse/ai-search-brand-visibility-radar.md).

## About this Actor

This example demonstrates how to use [AI Crawler Readiness Audit & llms.txt Draft](https://apify.com/hirepulse/ai-search-brand-visibility-radar.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/hirepulse/ai-search-brand-visibility-radar.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

This Task's input is already configured above. Use it as-is rather than inventing a new one.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/hirepulse/ai-search-brand-visibility-radar.md

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).