Preview it before anyone else does
The editor and the rendered listing sit side by side, so a broken heading or a section that never made it in is obvious while you are still writing rather than after a release.
StatWP rank, momentum and install estimates on wordpress.org.Chrome extension: StatWP on wordpress.org
Add to ChromeLearn moreWordPress.org listing
See how your plugin or theme readme.txt will look on WordPress.org, what headers are missing, and where SEO can improve.
See your listing the way WordPress.org renders it
Paste a readme and the problems surface before you ship it.
Nothing to preview yet — start typing on the left.
This preview is a from-scratch reimplementation of WordPress.org’s documented readme.txt rendering rules, not their own parser. It matches the spec closely but is not guaranteed pixel-for-pixel identical for every edge case.
Inside the Readme Checker
Paste your readme.txt and see it exactly as WordPress.org will render it, with the header fields validated and the search-facing copy scored while you edit.
The editor and the rendered listing sit side by side, so a broken heading or a section that never made it in is obvious while you are still writing rather than after a release.
Your name, short description and tags are what people read in search results. We check length, whether your lead tag actually appears, and whether the description says anything searchable.
It previews readme.txt the way WordPress.org typically renders it, flags missing required headers, and (on Power User) scores keyword coverage in the listing copy.
No. Use it while you draft. Always confirm against WordPress.org plugin or theme submission rules before you upload.
Yes. Switch between plugin and theme samples. Theme style.css headers and plugin readme.txt rules differ, and the checker follows each format.