> ## Documentation Index
> Fetch the complete documentation index at: https://impossible.sh/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Elementor integration

> What Impossible can do with Elementor-built pages: edit widgets, add sections, search content.

# Elementor integration

When your site uses Elementor for page building, Impossible uses Elementor-specific tools to edit those pages safely. Standard page edits do not work on Elementor pages.

## Prerequisites

* Elementor plugin installed and active
* Pages built with Elementor (not the block editor)
* Impossible connected

## What you can do

| Capability              | Description                                             |
| ----------------------- | ------------------------------------------------------- |
| **Edit widget content** | Change headings, paragraphs, button text, links, images |
| **Add sections**        | Add new sections with containers and widgets            |
| **Remove elements**     | Remove specific widgets or sections by ID               |
| **Search content**      | Find text or elements across the page                   |
| **Regenerate CSS**      | Refresh Elementor CSS after layout changes              |

## How it works

Elementor pages store layout and content in `_elementor_data` (JSON). Impossible:

1. Reads a summary first (Elementor data can be large)
2. Searches for the content you want to change
3. Applies targeted updates to specific widgets or sections
4. Regenerates CSS when needed

You do not need to know widget IDs or technical details. Describe what you want in plain language.

## Common widget types

| Widget           | What you can change   |
| ---------------- | --------------------- |
| Heading          | Text, size, alignment |
| Text editor      | Paragraph content     |
| Button           | Label, link, style    |
| Image            | Image swap, alt text  |
| HTML             | Raw HTML content      |
| Accordion / Tabs | Tab content, labels   |

## Conflict handling

If you try to edit an Elementor page with a normal prompt (e.g. "Change the hero text") and the agent reports a **page builder conflict**, it means the page uses Elementor. The agent will switch to Elementor tools automatically. You can also be explicit:

* "Change the hero heading to X" (agent uses Elementor tools)
* "Update the button link on the Elementor page"
* "Add a new section with two columns below the hero"

## Best practices

1. **Be specific about the element** — "Change the hero heading" or "Update the first button" helps the agent find the right widget
2. **One change at a time** — For complex edits, break into steps
3. **Reference visible content** — "The paragraph that says 'Welcome to our site'" helps with search

<Warning>
  Do not ask Impossible to "convert" an Elementor page to blocks or vice versa. Stick to editing within the current page builder.
</Warning>

## Site-wide styling

For CSS that affects Elementor output (e.g. global button styles, spacing), `write_styles` still works. You can say "Make all buttons on the site use the accent color" and the agent will add CSS accordingly.

## Next steps

* [Elementor prompts](/docs/integrations/elementor-prompts) — Curated prompt examples for Elementor pages