MarkuClean Markup Cleaner cleans and normalizes post content in supported WordPress editing contexts.<\/p>\n\n
It removes unwanted characters, markup artifacts, and copy-and-paste leftovers from post title, content, and excerpt values. This includes known special characters and malformed sequences commonly introduced by AI-generated content and external copy tools, such as mis-encoded quotes, dashes, ellipses, non-breaking spaces, zero-width characters, and numeric data-start\/data-end markers.<\/p>\n\n
The plugin helps keep content consistent and clean where cleanup is supported. It works with standard WordPress content edited in Gutenberg and TinyMCE-based workflows.<\/p>\n\n
For safety, builder-managed content is skipped. Elementor, WPBakery \/ Visual Composer, Beaver Builder, Divi Builder, Oxygen, Bricks, SiteOrigin, and similar editors often store structured markup, shortcode trees, JSON-like payloads, or hidden metadata. The plugin returns that content unchanged.<\/p>\n\n\n
Install from WordPress admin:<\/p>\n\n
Manual installation:<\/p>\n\n
\/wp-content\/plugins\/<\/code>.<\/li>\n- Activate the plugin in WordPress admin.<\/li>\n
- Open Settings > AI Content Cleaner and configure the enabled post types and cleanup modes.<\/li>\n<\/ol>\n\n\n
\nWhy does the plugin not work with Elementor or other builders?<\/h3><\/dt>\nThis is intentional. Builders store structured markup, shortcodes, JSON-like payloads, and metadata that the plugin does not modify.<\/p><\/dd>\n
What characters does the plugin remove or normalize?<\/h3><\/dt>\nIt can normalize configured character replacements such as mis-encoded quotes, dashes, ellipses, non-breaking spaces, zero-width characters, and similar copy artifacts. It also removes numeric data-start\/data-end markers and selected AI paste remnants where supported.<\/p><\/dd>\n
Does it change existing content permanently?<\/h3><\/dt>\nOnly when save cleanup is enabled and the current content passes the safety checks. Frontend cleanup and tester previews do not change stored content.<\/p><\/dd>\n
Can I limit it to specific post types?<\/h3><\/dt>\nYes. Enabled post types are configured in the plugin settings and are enforced across supported frontend, editor, and save-time flows.<\/p><\/dd>\n
What is the difference between display cleanup and save cleanup?<\/h3><\/dt>\nDisplay cleanup changes frontend output only and does not write to the database. Save cleanup modifies stored content when it is enabled and the current content passes the safety checks.<\/p><\/dd>\n
Is it safe to use on live websites?<\/h3><\/dt>\nIt is designed to skip unsupported contexts and builder-managed content. Use the tester first and review save cleanup settings before applying cleanup to existing content.<\/p><\/dd>\n\n<\/dl>\n\n\n
1.0.2<\/h4>\n\n\n- Fix: prevent fatal errors with legacy WPBakery \/ Visual Composer on PHP 8.3<\/li>\n
- Fix: harden all WordPress hook callbacks against unexpected input types<\/li>\n
- Fix: ensure wp_insert_post_data callbacks are safe under legacy conditions<\/li>\n
- Improvement: extend legacy WPBakery \/ Visual Composer detection<\/li>\n
- Improvement: increase overall runtime compatibility with older plugins and themes<\/li>\n<\/ul>\n\n
1.0.1<\/h4>\n\n\n- Fix: Save cleanup is now truly opt-in, no stored content is modified when disabled<\/li>\n
- Fix: Removed hardcoded \"ChatGPT\" text removal from sanitizer<\/li>\n
- Improvement: DOM cleanup now triggers only on structural AI\/UI markers, not keywords<\/li>\n
- Fix: Prevent unintended content mutation in supported editors (Gutenberg, Classic)<\/li>\n
- Fix: Sidebar preview default value is now consistent across settings, UI, and runtime<\/li>\n
- Fix: Regex\/replacement fields now preserve valid patterns (<, >, etc.)<\/li>\n
- Fix: PHP version requirement comment aligned with actual minimum version<\/li>\n
- Improvement: Updated admin UI examples to avoid misleading cleanup rules<\/li>\n
- Improvement: Increased overall sanitizer safety and reduced false-positive cleaning<\/li>\n<\/ul>\n\n
1.0.0<\/h4>\n\n\n- Initial release.<\/li>\n<\/ul>","raw_excerpt":"MarkuClean Markup Cleaner cleans and normalizes post content in supported WordPress editing contexts.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/twd.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/287157","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/twd.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/twd.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/twd.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=287157"}],"author":[{"embeddable":true,"href":"https:\/\/twd.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/ivijanstefan"}],"wp:attachment":[{"href":"https:\/\/twd.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=287157"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/twd.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=287157"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/twd.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=287157"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/twd.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=287157"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/twd.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=287157"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/twd.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=287157"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}