Use cases · Agencies and freelancers

Take over a client site in minutes.

An overview of a new client site before the kick-off call, updates one plugin at a time, audits and monthly reports, and a change log that shows the client exactly what was done.

What’s different here

Client sites, handled with care.

Read-only first

Start every new client site with a read-only connection. Add permissions only when the client agrees to changes.

One connection per person

Give each person and each AI app their own connection, with its own permissions and log. Team gives a site 3 connections, Crew 10. Revoke one without touching the others.

A record of every change

Changes are grouped by work session and app, with what changed and how to roll it back. Useful for client reports.

Many sites, one AI app

Add each client site to your AI app as its own connection. Claude Code, Cursor or Codex can then check several sites in one session, each within its own permissions.

Example

One job, start to finish.

A made-up session on a fictional demo site. It only reads, so it works on the Free plan too.

Claude Code PowerWP your-store.com
Example · Claude Code · Demo Store

I just took over this site. Give me an overview: stack, plugins, problems and risks. Change nothing.

site_overviewsite_healthplugins_listupdates_checkerror_log_readusers_list

WordPress 7.1 on PHP 8.1 with 34 plugins, 6 inactive. Top risks: 2 plugins with updates waiting, PHP warnings printed on the shop page, and an administrator account named “admin”. The full report has 11 points, most urgent first.

Read-only · nothing changedNothing was written, so there is nothing to roll back
Use cases

28 problems your AI app can solve.

In each group, the ones made for agencies and freelancers come first; the rest work on any site. Examples run on a fictional demo store or blog. Copy a prompt, or describe your own problem in your own words.

When something breaks

A crash, a checkout that won’t take payments, e-mails that never arrive. Your AI app reads the logs, finds the cause and fixes it with you.

Any siteFree plan

Something broke and nobody knows what changed

A page, form or checkout stopped working. Updates ran, several people edited the site, and nobody can say what changed or when it started.

Example prompt

Something broke on the site and I don’t know what changed. Build a timeline of the last 7 days: errors, updates, recorded changes and modified files. Change nothing.

How your AI app solves it

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

Read-only diagnosticsReads only, nothing changes
Any site

Too many redirects, or the site points to the wrong address

Browsers show “too many redirects”, or visitors land on an old domain, a staging address or the wrong http or https version.

Example prompt

My site shows “too many redirects”. Check the site address and home address in the settings, my redirect and https plugins, and what a visitor gets. Show me the fix before you change anything.

How your AI app solves it

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.
DeveloperRecorded; a cache flush can’t be rolled back
Any site

Your site shows a critical error

Visitors see “There has been a critical error on this website” or a blank page, often right after an update or an edit.

Example prompt

My site shows “There has been a critical error”. Find out why, tell me your smallest fix and what it would affect, and wait for my OK before you change anything.

How your AI app solves it

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

DeveloperCheckpoint first, one-step rollback
Any site

Scheduled posts miss their time and background jobs pile up

Posts show “Missed schedule”, e-mails and updates arrive late, and a queue of pending background jobs keeps growing.

Example prompt

Two scheduled posts didn’t publish and WooCommerce shows thousands of pending actions. Find out what’s overdue, failed or stuck, and why. Ask before you run or delete anything.

How your AI app solves it

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.
DeveloperRecorded; a job that already ran stays done

Security and access

Hacked files, spam accounts, people who shouldn’t have admin access and backups nobody has tested.

Any site

Your site was hacked: spam pages, redirects or strange files

Google shows spam pages for your domain, visitors land on other sites, or you find files and admin accounts you never created.

Example prompt

My site shows spam pages in Google and I found files I don’t recognize. Scan for signs of a hack, back up first and list what you find. Remove nothing until I approve each item.

How your AI app solves it

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

Full accessBackup first; every removal is recorded
Any site

Too many people have admin access

Former staff, freelancers and old agencies still have administrator logins, and nobody knows which accounts are still needed.

Example prompt

List everyone with an administrator or editor role: when each account was created, what it published and when it was last active. Don’t change anything. I’ll tell you which to downgrade or remove.

How your AI app solves it

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.
Full accessCheckpoint first, one-step rollback
Any site

Old plugins and themes nobody uses

