Giving an AI tool access to your CMS is not useful by itself. The useful part is giving it a clear job, enough context to do that job, and a stop sign before it publishes something dumb.
Once Grok, ChatGPT, or another compatible tool is connected to Forma, these are five good places to start.
1. Audit the site before changing it
Forma exposes pages, posts, snippets, media, site settings, and SEO health through the same Site editor connection. Ask the tool to inventory the site first.
Try:
Read this Forma site without changing anything. Summarize the site structure, brand voice, important calls to action, and current SEO health. Then rank the five most useful improvements by impact and effort.
This forces the agent to look at the actual site instead of inventing a redesign from one sentence.
Forma's list endpoints already attach simple SEO status and issues to each page and post. A tool can spot missing descriptions, duplicate titles, absent social images, and similar gaps without opening every document one by one.
2. Improve one page with a review step
“Make the homepage better” is a bad prompt because better has no definition.
Try:
Read the homepage and the site's public identity. Propose a tighter headline, a clearer supporting paragraph, and one stronger call to action for a first-time visitor. Preserve the current structure and links. Show me the proposed copy before updating the page.
After reviewing the draft:
Apply that copy only. Do not change CSS, layout, navigation, or images. Then read the public homepage and confirm the new headline appears.
The second prompt narrows the write. The final verification makes the agent check the result instead of assuming a successful API response means a good page.
3. Run an SEO cleanup
Forma keeps sitewide SEO and per-page SEO in the CMS instead of hiding it behind a plugin. A connected tool can inspect both.
Try:
Find every published page or post with a missing or weak SEO title, description, or social image. Do not change anything yet. Return a table with the URL, issue, and your proposed title and description.
Then approve a subset:
Update only the title and description for the first three URLs. Keep titles under about 60 characters, descriptions useful rather than keyword-stuffed, and leave canonical URLs and robots settings unchanged.
This is the kind of repetitive work agents are good at: many small, structured edits with explicit boundaries.
4. Draft a post in the existing voice
The tool can read published posts before writing, which is more reliable than describing your voice as “professional but approachable.”
Try:
Read the five most recent posts and identify the recurring voice, average section length, and formatting habits. Draft an 800-word post about [topic] in that voice. Add a useful SEO title and description. Save it as an unpublished draft. Do not publish it.
The last two sentences matter. In Forma, a post without a publish date stays private and returns a 404 publicly. Drafting and publishing are separate decisions.
For a second pass:
Cut repetition, remove generic AI phrases, and make the opening earn the reader's attention in the first three sentences. Keep it unpublished.
5. Update media with a rollback plan
A connected Site editor can upload media and attach it to content, but it cannot delete files. That asymmetry is intentional: adding a new image is reversible; destroying the only copy of an old one may not be.
Try:
Check the featured image on [post]. Tell me its current file and dimensions. Upload the attached replacement with a descriptive filename and alt text, update only that post's featured image, and verify the public social metadata. Do not delete the old file.
Before the first agent write, Forma creates one last-known-good checkpoint. Settings → Access then shows Put it back and This looks good.
Use Put it back if the editing session went wrong. Use This looks good only after you have looked at the public site and decided the current version is the new safe point.
Grok, ChatGPT, and the two connection paths
For a remote MCP connector, copy the URL from Settings → Access → AI chatbots. The tool should discover OAuth automatically, send you to Forma to sign in, and show the approval screen.
For a ChatGPT Custom GPT Action, use Settings → Access → API keys instead:
- Create a Site editor key.
- Import the OpenAPI schema URL shown in the card.
- Choose API key authentication with a Bearer header.
- Store the key in the authentication field — never in a chat message.
Both paths reach the same curated Site editor surface. Neither gives the model a shell or the keys to the server.
A simple operating rule
Use this rhythm:
- Read
- Propose
- Approve
- Write
- Verify publicly
- Accept the checkpoint
Agents move quickly. The workflow should make them pause in the right places.