What does a Search Visibility FTE own?
A Search Visibility FTE owns a website's organic visibility end to end: being the answer on Google and Bing, and being cited by ChatGPT, Claude, Gemini, Perplexity, and AI Overviews. It is hired per property, meaning per website, so its memory, targets, and setup belong to that site.
The role is accountable for outcomes rather than output. Its targets are things like share of answers for a topic cluster and citations in a set of AI assistants, not a count of articles published. That distinction shapes every mechanism below.
How does it decide what is worth writing?
Before a word is written, the Search Visibility FTE issues a worth-it verdict for each candidate topic: WRITE, REFRESH, MERGE, or SKIP, with the reason attached. A topic is worth writing when the site has no page that answers it and competitors do, or when an existing page is decaying.
This is the mechanism that separates it from a content tool. A tool writes what it is asked to write; the FTE argues, with evidence, that refreshing an existing page beats a new article this week, or that a topic should be skipped because the site cannot credibly win it. The verdicts arrive in the approvals queue with the reasoning attached.
How does the fact gate work?
Every claim in a draft passes a fact gate before the draft can be proposed for publishing. Each factual statement needs a source; a claim without one is flagged rather than silently included, and a draft carrying unsourced claims is held back.
The approval shows the claim count, the sourced count, and anything flagged, so the manager can see the state of the evidence at a glance. This is also why the role gets cited: models and reviewers reward claims that survive checking, and the gate makes that the default rather than the exception.
What does the manager actually approve?
The manager approves the draft in its final form, rendered as it will publish, with its sources visible. Approving a description of an article is not the same as approving the article, so the preview is the real thing.
On approval, the Search Visibility FTE publishes through the connected channel: the WordPress or Shopify API, or a signed endpoint into the site's own Next.js repository. Nothing goes live on an assumption, and the publish itself is recorded in the audit trail with the approver's name.
- Verdict: why this topic, why now, and what the alternative was
- Draft: rendered as it will publish, with every source attached
- Fact gate: claims counted, sourced, and flagged
- Publish target: which connected channel it will go to
How does it measure whether it worked?
The Search Visibility FTE measures two things after publishing: rankings in Google via Search Console, and citations in a tracked set of AI assistants. A page that ranks but is never cited by assistants is only half a result, and the role reports both honestly.
Measurement runs on a schedule rather than on request, which is what lets it notice decay. When a page starts losing position or citations, the FTE queues a refresh proposal before the traffic drop shows up in anyone's dashboard.
What does it need from you to start?
To start, the Search Visibility FTE needs three things: the website and where it publishes, read-only access to Google Search Console, and the brand rules including the topics it must never publish on. It pre-fills what the platform already knows from onboarding and asks only for what is genuinely new.
It starts at Level 0 autonomy, proposing everything. Refreshes of pages you have approved many times are the usual first promotion, because the pattern is repetitive and the risk is low; new topics and anything touching a sensitive subject keep their gate.
What does a Search Visibility FTE cost, and what does it need from you?
A Search Visibility FTE consumes tokens from the organization's wallet for the work it does: measuring the prompt set, drafting pages, running the fact gate, and writing its morning brief. Reading its workspace and approving pages costs nothing. Its per-FTE budget in Setup bounds the spend, the morning brief shows spend against that budget every day, and an empty wallet pauses it rather than running on credit. Usage is reported per role, so the tokens behind each published page are visible.
What it needs from you is scoped access and a decision cadence. Access means a connection to the site's CMS or repository with the narrowest permissions the tool allows, and to the search console where you have one, each granted per property and revocable from the workspace. The cadence means about five minutes a day on the brief and approvals, half an hour a week on send-back reasons in the first month, and thirty minutes a month on the review. It also needs an honest Brand Brain: the product facts, the voice, and the claims the brand never makes, confirmed by you before the first draft.