For a title, a redirect or an FAQ block, the agent is the right hand; for anything structural, a developer still is. The real cost of a small fix is rarely the minute of work itself, it is the brief, the queue and the deploy around it, and that is exactly the part an agent at $49 or $149 a month removes.
Most sites carry a backlog of jobs too small to justify a developer's time and too numerous to ignore: a title that undersells the page, a redirect nobody set up, an FAQ block that was never written. Deciding whether that backlog needs an AI agent on the site or a person with an editor open comes down to one question: is the job a page-level field the agent can write and show you first, or does it touch the application itself?
The process, almost every time. A developer, freelance or on retainer, bills for the time around the fix as much as the fix itself: the brief, finding the file, the change, the deploy, and someone checking it landed. A one-line title edit and a half-day structural fix can sit in the same queue and take the same number of days to come back.
Why it matters: a backlog of ten-minute jobs never clears this way. Each one is too small to open a ticket for, so it piles up, and the pages that would benefit keep losing wins a search or an AI engine was ready to give them for free.
On anything the agent already knows how to write and show you
before it happens. A page's title, its search description, an
answer-first opening paragraph, an FAQ block with its schema, a 301
redirect it names and checks before applying, and, since October 2026,
a general change hand for a stylesheet, a head snippet, a replaced
passage, a new page or a response header. Four more things it switches
on itself with one click each: crawler access in robots.txt,
Organization data, the sitemap, and /llms.txt. Every one
of these is shown to you exactly as it will appear, and applies the
moment you approve it, whether that lands as a WordPress revision or a
commit on a connected repository.
Anything structural, anything in the application itself, and anything that needs a business judgement rather than a page edit. The agent is coded to never touch theme or plugin files, never create or change users, passwords or DNS, never flip noindex on its own, never edit checkout, cart, account or locked pages, and never delete content or change a price. Those limits are enforced in code, so a developer is still the only hand for a new feature, a database change, or a decision about what something should cost.
$49 a month on Starter, or $149 a month on Growth. Starter gives around 200 answers and 100 page checks a month on one or two sites; Growth gives about five times that usage across every site on the account, each with its own agent, memory and token. Usage is metered by the work done, not by how many small jobs you ask for, so a backlog of titles and redirects draws on the same allowance one larger request would.
| Job | Who should do it | Why |
|---|---|---|
| Rewrite a page title or search description | The agent | It writes the exact text and publishes it once you approve |
| Fix a redirect for an old URL | The agent | Names the redirect, checks the destination answers, undo is one click |
| Add an FAQ block with its schema | The agent | Writes the questions and the matching markup together, in its change hand |
Allow AI crawlers, turn on the sitemap or /llms.txt | The agent | Four reversible switches, one click each |
| Replace a paragraph, add a stylesheet or a head snippet | The agent | Covered by the general change hand added October 2026 |
| Publish a brand-new page | The agent drafts, you decide | It writes the page but never publishes a new one without your approval |
| Change a price or edit a locked page | A person | The agent is coded to never touch prices or pages you mark locked |
| Install, update or remove a plugin or theme file | A developer | Theme and plugin files are outside what the agent will ever touch |
| Create or change a user, a password, DNS or hosting | A developer | Enforced in code as something the agent never does |
| Build new functionality, such as checkout logic | A developer | This is application code, not a page field or a switch |
None of this requires buying anything first, and each step takes a few minutes:
For a page's title, description, FAQ, a redirect or a passage of text, the agent is usually faster and cheaper, because that is exactly what it is built to write and apply on your approval. For anything structural, such as checkout logic, a plugin or a database, a developer is still the right hand.
$49 a month on Starter, with around 200 answers and 100 page checks a month, or $149 a month on Growth, with around five times the usage and every site on the account covered. Neither plan counts how many small jobs you ask for within that usage.
It never touches theme or plugin files, never creates or changes users, passwords or DNS, never flips noindex on its own, never edits checkout, cart, account or locked pages, and never deletes content or changes prices. Those stay a developer's or a person's job, enforced in code.
No. It replaces the specific backlog of small, page-level jobs that are individually too minor to brief a developer for and collectively never get done. Anything that needs the application's own code, or a business judgement about price or content, is still a person's call.
The agent shows you the exact change first, whether that is a switch, a piece of writing or a commit, and applies it the moment you click approve. The only lag left is however long you take to read it, not a queue, a brief or a deploy.
The free check reads your site the way ChatGPT, Claude and Perplexity read it, and returns a plan marked switch, words for approval, or a person's job. 3 minutes, evidence included.
The product: Reflexa Agent · how it works · på svenska