Skip to main content
How Can We Help?

Gutenberg

Posted
Updated
ByEmily Gomez
Bluvia A/B Testing works with the WordPress Gutenberg editor for test types that support full page or content editing.
When you create a Variant of Gutenberg-built content using a supported Test Type, Bluvia A/B Testing opens the Variant in Gutenberg so you can make changes using the same block editor as the original content.
Not every Test Type uses Gutenberg. Headline, CTA / Button, and Menu tests are configured directly within Bluvia A/B Testing and do not open the Gutenberg editor.

How Gutenberg Works With Bluvia A/B Testing

When you create an experiment that supports full content editing, start by selecting the page or post you want to test.
Bluvia A/B Testing uses the original content as the starting point for your Variant.
If the original content was built with Gutenberg, selecting Edit for the Variant opens the WordPress block editor.
You can then make your changes using the same Gutenberg blocks and editing tools you normally use to manage the content.
You don’t need to recreate the page in a separate Bluvia A/B Testing editor.

Which Tests Open in Gutenberg?

Gutenberg opens when the Test Type allows you to edit the full content of a Gutenberg-built page or post.
Other Test Types provide their own editing experience directly within Bluvia A/B Testing.
The following tests do not open Gutenberg:
  • Headline: Configure the Headline Variant directly within Bluvia A/B Testing.
  • CTA / Button: Configure the CTA or Button Variant directly within Bluvia A/B Testing.
  • Menu: Configure the Menu Variant directly within Bluvia A/B Testing.
The editing experience depends on both the Test Type and how the original content was built.

Saving Your Changes and Returning to Your Experiment

When you’re finished editing your Variant, save your changes in Gutenberg before returning to Bluvia A/B Testing.
To save and return:
  1. Select Save draft or Publish in Gutenberg to save your changes.
  2. Confirm that your changes have been saved.
  3. Select the dedicated Back button to return to your Bluvia A/B Testing experiment.
The Back button returns you to the experiment workflow but does not replace Gutenberg’s save or publish action.
Always save your changes before selecting Back. Otherwise, changes made in the Gutenberg editor may not be included in your Variant.
Once you return to Bluvia A/B Testing, you can continue reviewing your Variants, configure the remaining experiment settings, and prepare the test for launch.
We recommend using the dedicated Back button rather than your browser’s Back button when returning from the editor.

What Can You Change?

When a Variant opens in Gutenberg, you can use the block editor to make the types of content and layout changes normally available for that page or post.
Depending on the content and blocks you’re using, this may include:
  • Headlines and copy
  • Images
  • Buttons
  • Columns and layouts
  • Block styling
  • Hero sections
  • Calls to action
  • New or existing content sections
The changes are made to the Variant being tested while the original content remains the Control during the experiment.

Editing a Gutenberg Variant

For a test that supports full content editing:
  1. Create a new experiment in Bluvia A/B Testing.
  2. Select the appropriate Test Type.
  3. Select the Gutenberg page or post you want to test.
  4. Create your Variant.
  5. Open the Variant for editing.
  6. Make your changes using Gutenberg.
  7. Select Save draft or Publish to save the Variant.
  8. Confirm that your changes have been saved.
  9. Use the dedicated Back button to return to your Bluvia A/B Testing experiment.
  10. Review your Variants and configure the remaining experiment settings.
  11. Preview the Control and Variant before launching.
  12. Launch the experiment when you’re ready.
Visitors participating in the experiment will receive the Control or a Variant according to your configured Traffic Allocation.

Preview Before Launching

Always preview your Gutenberg Variant before starting the experiment.
Check that:
  • Blocks display correctly.
  • Images and media load.
  • Buttons and links work.
  • Layout changes appear as expected.
  • Interactive blocks function correctly.
  • The page looks correct across the devices important to your audience.
  • Your Conversion Goal works as intended.
Previewing is particularly important after making larger layout or structural changes.

Gutenberg Blocks and Other Plugins

WordPress plugins can add their own blocks to Gutenberg.
If your page uses blocks provided by another plugin, those blocks may depend on that plugin’s scripts, styles, or other functionality.
If a specific block doesn’t work correctly in a Variant, first confirm that it works correctly on the original page.
Then preview the Variant to determine whether the problem only occurs during the experiment.
If necessary, review JavaScript Conflicts, Cache Issues, or contact Bluvia A/B Testing Support.

Troubleshooting Gutenberg Experiments

If your Gutenberg Variant doesn’t look or behave as expected:
  1. Confirm that the original page works correctly.
  2. Preview the Variant.
  3. Check the affected blocks or functionality.
  4. Review whether caching or optimization is serving outdated content.
  5. Check for JavaScript conflicts if interactive blocks aren’t working.
If you need to check the original page without the experiment running, pause the experiment first.
See the Troubleshooting section for additional guidance.

Related Articles

Continue with:

Tags: