The execution layer for your
client WordPress sites

One team per client site

RankHive organizes everything by team. A team holds its members, one Search Console connection, its site, a queue of drafted changes, a Change Log and a subscription. For an agency, the setup that fits is one team per client site: your staff are members of every client team, and a client you invite sees only their own.

You switch clients from the team switcher at the top of the app, which shows the team and site you are working in. Everything after the switch (the queue, the Keywords page, the Content Calendar, the Change Log) belongs to that client. There is no view across all clients at once.

The Search Console connection belongs to the team, not to your login. Each client team connects to Google separately, so you can use one agency Google account for every client or a different one per client, depending on how each client granted access.

Keep one person, usually an agency lead, as the owner of every client team. Owners handle billing, members and the WordPress connection; members do the weekly review. The table above shows the split. For the wider rollout across a portfolio, with a 90-day plan and a weekly routine, see our guide to WordPress SEO automation for agencies.

Client approval workflows

Every change RankHive drafts waits in the client team’s queue with the current text, the proposed text and the Search Console evidence behind it: the page, the query, its impressions and its position. Someone has to approve it before anything is written to WordPress. For an agency, the question is who.

Your team approves. A strategist works the queue each week: discards what misses the brand voice, giving a reason; asks for a rewrite with a short instruction where a draft is close; edits small things directly; and approves the rest, one at a time or a whole audit at once. You report what shipped from the Change Log. This is the lightest setup and suits clients who pay you to decide.

The client approves. Invite the client contact to their team as a member. They see the same queue and can approve, edit and discard. Be clear about what that gives them: with no read-only or approve-only role, a client member can also revert changes, schedule articles and invite other people to the team. They cannot manage billing, members or the WordPress connection. If a client should only look, show them on a call or send a summary instead of a login.

A split. Your team approves the technical changes (titles, descriptions, internal links, alt text, redirects) and the client signs off new articles, because articles make claims about their business. Drafts appear in the Content Calendar with Review draft and Approve and schedule buttons, so the client can work there while your team handles the audit queue. When articles are ready for approval, RankHive emails every member of the team, so the client hears about them without you forwarding anything.

Whichever model you pick, agree the rules with the client in writing: what your team approves without asking, what needs their sign-off, and how quickly they reply. A queue that waits a month for a client answer ships nothing.

What you can report to a client

RankHive’s reporting is the app itself. The Overview shows the client’s clicks, impressions, click-through rate and average position for the last seven days against the seven before, from their Search Console property, plus what needs a decision, what is scheduled and what was applied recently. Search Console data runs about two days behind.

The Change Log is the record of work done. It lists every change with its date, page, old value and new value, and you can filter it by status (applied, failed or reverted), by change type and by page. For a monthly update, filter to applied changes and summarize them: which pages got new titles, which posts gained internal links, which articles published.

What it does not have: no PDF or CSV export, no scheduled report emails and no report builder, and the Change Log does not show which team member approved a change. Pair it with your reporting tool and put the Change Log summary next to the traffic charts. Our guide to white-label SEO reporting covers building that client report; the Change Log supplies the section on what you did.

Tie changes to results with care. A title approved on the 3rd and a rise in clicks by the 20th is a correlation, not proof. In Search Console you can filter the Performance report to one page and compare two date ranges, which is the honest way to show a before and after.

White-label: what your client will see

RankHive is not white-label. There is no client portal under your domain, no custom branding, and nothing you can resell as your own product.

A client meets RankHive in three places. If you invite them, the app is RankHive-branded, at RankHive’s address. The emails it sends, such as the one saying articles are ready for approval, are RankHive-branded and go to every member of the team. And the plugin in their WordPress admin is called RankHive AI SEO Agent.

So tell clients you use it, the way you would name any tool in your stack. If you need a branded client portal, use a reporting tool built for that; our white-label SEO reporting guide compares the options. RankHive then sits behind it as the place the work gets done.

Pricing per client site

Each client team needs its own subscription, and each subscription covers one WordPress site: $49.99 a month or $499.99 a year.

The arithmetic is linear. Five client sites cost $249.95 a month, or $2,499.95 a year on yearly billing. Ten cost $499.90 a month, or $4,999.90 a year. There is no agency discount, no minimum and no seat charge: add as many of your staff to a team as you need.

Each subscription includes the weekly audit and up to 16 drafted articles a month for that site. The article count resets every month, on yearly plans too, and it doesn’t pool across clients.

Billing belongs to the team. Most agencies pay for client sites and pass the cost on in the retainer. If a client wants to pay directly, they need to be an owner of their team, because only owners can manage billing.

Cancel any time; access continues to the end of the paid period, and there are no refunds. There is no free plan or trial. Before you pay, onboarding shows the first places RankHive found to look in the client’s Search Console data, which is a fair check that the site has enough data to work with.

Handing a site back to the client

Engagements end. When one does, the client keeps everything RankHive changed. Titles, descriptions, canonicals, content edits and alt text are saved in WordPress. Structured data, redirects and robots.txt rules are served by the RankHive plugin, so the client should keep it installed if they want those to keep working; uninstalling it deletes its redirects.

If the client wants to keep using RankHive, hand over the team rather than starting again. The primary owner can transfer ownership to an existing member, so invite the client contact first, then transfer. The subscription belongs to the team, not to a person, so it carries on, and the queue and Change Log stay with the team. The new owner manages billing and decides which of your staff stay.

One detail to settle first: the team’s Search Console connection uses the Google account it was set up with. If that is your agency account and the client then removes it from their property, RankHive stops getting their data. Leave that access in place, or contact us before you remove it.

If the client is not continuing, an owner cancels the subscription from the team’s Billing page. The changes stay on the site either way.

What this frees your team to do

The work that justifies a retainer is judgment: which markets to enter, how to restructure a catalog, why a competitor is winning, what to do after a traffic drop. None of that is automatable and none of it should be.

The work that fills the week is execution volume. Moving that into a review queue lets a senior strategist cover more accounts without the quality falling, because they spend their hours on decisions rather than typing.

The honest framing is not headcount reduction. It is that the fixes everyone agreed on in March actually ship in March.

What RankHive does not do for agencies

There is no multi-site dashboard. Each client site is a separate team and subscription. You switch between teams from one login, but there is no single view across your portfolio. Twenty sites means twenty teams to switch between.

There is no white-label, no report export and no read-only role. Clients who get a login can act, not just look.

There is no consolidated billing and no agency tier. Every site is $49.99 a month, billed per team.

There is no backlink or competitor research. Keep your research platform; RankHive works after research, on execution.

These are absences, not roadmap hints. We would rather you know now than find out after onboarding three clients.

When to look elsewhere

If you need a single dashboard across every client, view-only client logins, or white-label reporting, buy something built for that. This is not it, and no configuration makes it so.

If your clients are mostly not on WordPress, the coverage will not justify the workflow change.

If what you actually sell is strategy and the execution is already handled by an in-house team with capacity, you do not have the problem this solves.