> For the complete documentation index, see [llms.txt](https://developers.weglot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.weglot.com/cms/wordpress/filters/page-builders.md).

# Page builders

Keep Weglot out of page builder editors and previews

Page builders edit and preview content in the original language, from the front end. Weglot must stay out of those requests: the builder would otherwise display translated markup, and could save it back as source content.

Weglot recognises them from the query string. When one of the parameters below is present in the URL with a non-empty value, Weglot does not register its front-end hooks at all — the page is served untranslated and no language switcher is injected.

These parameters are excluded by default, so those builders need no configuration:

| Parameter                | Page builder | Excluded since   |
| ------------------------ | ------------ | ---------------- |
| `elementor-preview`      | Elementor    | earlier versions |
| `_breakdance_doing_ajax` | Breakdance   | earlier versions |
| `in-front-editor`        | Brizy        | 6.3              |
| `is-editor-iframe`       | Brizy        | 6.3              |
| `brizy_media`            | Brizy        | 6.3              |

Values PHP treats as falsy — an empty string, or `0` — do not trigger the exclusion.

#### weglot\_page\_builder\_query\_params

Use this filter to support a builder that is not listed, or to drop an entry that conflicts with another plugin.

{% hint style="info" %}
Available since Weglot 6.3. On earlier versions the list is hard-coded and cannot be extended.
{% endhint %}

| Argument        | Type  | Description                                            |
| --------------- | ----- | ------------------------------------------------------ |
| `$query_params` | array | Query parameter names that disable Weglot when present |

**Add a page builder**

Append the query parameter the builder sets while editing:

```php
<?php

add_filter( 'weglot_page_builder_query_params', 'custom_weglot_page_builder_params' );
function custom_weglot_page_builder_params( $query_params ) {
    $query_params[] = 'ct_builder'; // Oxygen.
    return $query_params;
}
```

Several at once:

```php
<?php

add_filter( 'weglot_page_builder_query_params', function( $query_params ) {
    return array_merge( $query_params, array( 'bricks', 'brx_preview' ) );
} );
```

**Remove a parameter**

`in-front-editor` and `is-editor-iframe` are not prefixed by their plugin. If another plugin uses one of those names on public URLs, translation would be skipped there. Remove the entry rather than patching Weglot:

```php
<?php

add_filter( 'weglot_page_builder_query_params', function( $query_params ) {
    return array_values( array_diff( $query_params, array( 'is-editor-iframe' ) ) );
} );
```

**Finding the right parameter**

Open a page in the builder's editor and look at the URL of the editing frame. The parameter the builder adds there — often the one carrying the post ID, or an `ajax`/`preview` flag — is the one to declare. Parameters are matched exactly, and the filter must return an array of strings.

{% hint style="info" %}
To disable Weglot whenever a builder is loaded, and not only inside its editor, see [Deactivate Weglot on Elementor](/cms/wordpress/use-cases/deactivate-weglot-on-elementor.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developers.weglot.com/cms/wordpress/filters/page-builders.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.