Use the WordPress Elementor skill in Claude Code Print

Quick answer

Use Jezweb's wordpress-elementor skill in Claude Code to guide changes to an existing Elementor page. Confirm the page and editor version, use the native visual editor for layout changes, and verify the saved page at phone, tablet and desktop widths. The skill currently declares Claude Code compatibility and requires separate authorized browser or WP-CLI access.

Applies to

Interactive Online-hosted WordPress sites already using Elementor. This community skill is published by Jezweb, not Elementor. It is separate from Elementor Pro, Elementor's built-in AI, and Elementor's supported MCP tools. Its older widget-oriented examples do not prove that every V4 Atomic element or third-party widget works through every method. Codex users should use a verified compatible workflow rather than assuming this skill's Claude-specific setup transfers unchanged.

1. Install the reviewed skill

1. Open the Jezweb repository and the exact source folder linked below. Read SKILL.md, its access prerequisites and the MIT license.
2. For a focused manual install, download or check out the repository outside the public website folder and copy the complete plugins/wordpress/skills/wordpress-elementor folder into the project's .claude/skills/ folder. Preserve existing modified copies.
3. Alternatively, use the repository's documented Claude marketplace method and select its wordpress plugin. That bundle also includes setup/content skills. Use one method and inspect the marketplace name and package before accepting.
4. Verify the skill is visible in the current Claude Code session. Confirm the browser or WP-CLI connection separately, using only the WordPress account and site you are authorized to edit.

2. Identify the page and what is shared

1. Record the page URL, page ID, status, Elementor version and whether the editor uses V3 widgets or V4 Atomic elements. Keep a recoverable page revision and relevant settings.
2. Open the intended page using Pages > All Pages > Edit with Elementor or the existing site entry point. Select the target element and confirm its text or image in the editor controls.
3. Check whether the element belongs to a shared template, global widget or global style. A request for one page does not authorize changing every page that uses a shared item.

3. Make one approved change

Use wordpress-elementor on the approved staging page only.
Identify the Services heading and its native widget or element.
Replace its text with "Practical help for your next project."
Preserve its ID, link, heading level, style and responsive settings.
Do not change shared templates or other pages.
Show the planned change before saving or publishing.

For layout, spacing, widgets and template changes, use the supported visual editor. For a text or image change, review the exact element and expected occurrence count before any programmatic operation. The published skill includes database search-and-replace examples. Those commands can affect multiple pages or templates in the selected table; they are not automatically limited to the page currently open. Request a page-specific method with exact before/after evidence, or make the edit through the native controls.

4. Verify the result and recovery

1. Use the editor's current preview and save/update controls. The label and location vary by Elementor version; confirm that the save completed.
2. Check the edited heading or image, button destination, image alternative text, layout and keyboard operation. Inspect phone and tablet previews and another page if a shared item was deliberately changed.
3. Reopen the page in Elementor to confirm its native elements remain editable. Verify the public or protected staging URL separately from the editor preview.
4. If the public result is stale, confirm the saved revision and clear only the relevant cache using the installed version's supported controls. Use history/revisions or the saved layout recovery when needed.

If the editor or connector is unsupported

If the skill cannot control the available browser, it can still prepare copy for a manual edit. If V4 MCP tools are required, follow Elementor's official requirements and verify supported abilities separately. A missing command or unsupported widget is a reason to inspect the setup, not to convert the entire page or run a site-wide replacement.

When to contact support

Contact Interactive Online when the hosting account, WordPress installation, document root or available access method is unclear. Provide the affected page URL, tool and plugin versions, time and time zone, and the exact redacted error. Exclude passwords, Application Passwords, keys, tokens, cookies and customer records. Skill publishers handle their own installation defects and feature requirements; AI subscriptions, paid builders and connector licenses are separate from hosting.

Related help

• Install and verify the skill
• Elementor AI and supported MCP tools
• Find the right WordPress editor
• Recover one page revision
• Clear the relevant cache

Documentation and downloads

• Jezweb WordPress Elementor skill source
• Jezweb marketplace, plugin list and license
• Elementor official MCP requirements
• WP-CLI search-replace scope and dry-run behavior

Documentation and source review by Interactive Online: November 2, 2026. Installation sources and instructions were reviewed. A new installation or connected editing test was not performed for this article; confirm the versions, tools and permissions available in your own environment.