Your plugin list keeps growing, some plugins are switched off or years behind on updates, and you don’t know which are safe to remove.

Example prompt

Which plugins and themes on my site are inactive or look abandoned? Back up first, then remove them one at a time after I approve each, and check the site after each one.

How your AI app solves it

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.
DeveloperBackup first; plugin data deleted on removal stays gone
Any site

You’re not sure your backups would work

You have never tried a restore, you don’t know where the backups live, and you’re not sure the last one is complete.

Example prompt

Check which backups exist, make a fresh full backup, download it to my Documents folder and confirm the checksums match. Tell me what the backup does not include.

How your AI app solves it

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.
DeveloperMakes a copy; nothing on your site changes
Any siteFree plan

A security check-up before something happens

Plugins are months behind, you can’t remember who has an admin login, and you’d rather find the weak spots before someone else does.

Example prompt

Run a security check-up: outdated software, changed core files, suspicious code, admin accounts, public leftover files and risky settings. Rank what you find. Change nothing.

How your AI app solves it

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

Read-only diagnosticsReads only, nothing changes
Any site

You need yesterday’s site back

A bad update, a hack or a bulk edit left the site in a state you can’t fix by hand. You want yesterday’s version.

Example prompt

I need the site as it was yesterday. Show me which backups you can restore, make a new backup of today’s site first, and don’t restore anything until I say yes.

How your AI app solves it

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.
DeveloperFresh backup first; a restore can’t be rolled back

Traffic and content

SEO texts, old articles, links, images and tags: the work that brings visitors and keeps them.

Any site

Missing or duplicate titles and descriptions site-wide

Pages share titles, lack meta descriptions, carry two H1s or sit behind a stray noindex, and nobody has checked them all.

Example prompt

Check the home page, the Cookware category and our five newest posts for missing or duplicate titles and descriptions, H1 problems and noindex mistakes. Don’t change any URLs. Show me the fixes before saving.

How your AI app solves it

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

Content managerCheckpoint first, one-step rollback
Any siteFree plan

A page doesn’t show up in Google

A page you published doesn’t appear when you search for its exact title, and you can’t tell whether something on your site is blocking it.

Example prompt

My page https://your-store.com/knife-care-guide/ doesn’t show up when I search for its title. Check why it might be missing from Google. Report only, change nothing.

How your AI app solves it

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

Read-only diagnosticsReads only, nothing changes
Any site

Hundreds of images without alt text

Many product photos and blog images have no alt text, so screen reader users hear nothing and search engines get no description.

Example prompt

Check https://your-store.com/ and list the images without alt text. Propose up to 12 words for the first ten, show them in a table, and save nothing until I approve.

How your AI app solves it

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

Content managerCheckpoint first, one-step rollback

Big projects

A rebrand, a new domain, a slow site, a new landing page: the projects you keep putting off.

Any site

Rebrand: a new name and new wording everywhere

After a rename, the old name hides in page text, products, menus, widgets, Elementor pages and e-mail texts, and by hand you will miss some.

Example prompt

We’re renaming the store. Find every place the old name appears, make a backup and run a dry run first. Leave web addresses and e-mail addresses alone. Replace nothing until I approve.

How your AI app solves it

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

DeveloperBackup first; every replacement is recorded
Any site

Move to a new domain or to https

After the move, pages still load images and links from the old address, or the browser warns about mixed content.

Example prompt

Our site now loads over https, but the database still has http://your-store.com addresses. Replace them with https://your-store.com. Back up first and show me the dry run before you change anything.

How your AI app solves it

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.
DeveloperBackup first; every replacement is recorded
Any site

A database full of revisions, transients and leftovers

The database keeps growing, backups get bigger and slower, and you can’t tell which tables or rows are to blame.

Example prompt

Show me what is bloating the database and how many rows each clean-up would remove. Then make a database backup and clean expired transients and revisions older than 30 days. Nothing else without asking.

How your AI app solves it

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.
DeveloperBackup first; some clean-ups can’t be undone
Elementor · Agency

Pages that don’t look like the rest of the site

Some pages use slightly different blues, button styles and font sizes, because widgets carry their own settings instead of your global styles.

Example prompt

