=== Four47 Labs – AI Visibility, GEO & LLMs.txt ===
Contributors: four47labs
Tags: llms.txt, robots.txt, geo, ai visibility, ai crawlers
Requires at least: 6.2
Tested up to: 7.1
Requires PHP: 7.4
Stable tag: 1.0.0
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Manage llms.txt, robots.txt and AI crawler rules with GEO-focused WordPress tools and technical AI visibility audits.

== Description ==

**Four47 Labs – AI Visibility, GEO & LLMs.txt** brings together technical controls for websites preparing for AI-driven discovery and traditional search crawling. Generate an llms.txt file, manage robots.txt directives, review AI crawler access and audit your WordPress configuration from one dashboard.

**AI visibility and GEO (Generative Engine Optimization)** are the focus of this plugin. It helps site owners manage signals and crawler-facing configuration relevant to AI systems. It does not optimize content for rankings, guarantee mentions in AI answers, or replace a full SEO plugin.

= Main features =

* **llms.txt generator:** Publish an llms.txt file using selected WordPress content, site details and descriptions.
* **robots.txt management:** Configure WordPress virtual robots.txt rules, disallowed paths, page exclusions and sitemap directives.
* **AI crawler controls:** Review and configure rules for OAI-SearchBot, GPTBot and Google-Extended.
* **AI visibility checks:** Inspect effective robots.txt behavior and crawler access at the site root.
* **Technical readiness audit:** Review configuration checks and a consistent readiness score from the WordPress dashboard.
* **SEO compatibility:** Complement existing SEO tools and use supported SEO metadata for llms.txt descriptions when available.

These are technical configuration tools for GEO and AI visibility, not a guarantee that AI assistants or search engines will crawl, index, cite or recommend your website.

= llms.txt =

Create and serve an llms.txt file from WordPress without editing files manually.

You can:

* Enable or disable llms.txt.
* Add a site description and organization information.
* Select which pages, posts, categories, and supported public post types should be represented.
* Use detected descriptions or provide custom descriptions for selected content.
* Review the generated public llms.txt file.

When available, Four47 Labs – AI Visibility, GEO & LLMs.txt can use descriptions from supported SEO metadata before falling back to WordPress excerpts or cleaned content.

= robots.txt management =

Manage crawler directives through the WordPress virtual robots.txt file from the administration area. Configure search-engine and AI-crawler rules without manually editing server files.

You can:

* Keep common WordPress areas away from crawlers.
* Add paths you do not want crawled.
* Select individual pages to disallow.
* Include the site sitemap.
* Add supported advanced directives.
* Review the resulting robots.txt output.

Four47 Labs – AI Visibility, GEO & LLMs.txt distinguishes between a WordPress virtual robots.txt file and a physical robots.txt file when this can be detected.

= AI crawler and GEO controls =

Review and configure robots.txt directives for supported AI-related crawlers, including:

* OAI-SearchBot
* GPTBot
* Google-Extended

The plugin also interprets the effective robots.txt rules and shows whether access to the site root is allowed or blocked for these crawlers.

Allowing a crawler does not guarantee that it will visit, index, cite, mention, or rank a site. Server, firewall, CDN, hosting, and other access controls can also affect crawler access.

= AI visibility and technical readiness audit =

The audit provides a technical readiness score and individual checks covering areas such as public accessibility, llms.txt, robots.txt, supported AI crawlers, and configuration consistency.

The score is a configuration aid. It is not an SEO score and does not predict rankings or visibility in any search engine or AI service.

= What the plugin does not do =

Four47 Labs – AI Visibility, GEO & LLMs.txt does not guarantee inclusion, ranking, citations, mentions, or traffic from search engines or AI assistants. It does not replace a complete SEO plugin and does not control third-party crawler behavior.

== Installation ==

1. Upload the `four47-labs-ai-visibility-controls` folder to `/wp-content/plugins/`, or install the plugin ZIP from Plugins > Add New > Upload Plugin.
2. Activate Four47 Labs – AI Visibility, GEO & LLMs.txt from the Plugins screen.
3. Open the plugin dashboard in the WordPress administration menu.
4. Configure llms.txt and robots.txt according to your site's requirements.
5. Use the dashboard and Audit screens to review the effective configuration.

Before changing robots.txt rules, review any existing crawler directives used by your site, hosting provider, security tools, CDN, or other plugins.

