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 Checklist
28 checks spanning crawlability, entity building, structured data, and citable content: the week-one worklist of our 30-day audit.
Open guideThe llms.txt Deployment Guide
Configuring llms.txt for your site from scratch: syntax, directory structure, how it divides labor with robots.txt, and the common mistakes we've caught on live client sites.
Open guideThe Three-Tier GEO Metrics Whitepaper
Citation rate, answer share, Pipeline contribution: what each one measures, how to capture it, and why traffic should never be your KPI. Includes weekly-report field definitions.
Open guideThe 3-Week Rewrite Loop Playbook
The fixed cadence of diagnose → rewrite → verify: how to prioritize gaps, what to actually change in a rewrite, and what evidence decides success or another lap in week three.
Open guideSix Engines, Six Citation Preferences
Where the citation logic of ChatGPT, Perplexity, AI Overviews, Gemini, Claude, and Copilot diverges, and why the same piece of content meets a completely different fate across engines.
Open guideHow to Evaluate a GEO Agency
How to choose a GEO vendor: the 12 questions to ask, the data to demand, and the red flags to run from, including how to size us up.
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.