AgizoAI.com

<p>AgizoAI HTML AI Clean Up adds a manual scan and clean-up tool to the WordPress post editor. It is designed for editors who copy and paste content from AI tools, chat assistants, document editors, page builders or rich-text sources and want to remove unnecessary hidden HTML code before saving.</p>
<p>AI-assisted and copied content can include invisible markup that is not useful in a normal WordPress article. This can include hidden comments, <code>data-*</code> tracking or tool attributes, copied accessibility attributes, inline styles, SVG blocks, hidden inputs, invisible <code>display:none</code> fragments, Microsoft Office markup, event attributes and empty wrapper attributes. This plugin helps scan and clean that noisy markup from the current editor content.</p>
<p>Version 1.6.3 includes Editor Quality Tools, HTML quality scoring, accessibility warnings, SEO-safe HTML checks and compliance-focused review notes for WordPress.org submission. Compatible with WordPress 7.00 using the WordPress.org readme field <code>Tested up to: 7.0</code>.</p>
<p>Official plugin page: https://www.agizoai.com/agizoai-html-ai-clean-up-wordpress-plugin</p>
<p>The clean-up runs in the browser inside the editor. It does not call an AI provider, does not send post content to an external server and does not publish or save anything automatically. After running the clean-up, the editor should review the post and save it manually.</p>
<p>The plugin is intentionally editor-focused. It does not add front-end scripts, tracking pixels, analytics, advertising code, remote fonts or external assets.</p>
<h4>Main features</h4>
<ul>
<li>Editor Quality Tools with HTML quality score from 0 to 100.</li>
<li>Accessibility warnings for missing image alt text, empty links, heading skips, duplicate IDs, tables without headers and untitled iframes.</li>
<li>SEO-safe HTML checks for H1 tags inside post content, unsafe links, long content without headings, long paragraphs, empty wrapper blocks and markdown artefacts.</li>
<li>Quality score column in the site-wide scanner.</li>
<li>Unified admin menu under AgizoAI HTML AI Clean Up with Overview, HTML Scan and Settings pages.</li>
<li>Scan recent posts, pages or public custom post types by status.</li>
<li>Site-wide summary showing scanned items, posts needing review and risk distribution.</li>
<li>Direct editor links for posts that contain hidden or noisy HTML.</li>
<li>Revision-safe clean-up for selected scanned posts.</li>
<li>Automatic WordPress revision backup before each changed post is saved, where revisions are supported.</li>
<li>Controlled selected-post bulk action with nonce and capability checks.</li>
<li>AI Paste Scan Report with detected hidden/noisy HTML counts.</li>
<li>Risk score: Clean, Low, Medium or High.</li>
<li>Recommended preset based on detected markup.</li>
<li>Auto Detect preset for common copy-paste sources.</li>
<li>Presets for AI Tool Paste, Google Docs Paste, Microsoft Word Paste, Page Builder Paste and Strict Article Clean.</li>
<li>Scan content without changing the article.</li>
<li>Preview a clean-up report before applying changes.</li>
<li>Clean the full post content manually.</li>
<li>Clean the selected Gutenberg block only.</li>
<li>Undo the last clean-up before saving.</li>
<li>Protected elements for shortcodes, embeds, tables, images, figures, WordPress block comments and JSON-LD schema.</li>
<li>Enable the editor tool on posts, pages or public custom post types from the settings page.</li>
<li>Configure Custom Clean rules from the settings page.</li>
<li>Works with the block editor where edited post content is available.</li>
<li>Falls back to the classic editor content field when needed.</li>
<li>No external API calls.</li>
<li>No tracking or remote logging.</li>
<li>No custom database tables.</li>
<li>No automatic post publishing.</li>
<li>No automatic bulk clean-up without explicit selected-post confirmation.</li>
</ul>
<h4>AI Paste Scan Report</h4>
<p>The Scan Content and Preview Clean Up buttons show a report before saving, including items such as:</p>
<ul>
<li>HTML comments.</li>
<li>Inline SVG blocks.</li>
<li>Script, style or noscript blocks.</li>
<li>Hidden inputs.</li>
<li>Hidden or invisible elements.</li>
<li><code>data-*</code> attributes.</li>
<li><code>aria-*</code> attributes.</li>
<li><code>role</code> attributes.</li>
<li>Inline <code>style</code> attributes.</li>
<li>Empty attributes.</li>
<li>JavaScript event attributes such as <code>onclick</code>.</li>
<li>XML or namespace attributes.</li>
<li>Microsoft Office formatting attributes/classes.</li>
<li>Strict Article Clean removals.</li>
<li>Protected items kept intact.</li>
</ul>
<h4>Risk score</h4>
<p>The plugin calculates a simple local risk score from the detected markup. Hidden elements, pasted scripts, event attributes and invisible code increase the risk more than harmless formatting attributes. The score is only a guide for editorial review and does not send data anywhere.</p>
<h4>Clean-up presets</h4>
<p>Auto Detect scans the content and chooses a suitable preset before cleaning.</p>
<p>AI Tool Paste targets attributes, comments, hidden fragments and wrappers commonly copied from AI chat or writing interfaces.</p>
<p>Google Docs Paste removes rich-text noise while protecting tables, images, links and article structure.</p>
<p>Microsoft Word Paste targets Office classes, XML-style attributes, inline styling and pasted formatting noise.</p>
<p>Page Builder Paste removes noisy wrappers more carefully while protecting embeds, figures and block structure.</p>
<p>Strict Article Clean is for editorial article HTML. It removes more formatting and keeps common content tags.</p>
<p>Safe Clean removes comments, common <code>data-*</code> attributes, empty attributes and pasted script/style fragments while preserving most visible formatting.</p>
<p>Standard Clean is recommended for normal AI copy-paste clean-up and removes hidden markup, inline SVG, styles and noisy wrapper attributes.</p>
<p>Aggressive Clean removes the most markup noise, including <code>id</code> attributes on <code>div</code> wrappers. Review carefully before saving.</p>
<p>Custom Clean uses the rule and protection checkboxes configured under <strong>AgizoAI HTML AI Clean Up > Settings</strong>.</p>
<h4>Protected elements</h4>
<p>Protected elements are temporarily shielded during clean-up so useful content is less likely to be altered. The default protections include:</p>
<ul>
<li>WordPress shortcodes.</li>
<li>iframe, embed, video and audio blocks.</li>
<li>Tables.</li>
<li>Image tags and alt text.</li>
<li>Figure and caption blocks.</li>
<li>WordPress block editor comments.</li>
<li>JSON-LD schema scripts.</li>
</ul>
<h4>Editor Quality Tools</h4>
<p>Version 1.6.3 includes a local HTML quality check inside the editor. The <strong>Check HTML Quality</strong> button analyses the current editor content without changing it and returns:</p>
<ul>
<li>HTML quality score from 0 to 100.</li>
<li>Accessibility warnings.</li>
<li>SEO-safe HTML checks.</li>
<li>HTML structure checks.</li>
<li>Word count used for the quality report.</li>
</ul>
<p>The accessibility checks can flag images without alt text, iframes without title attributes, links without visible text, weak link text, skipped heading levels, duplicate IDs and tables without header cells.</p>
<p>The SEO-safe HTML checks can flag H1 tags inside the post body, unsafe or empty links, long content without subheadings, long paragraphs, markdown artefacts and very short content. These checks are editorial helpers only; they do not replace a full SEO plugin or a manual accessibility review.</p>
<h4>Site-wide scanner and revision-safe selected clean-up</h4>
<p>The scanner under <strong>AgizoAI HTML AI Clean Up > HTML Scan</strong> checks existing content for hidden AI/paste markup and shows which posts may need review. It can check recent editable content by post type and status. Results include:</p>
<ul>
<li>Post title and edit link.</li>
<li>Post status and last modified date.</li>
<li>Risk level and numeric risk score.</li>
<li>Recommended clean-up preset.</li>
<li>Detected items such as hidden comments, <code>data-*</code> attributes, inline styles, hidden elements, pasted scripts, SVG blocks and Microsoft Office markup.</li>
<li>HTML quality score and quality warning count.</li>
</ul>
<p>Version 1.4.0 adds a controlled selected-post clean-up action to the scanner. After scanning, an authorised editor can select specific flagged posts, choose a clean-up preset and run <strong>Clean selected posts</strong>. The plugin creates a WordPress revision backup before each changed post is saved where revisions are supported by that post type.</p>
<p>This selected-post action is not automatic. It requires a logged-in authorised user, a valid nonce, selected post IDs and edit permission for each post. It does not publish drafts, does not change post status and does not call any external service.</p>
<h4>Important note</h4>
<p>This plugin is a clean-up helper, not a replacement for editorial review. Always review the cleaned content before saving, especially if your article intentionally contains embeds, custom scripts, inline SVG, hidden accessibility text or advanced HTML.</p>
<h4>Developer filter</h4>
<p>Administrators can enable post types from the settings page. Developers can also extend supported post types with this filter:</p>
<pre><code>add_filter( 'agizohacu_supported_post_types', function( $post_types ) {
    $post_types[] = 'page';
    return $post_types;
} );
</code></pre>
<h4>Requirements</h4>
<ul>
<li>WordPress 6.0 or later.</li>
<li>Tested up to WordPress 7.00 (<code>Tested up to: 7.0</code> in the WordPress.org readme format).</li>
<li>PHP 8.1 or later.</li>
</ul>
<h3>Plugin Page</h3>
<p>Official plugin page: https://www.agizoai.com/agizoai-html-ai-clean-up-wordpress-plugin</p>
<h3>External Services</h3>
<p>This plugin does not connect to any external service. It does not send prompts, post content, metadata, API keys, analytics events or logs to any remote endpoint.</p>
<h3>Privacy</h3>
<p>AgizoAI HTML AI Clean Up does not collect, store or transmit personal data. It does not create cookies, tracking pixels or remote requests. It does not add front-end scripts.</p>
<h3>Security and Review Notes</h3>
<ul>
<li>All global PHP identifiers use the unique <code>AGIZOHACU</code> / <code>agizohacu</code> prefix. The plugin does not declare unprefixed global functions.</li>
<li>Settings are registered through the WordPress Settings API and sanitised before storage.</li>
<li>Admin forms use WordPress nonces, and AJAX actions use nonce and capability checks.</li>
<li>Admin output is escaped according to context. Dynamic scan results are returned as JSON and rendered with text-safe DOM methods.</li>
<li>The plugin does not track users, send analytics, create cookies, use remote logging or call external APIs.</li>
<li>The plugin does not register push notifications, service workers or browser notification prompts.</li>
<li>The plugin does not cache public, private or logged-in pages.</li>
<li>The plugin does not inject popups, advertising overlays or front-end scripts.</li>
</ul>


