Edit Elementor pages by asking.

Rescue mode keeps connections that use a key working. Your AI app reads the error log, finds the plugin or change behind the crash, rolls it back or switches it off after your OK, then checks your key pages.

1. Reads the error log and names the plugin, theme or recent change behind the crash.
2. Tells you the smallest fix and what it would affect, then waits for your OK.
3. Sets a checkpoint, then rolls the change back or switches the culprit off.
4. Checks that your home page and other key pages load again, then turns rescue mode off.

Recipe /site_recovery

Your AI app lines up the evidence: when each error first appeared, which changes PowerWP AI recorded, and which files and plugins changed lately. It names the likely cause and what to check. Nothing on your site changes.

1. Reads the error log and finds when each error first appeared.
2. Lists recent changes recorded by PowerWP AI, plugin versions and files modified in the same days.
3. Loads the pages that look wrong, as a visitor and as an admin.
4. Ranks the likely causes with the evidence and suggests the next step.

Recipe /diagnose_site

Your AI app compares the site and home addresses with the address visitors use, finds the plugin or setting behind the loop and fixes it after your OK. It needs a connection that can still reach your site.

1. Checks what a visitor gets when opening the site and where it is sent.
2. Compares the site address and home address in the settings with the address you use.
3. Looks for a redirect plugin behind the loop, or an .htaccess rule (changing that needs Full access).
4. Fixes the setting or switches the plugin off after your OK, clears caches and tests again.

Your AI app reads WP-Cron and the WooCommerce queue, finds the overdue, failed and stuck jobs and why they stall, and runs or clears the ones you approve. It also tells you if WP-Cron is switched off.

1. Lists overdue WP-Cron events and checks whether WP-Cron is switched off on your server.
2. Counts queued background jobs by status and reads why the failed ones failed.
3. Explains what each stuck job does and what running or clearing it would trigger.
4. Runs or removes only the jobs you approve, then checks the queue again.

Your AI app scans for suspicious files, changed core files, unknown admins and injected redirects, makes a backup, and removes what you approve, one item at a time. A scan finds signs. It can’t promise a clean site.

1. Scans for suspicious files, changed core files, unknown administrators and strange redirects.
2. Searches your pages and posts for spam and injected links, then shows everything ranked by risk.
3. Makes a backup and sets a checkpoint, then removes only the items you approve.
4. Lists what you must do yourself, such as changing passwords and asking a professional to check.

Recipe /security_audit

Your AI app checks updates, core and plugin files against the official ones, suspicious code, admin accounts, exposed files and risky settings. You get a list ranked by urgency. It changes nothing.

1. Lists outdated WordPress, plugins and themes, and the ones nobody seems to maintain.
2. Compares core and wordpress.org plugin files with the official copies and lists what it couldn’t check.
3. Reviews administrators, open registration, debug settings and files that should not be public.
4. Ranks the findings as critical, should fix and nice to have, with the evidence for each.

Recipe /security_audit

Your AI app lists every account by role, with its creation date, post count and last recorded activity. After your OK it lowers roles or removes accounts and reassigns their content to someone you choose.

1. Lists administrators and other privileged accounts, flagging recently created ones.
2. Checks whether visitors can register and with which role.
3. Proposes keep, downgrade or remove for each account and waits for your OK.
4. Sets a checkpoint, then changes roles and removes accounts one at a time.

Your AI app lists inactive, outdated and unmaintained-looking plugins and themes, makes a backup, and removes them one by one after your OK. It deactivates first and checks your site before deleting.

1. Lists installed plugins and themes, which are inactive, and which have no update path.
2. Checks what still depends on them, such as the parent of your active theme.
3. Makes a backup and sets a checkpoint before the first removal.
4. Deactivates one item at a time, checks your site, and deletes only what you approve.

Your AI app lists the backups made with PowerWP AI, makes a fresh backup of today’s site, then restores the database, the files or both from the backup you pick. It restores only when you say go.

