Builder Integrity detects WordPress editor and page-builder problems before they become content problems.

WHAT IT DETECTS

When editor state and stored content stop agreeing.

WordPress content can accumulate stale editor signals, malformed block structure, mixed builder state or metadata that no longer matches the content being rendered. Builder Integrity separates those signals so you can review the record before making changes in WordPress.

A WordPress page can continue to render while its stored editor state is already inconsistent. A page may contain Gutenberg block comments together with builder metadata, old Elementor data can remain after content has changed, or malformed block delimiters can stay hidden until the page is edited again. These conditions are difficult to diagnose from the front end because the visible output may still look normal.

Builder Integrity examines the stored content and editor signals directly. It distinguishes positive builder evidence from weaker historical markers, then classifies the record instead of assuming that one metadata value defines the active editor. This makes the diagnostic result useful before migrations, content cleanup, translation workflows such as REEID Translate, theme changes or troubleshooting unexpected editor behaviour.

WHY CHECK EDITOR INTEGRITY?

Where Builder Integrity helps.

Editor inconsistencies often become visible only when somebody opens a page for editing, changes builders, runs a migration, translates content or updates a plugin. Detecting the state earlier gives you a clearer starting point.

For Gutenberg content, Builder Integrity checks the block-comment structure rather than relying only on whether WordPress can render the page. It can identify orphan closing markers, mismatched delimiters, unclosed blocks, invalid block attribute JSON and malformed WordPress block comments that may otherwise appear as ordinary HTML.

Need to inspect and manually edit stored source? REEID Builder Integrity PRO adds a dedicated editable source workspace with stale-write protection and revision-backed saves.

For Elementor and SiteOrigin, the plugin records builder-specific evidence separately from Gutenberg and Classic content signals. This is useful when a record has been edited by more than one system over time or when old builder metadata remains after a workflow change.

The goal is diagnosis, not automatic cleanup. Mixed or unusual states remain diagnostic findings for manual review. Builder Integrity Free does not rewrite the record.

SUPPORTED IN 0.1.0

Conservative by design.

The first release focuses entirely on detection and diagnosis. Builder Integrity Free does not modify stored content, reconstruct Gutenberg content or migrate between builders.

• Bounded site diagnostics from WordPress admin
• Per-record diagnostics
• WP-CLI scanning
• Gutenberg structural fault detection
• Elementor and SiteOrigin state detection
• Classic/non-block content detection
• Read-only diagnostic findings and technical signals
• Read-only source evidence for supported records
• Native WordPress editor handoff for corrections

Builder Integrity does not send site content to external services and does not include telemetry.

What the first release does not do

Version 0.1.0 does not attempt Gutenberg reconstruction, automatic builder conversion, bulk content rewriting, hidden metadata cleanup or general-purpose source editing. Detected inconsistencies remain diagnostic information for review in the normal WordPress editing workflow.

Builder Integrity Free does not apply changes to the record. When a finding needs correction, use the provided editor handoff to open the record in WordPress or its active page builder.

Who is Builder Integrity for?

Builder Integrity is intended for WordPress administrators, developers, agencies and site maintainers who need to understand how content is actually stored before editing, migrating or troubleshooting it. The admin diagnostics provide a bounded site scan and individual record inspection, while WP-CLI provides the same classification workflow for technical audits and larger sites.