AgizoAI HTML AI Clean Up

Scan, score and clean AI-generated or pasted HTML with accessibility warnings, SEO-safe checks and revision-safe clean-up.

Steven

<p>WP-Syntax provides clean syntax highlighting using<br />
<a href="http://qbnz.com/highlighter/" rel="nofollow ugc">GeSHi</a> — supporting a wide range of popular<br />
languages.  It supports highlighting with or without line numbers and maintains formatting while copying snippets of code<br />
from the browser.</p>
<p>It avoids conflicts with other 3rd party plugins by running an early<br />
pre-filter and a late post-filter that substitutes and pulls the code snippets<br />
out first and then pushes them back in with highlighting at the end.  The<br />
result is source code formatted and highlighted the way you intended.</p>
<p>Usage, Supported Languages, Styling Guidelines, and Release Notes are available<br />
in the <a href="https://wordpress.org/extend/plugins/wp-syntax/other_notes/" rel="ugc">Other Notes</a> section.</p>
<p>Want to contribute? WP-Syntax can be found on GitHub. <a href="https://github.com/shazahm1/WP-Syntax" rel="nofollow ugc">Fork and submit your pull requests today!</a></p>
<h4>Basic Usage</h4>
<p>Wrap code blocks with <code><pre lang="LANGUAGE" line="1"></code> and <code></pre></code> where <strong>“LANGUAGE”</strong><br />
is a <a href="http://qbnz.com/highlighter/" rel="nofollow ugc">GeSHi</a> supported language syntax.<br />
The <code>line</code> attribute is optional. <a href="https://wordpress.org/extend/plugins/wp-syntax/other_notes/" rel="ugc">More usage examples</a></p>
<h3>Usage</h3>
<p>Wrap code blocks with <code><pre lang="LANGUAGE" line="1"></code> and <code></pre></code> where <strong>“LANGUAGE”</strong> is a <a href="http://qbnz.com/highlighter/" rel="nofollow ugc">GeSHi</a> supported<br />
language syntax. See below for a full list of supported languages.<br />
The <code>line</code> attribute is optional.</p>
<p><strong>Example 1: PHP, no line numbers</strong></p>
<pre><code><pre lang="php">
<div id="foo">
<?php
  function foo() {
    echo "Hello World!\\n";
  }
