LLMS.txt Auditor

Store Positioning

Store title: LLMS.txt Auditor

Short description: Check for llms.txt / AI crawler policy guidance and produce structured readiness reports.

SEO title: LLMS.txt Auditor — technical SEO, web, and domain audit

SEO description: Check for llms.txt / AI crawler policy guidance and produce structured readiness reports. Use it to find crawlability, indexability, security, metadata, and page-quality issues with evidence-backed rows and audit reports.

Categories: SEO_TOOLS

Keywords: llms, txt, auditor, structured data, web/domain audit

Fixed-Inclusive PPE Pricing

This actor uses pay-per-event pricing. Event prices include Apify platform usage; users are not expected to pay a separate platform-usage pass-through charge for the configured pricing model.

• Tier: W1 — Web/domain audit
• Primary event: page-audited at $0.00490 base
• Default max charge: $10.00
• Store discounts: FREE/BRONZE base, SILVER discounted, GOLD deepest approved discount

Event set:

• actor-start: base $0.00500, GOLD $0.00400. Llms Txt Auditor: charged when actor start is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• page-audited: base $0.00490, GOLD $0.00392. Llms Txt Auditor: charged when page audited is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• record-extracted: base $0.00372, GOLD $0.00298. Llms Txt Auditor: charged when record extracted is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• finding-emitted: base $0.00372, GOLD $0.00298. Llms Txt Auditor: charged when finding emitted is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• audit-report-generated: base $0.05000, GOLD $0.04000. Llms Txt Auditor: charged when audit report generated is completed. The price includes Apify platform usage; no separate usage pass-through is intended.

Public Task Concepts

• Audit public URLs for LLMS.txt Auditor issues
• Find LLMS.txt Auditor problems across a website
• Generate a technical LLMS.txt Auditor report
• Audit llms issues across supplied public inputs
• Extract evidence-backed llms rows for client QA

What It Does

Check for llms.txt / AI crawler policy guidance and produce structured readiness reports.

This local package is part of the Junipr Apify actors 171-200 premium build for ChatGPT review.

What It Does Not Do

• It does not call live Apify APIs.
• It does not publish, upload Store assets, create public tasks, or configure live PPE.
• It does not claim publish readiness.
• It does not make unbounded network calls in the supplied examples path.

Input Fields

Seed shape: inputItems, maxItems, includeReport

The tiny fixture is available at examples/input.tiny.json and mirrored at fixtures/input.tiny.json for the local runner.

Output Fields

• domain
• checkedUrl
• statusCode
• found
• contentType
• policySignals
• allowSignals
• disallowSignals
• issues
• readinessStatus

Public Task Examples

Audit llms.txt policy content for a website

• Search intent: audit llms.txt policy content for a website
• Specific input: Fixture input shaped for audit llms.txt policy content for a website.
• Expected output: Dataset rows with domain, checkedUrl, statusCode, found plus local KVS report evidence.
• Why run it: Publishers, SEO teams, legal/content teams, agencies would run this to get a bounded local proof before any live Apify review or production use.

Check AI crawler allow and disallow rules

• Search intent: check ai crawler allow and disallow rules
• Specific input: Fixture input shaped for check ai crawler allow and disallow rules.
• Expected output: Dataset rows with domain, checkedUrl, statusCode, found plus local KVS report evidence.
• Why run it: Publishers, SEO teams, legal/content teams, agencies would run this to get a bounded local proof before any live Apify review or production use.

Verify contact metadata in an llms.txt file

• Search intent: verify contact metadata in an llms.txt file
• Specific input: Fixture input shaped for verify contact metadata in an llms.txt file.
• Expected output: Dataset rows with domain, checkedUrl, statusCode, found plus local KVS report evidence.
• Why run it: Publishers, SEO teams, legal/content teams, agencies would run this to get a bounded local proof before any live Apify review or production use.

Prepare content-use policy rows for legal review

• Search intent: prepare content-use policy rows for legal review
• Specific input: Fixture input shaped for prepare content-use policy rows for legal review.
• Expected output: Dataset rows with domain, checkedUrl, statusCode, found plus local KVS report evidence.
• Why run it: Publishers, SEO teams, legal/content teams, agencies would run this to get a bounded local proof before any live Apify review or production use.

Review llms.txt readiness before public release

• Search intent: review llms.txt readiness before public release
• Specific input: Fixture input shaped for review llms.txt readiness before public release.
• Expected output: Dataset rows with domain, checkedUrl, statusCode, found plus local KVS report evidence.
• Why run it: Publishers, SEO teams, legal/content teams, agencies would run this to get a bounded local proof before any live Apify review or production use.

Tests

• Actor-specific fixture tests live in test/llms-txt-auditor.test.ts.
• Node-based local suites validate dataset schema conformance, output samples, local smoke runs, and PPE guard behavior.

FAQ

Is this live on Apify?

No. This is a local package for ChatGPT review only.

Is it publish-ready?

No. It needs later live tiny-run validation and console configuration before any publication decision.