AI writing assistant in WordPress: what it does
By Aleksan Aharonyan ·
An AI writing assistant in WordPress is a plugin feature that adds AI text actions to the field someone is typing in, so they can draft, rewrite, shorten, expand or correct a passage before submitting it. The AI itself runs on a provider account that the site owner connects with their own API key, and the assistant only edits text: it never publishes anything by itself.
Key takeaways
- An AI writing assistant appears as a button next to an editor field, offers actions such as write from a prompt, improve, fix spelling, shorten and expand, and previews the result before the user keeps it.
- The site owner connects an API key from a provider such as OpenAI, Anthropic Claude, Google Gemini or OpenRouter and pays that provider for the requests; AI usage is billed by the provider, not included with the plugin.
- The feature is switched on per form, can be limited to logged-in users or opened to guests, and carries a daily request limit per user.
- AI writing help improves the text, but review still decides what goes live: keep new contributors on the Pending post status and read the post yourself.
What is an AI writing assistant in WordPress?
An AI writing assistant is a set of writing actions attached to a text field and backed by a large language model the site owner has connected. WordPress gets this through plugins that hook into an editor: the block editor for staff posts, or a front-end submission form when the writing comes from visitors and members.
Three jobs get called “AI”, and they are worth separating:
- Writing help changes the text in front of it: a draft from a prompt, a tighter sentence, a spelling fix, a shorter version.
- Generation fills in fields after submission, such as an excerpt, tags or an SEO meta description.
- Moderation reads a finished submission and decides whether it should wait for review.
The same provider key can power all three, but they are separate settings, and a site can use one without the others. This article is about the first: the button a contributor presses while writing.
What the ✨ AI button does inside a post submission form
The ✨ AI button opens a short list of actions on the field it sits next to: write from a prompt, improve writing, fix spelling and grammar, make shorter, make longer. The result appears in a preview, and the user chooses to replace the field’s text or insert the result below it, so nothing changes until they accept it.
That preview is the part worth understanding. AI output is a suggestion, and the person submitting the post stays the author of the text that gets saved. A contributor writing in a second language can keep their own structure and have the grammar cleaned up; a guest who froze at the empty box can ask for a first paragraph and then edit it.
In Front User Submit, a free plugin for frontend post submission and guest posting forms, the button appears next to the Post Title, Textarea, MD Editor, EditorJS and TinyMCE fields, so it follows whichever content editor you picked for that form. The AI writing assistant documentation lists every action and the settings behind the button.
Who pays for it: your own API key
The site owner pays, through an account with an AI provider, and the plugin does not charge for AI usage. You create a key with OpenAI, Anthropic Claude, Google Gemini or OpenRouter, or point the plugin at any OpenAI compatible API, including a local model running on your own server through Ollama or LM Studio. Each provider bills you directly at its own rates.
Two details matter for security and for how the feature behaves:
- Requests are sent from your server, so the key never appears in the page a visitor loads.
- The key can live in
wp-config.phpinstead of the database, which keeps it out of exports and backups of the options table.
A local model removes the per-request bill and keeps the text on your machine, at the cost of running and maintaining the model yourself, usually with weaker writing quality than the hosted providers. The AI setup documentation covers the provider list, the wp-config.php option and the connection test.
That connection test is worth running before you announce anything: it checks the key from the server, so a typo or a key without the right permissions shows up in the settings page instead of in a contributor’s failed click.
Who gets to use it: logged-in users, guests and daily limits
AI is off in every form until you turn it on for that form, which is the right default: a site owner who never wanted AI in the submission flow should not have to switch it off. Once it is on, two settings decide who can press the button and how often.
The access setting offers logged-in users only, which is the default, or everyone including guests. Front User Submit uses that same choice: the “Who can use it” option on the form sets whether the ✨ AI button is for members or for visitors as well, and a daily request limit per user caps how many requests one person can make, with administrators and editors exempt.
The limit is your cost control. A per-user daily cap keeps one enthusiastic contributor from running through your provider budget in an afternoon, and the exemption for administrators and editors means your own testing is never blocked.
Guests need one more piece. Letting visitors submit through the form at all requires guest posting, which is a Pro feature, so on a free site the AI button is effectively for logged-in members. If you want an open submission page where strangers write with AI help, budget for Pro; on the free version, add the registration and login shortcodes so visitors can sign up first.
What AI writing help should not do for submitted posts
AI writing help should not be given the publishing decision. It edits a passage; it does not know your rules, your house style or whether the person submitting is trustworthy, so the post status and the review queue still do that work.
Three more things to keep out of its hands:
- The final read. A grammatically clean post can still be wrong, off-topic or copied, and smoother wording makes a bad submission look better than it is. Read the post, not just the changed sentences.
- The moderation call. Front User Submit Pro adds AI moderation that checks new posts for spam, abuse and your own rules and saves flagged posts as Pending or Draft; if the provider is down, the post is saved as usual. Treat a pass from moderation as one filter, not as approval.
- The user’s own voice. Some contributors write better without suggestions, and some sites need to publish writing that is clearly the author’s. Make the button available, not compulsory, and do not rewrite a submission with AI after the author has approved it without telling them.
There is a privacy side too: whatever text a user sends to a hosted provider leaves your server. Check the provider’s terms for how submissions may be used, or run a local model if the text cannot leave your infrastructure.
Setting it up on a form, step by step
This is the order that avoids the usual mistakes: the key first, the form second, access last.
- Pick the form. Turn AI on first for the form new contributors use, where the writing is usually weakest, and leave member forms alone until you see how it goes. Each form has its own switch.
- Create the API key at the provider. Generate a key for this site only, and set a spending limit in the provider’s dashboard if it offers one.
- Store the key. Paste it into the AI settings, or define it in
wp-config.phpif you prefer, then run the connection test before saving. - Choose the access setting. Logged-in users only is the safer start; open it to guests only when the form itself accepts guests (guest posting is Pro).
- Set the daily limit. Leave the default in place on a small site and lower it if your provider budget is tight. Administrators and editors are not limited either way.
- Explain the button on the page. A short note above the form, or a paragraph field on Pro, telling people the ✨ AI button exists and that they should check the result, is worth more than any setting.
How to check it worked:
- Open the form in a private window while logged out. If access is set to logged-in users only, the AI button should not be there; if it is, the setting did not save.
- Submit a test post from a test account and use each action once, checking that the preview appears and that both “replace” and “insert below” behave.
- Run past the daily limit from one account and confirm requests stop, while an administrator account still works.
- Check the page source or the network tab and confirm the API key does not appear anywhere in the browser.
FAQ
Does an AI writing assistant add a monthly AI fee?
Not from the plugin. You connect your own API key from OpenAI, Anthropic Claude, Google Gemini, OpenRouter or an OpenAI compatible endpoint, and the provider bills you for the requests at its own rates. A local model through Ollama or LM Studio removes the per-request cost, but you run and maintain that model yourself.
Can visitors who are not logged in use the AI button?
Yes, if the form’s access setting is opened to everyone and the form accepts guest posts. Guest posting is a Pro feature, so on the free version the AI button stays with logged-in members. Without guest posting, a visitor who is not logged in sees the restricted-page message instead of the form.
Does the AI write the whole post for my users?
It can draft from a prompt into a single field, and the user can expand or shorten that text, but the assistant does not fill the whole post, choose categories or publish anything. The post still follows the form’s post status, so a Pending setting holds every submission for your review.