Yes, in plain words. The agent writes the exact title and search description, shows them to you exactly as they will appear on the page, and nothing changes until you press apply. Here is the smallest, most common job on a site, done once, start to finish.
This is the smallest job the Reflexa agent does, and the one almost every site has sitting somewhere: a title that is too long, missing, or just not the words a buyer actually types. Reflexa's own Search Console data for October 2026 shows real owners searching for exactly this, in queries such as "how to correct ai about a product feature or pricing change", sitting at position 6. Below is one request, worked through end to end.
You name the page and say what is wrong with the title, in your own words, and the agent writes a replacement. "The title on /pricing is too long and gets cut in Google" or "the FAQ page's title doesn't say what the page is actually about" is enough. The agent reads the page, writes the exact new title and the search description that goes with it, and puts both in front of you before doing anything else.
Why it matters: you are not filling in a form field yourself and hoping it is right. You are reviewing a finished proposal, written for that specific page.
The page itself and what the agent already knows about the site, not a generic rewrite template. It reads the page's existing copy, the site's Organization data, and the result of the structural checks already run on that page, so a title about a pricing plan is written from the plan's actual name and price, not a placeholder. Nothing is invented that is not already true of the page.
The exact title and the exact search description, in the dashboard, exactly as they will appear on the page, not a summary of the change. Nothing is sent to your site until you read it and press apply. If the proposal is wrong, say so and ask again; nothing is live yet.
Rule of thumb: if you cannot read the exact words before they go live, it is not a proposal, it is an announcement after the fact. Reflexa's rule is the opposite.
Depends on where the page lives, but either way it lands as something you can point to and undo, never a silent edit.
| Where the page lives | Where the approved title lands |
|---|---|
| WordPress | A revision, with the previous title kept, so it can be restored exactly |
| A connected repository (GitHub App or GitLab token) | A commit on your default branch, named for what was approved, read before it merges |
| Shopify or Webflow (platform API) | Written through the platform's own API, which is where title and description writes are allowed |
Do this: for the full list of what each kind of site lets the agent touch, see Can an AI agent actually change my website?
Yes, every time, and the undo matches how the change landed. On WordPress the previous revision restores the old title exactly. On a repository, another commit reverses it. Nothing is ever written into your theme or your content directly, so there is no edit that only the agent can see how to reverse.
No. It proposes a new title where something is actually wrong with the current one, not as busywork. The site's own structural checks already know which titles are too long, missing, or duplicated across pages, and that is what tells you which titles are worth the five minutes. A title that already does its job is not rewritten just to produce a before-and-after.
Why it matters commercially: you are not paying for churn. The work is pointed at the pages a check actually flagged, which is also the fastest way to see whether the change did anything, since you are not guessing which of forty edits moved something.
The same checks run across the whole site, worst first, so every page with a real title problem shows up together, not one brief at a time. Instead of writing forty separate requests to a developer or a copywriter, the flagged pages come back as one list, each with its own evidence and its own proposed title. You still read and approve each one, but you are reviewing one list in one sitting, not managing forty tickets.
None of this requires buying anything, and each step takes a few minutes:
Yes. You ask in plain words, the agent writes the exact title and search description, shows them to you exactly as they will appear, and nothing changes until you press apply.
The page itself and what it already knows about the site, not a generic template: the existing copy, the site's Organization data, and the structural checks already run on that page.
On WordPress it lands as a revision with the previous title kept, so it can be restored exactly. On a connected repository it lands as a commit on your default branch, named for what was approved, which you read before it merges.
Yes. A WordPress revision restores the exact previous title, and a commit is undone with another commit. Nothing is written into your theme or your content directly.
The same checks that flag one page's title run across the whole site, worst first, so every page with a real title problem shows up together in one plan. You still approve each line, but you review it as one list instead of writing forty separate briefs.
The free check reads your pages the way ChatGPT, Claude and Perplexity read them, and flags titles worth fixing first. 3 minutes, evidence included.
The product: Reflexa Agent · how it works · på svenska