Elementor Content

Manipulate Elementor's JSON conservatively. Prefer an exported template or staging copy; treat direct _elementor_data writes as a low-level fallback, since widget schemas and internal metadata vary by Elementor, Pro, addon, and feature version.

Workflow

1. Identify the target: JSON template or WordPress installation.
2. For WordPress, confirm the site, post ID, post type, installed Elementor/Pro versions, and available CLI commands. Never copy version metadata from examples.
3. Read the complete document and make a timestamped backup before mutating.
4. Inspect a same-site element of the desired type when touching unfamiliar controls. Preserve unknown keys and existing value shapes.
5. Make the smallest tree/settings change that satisfies the request. Preserve IDs of unchanged elements; generate collision-free IDs only for new ones.
6. Validate JSON, structure, responsive/global references, content quality, and security before writing.
7. Write once, read back, parse again, and compare against the intended result.
8. Run Elementor's supported cache-regeneration command, clear other caches only when relevant, and visually verify editor plus frontend at relevant breakpoints.
9. Restore the backup if validation or rendering fails.

Never mutate a live production page when staging or a draft workflow is available. Never publish, delete, or bulk-update content beyond what the request authorizes.

Choose the Right Reference