On WordPress, no developer needed: Reflexa is a plugin you upload, activate and give one token, and it takes over from there. A custom-coded site is the one case that does need a developer, since there the same job is one file added to the middleware, CDN worker or page template instead of a plugin screen.
Three steps, start to finish. Download the plugin from the dashboard's Agent page, then upload it under Plugins → Add New → Upload Plugin and activate it. Paste the site's token into the one field on the plugin's settings page; the token belongs to that single site and grants nothing beyond it. That's it, there is no FTP and no theme file to open.
Once activated, the agent checks in on its own every 15 minutes, and immediately whenever an administrator opens the Reflexa page inside WordPress. Each check-in picks up whatever you approved since the last one, applies it, and reports back, so nothing waits on you to trigger it manually.
The same work the agent does anywhere, just applied through WordPress's own options and revisions instead of a repository file. This is the installed half of everything the Reflexa agent does on your site; the free check that finds the issues in the first place runs from outside and needs no install at all.
| What it serves | What that means on WordPress |
|---|---|
| AI visit counting | Every GPTBot, ClaudeBot or PerplexityBot fetch is counted page by page, the traffic your analytics never records |
| Crawler access | Appends the AI-crawler groups to robots.txt so the engines you allow can actually reach your pages |
| Structured data | Puts the Organization JSON-LD into every page's head, generated from the plugin, not hand-edited |
| Discovery files | Serves /llms.txt, the sitemap and the domain proof directly from the plugin |
| Page text | Writes a page's title, search description, opening paragraph or FAQ block and publishes it as a revision once you approve it |
Yes, in exactly one way: who does the install. On WordPress the four switches live in the plugin's own options screen and page edits land as ordinary revisions, so there is nothing for a developer to touch. On a custom-coded site, the same job is one file added to the middleware, a CDN worker, or a page template, which takes a developer a few minutes once and then runs the same way from inside the site afterward.
| WordPress | Custom-coded site | |
|---|---|---|
| Who installs it | You, no developer | A developer, once |
| How it's installed | Upload a plugin, paste a token | One file in middleware, a CDN worker or a page template |
| Where switches live | The plugin's settings screen | The same dashboard, applied through the installed file |
| Where page edits land | An ordinary WordPress revision | A file in your repository, handed to you to commit |
Yes, all of it. Turning a switch off puts the site back to how it was, since nothing permanent was rewritten to turn it on. A page-text edit was saved as a normal WordPress revision with the previous value kept, so it restores exactly the way reverting any other WordPress edit does.
Why it matters: because every change is reversible by the platform's own history, there is no separate undo system to trust, just the revisions screen you already know.
Deactivating the plugin stops the switches from being applied going forward; whatever was last set stays as it is, so turn each switch off yourself first if you want the site fully reverted. Your checks and everything the agent has recorded about the site stay in your Reflexa account either way.
None of these require installing anything first:
Bottom line: WordPress needs no developer at all, upload, paste a token, done; a coded site needs one a single time, for one file, and the agent runs itself from there.
No. Download the plugin from the dashboard, upload it under Plugins → Add New → Upload Plugin, activate it, and paste in the site's token. There is no FTP and no theme file to touch.
It counts every AI visit page by page, serves /llms.txt and the sitemap, appends the AI-crawler groups to robots.txt, puts Organization JSON-LD into every page's head, and writes a page's title, search description, opening paragraph or FAQ as a revision you approve.
Every 15 minutes, and immediately whenever an administrator opens the Reflexa page in WordPress. It picks up whatever you approved since the last check-in, applies it, and reports back.
Yes. Deactivating the plugin stops the switches from being applied going forward; page edits were saved as ordinary WordPress revisions, so they restore the same way any other revision does.
Yes. A coded site needs one file added to its middleware, CDN worker or page template, which takes a developer a few minutes once. WordPress needs none of that because the plugin does the same job from inside the dashboard.
The free check reads your site the way AI crawlers do and shows every finding with its evidence, no card and no install needed.