Product
Solutions
Compare
Resources
Get early access Talk to us
On-page SEO management

On-page SEO for every WordPress site you manage

One editor for the search result, share cards, heading outline, canonical, indexing rules and structured data of any page on any site you have connected. Saved through the SEO plugin that site already runs.

Available now in early access. Included on every plan.

WPCentrify Content and SEO dashboard showing total pages, pages with SEO issues, average SEO score and a Google search preview for a managed WordPress site
The problem

Thirty sites, thirty different SEO setups

A portfolio is never uniform. One client is on Yoast because a previous agency put it there, another on Rank Math, a third on nothing at all. Each has its own builder, its own login and its own idea of where the description field lives.

That variety is why portfolio-wide SEO work tends not to happen. Any procedure you write down is wrong for a third of the sites, so the work stays per-site, and per-site work across forty sites quietly becomes no work at all.

This page is the part of WPCentrify that removes the variety without removing the plugins. One editor, the same on every site, saving through whatever each one already has.

What this is for

  • Changing a title or description without logging into the client site
  • Finding every page across the portfolio that search engines cannot see
  • Checking a share card before a client posts the link
  • Fixing a heading structure without waiting for a page builder to load
  • Giving a junior visibility of SEO without giving them the ability to change it
How it works

Handed to the plugin that owns the page

Nothing here layers a second set of tags over what a site already outputs. Each change is passed to the SEO plugin that owns that page, which is what keeps a portfolio's output clean and keeps your work portable. The reasoning, and what it saves you, is set out in managing WordPress SEO across every site.

01

A single source of tags

Every page draws its output from one place, so conflicting titles, descriptions and canonicals are not something you have to go looking for afterwards.

02

Portable by construction

What you write is stored by the client's own plugin. Cancel and the site is unchanged: no export step, nothing to unpick, nothing for the client to lose.

03

Fields matched to the site

The editor asks each site what it is able to store and draws that. Every control in front of you is one the site will honour, and each absence carries its reason.

04

One page or a batch

Work a single page in detail, or select a set and switch indexing or publish status across all of them together. Totals for the site sit above the list.

Capabilities

What you get

The search result

Set the title and description Google shows, with a character count and a pixel-width readout beside a preview of the result itself. Name a focus keyword and the editor reports where it appears and where it does not.

Share cards

Give Open Graph and X their own values or let them inherit. Choose the image from the site's media library or upload one, and check both cards render before a client posts the link.

Heading outline

The page's real outline in document order. Retitle any heading, promote or demote it where the builder allows, and see at a glance which ones the theme contributed rather than the page.

Indexing rules

Index or noindex and follow or nofollow per page, the canonical address, and the narrower directives, nosnippet, noimageindex, notranslate and the max-snippet family, on plugins that expose them.

Structured data

Choose from the types your plugin offers, or paste your own JSON-LD and have it validated before it goes anywhere. Templates cover the common cases, and a warning appears if the live page already emits that type from elsewhere.

Scored, with the reason

A figure out of 100 for each page and a named reason for every point lost, from a live page that search engines have been told to skip through to a heading level used twice.

Narrow it to the work

Restrict the list to a status, a content type, anything scoring badly or anything carrying a noindex. Order by score, word count or last edit, then start at the top.

The page record

Rename it and watch the resulting address update as you change the slug. Move it between draft, pending, private and published, reassign the author, and set the excerpt, taxonomy terms and featured image.

Configured against rendered

Read back what the public page is genuinely sending: title, description, indexing directives, canonical, every social tag and every data block. Set beside your configuration, it catches a cache still serving last week.

The same editor everywhere

Whatever plugin and builder a given client happens to run, the screen looks and behaves the same. A portfolio stops being a collection of separate procedures.

Two levels of access

Content is its own permission. Grant View and somebody reads the scores and previews; grant Manage and they can act on them. Without either, the verdicts stay hidden.

Nothing to install

No extra plugin, no separate licence, no per-site setup. If the site is connected, the Content tab is already there.

Coverage

Built around whatever each client already runs

Six plugins can be edited directly: Yoast SEO, Rank Math, All in One SEO 4, SEOPress, The SEO Framework and Slim SEO. Each offers a different set of per-page options, and the screen mirrors that set rather than a lowest common denominator, so a field you can see is a field that will save.

Anything else, Squirrly and SmartCrawl among them, is identified by name and then left alone. WPCentrify will not write beside a plugin it cannot read, so there is never a contest for the same tags. The page record and the heading outline still work on those sites.

Where a site runs nothing at all, WPCentrify covers the fields itself until a plugin turns up, at which point a single action hands everything over.

Heading edits by builder

  • Full editing: Gutenberg and classic, Elementor, Beaver Builder, Bricks
  • Wording only: Divi 4, WPBakery
  • Listed, not writable: Divi 5, Oxygen
What to expect

What a save reports back

A save is settled field by field. The result names what was applied and what was not, with the reason attached, so a partial write stays visible instead of being rounded up to success.

Two people cannot overwrite each other either. If the page moved in WordPress between opening and saving, the write stops and offers a reload. Anything that does go through is logged against your account, the site, the page and the fields involved.

What you get from all of this is control over what search engines are told, and proof of what changed. It is not a rank tracker, a keyword research tool or a backlink index, and it claims no position in anybody's results.

Scope

  • Six plugins editable, the rest identified and untouched
  • Divi 5 and Oxygen headings listed but not writable
  • Redirects visible, read-only, on every plugin that has them
  • Posts and pages, not custom post types or media library items
  • A management layer, with no keyword research or rank tracking
Answers

Questions about on-page SEO management

No, and that is the point. The editor adapts to whichever of the six supported plugins a site runs, and identifies the rest without touching them. You are not standardising forty sites on one plugin so that a tool works.

Because the plugins differ. Each exposes a different set of per-page options, and the editor draws only what the active one can store. Where something is absent, a line names the plugin responsible, so the gap is explained rather than mysterious.

Not by accident. If the page moved in WordPress between the moment you opened it and the moment you saved, the write stops and offers a reload rather than replacing whatever the other person did.

Nothing is written until you save. The result then lists every field it touched, and the log keeps a record of who changed what, on which site and when.

Yes. Content is a permission in its own right, with View and Manage levels. View shows the scores, issues and previews. Manage adds the ability to act on them. Without the permission, SEO verdicts do not appear at all.

The Live section fetches the public page and reports what it is really serving, set beside what you configured. A caching layer holding an old copy shows up as a difference rather than as a mystery.

Custom post types and the media library sit outside it. Redirects are visible but read-only. Headings on Divi 5 and Oxygen pages are listed rather than editable. And there is no keyword research or rank tracking here.

Yes, on every plan at no extra cost, with nothing separate to install or licence.

Available now

Take SEO off the per-site pile

One editor for the search result, share cards, heading outline and structured data of every page you are responsible for, saved through the plugin each site already has.

Free during early access. No credit card required.