Which property, publishing route, and console does the role cover?
Fill in the website the role serves as its property, the publishing route, a CMS through its API, a pull request to the repository, or the endpoint package, and the search console connection. State that the route's connection can draft and propose but not publish without approval, and for a repository can open pull requests but not merge.
Verify: the connection list in Setup shows the route scoped to this property with the stated permissions.
- Property: ______
- Route: CMS ______ / pull request to ______ / endpoint on ______
- Search console: ______
Which sources does the fact gate check against?
List the documents and data the fact gate treats as sources: the product documentation, the policy pages, the pricing page, the brand guidelines, named public sources, and the Brand Brain's confirmed facts. State that any claim not traceable to one of them blocks the draft, that statistics, studies, customers, and quotes without a source never pass, and who may add a source.
Verify: a draft with a deliberately unsourced sentence is blocked in a test and returned with the sentence identified.
- Documentation: ______
- Policy and pricing pages: ______
- Brand guidelines: ______
- Named public sources: ______
- Source additions approved by: ______
What does the Search Visibility FTE own: measurement, verdicts, drafts, proposals?
The Search Visibility FTE owns running the nine-check audit and reporting fails; sampling the prompt set on the schedule and recording citations with dates; proposing topics with a worth-it verdict from the inputs in section 4; drafting approved topics to the content standard with every claim through the fact gate; proposing improvements to existing pages; and reporting in the performance view with unmeasured items labelled. It proposes; a person approves.
Verify: the first topic proposal carries a verdict with reasons and evidence, and the first draft carries its fact-gate result.
What is in the prompt set, and what feeds a worth-it verdict?
Write the prompt set: the primary questions buyers ask and their fan-out sub-queries, five to nine each, and the engines to sample, with the schedule, typically weekly, and the rule that the set changes only at a quarterly review. State the four verdict inputs: demand from search and sampled data, position from existing pages, competition from who is cited now, fit from the Brand Brain's statement of what the organization should be visible for.
Verify: the first sample is recorded and dated before any draft is approved.
- Primary questions: ______
- Engines sampled: ______
- Schedule: weekly, set revised quarterly
- Verdict inputs: demand, position, competition, fit
Which claims always need a named approver, and what does it never do?
List the claim categories that always route to a named approver in addition to the fact gate: outcome and effectiveness claims, comparative claims, regulated claims in your sector, anything about a named competitor, and any page in a category you designate clinical, legal, or financial. State what the role never does: never publishes without approval unless a narrow class has been explicitly promoted, never adds a source to pass a claim, never changes the prompt set mid-quarter, never estimates an unmeasured metric.
Verify: the routing per category appears in Setup and publishing shows as gated.
What are the targets, and what counterweights each one?
Set three targets. Pages published that passed the fact gate, counterweighted by the send-back rate on drafts. Citation presence on the sampled prompt set per engine, counterweighted by the rule that no page carries an unsourced claim. Console impressions and clicks for target queries where connected, counterweighted by the share of verdicts overturned by the manager, so the FTE is not rewarded for saying yes to everything. Each names its evidence source, and unmeasured engines are marked unmeasured.
Verify: the Targets tab shows each with evidence and the performance view marks what it cannot measure.
How do you use this template?
Copy the sections into the first-run wizard, list the approved sources before anything else, fill every blank, and test the remit against the site's existing pages: the FTE's audit should flag the pages that fail the structure and verifiability checks, and its first verdicts should say no to topics the site already answers. Read the send-back reasons weekly; by the second month they should be about tone.
Publishing stays gated unless a recorded governance decision promotes a narrow class such as date corrections; most organizations never do, and the remit works fine that way.