Review our Elementor global colors and fonts. Check the home page and our two main landing pages for hard-coded colors or fonts, and show me a table. Fix nothing until I pick the rows.

How your AI app solves it

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

Content managerCheckpoint first, one-step rollback
Any site

Leftovers from an old page builder or plugin

Text like [vc_row] shows on pages after a plugin was removed, and old options and tables stay behind in the database.

Example prompt

Since we dropped the old page builder, some pages show [vc_row] and similar text. Find those pages, and any leftover options and tables. List everything first, back up, and ask before deleting anything.

How your AI app solves it

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.
DeveloperBackup first; changes are recorded
Any site

Replace a plugin without breaking pages

You want to swap a plugin, but its shortcodes, blocks and settings are spread across the site and removing it could break pages.

Example prompt

I want to replace our old gallery plugin with a new one. Find everything that uses it first: shortcodes, blocks and settings. Give me a plan, and change nothing until I approve it.

How your AI app solves it

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

DeveloperCheckpoint first; a backup when the plugin keeps data
Business site · Agency

Launch a new site without surprises

Before launch you worry about forgotten basics: search engines still blocked, demo content left in, forms that don’t send, no backup and no HTTPS.

Example prompt

We launch on Monday. Check what is often forgotten: search engines blocked, sample content, debug mode, HTTPS, redirects, forms and e-mail, and a recent backup. Report first, then fix only what I approve.

How your AI app solves it

Your AI app checks the launch basics: search visibility, test content, forms and e-mail setup, HTTPS, redirects, backups and speed. It reports a short fix list and applies the fixes you approve, with a checkpoint first.

  1. Checks the “discourage search engines” setting, noindex tags, robots.txt and the sitemap.
  2. Looks for sample posts, test pages, demo plugins and test accounts, and lists them for you to review.
  3. Checks HTTPS, redirects, form and e-mail setup, debug mode and how fast key pages load.
  4. Makes a backup and a checkpoint, then applies only the fixes you approve.
DeveloperBackup first; fixes are recorded
Any site

A slow site or store

Pages load slowly, the admin drags and checkout feels heavy, and you can’t tell whether plugins, hosting, images or the database are to blame.

Example prompt

My site feels slow. Measure the home page and two typical pages, rank what to fix by effect, and change nothing until I choose the first fix. Measure again after each one.

How your AI app solves it

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

DeveloperRecorded; a cache flush can’t be rolled back

Every week and month

Updates, reports and check-ups that keep a site healthy, done the same careful way every time.

Any site

Update day without fear

Plugin updates are waiting, but the last time one broke the site, you found out from a visitor. So the updates keep waiting.

Example prompt

Update my plugins safely: show me the list first, then back up, update one at a time, and check the home page, the shop and the cart after each. Stop at the first problem.

How your AI app solves it

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

DeveloperBackup first; each update can be rolled back
AgencyFree plan

Take over a client site you’ve never seen

A new client hands you a site with no documentation. You don’t know the stack, what is broken or what is risky.

Example prompt

I just took over this site and have no documentation. Give me an overview: stack, plugins, theme, what is broken, what is risky, and a plan. Read only. Then suggest what to save in the site memory.

How your AI app solves it

Your AI app reads the whole setup and writes a ranked report with a fix for each problem, all read-only. With Content manager it can also propose notes for the site memory, which you approve.

  1. Reads the stack: WordPress, PHP, theme, plugins, caching, and the store if there is one.
  2. Reads the error logs, Site Health and recent changes to find what is broken.
  3. Checks core files, admin users and risky settings, and times a few key pages.
  4. Writes a prioritized report with a proposed fix for each problem.

Recipe /diagnose_site

Read-only diagnosticsReads only, nothing changes
AgencyFree plan

Write the client’s monthly report

Each month you piece together what you changed, what you updated and what is still open, then write it for the client.

Example prompt

Write the monthly report for the client: what we changed this month, which updates we made, what we fixed, and what is still open. Use the change log. Plain words, no jargon.

How your AI app solves it