?>
</div>
</pre>
</code></pre>
<p><strong>Example 2: Java, with line numbers</strong></p>
<pre><code><pre lang="java" line="1">
public class Hello {
  public static void main(String[] args) {
    System.out.println("Hello World!");
  }
}
</pre>
</code></pre>
<p><strong>Example 3: Ruby, with line numbers starting at 18</strong></p>
<pre><code><pre lang="ruby" line="18">
class Example
  def example(arg1)
    return "Hello: " + arg1.to_s
  end
end
</pre>
</code></pre>
<p><strong>Example 4: If your code already has html entities escaped, use <code>escaped="true"</code> as an option</strong></p>
<pre><code><pre lang="xml" escaped="true">
&lt;xml&gt;Hello&lt;/xml&gt;
</pre>
</code></pre>
<p><strong>Example 5: PHP, with line numbers and highlighting a specific line</strong></p>
<pre><code><pre lang="php" line="1" highlight="3">
<div id="foo">
<?php
  function foo() {
    echo "Hello World!\\n";
  }
?>
</div>
</pre>
</code></pre>
<p><strong>Example 6: PHP, with a caption (file and/or file path of the source file)</strong></p>
<pre><code><pre lang="php" src"https://github.com/shazahm1/Connections/blob/master/connections.php">
<div id="foo">
<?php
  function foo() {
    echo "Hello World!\\n";
  }
