WordPress Core
- Title
- Content
- Excerpt
- Slug
- Featured Image
- Author
ContentLatch
Your WordPress content has rules. Make WordPress enforce them.
Define the content rules your site depends on, then automatically validate them before publication. Built for WordPress Core and Advanced Custom Fields (ACF).
Editing content.
Rule
Contentcontains"healthy"Blocking
Content
This recipe is a healthy choice for weeknight dinners.
What it does
Your content model can have rules. ContentLatch makes those rules enforceable.
ContentLatch is a WordPress plugin for content governance and publishing QA. Instead of only asking whether content feels ready to publish, it asks whether content conforms to the rules your site depends on—and enforces the answer.
Publishing checklist
Is this content ready to publish?
ContentLatch
Does this content conform to the rules we’ve defined for it?
- Content model Core & ACF fields
- Defined rules WHEN · THEN · severity
- ContentLatch On supported save paths
- Outcome Pass · warn · or block
How it works
From rule to enforcement
ContentLatch follows a clear path: define the rule, choose when it applies, validate content, and audit what already exists.
Workflow steps
01
Define
Create the rules your content requires.
02
Target
Choose the WordPress Core or ACF field the rule applies to.
03
Condition
Define when the rule should apply with a WHEN condition.
04
Validate
Require, constrain, or check the content with a THEN validation—or use a condition-only rule.
05
Enforce
Blocking rules prevent publication. Warnings surface without blocking.
06
Audit
Review existing published and private content against the same active rules.
Product surfaces
Rules, validation, and audit
ContentLatch connects three surfaces: the Rule Builder where you define content rules, the editor where Blocking and Warning findings appear, and Audit where existing content is reviewed.
Restricted terminology
- WHEN
- Contentcontains"healthy"
- THEN
- No validation needed
SeverityBlocking
Rule preview
When Content contains "healthy", this rule blocks publishing.
In WordPress
Real product surfaces
The Rules screen and a block-editor Blocking notice from a working ContentLatch install—real WordPress UI when a publishing rule fails, not concept mockups.
Capabilities
Built for WordPress Core and ACF
Rules target the fields your content model already uses—then ContentLatch evaluates them in Classic Editor and the block editor on supported save paths.
ACF scalars
- Text
- Textarea
- Number
- Range
- URL
- Password
- WYSIWYG
- Select
- Radio
- Button Group
- True / False
- Date Picker
- Date / Time Picker
- Color Picker
ACF structures
- Group
- Repeater
- Flexible Content
- Clone
- Nested Repeater (two levels)
Repeater, Flexible Content, and Clone require ACF Pro. Some relationship-style and media field types are outside V1. Full field support is detailed on the Features page.
When a rule fails
Blocking prevents publishing and updates to published/private content. Warning surfaces the issue without blocking.
When content passes
Matching rules stay quiet—editors publish without an extra ContentLatch step.
Editors
Classic Editor · Block editor (Gutenberg) · ACF and Core validation paths
Audit
Review existing published and private content against the same active rules.
Who it’s for
Built for teams that depend on content standards
ContentLatch is for WordPress teams that need shared rules—not one-off reminders before publish.
-
Site owners
Keep required content standards consistent across a site.
-
Agencies
Encode client-specific content requirements instead of relying entirely on manual review.
-
Editorial teams
Catch rule violations before they become published-content problems.
Next step
Make your content rules enforceable.
Define the rules. Let WordPress enforce them.
Installation docs cover requirements and setup. There is no public download yet. If you need access for development or testing, contact us.