Amr Issa

Raptor Content Refiner adds a manual “Refine Content” button to both the Gutenberg block editor and the Classic Editor. When you click it, the plugin sends your content to an AI service that restructures it into a clean, SEO-friendly, and easy-to-read format.
What it does:
<ul>
<li>Removes unnecessary HTML tags, messy markup, and redundant elements</li>
<li>Applies proper heading hierarchy (H1 through H6 in logical order)</li>
<li>Structures content into clean paragraphs, lists, and blockquotes</li>
<li>Eliminates inline styles, empty tags, deprecated attributes, and div soup</li>
<li>Improves readability, visual clarity, and on-page SEO</li>
<li>Preserves the original meaning, intent, images, and hyperlinks</li>
</ul>
Key features:
<ul>
<li>Works with posts, pages, and any custom post type</li>
<li>Never runs automatically — you are always in control</li>
<li>Supports both Gutenberg (block editor) and Classic Editor</li>
<li>Compatible with WordPress 5.8 through 7.0+</li>
<li>On WordPress 7.0+, integrates with the built-in AI Client and Connectors API</li>
<li>On WordPress 5.8–6.x, provides its own settings page for API key configuration</li>
<li>Supports OpenAI, Anthropic, and Google AI providers</li>
</ul>
<h3>External Services</h3>
This plugin connects to third-party AI services to process and restructure your content. No data is sent automatically. External API calls are made only when you manually click the “Refine Content” button.
Data transmitted: Only the HTML content of the post you are editing is sent to the AI service. No personal data, metadata, or site information is transmitted.
Depending on your configuration, the plugin may connect to one of the following services:
<h4>OpenAI</h4>
<ul>
<li>Service: OpenAI API (https://openai.com)</li>
<li>API Endpoint: https://api.openai.com/v1/chat/completions</li>
<li>Terms of Use: https://openai.com/policies/terms-of-use</li>
<li>Privacy Policy: https://openai.com/policies/privacy-policy</li>
</ul>
<h4>Anthropic</h4>
<ul>
<li>Service: Anthropic API (https://www.anthropic.com)</li>
<li>API Endpoint: https://api.anthropic.com/v1/messages</li>
<li>Terms of Service: https://www.anthropic.com/legal/consumer-terms</li>
<li>Privacy Policy: https://www.anthropic.com/legal/privacy</li>
</ul>
<h4>Google AI</h4>
<ul>
<li>Service: Google AI Gemini API (https://ai.google.dev)</li>
<li>API Endpoint: https://generativelanguage.googleapis.com/v1beta/models/</li>
<li>Terms of Service: https://policies.google.com/terms</li>
<li>Privacy Policy: https://policies.google.com/privacy</li>
</ul>
On WordPress 7.0+, the plugin uses the built-in WordPress AI Client and Connectors API. The specific AI service used depends on which connector the site administrator has configured in Settings > Connectors.
<h3>Source Code and Build Process</h3>
This plugin’s JavaScript is bundled with @wordpress/scripts (webpack-based). The human-readable source files are included in the <code>src/</code> directory inside the deployed plugin, and <code>package.json</code> documents the build tool and its dependencies.
To rebuild the assets from source:
<ol>
<li>Install Node.js dependencies: <code>npm install</code></li>
<li>Build the assets: <code>npm run build</code></li>
</ol>
This regenerates <code>build/index.js</code>, <code>build/index.asset.php</code>, <code>build/style-index.css</code>, and <code>build/style-index-rtl.css</code> from the files in <code>src/</code>.
The Classic Editor JavaScript (<code>assets/classic-editor.js</code>) and CSS (<code>assets/classic-editor.css</code>) are not bundled and are loaded directly — no build step is required for those files.

Raptor Content Refiner

One-click AI-powered content restructuring. Cleans messy markup, fixes heading hierarchy, and improves readability and SEO across posts, pages, and cu …

AS OF MAY 2016, THIS PLUGIN IS NOT BEING MAINTAINED AND WILL NOT RECEIVE ANY FUTURE UPDATES. 
CONTACT ME IF YOU’D LIKE TO LIST AN ALTERNATIVE HERE.
Shows word and sentence counts plus a readability analysis of the post 
currently being edited using three different readability measurements.
Readability analysis is an attempt to show how difficult a text is to read. 
There are several methods of doing readability analysis. The most popular 
methods are used here. The Flesch and Flesch-Kincaid methods use formulas based 
on the average number of words per sentence and the average number of syllables 
per word. The Gunning-Fog method uses a formula based on the average number of 
words per sentence and the percentage of “hard” words (words with 3 or more 
syllables) in the passage.
Both the Gunning-Fog and the Flesch-Kincaid give a score that is the number of 
years of education the reader must have completed to understand the text. 
Different types of writing calls for different scores. Technical subjects may 
require a higher level of education so a higher Fog or Kincaid score is 
acceptable. Informal writing may try for a score in the 7-10 range. The Flesch 
score is a percentage. The higher the value, the better the readability.

FD Word Statistics Plugin

Shows word and sentence counts plus a readability analysis of the post currently being edited using three different readability measurements.

Raptor Content Refiner vs FD Word Statistics Plugin