== Frequently Asked Questions ==

= Is this a GEO or SEO plugin? =

It provides GEO-focused technical configuration and crawler controls, including llms.txt, robots.txt and AI crawler visibility checks. It complements conventional SEO plugins but does not perform keyword research, content optimization or ranking analysis.

= Does robots.txt control AI crawler access? =

The plugin helps publish and interpret robots.txt directives for supported crawlers. These directives express preferences to compliant crawlers; they are not a firewall and cannot enforce access at the server level.



= Does llms.txt make my site appear in ChatGPT or other AI assistants? =

No. The plugin can generate and expose an llms.txt file, but llms.txt does not guarantee crawling, indexing, citations, mentions, or inclusion in an AI product.

= What is the difference between OAI-SearchBot and GPTBot? =

They are separate OpenAI user agents with different documented purposes. Four47 Labs – AI Visibility, GEO & LLMs.txt keeps their robots.txt controls separate so site owners can make independent choices for each crawler.

= What is Google-Extended? =

Google-Extended is a token used by Google to control certain uses of site content for Gemini-related systems. It is separate from the standard Google Search crawler controls.

= Does blocking an AI crawler stop it at the server? =

No. robots.txt communicates crawling preferences to compatible crawlers. It is not a firewall or server-level access control.

= Why are GPTBot and Google-Extended shown as optional in the audit? =

Allowing or blocking these crawlers can be an intentional site-owner decision. The plugin therefore reports the configured state without treating either choice as automatically good or bad.

= Does allowing OAI-SearchBot guarantee visibility in ChatGPT Search? =

No. Allowing OAI-SearchBot removes a robots.txt restriction for that crawler, but it does not guarantee crawling, inclusion, ranking, citation, or visibility.

= Can I use AI Visibility with an SEO plugin? =

Yes. The plugin is designed to complement SEO tools rather than replace them. It can also use supported SEO description metadata when generating llms.txt descriptions.

= What happens if my site already has a robots.txt file? =

The plugin checks the available robots.txt configuration and indicates when a physical file may take precedence over WordPress's virtual robots.txt behavior. Review the detected state before enabling management.

= Does AI Visibility modify my theme or WordPress core files? =

No. The plugin uses WordPress APIs and its own settings. It does not modify WordPress core or theme PHP files.

= What does the technical audit score mean? =

It summarizes selected technical configuration checks performed by AI Visibility. It is not an SEO score and should not be interpreted as a prediction of search or AI visibility.

== Screenshots ==

1. AI visibility dashboard with technical readiness overview.
2. llms.txt configuration and content selection.
3. robots.txt configuration and crawler controls.
4. AI crawler and GEO-related visibility status.
5. Technical audit with individual configuration checks.

== Privacy ==

The plugin stores its configuration in the WordPress database.

The plugin does not require visitors to submit personal data and does not add visitor tracking or advertising functionality.

Some checks may request public resources from the site's own URL in order to inspect the effective configuration. Access to third-party crawlers is ultimately controlled by the site's robots.txt rules and by any server, hosting, firewall, CDN, or security configuration outside this plugin.

== Changelog ==

= 1.0.0 =
* Unified the Dashboard score and quick audit with the same audit report used by the full Audit screen.
* Removed per-check point labels from the Dashboard quick audit to avoid presenting two scoring models.
* Added a search filter for long robots.txt page lists.
* Finalized the first stable release after public llms.txt, robots.txt, crawler visibility, and audit validation.

= 0.7.37 =
* Clarified AI crawler visibility so an absent root directive is shown as "No rule" instead of being presented as an explicit allow rule.
* Added rewrite-rule cleanup on plugin deactivation.
* Refreshed Spanish translation metadata.

= 0.7.36 =
* Improved automatic llms.txt descriptions by ranking prose candidates and avoiding structured lists and recurring boilerplate.
* Improved llms.txt automatic descriptions to prefer meaningful prose paragraphs over route statistics, tables and structured page data.

= 0.7.32 =
* Prepared plugin metadata and readme for WordPress.org distribution.
* Documented llms.txt, robots.txt, AI crawler controls, and technical audit behavior.
* Added installation, FAQ, screenshots, privacy, and crawler limitation information.
* No functional changes to the plugin's public-file generation or audit logic.