You already treat a tracking pixel as a credential. A help tab that mints a standing admin password is the same class of object. Inventory it like a pixel, not like a chatbot.
Your help tab issued an admin key.
Most mid-market marketing sites still run on WordPress. The plugin that writes titles, schema, and redirects is not a writing assistant. It sits on the same box that serves pricing, demo, and docs. When that plugin can mint a WordPress Application Password for the administrator who clicked Help, the marketing site just issued a standing credential. That is a production event. It is not a support convenience.
On August 26, Rank Math shipped 1.0.277. The WordPress.org changelog says the release added a Support Agent that answers questions from inside the plugin, and added abilities for AI assistants to configure Rank Math settings. It also lists a round of security hardening (Rank Math on WordPress.org). Search Engine Journal reported that when a site administrator connected to a free Rank Math account opens Help and Support, the plugin can create an Application Password tied to that user, labeled WAP Rank Math Support Agent, and that closing the tab does not revoke it (Search Engine Journal). WordPress core documents Application Passwords as revocable, per-application credentials that are supposed to go through an authorization screen the user can approve or reject (WordPress Developer Resources).
A day later, 1.0.277.1 (August 27) fixed the Help and Support AI Assistant incorrectly showing an HTTPS-required notice on every admin page when Application Passwords had been disabled by another plugin. That patch is about a notice. It is not a substitute for checking whether a password already exists on the profile.
Treat The Help Tab Like A Deploy
This week, open WordPress Admin, Users, Profile, Application Passwords. If you see anything starting with WAP, revoke it unless you explicitly want a vendor agent to act as that administrator. Then ask who on the marketing team can open Rank Math Help and Support while the site is connected to a Rank Math account. If the answer is anyone with an admin login, that is the access list. Shrink it.
Do the same inventory you already do for pixels. Name the owner. Name the system that received the credential. Name whether it expires. Application Passwords do not expire when you close a tab. They sit until someone revokes them.
If you are not on Rank Math, still run the check. Any plugin that offers in-dashboard AI support can follow the same pattern. The operating object is the Application Password list, not the brand of the plugin.
Do Not Confuse A Chat Widget With A Key
A support chat that answers "how do I set a canonical" is copy. A support chat that can change settings, or that holds an administrator Application Password, is a privileged integration. Put it on the same change-control list as a new GTM container, a new Shopify pixel, or a new HubSpot private app. If you would not let an unpaid vendor login mint itself from a help panel, do not leave this one live because the panel was labeled Help.
The Operating Move
This morning: revoke stray WAP passwords, screenshot the empty list for the record, and restrict Help and Support to one named admin. Then add Application Passwords to the same weekly site hygiene as SSL, Search Console users, and tag-manager publish rights.
Your help tab issued an admin key. Pull it.
