KI-Console Connect

KI-Console Connect detects known AI crawler visits server-side by matching incoming request user agents against a crawler catalog. It helps site owners see when bots such as GPTBot, ChatGPT-related fetchers and other AI crawlers request their WordPress site. The plugin works without adding frontend JavaScript and does not track normal human visitors. Local counters in WordPress show matched crawler visits for the last 7 and 30 days. When an API token from KI-Console is configured, the plugin validates the connected WordPress domain, caches plugin entitlements, retrieves the KI-Console tracking key automatically, syncs llms.txt content when enabled, and renders a local score badge. The badge can also be placed manually with the [kicc_badge] shortcode. The llms.txt route, footer badge and optimizer modules are off by default. The plugin does not add frontend JavaScript and does not load external badge images, CSS or scripts. The optional optimizer can add AI crawler robots.txt allowances, sitemap hints, conservative meta tags, Organization/WebSite schema and IndexNow pings at runtime through WordPress hooks. If a physical robots.txt exists, administrators can optionally add a clearly marked reversible KI-Console block. If the API token becomes invalid, the service is inactive, or the plugin is disabled or uninstalled, these optimizations stop automatically or are removed best effort. The crawler catalog is cached locally and includes a bundled fallback list, so detection can continue if the remote catalog is temporarily unavailable.

0.5.8

• No remote request and no cron event on activation. The bundled crawler catalog makes the plugin fully functional offline.
• Catalog updates now run only while an administrator has explicitly connected the site with an API token; removing the token clears the scheduled event.
• The catalog request no longer sends the site URL in its User-Agent.
• Badge link output now carries rel="nofollow".

0.5.6

• Ausgabe der llms.txt über wp_kses() abgesichert (von den WordPress-Coding-Standards anerkannte Funktion).
• Eingaben im Adminbereich werden direkt beim Zugriff bereinigt.
• Pfadermittlung lädt im Frontend keine Admin-Dateien mehr nach.

0.5.5

• Pfade zu Dateien im Seitenwurzelverzeichnis über get_home_path() statt über die Konstante ABSPATH bestimmt.
• Sitemap-Adresse über get_sitemap_url() ermittelt.
• Nonce- und Berechtigungsprüfung für die Rückmeldungen im Adminbereich ergänzt.
• Ausgabe der llms.txt über wp_strip_all_tags() abgesichert.

0.5.4

• Wartungs-Release: konsistente Versionierung und sauberer WordPress.org-Build.

0.5.3

• Fixed llms.txt output being HTML-escaped (for example > became >); the file is now served as clean plain text.

0.5.2

• Fixed a 301 redirect (/llms.txt -> /llms.txt/) that could make the served llms.txt appear unavailable when rewrite rules were stale after an update; the file is now served reliably before canonical redirects run.

0.5.1

• WordPress.org readiness: hardened input sanitizing and output escaping, completed the translation template, prefixed the badge shortcode to [kicc_badge] and refreshed the external services documentation.

0.5.0

• Added manual IndexNow submission from the admin UI.
• Added optional, reversible physical robots.txt block handling.
• Kept frontend assets local and optimizer output runtime-only by default.