{"id":348730,"date":"2026-08-25T08:31:48","date_gmt":"2026-08-25T08:31:48","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/ai-crawler-inspector\/"},"modified":"2026-08-25T08:31:13","modified_gmt":"2026-08-25T08:31:13","slug":"phylax-ai-crawler-inspector","status":"publish","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/phylax-ai-crawler-inspector\/","author":8024611,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"0.1.0","stable_tag":"0.1.0","tested":"7.0.4","requires":"6.5","requires_php":"8.0","requires_plugins":null,"header_name":"Phylax AI Crawler Inspector","header_author":"\u0141ukasz Nowicki","header_description":"Inspect robots.txt, llms.txt, HTTP responses and HTML signals for AI-related agents.","assets_banners_color":"041c3f","last_updated":"2026-08-25 08:31:13","external_support_url":"","external_repository_url":"","donate_link":"https:\/\/paypal.me\/lukasznowicki77","header_plugin_uri":"https:\/\/phylax.pl\/wp-plugins\/","header_author_uri":"https:\/\/phylax.pl\/","rating":0,"author_block_rating":0,"active_installs":0,"downloads":50,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"0.1.0":{"tag":"0.1.0","author":"lukasznowicki","date":"2026-08-25 08:31:13"}},"upgrade_notice":{"0.1.0":"<p>Initial release of Phylax AI Crawler Inspector. Read-only diagnostics for robots.txt, llms.txt, headers and HTML signals.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3664890,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3664890,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3664890,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3664890,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.1.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3664890,"resolution":"1","location":"assets","locale":"","width":4050,"height":2700},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3664890,"resolution":"2","location":"assets","locale":"","width":4050,"height":2700},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3664890,"resolution":"3","location":"assets","locale":"","width":4050,"height":2700},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3664890,"resolution":"4","location":"assets","locale":"","width":4050,"height":2700}},"screenshots":{"1":"Tools \u2192 Phylax AI Crawler Inspector \u2014 site overview with robots and llms findings.","2":"URL inspector showing headers, canonical and HTML robots signals.","3":"Bot comparison results with explicit network-location limitations.","4":"Expandable finding evidence and client-side JSON\/CSV export actions."}},"plugin_section":[],"plugin_tags":[246479,23519,244604,12753,167235],"plugin_category":[],"plugin_contributors":[82008],"plugin_business_model":[],"class_list":["post-348730","plugin","type-plugin","status-publish","hentry","plugin_tags-ai-crawlers","plugin_tags-diagnostics","plugin_tags-llms-txt","plugin_tags-robots-txt","plugin_tags-technical-seo","plugin_contributors-lukasznowicki","plugin_committers-lukasznowicki"],"banners":{"banner":"https:\/\/ps.w.org\/phylax-ai-crawler-inspector\/assets\/banner-772x250.png?rev=3664890","banner_2x":"https:\/\/ps.w.org\/phylax-ai-crawler-inspector\/assets\/banner-1544x500.png?rev=3664890","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/phylax-ai-crawler-inspector\/assets\/icon-128x128.png?rev=3664890","icon_2x":"https:\/\/ps.w.org\/phylax-ai-crawler-inspector\/assets\/icon-256x256.png?rev=3664890","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/phylax-ai-crawler-inspector\/assets\/screenshot-1.png?rev=3664890","caption":"Tools \u2192 Phylax AI Crawler Inspector \u2014 site overview with robots and llms findings."},{"src":"https:\/\/ps.w.org\/phylax-ai-crawler-inspector\/assets\/screenshot-2.png?rev=3664890","caption":"URL inspector showing headers, canonical and HTML robots signals."},{"src":"https:\/\/ps.w.org\/phylax-ai-crawler-inspector\/assets\/screenshot-3.png?rev=3664890","caption":"Bot comparison results with explicit network-location limitations."},{"src":"https:\/\/ps.w.org\/phylax-ai-crawler-inspector\/assets\/screenshot-4.png?rev=3664890","caption":"Expandable finding evidence and client-side JSON\/CSV export actions."}],"raw_content":"<!--section=description-->\n<p>Phylax AI Crawler Inspector is a read-only diagnostic plugin for WordPress administrators who need clear evidence of how their site is presented to AI-related crawlers, search bots, training bots and user-triggered fetchers.<\/p>\n\n<p>It inspects the served robots.txt, evaluates known AI-related user agents, checks the optional \/llms.txt file, follows same-site redirect chains, reviews HTTP headers and HTML signals (canonical, meta robots, X-Robots-Tag), and can compare a neutral request with selected bot user agents.<\/p>\n\n<p>Findings keep crawl access, HTTP access and indexing directives separate. The plugin explains evidence and limitations; it does not claim that any AI product has indexed, trained on, cited or ranked your site.<\/p>\n\n<p>Product principle: inspect, explain and export. Do not modify, block, optimise or track. This is not an llms.txt generator.<\/p>\n\n<h3>Features<\/h3>\n\n<ul>\n<li>Site overview audit of robots.txt, \/llms.txt and the home page (bounded request budget)<\/li>\n<li>Robots Exclusion Protocol evaluation for a curated AI-related bot registry<\/li>\n<li>Structural validation of optional \/llms.txt (neutral when absent)<\/li>\n<li>Same-site URL inspector for headers, redirects, canonicals and HTML robots signals<\/li>\n<li>Bounded bot response comparison (status, redirects, headers and HTML signals \u2014 never raw bodies)<\/li>\n<li>Sitemap discovery from robots.txt, HTML\/HTTP Link signals and WordPress core sitemap declarations (no deep crawl)<\/li>\n<li>Structured findings with severity, status and expandable evidence<\/li>\n<li>Client-side JSON and CSV export from the current audit result<\/li>\n<li>Tools \u2192 Phylax AI Crawler Inspector admin screen with accessible status updates<\/li>\n<li>No custom database tables, no SaaS calls and no crawler-visit logging<\/li>\n<\/ul>\n\n<h3>What the plugin does not do<\/h3>\n\n<ul>\n<li>Edit, inject or generate robots.txt or llms.txt<\/li>\n<li>Block crawlers with PHP, server or firewall rules<\/li>\n<li>Log crawler visits, IPs or analytics<\/li>\n<li>Contact external SaaS APIs or require an account<\/li>\n<li>Produce overall numerical scores, graded rankings or ranking guarantees<\/li>\n<li>Crawl the entire website or schedule WP-Cron scans<\/li>\n<li>Accuse cloaking or claim to know what an external crawler sees from another network location<\/li>\n<li>Create custom database tables or modify site SEO settings<\/li>\n<\/ul>\n\n<h3>Privacy<\/h3>\n\n<p>Phylax AI Crawler Inspector does not collect telemetry, analytics or promotional data. It does not call external SaaS APIs, load remote fonts or third-party admin scripts, or set its own cookies.<\/p>\n\n<p>Audits use the WordPress HTTP API to request the administrator\u2019s own site (same-site only). Response bodies are parsed in memory and are not permanently stored. Exported JSON\/CSV reports are generated in the current admin browser session from the structured result and are not saved on the server by the plugin.<\/p>\n\n<p>The only short-lived server-side data is an optional per-user audit cooldown transient (<code>aici_audit_cd_{user_id}<\/code>). Uninstall removes only plugin-owned <code>aici_<\/code> options and transients. The plugin does not create custom database tables and does not log crawler visits.<\/p>\n\n<!--section=installation-->\n<ol>\n<li>Upload the <code>phylax-ai-crawler-inspector<\/code> directory to <code>\/wp-content\/plugins\/<\/code>, or install the ZIP through Plugins \u2192 Add New \u2192 Upload Plugin.<\/li>\n<li>Activate the plugin through the Plugins screen.<\/li>\n<li>Open Tools \u2192 Phylax AI Crawler Inspector.<\/li>\n<li>Run a site overview audit, inspect a public URL, or compare selected bot user agents.<\/li>\n<\/ol>\n\n<!--section=faq-->\n<dl>\n<dt id=\"does%20this%20guarantee%20that%20chatgpt%20or%20claude%20can%20see%20my%20website%3F\"><h3>Does this guarantee that ChatGPT or Claude can see my website?<\/h3><\/dt>\n<dd><p>No. The plugin reports what your site publishes and what same-site HTTP requests return from the WordPress server\u2019s network location. Provider crawler policy, CDN\/WAF rules, IP reputation and remote network location can all differ. It cannot guarantee inclusion, citation or visibility in any AI product.<\/p><\/dd>\n<dt id=\"does%20llms.txt%20improve%20ai%20rankings%3F\"><h3>Does llms.txt improve AI rankings?<\/h3><\/dt>\n<dd><p>There is no guarantee. llms.txt is an optional proposed discovery format. Absence is treated as neutral, not as an AI-specific failure. Presence is validated structurally; the plugin does not claim ranking or citation benefits.<\/p><\/dd>\n<dt id=\"does%20robots.txt%20securely%20block%20a%20bot%3F\"><h3>Does robots.txt securely block a bot?<\/h3><\/dt>\n<dd><p>No. robots.txt is an advisory protocol. Compliant crawlers may honour it; others may not. Actual access control requires server-side enforcement (authentication, firewall, CDN or application rules). The plugin separates published robots rules from observed HTTP responses.<\/p><\/dd>\n<dt id=\"why%20does%20the%20plugin%20say%20a%20bot%20is%20allowed%20but%20the%20http%20test%20returns%20403%3F\"><h3>Why does the plugin say a bot is allowed but the HTTP test returns 403?<\/h3><\/dt>\n<dd><p>Published robots rules and live server, CDN or WAF behaviour are different layers. A bot may be allowed in robots.txt while the HTTP response is challenged, blocked or redirected. Findings keep those layers separate and do not automatically accuse cloaking.<\/p><\/dd>\n<dt id=\"does%20the%20plugin%20send%20my%20data%20anywhere%3F\"><h3>Does the plugin send my data anywhere?<\/h3><\/dt>\n<dd><p>No. Audits use the WordPress HTTP API to request the administrator\u2019s own site (same-site only). The plugin does not call external SaaS APIs, load remote fonts or third-party admin scripts, or set its own cookies.<\/p><\/dd>\n<dt id=\"does%20the%20plugin%20log%20ai%20crawler%20visits%3F\"><h3>Does the plugin log AI crawler visits?<\/h3><\/dt>\n<dd><p>No. It does not record crawler traffic, visitor IPs or analytics events.<\/p><\/dd>\n<dt id=\"does%20the%20plugin%20change%20my%20robots.txt%20or%20llms.txt%3F\"><h3>Does the plugin change my robots.txt or llms.txt?<\/h3><\/dt>\n<dd><p>No. Version 0.1.0 is strictly read-only for site configuration and content files.<\/p><\/dd>\n<dt id=\"who%20can%20run%20audits%3F\"><h3>Who can run audits?<\/h3><\/dt>\n<dd><p>Only administrators (capability <code>manage_options<\/code>) with a valid WordPress REST nonce. Arbitrary external domains cannot be audited.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>0.1.0<\/h4>\n\n<ul>\n<li>Initial public release.<\/li>\n<li>Site overview: robots.txt evaluation, optional llms.txt validation and home-page overview with sitemap discovery.<\/li>\n<li>URL inspector and bounded bot response comparison.<\/li>\n<li>Authenticated same-site REST audits with SSRF protections and per-user cooldown.<\/li>\n<li>Accessible Tools admin screen with structured findings and client-side JSON\/CSV export.<\/li>\n<li>Privacy-preserving uninstall of plugin-owned options and transients only.<\/li>\n<\/ul>","raw_excerpt":"Inspect how this site responds to AI-related agents. Audit robots.txt, llms.txt, redirects, headers and HTML without changing the site.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/348730","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=348730"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/lukasznowicki"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=348730"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=348730"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=348730"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=348730"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=348730"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=348730"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}