Amr Issa

<p>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.</p>
<p><strong>What it does:</strong></p>
<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>
<p><strong>Key features:</strong></p>
<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>
<p>This plugin connects to third-party AI services to process and restructure your content. <strong>No data is sent automatically.</strong> External API calls are made only when you manually click the “Refine Content” button.</p>
<p><strong>Data transmitted:</strong> 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.</p>
<p>Depending on your configuration, the plugin may connect to one of the following services:</p>
<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>
<p>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.</p>
<h3>Source Code and Build Process</h3>
<p>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.</p>
<p>To rebuild the assets from source:</p>
<ol>
<li>Install Node.js dependencies: <code>npm install</code></li>
<li>Build the assets: <code>npm run build</code></li>
</ol>
<p>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>.</p>
<p>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.</p>


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 …

Joost de Valk

Yoast

Anton Timmermans

Jip Moors

Omar Reiss

Taco Verdonschot

<p>The purpose of this SEO plugin is to purge attachment URLs out of Google’s index as fast as possible. This helps sites<br />
that might have suffered from having too many thin content pages in the search index by removing them in the fastest<br />
way possible.</p>
<h3>What does this plugin do?</h3>
<p>This plugin makes all your attachment URLs return an HTTP 410 status. It then creates an XML sitemap with a recent last<br />
modified date, containing all those URLs. The XML sitemap with recent post modified date makes Google spider <em>all</em> those<br />
URLs again. The 410 status code makes sure Google takes them out of its search results in the fastest way possible.</p>
<p>With a nice trick, we also show end users the actual attachment image, so the user experience is not as poor as when<br />
they see an error page.</p>
<h3>Yoast SEO required</h3>
<p>This plugin is an extension to <a href="https://wordpress.org/plugins/wordpress-seo/" rel="ugc">Yoast SEO</a>. It requires it to work.</p>
<h3>How long should you run this plugin?</h3>
<p>After 6 months the attachment URLs should be gone from the search results. If you then remove the plugin, and keep<br />
Yoast SEO’s redirect setting on “Yes”, you have the best long term behavior for attachment URLs: to redirect to the<br />
actual attachment.</p>
<h3>Does Google condone this?</h3>
<p>This method has been discussed with and OK’d by Google.</p>
<h3>From within WordPress</h3>
<ol>
<li>Visit ‘Plugins > Add New’</li>
<li>Search for ‘Yoast SEO: Search Index Purge’</li>
<li>Activate Yoast SEO: Search Index Purge from your Plugins page.</li>
<li>Go to “after activation” below.</li>
</ol>
<h3>Manually</h3>
<ol>
<li>Upload the <code>yoast-seo-search-index-purge</code> folder to the <code>/wp-content/plugins/</code> directory</li>
<li>Activate the Yoast SEO: Search Index Purge plugin through the ‘Plugins’ menu in WordPress</li>
<li>Go to “after activation” below.</li>
</ol>
<h3>After activation</h3>


Yoast SEO: Search Index Purge

Remove attachment URLs from Google's index as fast as possible to prevent thin content penalties.

Raptor Content Refiner vs Yoast SEO: Search Index Purge