Your AI visibility, inside your WordPress

• You know AI answers on your behalf, and you have no way to start checking it.
• The plugins that do something similar ask you to paste your OpenAI key into the dashboard.
• And you are not going to set up another tool and another password to look at one number a month.

The tool you have to open separately is the one nobody opens.

1. 1

   You install and accept

   The signup is triggered by a person pressing a button, not by activating the plugin. The difference is not about friction: to handle your email and run requests in your name you have to have said yes, and it is recorded when.

2. 2

   We check the domain is yours

   Citenza loads your site once and checks it returns a code only you and it know. Without that nothing is measured, and that is why nobody can register somebody else's domain and spend budget in their name.

3. 3

   And you never touch it again

   The sweep is launched by Citenza's server every fortnight, not by your WordPress. That matters: if it depended on the WordPress cron, a high-traffic site would measure every minute and a site with no visits would never measure.

• How many answers name you out of how many were counted, never a bare percentage.
• How many times you are cited with a link, which with these two engines is usually few, and we say so.
• The date of the next refresh, so you know when to look again.

• Anyone with a WordPress who does not want one more tool to open.
• Agencies running several sites that want measurement left running on each one.
• Anyone wanting to try the product with no card and no commitment.

The plugin is free and needs no paid plan to install. It registers the site on the free plan, which is permanent and does not expire: five questions, two engines and a refresh every fortnight. Paid plans add Claude, Perplexity, Google AI summaries, competitors, alerts and full history, and are bought from the website, not from the plugin.

See the full pricing

Do I have to give my OpenAI key?

No, and if a plugin asks for it, think twice: it would end up in the options table in plain text, in a database that gets backed up unencrypted, restored in test environments and moved with the site when it changes hosting. Here the only thing stored is a token that only works for this site.

Does it slow my site down?

It does not touch the front end. The only function that runs on a public visit is the verification code check, which compares a string and finishes. Everything else lives in the dashboard, and the data is cached for a day so the screen never waits for a call.

What if I uninstall the plugin?

Everything it wrote into your database is deleted, including the token. Your Citenza account still exists and you enter with the signup email. Deleting somebody's account from a plugin any administrator can uninstall would be a destructive function far too easy to trigger by accident.

Why is the number I see so small?

Because it is ten answers and four of the five questions do not mention your brand: we watch whether your site emerges on its own, which is the only thing that means anything. A tool showing you 80 per cent on day one is almost certainly asking about your name, and then it measures whether the model can read, not whether it recommends you.