Can AI read plugin pages on WordPress.org?
A lot of it can be read. On 2026-11-10 we read wordpress.org's robots.txt and one plugin page (Contact Form 7): the plugin page is not blocked by robots.txt, and the full description, rating, install count and update date are all in the HTML, along with a SoftwareApplication JSON-LD block. Whether AI reads and cites these pages is not stated by the directory and we have no evidence of actual citations, so it is not verified.
| What we checked | Result (2026-11-10) | What it tells you |
|---|---|---|
| robots.txt | Names GPTBot, ClaudeBot, anthropic-ai, Google-Extended, Applebot-Extended, PerplexityBot, Bytespider, CCBot and Copilot, each group with Allow: /; blocks only /wp-admin/, /search, /?s= and /plugins/search/; lists 9 sitemaps | Plugin pages are explicitly open to these crawlers; OAI-SearchBot, ChatGPT-User, Claude-User and Perplexity-User are not named, fall under the * rules, and are not blocked either |
| Plugin page HTML (about 196 KB) | The title is “Plugin name – WordPress plugin | WordPress.org”; the meta description and og:description both equal the readme's short description; the canonical points to itself | The short description is the first sentence both search results and AI see |
| Structured data | One JSON-LD block, typed SoftwareApplication plus Product: applicationCategory (Plugin), operatingSystem (WordPress), softwareVersion, downloadUrl, dateModified, aggregateRating, download count, images | Version, update date, rating and review count appear as structured data; the directory generates it, and you can influence it only through the readme and the plugin header |
| Visible page text | Headings for Description, Installation, FAQ, Reviews and Changelog in full; the side column has active installations, last updated, required WordPress and PHP versions, tested-up-to version, languages and the count per star rating | Readable without running scripts; every readme field maps to a block of text on the page |
| Plugin sitemap | /plugins/sitemap.xml is a sitemap index pointing to sitemap-index-1.xml (37 entries) and an image sitemap; one child sitemap holds 1,000 URLs, including plugin pages | New plugins and updates have a chance of being discovered by crawlers |
| Public JSON API | api.wordpress.org/plugins/info/1.2/ returns JSON: version, requirements, rating, installs, sections (description, installation, faq, changelog and more), tags | There is a ready-made interface for reading plugin data programmatically; whether AI products use it is not verified |
Unlike a WordPress website (your own site), whose crawler rules, structured data and server-rendered content are covered in How to optimize a WordPress site for AI search, this guide covers only the plugin directory page and what plugin authors still need to add on their own site.
What is the official limit of each readme.txt field, and how should you write it?
Almost all the text on a plugin page comes from readme.txt and the header of the main plugin file. The limits below come from the Plugin Handbook (viewed 2026-11-10); the “How to write it” column is our suggestion.
| Field | Docs | How to write it |
|---|---|---|
| short description (the first paragraph after the header) | No more than 150 characters, no markup; longer text is cut off; shown directly under the plugin name | One sentence: for whom and what it does, no “best”, no keyword stuffing; it is the meta description |
| Tags | 1 to 5; do not use a competitor's plugin name as a tag; tags only your plugin uses are not shown | Pick words users really search, such as reviews or product reviews, not long phrases |
| Requires at least, Requires PHP | Since WordPress 5.8 they are read from the main plugin PHP file; these two lines in the readme are no longer parsed | Get them right in the main file header; the version requirements in the side column come from there |
| Tested up to | Write the WordPress major version; minor versions are ignored | Test and update after each WordPress major release; the “tested up to” value in the side column is one clue AI may use to judge whether a plugin is still maintained (inference, not verified) |
| Description section | No length limit is given; the docs only warn that a readme over 10k may cause errors, and the description should explain the plugin, not sell it | Define the plugin in the first paragraph; use second-level headings for features, who it is for and how it differs from similar plugins |
| FAQ section | The docs say the FAQ should actually address issues | One question, one answer; use users' own words, such as “Is it compatible with WooCommerce?” |
| Changelog section | The docs recommend keeping only the current release in the readme and older ones in changelog.txt | Write the version number and the real date for each entry |
| Images (assets directory) | banner-772x250 (high-DPI 1544x500); icon-128x128, 256x256 or icon.svg; screenshot-1.png onward, lowercase filenames, each with a matching line in the readme | Write each screenshot caption as a full sentence; do not rely on the image alone |
One fact the docs do not state but we saw in testing: the readme's Description, Installation, FAQ and Changelog are all in the plugin page's HTML (and in the API's sections), so the readme is all of the body text you control on the directory page. For how to write a changelog page see Do changelog pages help AI search?; for comparison pages see How do you write an “X vs Y” comparison page that AI cites?.
With a directory page, why do you still need your own website?
Because the directory page only fits a readme: the format is fixed, it has none of the “how is it different from plugin X” or “which kind of site is it for” content that AI uses as answer material, and it has no room for your pricing, support policy or case studies. Put these on your own pages and keep them consistent with the readme.
| Page | Question it answers | What goes in |
|---|---|---|
| Plugin landing page | What is this plugin and who is it for? | The first paragraph matches the readme's short description; a feature table; the required WordPress and PHP versions; a link to the directory page; the update date |
| Comparison page | How does it differ from plugin X? | One comparison table, with a source and a date for every item |
| Changelog page | What changed in the latest version? | Version number, date and change categories, consistent with the readme's Changelog |
| Pricing page (if you have a paid version) | Which features are in which version? | List features and prices by version, with an update date |
Structured data: the directory page already carries SoftwareApplication; add one to your own landing page too, with fields that match the text, as described in Should a SaaS add SoftwareApplication structured data?. If the plugin is also an open-source project on GitHub, see How do open source projects get recommended by AI search? Six places beyond the README for the README and repository.
How do you make a plugin easier for AI to recommend, step by step?
1. Get the start of the readme right
Keep the short description within 150 characters and write it as one full sentence; an example is below. Define the plugin in the first paragraph of the Description.
=== Example Reviews Plugin === Contributors: yourwordpressorgusername Tags: reviews, product reviews, testimonials Requires at least: 6.0 Tested up to: 6.8 Requires PHP: 7.4 Stable tag: 1.4.0 License: GPLv2 or later Collect and display product reviews on WooCommerce stores, with email requests and a reviews block. == Description == Example Reviews Plugin sends a review request after an order ships and shows the reviews on product pages. == Changelog == = 1.4.0 - 2026-11-03 = * Added: reviews block for the block editor.
2. Update Tested up to and the Changelog for every version
One entry per version with the real date; move older entries to changelog.txt and keep the readme under 10k.
3. Write the FAQ in users' own words
Pick the most common questions from the support forum, one question and one answer each.
4. Build a plugin landing page on your own site
The first paragraph matches the short description; add a feature table, version requirements, a link to the comparison page and the changelog. Check your site's crawler rules with AI crawler check; the rules are covered in How to write robots.txt for AI crawlers.
5. Add SoftwareApplication structured data to your site
Name, version, applicationCategory and operatingSystem match the directory page; how to write it is in Should a SaaS add SoftwareApplication structured data?.
6. Test again in two months with the same questions
Ask ChatGPT and Perplexity “a question of your kind + WordPress plugin”, and note whether you are mentioned; if not, go back to step 3 and add FAQ and comparison pages.
This also applies if your site is not WordPress; if it is, the pitfalls that plugins, themes and SEO plugins bring are covered in How to optimize a WordPress site for AI search.
If you build a Google Workspace add-on, the Marketplace app page's robots.txt and sitemap tests and the vendor's listing requirements are in How do AI search tools find Google Workspace add-ons? The Marketplace app page, tested.
If you build a Jira or Confluence app, the Atlassian Marketplace app page's robots.txt and sitemap tests and the vendor's naming rules are in How do AI search tools find Atlassian Marketplace apps? App pages tested, plus the vendor's requirements.
FAQ
Will ChatGPT cite pages in the WordPress plugin directory?
We found no official statement and have no evidence of actual citations, so it is not verified. What we can confirm: on 2026-11-10 wordpress.org's robots.txt says Allow: / for GPTBot, ClaudeBot, PerplexityBot and others, plugin pages are not blocked, and the description and rating are in the HTML.
What is the maximum length of the readme.txt short description?
The official readme.txt documentation (viewed 2026-11-10) says no more than 150 characters and no markup; longer text is cut off. It is also the plugin page's meta description.
How many tags can a plugin have?
The docs say 1 to 5; a competitor's plugin name must not be used, and tags only your plugin uses are not shown.
Does the rating on a plugin page affect AI recommendations?
Not verified. The docs do not say. What we can confirm is that the rating and review count are in the plugin page's HTML and JSON-LD.
Does Requires PHP go in the readme or the main file?
The docs (viewed 2026-11-10) say that since WordPress 5.8 the readme's Requires PHP and Requires at least are no longer parsed and are read from the header of the main plugin PHP file.
Sources
- WordPress.org · wordpress.org/robots.txt (Read 2026-11-10)
- WordPress.org · Example plugin page (checked for what the HTML contains) (Read 2026-11-10)
- WordPress.org · wordpress.org/plugins/sitemap.xml (Read 2026-11-10)
- WordPress Developer Resources · How Your readme.txt Works (checked 2026-11-10)
- WordPress Developer Resources · Plugin Assets (checked 2026-11-10)
- kagentx evaluations: the data on the case study pages; each example gives its date.