SEOPress FAQ v2 Error: “Block contains unexpected or invalid content”

If your SEOPress FAQ v2 block throws “Block contains unexpected or invalid content,” it’s usually a serialization mismatch between how the block content was saved and how it’s now generated, often after a plugin update. Below are the fastest, safest fixes: update SEOPress to a version that includes the FAQ block fix, then Attempt Block Recovery or recreate the block so the new format is saved cleanly.

The SEOPress FAQ v2 block shows “Block contains unexpected or invalid content.” What’s the fix?

Use this sequence (top to bottom) until the error is gone:

1) Update SEOPress (fix included)

Update SEOPress to a fixed version (9.1+). A recent release notes entry mentions: “FIX JSON FAQ schema with our FAQ block.” After updating, refresh the editor and test again.

2) Try the editor’s built‑in recovery

  1. Click the block’s error box → Attempt Block Recovery.
  2. If recovery fails, click the three dots () on the block → Resolve:
    • Attempt Recovery again, or
    • Convert to HTML (keeps the markup, but you’ll lose block controls).

3) Quick, reliable fix: recreate the block

  1. Select the entire FAQ v2 block → delete it.
  2. Insert a fresh FAQ v2 block and re‑enter your Q&A.
  3. Click Update to resave with the current block schema.

4) If you need to report or reproduce

  1. Open the List View, select the FAQ v2 block, open its menu, and choose Copy.
  2. Paste the copied block code into a Code block (or a support reply) so developers can reproduce the exact content.

Why this happens

When a block is saved, WordPress stores a canonical version of its content. If a subsequent plugin update changes the block’s output (for example, how JSON‑LD text strings or HTML entities are escaped), the editor compares “what’s in the database” with “what the block now outputs” and flags a mismatch. Updating, then resaving (or recreating) realigns the stored content with the block’s current serializer.

Developer tip (optional)

On pages that can’t be recovered, inspect the embedded JSON‑LD. Look for differences like escaped HTML strings vs. unescaped tags inside acceptedAnswer.text. Resaving with the updated block normalizes this automatically.

What are exact steps to make sure this never returns?

Prevent it going forward

  • Keep SEOPress current so your blocks and serializers match the version in use.
  • After major updates, open key pages that use FAQ v2, ensure no recovery notices appear, and click Update to resave.
  • Avoid mixing old and new formats (e.g., pasting legacy block markup into modern pages) without resaving.
  • Version‑control your content or export a copy before bulk edits so you can quickly roll back if needed.

Checklist if you still see the error

  1. Confirm SEOPress is 9.1+ and active on this site.
  2. Disable other editor‑altering plugins temporarily to rule out filters altering block output.
  3. Recreate the block, update the page, then test in an incognito window.

If you’re on multisite or staging, repeat the test with the same theme and plugin set to isolate environment‑specific differences.

Need human WordPress help?

WP Assistant is a free tool created by Atiba Software, a WordPress design and development company located in Nashville, TN. If you need more personalized WordPress assistance let us know, and we’ll get back to you ASAP!