1. Lists the backups PowerWP AI made, with date, type and size, and helps you pick one.
2. Makes a fresh backup of the site as it is now, so you can return to it.
3. Prepares the restore from the backup files on your computer, or points you to the Backups screen.
4. Restores after your explicit yes, keeps the site in maintenance mode meanwhile, then checks key pages.

Your AI app lists the backups made with PowerWP AI, makes a fresh one, downloads it to your computer and compares the checksums. The server copy is removed once the download is confirmed. It can’t test a restore.

1. Lists the backups made with PowerWP AI, with date, type and size.
2. Makes a fresh full backup and waits until it is ready, listing anything it had to skip.
3. Downloads it to your computer: Claude Code does this itself, other apps give you links.
4. Compares checksums to confirm every file arrived intact, then removes the server copy.

Your AI app checks the page the way a crawler sees it: status, redirects, noindex, canonical, robots.txt, sitemap and thin content. It can’t see Search Console, so you get the likely causes and fixes, not a verdict.

1. Loads the page like a visitor and reports its status, redirects and load time.
2. Looks for noindex, a canonical pointing elsewhere, and a site-wide “discourage search engines” setting.
3. Checks that robots.txt and the sitemap respond, and whether any other page links to it.
4. Lists what to fix, most likely cause first, and what only Search Console can confirm.

Recipe /page_seo_check

Your AI app checks your key pages for titles, descriptions, headings, canonicals, noindex and structured data, and ranks what is wrong. After you approve the exact wording, it sets a checkpoint and saves the fixes.

1. Takes your key pages from the site memory, or asks which ones matter most.
2. Reads each page as a search engine does: title, description, headings, canonical, robots and structured data.
3. Lists what is missing, duplicated or marked noindex by mistake, with exact new texts and character counts.
4. Sets a checkpoint, saves only the fixes you approve and checks the pages again.

Recipe /page_seo_check

Your AI app finds the images without alt text, proposes a short description for each from its file name, title and the page it is used on, and saves the ones you approve in small batches.

1. Checks your key pages and the Media Library for images without alt text.
2. Proposes a short text for each image in a table, for you to check against the picture.
3. Sets a checkpoint, then saves the approved texts in small batches.
4. Checks the pages again and lists which images still have no alt text.

Recipe /accessibility_check

On Elementor 4, your AI app builds a complete page from your brief as a draft, using your global colors, fonts and classes. You ask for changes in plain words, preview it, and publish only when you say so.

1. Reads your global colors, fonts and an existing page of the same kind to learn your style.
2. Proposes the sections and exact texts, and asks you for prices, dates and claims it cannot know.
3. Sets a checkpoint, then builds the page as a draft, with a dry run first.
4. Shares a preview link, changes what you ask for and publishes only after a clear yes.

Recipe /elementor_new_page

Your AI app compares your global colors, fonts and classes with what key pages actually use, and lists widgets with hard-coded values and the global style each should use. It fixes the ones you approve.

1. Reads your global colors, fonts, variables and classes and notes duplicates.
2. Checks typical widgets on your key pages for hard-coded colors and fonts instead of global styles.
3. Reports each finding with the page, the element, its current value and the global style to use.
4. Sets a checkpoint, then fixes the widgets you approve, with a dry run first.

Recipe /elementor_design_review

Your AI app finds the widgets that hold the old text or link, shows a table of old and new values, and runs a dry run first. After your OK it changes the chosen widgets through Elementor.

1. Searches your pages and templates for the old text or link and lists where it appears.
2. Shows a table with page, widget, current value and proposed value, and lets you pick rows.
3. Sets a checkpoint, then runs a dry run for each page and shows the result.
4. Applies the approved rows through Elementor and checks each page for errors.

Recipes /elementor_page_outline /elementor_edit_page

Your AI app searches the database and theme files for the old name, shows the matches per table with samples, makes a backup, and replaces the name where you approve. Names inside images stay as they are.

1. Searches pages, products, menus, widgets, Elementor data, e-mail texts, settings and theme files for the old name.
2. Makes a backup and sets a checkpoint before anything changes.
3. Runs a dry run per spelling and shows the matches, so web addresses and e-mail addresses can stay.
4. Replaces the name after your OK, then checks the key pages for errors.

