Quests · Across the whole method
What to do next, in one file
Measuring tells you where you stand. Quests tells you what to do about it: your own decided moves and the rows your measurement puts up for review, in the one place the work resumes.
Two kinds of rows, one file
A quest is a move you decided, written in your words and kept where you will look for it. Alongside them, the file carries what the measurement puts up for review: a domain the engines keep citing while no tracked keyword covers it, a page whose canon has moved since it was last verified, a proof older than your current wording, a page where an engine showed your brand. Each of those rows is acted on in its own tool, and clears itself once the move is made.
- Your quests open and close by hand: it is your file, and a wording is corrected at any time
- The rows the measurement puts up clear on their own once the move is made
- One file per brand, or every brand of the account in a single read
How the file works for you
Open it to know where to resume
Your open quests first, newest at the top, and next to them what the measurement is holding for review. An empty file with the measurement running means there is nothing to correct today.
Record the move you decided
One short wording, notes for the context and the links. Sending the same one twice returns the quest already in the file, so a retry never doubles a line.
Close it, or set it aside
Done when the move happened, set aside when you decided against it. Both keep the quest in the closed history, dated, and reopening puts it back in the file.
Its place in the method
Quests carries no step of its own: it runs across them all. Every step feeds it, a canon that moves, a survey that uncovers a domain, a page that falls out of phase, and the file answers what the work asks every morning: what to do today, and where to pick it up.
Prepaid credits, no subscription: you pay for the checks that run. The whole grid is public.
See pricingCommon questions
What do I actually do to get cited by AI assistants?
You decide what the AIs should say about you, measure what they answer, align the pages you have the final say on, get corroborated on the pages someone else holds, and date every move. Quests is where that work becomes a list: the moves you decided, and the rows your own measurement puts up for review, in the order the work resumes.
How do I keep a GEO to-do list?
In one file per brand, next to the measurement that produced it. A quest carries a short wording and your notes; it opens and closes by hand, and the closed ones stay readable with their dates, so last quarter is still there when you report on it.
What does the measurement put in the file by itself?
Four kinds of rows: a domain the engines keep citing while no tracked keyword covers it, a page whose canon has moved since it was last verified, a corroboration older than your current wording where someone can be asked for an update, and a page where an engine showed your brand with no proof recorded yet. Each one is acted on in its own tool and leaves the file once the move is made.
Can my AI assistant read and write the file?
Yes. The quest file is read and written through the REST API and the MCP server, with the same keys as the rest: your assistant reads what is open, adds the move you have just decided, and closes the one it carried out. Adding the same quest twice returns the one already there, so an assistant that retries never doubles a line.
Can I reopen a quest I closed too early?
Yes: reopening puts it back in the file, its wording, its notes and its dates intact. A quest set aside and done after all becomes done, since the last move is what the file remembers.
Make AIs recommend you
Create a tracker in minutes: your prompts, your engines, your cadence. First checks within 24 to 48 hours.
No subscription. Credits from $10 that never expire. Pause anytime: the history stays yours.