OperStack AI Visibility

When somebody asks ChatGPT or Perplexity a question your business answers, the assistant fetches a handful of pages and quotes them. If it cannot reach your site, cannot tell what your business is, or finds nothing on the page worth quoting, it names somebody else.

Three things happen here that do not happen in a file generator.

1. It answers the question nobody can answer

How many people did ChatGPT actually send you last month? Almost no site owner knows. In Google Analytics those visits hide under “direct” or sit as a referral from chatgpt.com that nobody opens. This plugin counts them on your own site and shows one small table: ChatGPT 12, Perplexity 3, Claude 1, by day and over seven, thirty and ninety days.

It is counted in the visitor’s browser rather than while the page is built, and that is the whole point: half of WordPress sites sit behind a page cache or a CDN, where the HTML is served without PHP running at all. Anything counted during the render would miss most of the traffic and report a number far too low.

Nothing about the visitor is stored, only which assistant and how many. The address is hashed for an hour so one person is not counted twice, and is never written to a row. If the answer is zero, you get a zero, which is also an answer.

2. It checks the page while you write it

Open any post or page and the AI Visibility box shows a traffic light and the checks behind it, re-read as you type. These are the things that decide whether a page is the one quoted, and none of them are about files:

• Does the first paragraph answer, or introduce? A page that opens with “In this article we will look at” is told so, and told what to put there instead.
• Are the subheadings the questions people type? “How much does it cost” is matched to a question. “Pricing” is not.
• Is there a list or a table? That is the shape an assistant reuses when it builds an answer.
• Is there a figure, a price or a date? Most questions that reach an assistant are how much, how long and how many. A page with no numbers on it answers none of them.
• Do the links say where they go? The words inside a link are read as a description of what is on the other end. “Read more” describes nothing.
• Is the title shown whole, is there enough on the page, is there a summary of its own, is it recent, and can an assistant read it at all (a password-protected page never will).

It runs on the text in the editor, before you save, and it makes no outbound request of any kind: your text goes to your own site’s PHP and the verdicts come back.

3. It fixes what it can, and says what it will not

Every finding on the site screen that the plugin can repair itself carries the button that repairs it. One click allows the answer fetchers, publishes the map, publishes the agent card, puts your business details into the page code, or clears the “discourage search engines” box that was silently overriding everything else.

Where it cannot, it says so plainly instead of pretending. If a robots.txt file sits in your web root, WordPress cannot override it: the screen says blocked rather than allowed, prints the exact lines to paste, and leaves the file alone, because editing a file in your web root is not this plugin’s business.

What it publishes

• robots.txt rules for OAI-SearchBot, ChatGPT-User, PerplexityBot, Perplexity-User, Claude-SearchBot, Claude-User, DuckAssistBot and Applebot. The training crawlers are left exactly as they are, because whether to feed them is your decision, not ours.
• A map at /llms.txt, a plain list of your pages with one line each, written for assistants rather than for people, and rebuilt as you publish.
• An agent card at /.well-known/agent.json, so an automated caller can find out what this site is and where its map lives.
• Business schema with your real type: a dentist marked as a dentist, a roofer as a roofing contractor, with your phone, address and hours.
• A meta description where your theme leaves one out, stepping aside quietly if Yoast, Rank Math, AIOSEO or SEOPress is already writing one.

Your assistant can do the setup

Everything the plugin knows is readable and writable over the WordPress REST API. Create an application password in your profile, give it to Claude or another assistant, and ask it to set the site up. It will read what is missing, ask you for the facts it cannot know (your phone, your address, your hours), write them in, and tell you what it could not do.

The plugin never invents a fact about your business. If it does not know your phone number, it says so instead of guessing.

What it does not do

It does not write your pages, promise rankings, or send anything anywhere. It has no account, no key and no telemetry, and it makes no request to any server but your own.

It also cannot tell you whether an assistant names you or a competitor when somebody asks, because answering that means asking them, and this plugin asks nobody anything. A free check that reads your site from the outside and answers that is at oper-stack.com/ai-visibility, and it needs no account either.