UNGATED OPERATOR HUB
Run AI search as an operating system, not a content stunt
Use this canonical path to move from a buyer question to observable evidence, a shipped change, and a dated re-test. Each linked guide supplies one working layer; the worksheet turns the first layer into something your team can use today.
START WITH THE JOB
Six operator jobs, in execution order
Open the guide that matches the decision in front of you. The sequence matters more than consuming every resource.
GEO Readiness: 28 Checks and a Prioritized Worklist
28 checks across crawl access, brand identity, applicable structured data, and useful content. Record evidence, distinguish optional settings, and prioritize corrections; this worklist does not predict AI citations.
Open guidellms.txt Guide: When to Use It and How to Maintain It
Decide whether to use llms.txt, then plan links, Markdown and maintenance. Google Search ignores it; verify other systems separately.
Open guideMeasure GEO with citations, recommendations and qualified opportunities
Define citations, unlinked brand mentions, recommendation presence in buying questions and qualified opportunities separately. Specify samples and denominators, and distinguish pipeline value, revenue and supported attribution conclusions.
Open guideA Content Rewrite Process With Clear Decision Points
Prioritize useful content changes, record what changed and review comparable evidence. A three-week planning example with practical reasons to continue, wait or stop.
Open guideSix AI Search Products: Modes, Sources, and Citations
Compare six AI search products by search mode, source access and citations, then plan content work and repeatable measurement.
Open guideChoose a GEO agency with verifiable scope and evidence
12 procurement questions, six evidence requests and five issues to clarify. Compare measurement methods, delivery scope, ownership and contract terms before deciding.
Open guideTHE OPERATING SYSTEM
Observe → decide → ship → prove
Technical readiness and AI visibility are related, but they are not the same measurement. Keep their evidence separate throughout the loop.
- 01
Observe
Record the engine, locale, prompt, date, answer mention, citation card, and cited source as separate fields.
Output: dated baseline, plus what was not checked
- 02
Decide
Rank gaps by buyer value, evidence strength, effort, and ownership. Select a small batch that can actually ship.
Output: prioritized queue with owner and decision reason
- 03
Ship
Change the source of truth: entity facts, crawler access, structured data, answer-first passages, or corroborating sources.
Output: URL and change log—not a recommendation deck
- 04
Prove
Re-run the same observation contract. Record improvements, misses, ambiguity, and attributable downstream actions.
Output: comparable re-test with limitations
WORKING TEMPLATE
Five-question Prompt Coverage worksheet
Define one commercially useful buyer question before opening a monitoring tool. Your answers stay in this browser and are never sent to Tenten.
THREE-WEEK CADENCE
Keep the batch small enough to learn
A fixed cadence creates comparable evidence and prevents a long audit from becoming a backlog nobody owns.
WEEK 1
Baseline and choose
Capture observations, select a narrow prompt cluster, and assign page-level changes.
WEEK 2
Build and publish
Ship owned-source fixes and log the exact URL, owner, and change date.
WEEK 3
Re-test and decide
Repeat the observation contract, then keep, revise, or retire the intervention.
CHANGE LOG
What this manual currently guarantees
- 2026-08-12 — Published a shared observation contract and ungated Prompt Coverage worksheet.
- Technical readiness scores are explicitly separated from live model mentions and citations.
- Performance figures require a reproducible prompt set, date, locale, engine, evidence type, and limitation note.
Start with your URL or your operating model
The URL Snapshot checks observable public signals. The Operations Grader checks whether your team can measure, own, publish, and attribute the channel.