Recipe /safe_change

Your AI app makes a backup, shows a dry run with the matches per table, then replaces the old address in content and settings, serialized and JSON data included. DNS, certificates and server redirects stay with your host.

1. Finds where the old address is stored: content, widgets, Elementor data and settings.
2. Makes a database backup and waits until it is ready.
3. Runs a dry run that lists the matches per table, then replaces them after your OK.
4. Clears caches, then checks the home page, shop pages and wp-admin for errors and leftover old addresses.

Your AI app measures key pages, then checks caching, plugins, autoloaded settings, scheduled tasks, large images and the database, and ranks the fixes by effect. It applies the ones you approve, one at a time, and measures again.

1. Measures how fast your server delivers the home page, a typical page and, for stores, the shop.
2. Looks for heavy plugins, oversized autoloaded settings, a scheduled-task backlog, uncached pages and large image files.
3. Ranks the fixes by expected effect and effort, and says which need a backup first.
4. Applies the fix you pick after a checkpoint, then measures again before the next one.

Recipes /performance_review /safe_change

Your AI app lists the biggest tables and counts what each clean-up would remove. After a backup it cleans in small steps, measures again and tells you which clean-ups cannot be rolled back.

1. Lists the largest tables and counts revisions, auto-drafts, expired transients, spam comments and orphaned rows.
2. Shows what each clean-up would remove and which ones cannot be undone.
3. Makes a database backup and waits until it is ready.
4. Cleans one task at a time after your OK, then measures the tables again.

Your AI app finds pages with raw shortcodes, plus options and tables that no active plugin uses. After a backup it cleans the content and keeps your text, then removes the leftovers you approve.

1. Searches posts and pages for leftover shortcodes and confirms on the live page that they show as text.
2. Finds options and tables that belong to the removed plugin and checks that no active code uses them.
3. Shows what it would change or remove, makes a backup and waits for your OK.
4. Cleans the content first, then removes the approved options and tables, and checks the pages.

Your AI app finds everything that uses the old plugin, makes a plan and sets a checkpoint, then installs and switches to the new one step by step. It checks the affected pages before the old plugin is deleted.

1. Searches content, theme files and saved settings for everything that uses the old plugin.
2. Writes a plan with each affected page and setting, and waits for your OK.
3. Makes a backup if the plugin stores data, sets a checkpoint and installs the new plugin.
4. Switches content and settings in small steps, checks the pages and keeps the old plugin deactivated.

Recipe /safe_change

Your AI app backs up the site, sets a checkpoint, updates one plugin at a time and checks your key pages after each, rolling back the one that breaks. WordPress core and PowerWP AI itself you update in wp-admin.

1. Lists the pending updates, flags big version jumps, and notes how your key pages and logs look now.
2. Proposes an order, waits for your OK, then makes a backup and sets a checkpoint.
3. Updates one plugin at a time and compares your key pages and the error log after each.
4. Rolls back the plugin that breaks something, and reports what changed, plugin by plugin.

Recipes /before_plugin_updates /safe_change

Your AI app runs the monthly check-up and writes it for the owner, not a developer: an overall status, a line each for updates, security, speed and errors, and at most five things to fix first.

1. Counts outdated plugins and themes, and checks Site Health and server versions.
2. Reads 30 days of error logs and reports only what repeats.
3. Checks for changed core files, suspicious files, new admin users and a backup routine.
4. Times your key pages, then writes one screen: what is fine, what needs attention, what it couldn’t check.

Recipe /monthly_checkup

Your AI app asks the setup questions for your kind of site and proposes your answers as facts and rules. You approve them in PowerWP AI › Memory, and every connected AI app follows them from then on.

1. Looks at your home page and key pages first, so it can suggest what they already say.
2. Asks the open questions in plain words, three or four at a time. You can skip any.
3. Saves each answer as a proposal: facts about your business, and rules like “ask before changing prices”.
4. Leaves out passwords, keys and customer data, then lists what waits for your approval.

Recipe /setup_memory