WordPress plugin readme short description under 150 characters
Use the first readme description line as a 150-character plugin-browser filter, not as a compressed homepage pitch.
Why this can grow a startup
WordPress says the readme controls the front-facing plugin directory output, and the short description line sits directly under the plugin name. That means the first sentence does shelf work before screenshots, FAQ, or support proof have a chance to help. If the line names the user and the job in plain language, the right admin keeps reading. If it turns into marketing sludge, it gets cut off and the page starts vague.
Company example
WordPress says the short description should be no more than 150 characters, should avoid markup, and will be cut off if it runs longer than that.
Source and metric
Source: WordPress Plugin Handbook: Plugin Readmes · Browse WordPress Plugin Handbook: Plugin Readmes tactics
WordPress recommends a 150-character short description because that line is what shows under the plugin name in the directory.
When to use it
Use this when Marketplaces, SEO, Positioning is relevant to plugin browser, readme, short description and you can run a bounded test with a free budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
Founder checklist
- Read WordPress Plugin Handbook: Plugin Readmes and identify what is directly supported.
- Choose one channel context: Marketplaces, SEO, Positioning.
- Define the test around WordPress recommends a 150-character short description because that line is what shows under the plugin name in the directory..
- Set an owner, evidence window, and stop condition before launch.
Explore the context
Apply this with an operator
Turn isolated search tactics into a crawlable visibility system tied to demand and proof.