nexya AI ^Pro

Newsletters written on the WordPress site, with your articles inside — sent in the background, at the pace your server can handle.

Who changed what on the WordPress site, and when. Down to the ACF fields, with the before and after values — and, with Pro, the rollback button

Audience figures measured by the site itself — without Google, without Matomo, without any stored IP address.

Cookie consent, and the blocking that goes with it. Nothing runs before the visitor agrees — no scripts, no embedded videos, no remote fonts

Fields that belong to you, stored in their own tables — and read in a single query per page.

The WordPress administration as the client sees it: menus reduced to the essentials, the admin bar tidied up — and, with Pro, dashboard colors all the way to the login page

The dashboard that brings together all nexya extensions. One module you turn on, one module you turn off — and nothing runs on the WordPress site while it's off

WordPress site emails actually get sent — and we know which ones didn't, with the exact reason provided by the SMTP server

Operations performed on the WordPress site, but not within it: closing it during maintenance, streamlining its database, making a backup

Background thumbnail regeneration, in batches, that continues even when you close the tab — and notifies you when it's finished. With Pro, folders to organize your media library.

What each page costs the site, and the settings that lighten it: a query monitor on every page, options loaded on each visit, the Heartbeat, revisions

Popups built section by section, opening at the right time — and which, with Pro, can close the shop and forms while they are active.

404 errors identified during visits, along with the number of hits to know which ones matter, and the 301 redirection that fixes them. With Pro, the target is suggested before you even look for it.

WordPress rights organized under the content type they belong to, finally readable. And the menu reduced to what the person in front of it actually needs to do there.

Setting up HTTP security headers without breaking the site, monitoring vulnerabilities in active WordPress extensions, and tracking file changes

What the WordPress site tells search engines about itself — and what it displays when you paste its address somewhere. Written once, applied everywhere, verifiable before publishing

Duplicate, reorder, add — three actions performed on WordPress content lists so you never have to do them by hand again

The site in several languages, WooCommerce shop included: every content with its versions, one address per language, and the site’s texts translated in one place.