1. Home
  2. Blog
  3. Artificial Intelligence (AI)

Don’t paste ChatGPT into WordPress

The default move is to open ChatGPT in another tab. Ask for a rewrite. Copy. Paste into the block editor. Fix the bits that sound like a stranger wrote them. Or install a WordPress AI plugin that drops a chat bubble in the admin and sells you credits for the same conversation, one hop closer to the dashboard.

It feels like using AI on your site. It is still a conversation happening somewhere else. The model cannot see your posts. It cannot trash a draft. It cannot set a featured image. You are the paste bridge.

Generatify copilot in WordPress admin, Claude selected, asking what it can help with
Generatify’s Pro copilot on Chatbot. It reads the site, prepares a change, and waits.

Generatify is built around the other job: an assistant that can read the site, prepare a change, and wait for you before anything is written. That is the Pro copilot on Generatify > Chatbot. On the front, the page agent acts on the site for visitors instead of describing it. The helpdesk agent answers questions. They are different jobs.

A conversation is not a change

Chat is the wrong unit of work.

When you paste from another tab, the unit is a reply. When you ask a credit-metered bubble “write me a post about shipping,” the unit is still a reply. The site does not change until you do the write yourself: create the draft, pick the category, set the image, hit update.

The job you actually wanted was: look at what is already on this WordPress install, prepare the edit, show me the preview, and do nothing until I confirm.

That is a different product shape. It needs read access to your content, write paths that refuse to run without an approval gate, and your own API key, because someone has to pay the model and it should not be a markup layer you cannot see.

We already have a roundup on integrating ChatGPT, Claude, and Gemini into WordPress. That post is about getting keys into a connector. This one is about what happens after: an assistant that works on the site instead of chatting beside it.

What the copilot actually does

The copilot is Pro. It needs a connected provider. It is not a general chatbot that happens to live in WordPress.

It can read without asking: site info, search posts, list recent posts, get a post, list users. That is how “which posts mention returns” or “what did I publish in March” work against your material, not against the open internet.

Every write stops and asks first. Create a post. Update a post. Trash a post. Set terms. Set a featured image. Generate an image. Moderate a comment. Change a Generatify setting. Nothing is written when the assistant decides to write it. The plugin prepares a preview and holds a token. The action only runs when you confirm. An assistant that tries to skip asking still cannot write. That gate is in the plugin, not in the prompt.

Read the preview, not the summary. The description in the chat is generated. The preview is what will actually be written. When they disagree, trust the preview.

Point at the exact post with the mention control instead of describing it. Attach images, PDFs, or CSVs when the task needs them. Auto picks a connected model for you. If the selector says “No AI Model Available,” no connector is set up yet.

Conversations live in browser local storage, not in the database. They stay on that machine. A new chat on another computer starts empty.

It can also work on files under wp-content, with hard limits: paths cannot escape via symlinks or .., source and text extensions only, .htaccess excluded, WordPress file-edit locks honored, and every write or delete copying the previous file into uploads/generatify-backups first. Protected options (site URL, home, active plugins, theme, admin email, and similar) stay out of reach. Those protections are real. They are not a substitute for backups. Work on staging when you ask it to modify code.

On the front: act vs answer

The dashboard copilot is for you. Visitors get two different tools.

The page agent acts. A visitor says what they want. The agent works through the site to do it: find the page, apply the filter, add something to the basket, with every step shown and stoppable. It runs in the visitor’s browser. It costs nothing per request. It is on by default, so check the front end before you assume it is not there. Position defaults to bottom-left so it does not sit on top of the helpdesk.

The helpdesk agent answers. Home tab, help articles, and a message tab. Contact mode is a form that emails you. That works on free. Conversation mode is live AI answers. That is Pro, needs a connected provider, and spends API credit on every visitor message. A free install can pick Conversation in the dropdown, but the answers endpoint is Pro. Use Contact mode on free.

Two floating buttons on a phone is a lot. They can coexist on opposite sides. If you only want one, pick helpdesk for a content or service site, and the page agent for a store or an app-like site where people are trying to finish something rather than learn something.

You pay the provider. The membership is the plugin.

Free Generatify never calls an AI provider. Toxicity checking and alt text run in the browser (the toxicity checker stops a real person writing something abusive before submit; it does not replace a spam plugin). Related posts analyze content on your server. The summary button opens a prepared prompt in ChatGPT. Smart compose uses a built-in phrase list. The page agent, helpdesk contact mode, and read-only browser AI tools (WebMCP) sit on that free layer too.

Pro is everything that needs a provider, plus the Connectors tab that holds the keys: ChatGPT (OpenAI), Claude (Anthropic), Gemini (Google), Kimi (Moonshot). Toggle plus key. The whole tab is Pro.

A licence unlocks connectors. It does not include AI usage. The provider bills you. DaftPlug never sees the usage and cannot cap it. Set a spending limit in the provider dashboard before you turn on anything visitors can trigger. Consumer ChatGPT Plus is not API access. Keys live in generatify_settings in the site database; anyone with admin or database access can read them, so give each site its own key. Generated images need ChatGPT or Gemini specifically, and they are the most expensive item by a wide margin. Helpdesk conversation mode is the spend to watch, because visitors decide how often it runs.

Content generation in the editor follows the same gate: brief in, draft in the editor, nothing published. Title, content, featured image, tags, and categories are independent checkboxes. Suggest tags waits for a tap. Suggest category proposes an existing category; it does not invent one. Check every factual claim before you publish. Untouched generated drafts read like everyone else’s. That is the ranking risk, not the fact that AI typed it.

One membership, not another AI credit meter

If you already pay a chat app and a WordPress AI plugin that resells tokens, you are paying twice for a conversation that still cannot touch the site without you as glue.

Generatify is one of five Pro plugins on a DaftPlug membership. One licence unlocks Generatify (AI), Progressify (PWA), Lightify (performance), Rankify (SEO and GEO), and Snapshotify (backups). Plans differ only by site count: Pro $37.99/year for 1 site, Pro Plus $74.99/year for 5, Pro Max $138.99/year for 100. Features are identical on all three. New Pro plugins shipped while you are subscribed join the membership. Checkout is Freemius. Fourteen-day money-back.

Install Generatify free from WordPress.org. That is the same plugin, with Pro features locked rather than removed. Rankify is not on WordPress.org yet, so do not search the directory for it. Start Rankify from its product page when you want that half of the membership.

You do not need a better paste workflow. You need an assistant that reads the site, prepares the change, and waits. Confirm that, and leave the other tab alone.