FAIR

Federated and Independent Repositories

First Page AI Readiness

Plugin Banner

First Page AI Readiness

by firstpagedigital

Download
Description

First Page AI Readiness is a diagnostic WordPress plugin for crawlability, indexability, content structure, machine-readable site navigation, and AI crawler policy clarity.

It is not a standalone llms.txt generator. It treats llms.txt as a curated navigation aid for agents already visiting the site—not as an AI discovery or ranking signal. The plugin focuses on deterministic technical audits, transparent scoring, crawlable and server-rendered content, cache-aware Markdown negotiation, privacy-safe public-content endpoints, crawler-policy controls, and browser-rendered versus source-HTML comparison.

The plugin does not guarantee AI rankings, AI citations, search visibility, traffic, or inclusion in AI-generated answers.

This initial public release includes deterministic audits and transparent scoring, curated Markdown endpoints, recoverable crawler-policy controls, browser-rendered versus source-HTML comparison, bulk Important Page descriptions, and strict public-content privacy exclusions.

llms.txt is treated as a navigational and technical-hygiene aid for an agent already visiting the domain. It does not guarantee discovery, ranking, citation, or inclusion in an answer.

Privacy

Deterministic audits use bounded same-origin HTTP requests and public WordPress content. The plugin excludes drafts, private and password-protected content, users, customer and order data, account surfaces, form submissions, credentials, and API keys from generated endpoints and exports.

External services

The plugin can contact the following third-party services only during the administrator actions described below.

Service: https://platform.openai.com/docs/api-reference/responses
Terms: https://openai.com/policies/services-agreement/
Privacy policy: https://openai.com/policies/privacy-policy/

Cloudflare DNS over HTTPS and Google Public DNS

When an administrator runs a Quick Audit or DNS-AID check, the plugin queries Cloudflare DNS over HTTPS and can fall back to Google Public DNS after a resolver-level failure. These requests send the site’s public domain, queried DNS record names, and record types. They do not send WordPress credentials, private content, customer data, or API keys.

Cloudflare service: https://developers.cloudflare.com/1.1.1.1/encryption/dns-over-https/
Cloudflare terms: https://www.cloudflare.com/website-terms/
Cloudflare privacy policy: https://www.cloudflare.com/privacypolicy/

Google Public DNS service: https://developers.google.com/speed/public-dns/docs/doh
Google terms: https://policies.google.com/terms
Google privacy policy: https://policies.google.com/privacy

Crawler and scanner documentation links

The Bot Access screen contains optional reference links to public crawler documentation from OpenAI, Anthropic, Perplexity, Common Crawl, Google, Apple, Amazon, and Meta. The readiness sidebar also links to the independent Is It Agent Ready scanner. The plugin does not request these documentation or scanner URLs in the background and sends no WordPress content to them. A request occurs only when an administrator chooses to open a link in their browser, under the destination site’s terms and privacy policy. These links are informational and are not required for the plugin to operate.

The Amazon reference identified during directory review is an ordinary link to the Amazonbot documentation. Opening it sends the administrator’s normal browser request to Amazon; the plugin itself sends no site content or credentials.

Amazonbot documentation: https://developer.amazon.com/en/amazonbot
Amazon conditions of use: https://www.amazon.com/gp/help/customer/display.html?nodeId=508088
Amazon privacy notice: https://www.amazon.com/gp/help/customer/display.html?nodeId=GX7NJQ4ZB8MHFRNJ

  1. Upload the fpd-ai-readiness directory to /wp-content/plugins/.
  2. Activate First Page AI Readiness from the WordPress Plugins screen.
  3. Open AI Readiness > Overview and run a quick audit.
  4. Review Discoverability, Content, and Bot Access Control findings before changing any setting.

On multisite, network activation initializes plugin-owned tables and settings independently for each site. Network administrators should review each site’s public-content and crawler-policy choices separately.

  1. Review the overall readiness score, category breakdown, audit status, and diagnostic findings from the Overview dashboard.

    Review the overall readiness score, category breakdown, audit status, and diagnostic findings from the Overview dashboard.

  2. Curate the public pages used by llms.txt and llms-full.txt, organize their sections, and update manual descriptions individually or by CSV.

    Curate the public pages used by llms.txt and llms-full.txt, organize their sections, and update manual descriptions individually or by CSV.

Does this plugin guarantee AI visibility?

No. Scores, structured data, and generated AI-readiness files are diagnostic aids only.

Can WooCommerce private data appear in generated files?

Orders, customers, sessions, carts, checkout, account pages, coupons, variations, and transactional records are excluded. Public products are excluded unless the product option is explicitly enabled.

Does the plugin edit a physical robots.txt file?

Never from an audit or bulk automatic fix. If an existing writable physical file owns the route, an administrator can review the complete replacement and explicitly choose Back up & replace or the guarded Back up & migrate to virtual robots.txt workflow. Migration preserves the complete reviewed policy, verifies the exact public body, media type, managed block, and physical-file removal, and recreates the original file automatically if any ownership or content check fails. Cache lifetime is retained as technical evidence but does not block migration. Restore the physical migration backup before deactivating or uninstalling the plugin because migrated virtual output requires the plugin to remain active.

Should every site publish DNS-AID records?

No. DNS-AID should advertise a real operational agent or organizational agent index, not a placeholder created only to improve a diagnostic score. When a real service exists, the Discoverability recommendation provides the required SVCB fields, DNSSEC steps, and verification commands in a short provider-neutral workflow. DNS changes remain manual at the authoritative provider and registrar; the plugin never stores DNS credentials or writes DNS records.

How are managed Web Bot Auth keys stored?

Managed mode requires PHP sodium. It generates an Ed25519 key, stores the private key only as authenticated ciphertext in a separate non-autoloaded database option, and derives its encryption key from WordPress authentication salts. The private key and ciphertext are never displayed. Changing the salts requires explicit key rotation and updates to the outbound agent and Cloudflare registration. The plugin signs the public directory response but does not sign unrelated WordPress HTTP requests.

1.0.1

  • Addressed WordPress.org review feedback for nonce validation, request sanitization, prefixed identifiers, external-service disclosure, and explicitly closed Markdown output buffering.
  • Includes deterministic audits and scoring, curated Markdown endpoints, crawler-policy controls, browser-rendered versus source-HTML comparison, and bulk Important Page description import.
  • Includes strict public-content privacy exclusions and two optimized WordPress.org directory screenshots.
Back to top