One Plugin, Every Client Site: The Agency Setup for the Ayzeo WordPress Plugin
The Ayzeo WordPress plugin is built around two things agencies already have: one project per client and one subscription for the agency. Each client site gets its own API token, your plan unlocks the features on every site, and no client ever needs an Ayzeo login. This is the setup we recommend, step by step, with the ten-minute weekly routine that follows.
Table of Contents Expand
1. Why This Works for Agencies
Three properties of the plugin make it fit the agency model without any special mode:
- A token belongs to a project, and a project is a client. Every API token is created inside one Ayzeo project and can only scan that project's domain. One client, one project, one token per site.
- The plan follows the project owner. When a client site calls Ayzeo, the platform checks the subscription of the organisation that owns the project, which is yours. A paid plan on your side unlocks deep scans, AI visibility queries and content pages on every client site, and a Pro or Enterprise plan adds the GEO dashboard. The client has no account and no bill.
- Quotas are counted per project. Daily budgets for scans and AI queries belong to the project, so ten clients are ten separate budgets, not one shared pool.
Everything that needs no account at all, the Site Audit, the one-click fixes, IndexNow, the AI crawler policy and llms.txt, works the moment the plugin is active. You can roll it out to every client today and connect tokens as you go.
2. Step 1: One Project per Client
Create a project in your Ayzeo organisation for each client, named after the client, with the client's live domain, region and language. During setup Ayzeo generates the tracked prompts for the client's industry from the site; confirm them and the project starts measuring visibility across the AI engines.
Two details matter for the plugin. The project domain is the only domain the site's token may scan, so use the live domain, not a staging host. And the project is where the client's history lives: prompts, citation results and content pages stay in your organisation, which keeps reporting consistent when your team changes.
3. Step 2: One Token per Site
Open the project, go to Project settings, API tokens, and create a token. Only a project owner or admin can do this. Name it after the site, for example the domain, so the token list reads like your client list. Copy the token once; it is shown in full only at creation.
A project can hold several tokens, and each one can be revoked on its own. Use that: one token per site, never one token shared across two sites, so revoking a client never touches another.
4. Step 3: Install and Connect
- On the client's WordPress, go to Plugins, Add New, search for Ayzeo and install the plugin from the WordPress directory. It needs WordPress 6.5 and PHP 7.4 or newer.
- Open Ayzeo, Settings, paste the token, press Test token and then Save and connect.
- The Settings screen now shows the project name, the domain, the plan the site inherits and how much of its daily limits it has used today.
Five minutes per site, including the login. If the client runs Yoast, Rank Math, All in One SEO or SEOPress, leave them in place: the plugin detects them and steps back where they already do the job.
5. Step 4: Switch On the Always-On Layer
These four settings keep working while nobody is looking, and they are the same on every client site:
- Site Audit. Open Ayzeo, Site Audit and run the first audit, then switch on "Run the audit once a week" under Settings, Preferences. The plugin picks the client's most important pages and checks them against the Ayzeo rulebook on the client's own server.
- IndexNow. Under Indexing and Crawlers, switch on automatic submission. Every new, updated and removed page goes to Bing and the other IndexNow engines within minutes, and ChatGPT search reads Bing. If another plugin already submits, Ayzeo tells you and stays off.
- AI crawlers. Check the policy tab once. Every AI crawler that nothing else on the site already addresses gets an explicit rule in robots.txt, grouped into search, assistants and training, and you can switch individual crawlers off for clients who want that. Sites with a physical robots.txt file get the block to paste instead.
- llms.txt. Write a short summary of the client's business and key pages in the editor. It is served at the client's domain under /llms.txt.
6. Step 5: Work the Findings
The audit lists pages worst first with their top issues. Open a page report and you get every check with its evidence and a recommendation, and for structured data, meta descriptions, Open Graph tags and image alt text, a fix you can preview and apply from the same screen. Fixes are reversible, and suggested titles and descriptions write into the SEO plugin's own fields, so nothing ends up duplicated.
For pages that matter most, run a deep scan with AI checks. It adds the checks that need the platform and comes back with suggested meta tags, JSON-LD and llms.txt content you apply in one click. Under AI Content, ask the questions the client's customers ask and see how the AI answers and which sources it considered, then generate a content page for the gap. It lands in the client's WordPress as a draft by default, which keeps the publishing decision with the client.
7. Step 6: Give the Client the Dashboard
On a Pro or Enterprise plan, the plugin's Overview page shows the client their own GEO numbers inside WordPress: visibility share, mention rate, citation rate and average mention position with the change against the previous seven days, sentiment, a trend chart over 7, 30 or 90 days, the competitors ranked next to their brand and a snapshot of the top tracked prompts. A widget on the WordPress dashboard shows the headline numbers at every login. No Ayzeo account is needed for any of it.
The key-figure tiles link into the full analysis on ayzeo.com. If the client should be able to follow those links, invite them to the project as a viewer. Viewers read the analysis and change nothing.
The weekly routine per client is about ten minutes: check the Overview for movement, open the audit for new findings, glance at the IndexNow log to confirm the week's pages went out.
8. What Each Client Gets, and What Stays Yours
| The client site gets | Stays with the agency |
|---|---|
| Site Audit, fixes, IndexNow, crawler policy, llms.txt on their own server | The Ayzeo subscription and the bill |
| Deep scans, AI queries and content drafts within the project's own daily budget | The project, its prompts, history and reports |
| The GEO dashboard inside WordPress | Token creation and revocation |
| A token scoped to their project, which can only scan their domain | Member roles: who is owner, admin, editor or viewer |
If your team uses an AI assistant, connect the Ayzeo MCP server once with your account: one connection covers every client project you are a member of, so "which client has the weakest ChatGPT presence this month" is a single question.
9. Offboarding a Client
Revoke the site's token in Project settings, API tokens. The connected features on the client site stop answering and the Settings screen reports the last call as failed with an invalid or revoked token; the local tools keep running for them. The project and its history stay in your organisation until you decide to delete it.
10. Frequently Asked Questions
- Q: Does my client need an Ayzeo account?
- A: No. The plugin authenticates with the project token, and the platform applies the plan of the organisation that owns the project, which is yours. The client only needs an account if you invite them to the project so they can follow the links into the full analysis on ayzeo.com.
- Q: Which plan do I need as an agency?
- A: Any paid plan on your organisation unlocks deep scans, AI visibility queries and content pages on every connected client site, because the plan applies to every project you own. The GEO dashboard inside WordPress needs Pro or Enterprise. The agency plans price per client project; see the agencies page for the current terms.
- Q: Can I use one token on several client sites?
- A: No. A token belongs to one project and can only scan that project's domain; a scan of any other URL is refused. Create one project per client and one token per site.
- Q: Do ten client sites share one daily quota?
- A: No. Scan and AI query limits are counted per project, so every client has its own daily budget under your plan. The plugin shows how much of the site's daily budget is used on its Settings screen.
- Q: Can the client see their numbers without logging in anywhere?
- A: Yes. On a Pro or Enterprise plan the Overview page and the WordPress dashboard widget show the client's GEO numbers inside their own WordPress admin. Only the links into the full analysis on ayzeo.com need a login.
- Q: What happens when I stop working with a client?
- A: Revoke the site's token. The connected features stop, the local tools on the client's server keep working, and the project with its history stays in your organisation until you delete it.
Set Up Your First Client Today
Create the project, mint the token, install the plugin, switch on the weekly audit and IndexNow. Half an hour for the first client, five minutes for every one after that.
Ayzeo for Agencies
One project per client, one plugin on every site, one plan for the agency. White-label reports, unlimited seats and per-client pricing on the agency plans.
Key Takeaways
- Project = client, token = site: tokens are minted inside a project and can only scan its domain.
- Your plan, every site: the platform checks the project owner's subscription, so clients need no account and no bill.
- Budgets per project: scans and AI queries are counted per client, never pooled.
- Always-on layer: weekly audit, IndexNow, crawler policy and llms.txt run on the client's server without you.
- Clean offboarding: revoke one token, keep the project history.