Your AI app reads the month’s change log and work sessions, adds the check-up for open risks, and writes it in client-friendly words with change numbers. Changes made by hand in wp-admin aren’t in the log.

  1. Reads the month’s change log and work sessions: what changed, when, and through which connection.
  2. Lists the plugin updates and fixes done, with their change numbers.
  3. Runs the monthly check-up to find the risks that are still open.
  4. Writes it in client-friendly words, without jargon or customer details.

Recipe /monthly_checkup

Read-only diagnosticsReads only, nothing changes
Any site

Teach every AI app your business once

Every new chat or AI app starts from zero, so you repeat your tone, your rules and your business facts every time.

Example prompt

Set up the site memory. Start with these rules: ask me before changing prices, never delete anything, and write in a friendly, plain tone with no exclamation marks.

How your AI app solves it

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

Content managerNothing applies until you approve it
Agency · Business site

Give a freelancer’s AI app access for a month

A freelancer will work on your site for a month. You don’t want to share your admin login or forget to cut off access later.

Example prompt

I’m helping with this site for a month. Start with a read-only look: what is outdated, what looks risky, and what is slowing the site. Send me the plan before you change anything.

How your AI app solves it

You create a separate connection for the freelancer’s AI app with the preset the job needs, an expiry date and an IP allow-list. Everything it changes is recorded, and you can switch it off at any time.

  1. Lets you create a separate connection for the freelancer in PowerWP AI › Connections.
  2. Limits it to a preset, such as Developer, which leaves out secrets and user accounts.
  3. Stops working at the expiry date you set, and only accepts the IP addresses you list.
  4. Records every change, so you can review or roll back their work, and revoke access any time.
DeveloperRecorded, so you can roll it back
Any siteFree plan

A monthly health report in plain words

You only look at the site when something breaks. Updates pile up, backups get old, and slow problems go unnoticed.

Example prompt

Do the monthly check-up and give me a short report in plain language. Rate each area, list at most five things to fix first, and tell me what you couldn’t check. Change nothing.

How your AI app solves it

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

Read-only diagnosticsReads only, nothing changes
Recipes

Recipes for every client site.

Every site gets the universal pack: diagnosis, security and speed reviews, safe changes, page SEO, broken links, accessibility, safe updates and site recovery. Store, content and Elementor packs switch on where they fit.

Site memory

Questions your AI app asks once.

Say “Set up the site memory” and your app asks these, then proposes what to remember. Nothing is saved until you approve it, and every AI app you connect gets the answers.

Never do

What must the AI never do on this site? For example: never change prices, never delete content, never touch the checkout, never mention a competitor.

Who approves

Who approves changes on your side, and who should be told if something goes wrong (you, a developer, your host)?

Quiet hours

When is the site busiest, and when are quiet hours for updates and bigger changes?

Key pages

Which pages matter most? List the home page, contact page, top products, services or articles, and any landing pages.

Business facts

Which facts may be stated about your business (name, address, opening hours, shipping and return rules, guarantees), and where is the official wording?

Brand voice

How should your site sound? Describe the tone (for example friendly, formal or playful), words you like or avoid, and paste one paragraph from your site that you are proud of.

Pricing for client sites

One plan per site. Every tool on every plan.

Each client site needs its own plan, with every tool and safety layer. The plan can be in your client’s name or yours. A paid plan also covers one local development copy of that site, such as localhost or a .test name, without using up its site.

Solo$9 a site, a month

1 AI connection

Team$23 a site, a month

3 AI connections

Crew$59 a site, a month

10 AI connections

Prices are in USD, billed every month or once a year (20% less) for each site until you cancel. There is no agency tier and no volume discount, and the Free plan is one per customer. Looking after many sites? Write to us.

Questions

Before you start.

Can the client see what we did?

Yes. PowerWP AI › Changes lists every change with the connection that made it, grouped by work session, and the activity log records every call. Ask your app to turn a month of it into a client report.

Can we stop access when a contract ends?

Revoke your connections under PowerWP AI › Connections and access ends at once. Connections can also have an expiry date.

Do staging copies need a license?

A staging copy on a public address needs its own plan. A local copy (localhost or a .test name) needs a key too: the site’s paid plan covers one without using up its site, and a second one counts as a site.

Start with a read-only check. It changes nothing.

Look at a client site read-only first. Your client can get the Free plan in their own name, and every paid plan has the Read-only diagnostics preset too.