?>
</div>
</pre><h3>Supported Languages</h3>
</code></pre>
<p>The following languages are most supported in the <code>lang</code> attribute:</p>
<p>abap, actionscript, actionscript3, ada, apache, applescript, apt_sources, asm,<br />
<strong>asp</strong>, autoit, avisynth, <strong>bash</strong>, bf, bibtex, blitzbasic, bnf, boo, <strong>c</strong>,<br />
c_mac, caddcl, cadlisp, cil, cfdg, cfm, cmake, cobol, cpp-qt, <strong>cpp</strong>,<br />
<strong>csharp</strong>, <strong>css</strong>, d, dcs, delphi, diff, div, dos, dot, eiffel, email, erlang,<br />
fo, fortran, freebasic, genero, gettext, glsl, gml, bnuplot, groovy, haskell,<br />
hq9plus, <strong>html4strict</strong>, idl, ini, inno, intercal, io, <strong>java</strong>, <strong>java5</strong>,<br />
<strong>javascript</strong>, kixtart, klonec, klonecpp, latex, <strong>lisp</strong>, locobasic, lolcode<br />
lotusformulas, lotusscript, lscript, lsl2, lua, m68k, make, matlab, mirc,<br />
modula3, mpasm, mxml, <strong>mysql</strong>, nsis, oberon2, <strong>objc</strong>, ocaml-brief, ocaml,<br />
oobas, <strong>oracle11</strong>, oracle8, pascal, per, pic16, pixelbender, <strong>perl</strong>,<br />
php-brief, <strong>php</strong>, plsql, povray, powershell, progress, prolog, properties,<br />
providex, <strong>python</strong>, qbasic, <strong>rails</strong>, rebol, reg, robots, <strong>ruby</strong>, sas,<br />
scala, scheme, scilab, sdlbasic, smalltalk, smarty, <strong>sql</strong>, tcl, teraterm,<br />
text, thinbasic, tsql, typoscript, <strong>vb</strong>, <strong>vbnet</strong>, verilog, vhdl, vim,<br />
visualfoxpro, visualprolog, whitespace, whois, winbatch, <strong>xml</strong>, xorg_conf,<br />
xpp, z80</p>
<p>See the <a href="http://qbnz.com/highlighter/geshi-doc.html" rel="nofollow ugc">GeSHi Documentation</a><br />
for a full list of supported languages.</p>
<p>(Bold languages just highlight the more popular ones.)</p>
<h3>Styling Guidelines</h3>
<p>WP-Syntax colors code using the default GeSHi colors.  It also uses inline<br />
styling to make sure that code highlights still work in RSS feeds.  It uses a<br />
default <code>wp-syntax.css</code> stylesheet for basic layout.  To customize your styling,<br />
copy the default <code>wp-content/plugins/wp-syntax/wp-syntax.css</code> to your theme’s<br />
template directory and modify it.  If a file named <code>wp-syntax.css</code> exists in<br />
your theme’s template directory, this stylesheet is used instead of the default.<br />
This allows theme authors to add their own customizations as they see fit.</p>
<h3>Advanced Customization</h3>
<p>WP-Syntax supports a <code>wp_syntax_init_geshi</code> action hook to customize GeSHi<br />
initialization settings.  Blog owners can handle the hook in a hand-made plugin<br />
or somewhere else like this:</p>
<pre><code><?php
add_action('wp_syntax_init_geshi', 'my_custom_geshi_styles');

function my_custom_geshi_styles(&$geshi)
{
    $geshi->set_brackets_style('color: #000;');
    $geshi->set_keyword_group_style(1, 'color: #22f;');
}
?>
</code></pre>
<p>This allows for a great possibility of different customizations. Be sure to<br />
review the <a href="http://qbnz.com/highlighter/geshi-doc.html" rel="nofollow ugc">GeSHi Documentation</a>.</p>


WP-Syntax

WP-Syntax provides clean syntax highlighting for embedding source code within pages or posts.

AgizoAI HTML AI Clean Up vs WP-Syntax