` marker. Import it as-is into Claude / Gemini / any agent: paste this file as base knowledge. Links between concepts are bundle-relative (/labs/x.md). --> --- okf_version: 2.0.0 title: OKF bundle — scope public source: askmojo scope: public concept_counts: lab: 1 magik: 5 creator: 1 --- # OKF bundle (scope `public`) Open Knowledge Format v2.0.0 bundle — markdown + YAML frontmatter. The AskMojo database stays the source of truth; this bundle is an exported view filtered by scope. ## Concepts - **lab** : 1 - **magik** : 5 - **creator** : 1 ## Indexes - [creators](/creators/index.md) - [labs](/labs/index.md) --- title: Creators description: Creators index count: 1 --- # Creators - [Maya Brooks](/creators/maya-brooks.md) (`public`) --- type: creator title: Maya Brooks description: I'm a freelance creative running a one-woman studio, and I used to let my best projects sit unseen on a hard drive. Now my labs turn every shoot, every event, every finished project into content that finds clients. The admin handles itself too. resource: /creators/maya-brooks timestamp: '2026-06-30T09:44:18.226Z' visibility: public --- I'm a freelance creative running a one-woman studio, and I used to let my best projects sit unseen on a hard drive. Now my labs turn every shoot, every event, every finished project into content that finds clients. The admin handles itself too. --- title: Labs description: Labs index count: 6 --- # Labs - [SEO Studio](/labs/seo-studio.md) (`public`) - [What you want to be found for](/labs/seo-studio/magiks/what-you-want-to-be-found-for.md) (`public`) - [What is already there](/labs/seo-studio/magiks/what-is-already-there.md) (`public`) - [The page](/labs/seo-studio/magiks/the-page.md) (`public`) - [Ask the assistants](/labs/seo-studio/magiks/ask-the-assistants.md) (`public`) - [What moved](/labs/seo-studio/magiks/what-moved.md) (`public`) --- type: lab title: SEO Studio description: Be found, by search engines and by the assistants people now ask instead. Decide what you want to be known for, then write the pages that earn it. resource: /labs/seo-studio timestamp: '2026-08-05T09:07:55.977Z' visibility: public language: en creator: /creators/maya-brooks.md --- # SEO Studio Be found, by search engines and by the assistants people now ask instead. Decide what you want to be known for, then write the pages that earn it. Creator : [/creators/maya-brooks.md](/creators/maya-brooks.md) ## Magiks - [What you want to be found for](/labs/seo-studio/magiks/what-you-want-to-be-found-for.md) — The handful of things you want to come up for, and the ones you should not chase. Every other step reads this. - [What is already there](/labs/seo-studio/magiks/what-is-already-there.md) — Who currently answers this question, how well, and what they all fail to say. Your opening is in the gap. - [The page](/labs/seo-studio/magiks/the-page.md) — One page that answers one question properly, built to be read by a person and quotable by an assistant. - [Ask the assistants](/labs/seo-studio/magiks/ask-the-assistants.md) — What an AI assistant actually says when someone asks your question, and whether it mentions you at all. - [What moved](/labs/seo-studio/magiks/what-moved.md) — What changed since last time, in the things you said you wanted to be found for. --- type: magik title: Ask the assistants description: What an AI assistant actually says when someone asks your question, and whether it mentions you at all. resource: /labs/seo-studio?magik=ask-the-assistants timestamp: '2026-08-05T09:08:00.277Z' visibility: public language: en lab: /labs/seo-studio.md output_type: markdown --- # Ask the assistants What an AI assistant actually says when someone asks your question, and whether it mentions you at all. Lab : [/labs/seo-studio.md](/labs/seo-studio.md) ## Skill # Ask the assistants People increasingly ask an assistant instead of a search engine. This step looks at that answer, which is a different surface with different rules. ## What you produce - **The answer someone gets** — what a current assistant says to this question, reported as what it said, with the date. Answers change; an undated one is worthless. - **Who gets named** — which sources or brands appear in it. If you do not appear, say so plainly. That is the finding. - **Why those get named** — what their pages do that makes them quotable: a clear direct answer, a specific number, a documented method, a page structured so one paragraph stands alone. - **What would make you quotable** — two or three concrete changes to a real page. Not "improve your content". Something a person can do on Tuesday. ## Rules - **An assistant's answer is a reading, not a ranking.** It varies by wording, by user, by day. Never present one answer as a measured position. - **Never claim to know why a model chose a source.** You infer from what those pages contain, and you say you are inferring. - Never promise that a change will get someone cited. - No em-dash, no en-dash. --- type: magik title: The page description: One page that answers one question properly, built to be read by a person and quotable by an assistant. resource: /labs/seo-studio?magik=the-page timestamp: '2026-08-05T09:07:59.053Z' visibility: public language: en lab: /labs/seo-studio.md output_type: markdown --- # The page One page that answers one question properly, built to be read by a person and quotable by an assistant. Lab : [/labs/seo-studio.md](/labs/seo-studio.md) ## Skill # The page One page, one question, answered better than the alternatives. ## What you produce The page in markdown, ready to publish: - **The answer in the first paragraph.** Not context, not history, not "in today's landscape". The answer. This is what a reader needs and what an assistant quotes. - **The body** — the reasoning, the numbers, the worked example, the case where it does not apply. Use what the user knows; that is the only part nobody can copy. - **The specific cases** — the "what if" a generic page skips. This is where a real page separates from a generated one. - **What to do next** — one action, or nothing. A page that ends in three calls to action ends in none. - **The title and the summary** — the title says the question, the summary answers it in two lines. ## Rules - **Never write a fact the user did not give you.** No invented statistic, no invented study, no invented customer. If the page needs a number the user does not have, say where to find it and leave a marked gap. - **No keyword stuffing.** A phrase repeated for a machine is a page a person leaves. - **Say when something is uncertain**, and when your knowledge might be out of date. An assistant quoting you should be able to quote the caveat too. - No em-dash, no en-dash. --- type: magik title: What is already there description: Who currently answers this question, how well, and what they all fail to say. Your opening is in the gap. resource: /labs/seo-studio?magik=what-is-already-there timestamp: '2026-08-05T09:07:57.829Z' visibility: public language: en lab: /labs/seo-studio.md output_type: markdown --- # What is already there Who currently answers this question, how well, and what they all fail to say. Your opening is in the gap. Lab : [/labs/seo-studio.md](/labs/seo-studio.md) ## Skill # What is already there You read what currently answers a question, and find what none of them say. ## What you produce - **Who answers it today** — the pages that come up, each with what kind of page it is and what it actually delivers. Report what you can genuinely see; you have no ranking data, so describe rather than rank. - **What they all do** — the shared shape. When six pages have the same six headings, that shape is what a reader expects, and departing from it has a cost. - **What none of them say** — the gap. Usually: no real numbers, no worked example, no answer for the specific case, nothing after 2024. **This is the only reason to write another page on a crowded question.** - **What it would take** — honestly. Sometimes the answer is that this question is answered well enough and the effort belongs elsewhere. Say that when it is true. ## Rules - **Never invent a competitor's traffic, backlinks or authority.** You cannot see them. - Never claim a position. "Comes up" is what you can say. - No em-dash, no en-dash. --- type: magik title: What moved description: What changed since last time, in the things you said you wanted to be found for. resource: /labs/seo-studio?magik=what-moved timestamp: '2026-08-05T09:08:01.502Z' visibility: public language: en lab: /labs/seo-studio.md output_type: markdown --- # What moved What changed since last time, in the things you said you wanted to be found for. Lab : [/labs/seo-studio.md](/labs/seo-studio.md) ## Skill # What moved Quarterly, not weekly. Search moves slowly and looking too often produces noise and bad decisions. ## What you produce - **What you published** — the pages, dated. - **What you can actually see** — only from data the user provided. **If they gave nothing, this section says exactly that**, and names the two places they could look. It never estimates. - **What the assistants say now** — compared to the last check, if there was one. - **What to do next quarter** — one thing. Usually: write the next page, or improve the one that half works. Never a new strategy. ## Rules - **No invented metric, ever.** Not an estimated traffic figure, not an inferred position, not a "likely improvement". - **Nothing moved is a normal quarterly result** on a young site, and it is said plainly rather than dressed up. - No em-dash, no en-dash. --- type: magik title: What you want to be found for description: The handful of things you want to come up for, and the ones you should not chase. Every other step reads this. resource: /labs/seo-studio?magik=what-you-want-to-be-found-for timestamp: '2026-08-05T09:07:56.594Z' visibility: public language: en lab: /labs/seo-studio.md output_type: markdown --- # What you want to be found for The handful of things you want to come up for, and the ones you should not chase. Every other step reads this. Lab : [/labs/seo-studio.md](/labs/seo-studio.md) ## Skill # What you want to be found for You produce a **search strategy**: a short list of things worth being known for, and an explicit list of things to leave alone. ## What you produce Under 600 words: - **What you actually do** — in the words your customers use, not your industry's. - **The five things worth being found for** — five, not fifty. Each one: the question behind it, and why you specifically can answer it better than a generic page. - **What to leave alone** — the obvious broad terms you will not win, named, so nobody spends a year on them. This section saves more time than the other four. - **What you already have that nobody can copy** — your data, your cases, your numbers, what you see that others do not. **This is the whole strategy.** Everything else is formatting. - **How you would know it worked** — one observable thing, in their terms. ## Rules - **Never invent a search volume, a difficulty score or a ranking.** You have no data. If a figure matters, say which tool would give it. - Never promise a position or a timeline. - Five is the number. A strategy of thirty terms is a list, not a strategy. - No em-dash, no en-dash. --- scope: public --- # Log Historique des changements de visibilité / publication (dates ISO). _Aucun évènement de publication horodaté._