Built in the order it has to be built.
Each layer depends on the one inside it. That is why the entity comes before any content, and why the whole thing takes three weeks rather than three months.
Start with an auditA site whose only job is to be pointed at.
Not a portfolio, not a blog. Home, about, topics, writing, contact. Person and WebSite schema, a sitemap, Search Console connected. Generated from your answers, on a domain you own in your own name, live within the first week, and passed through 23 publish checks before anyone sees it.
A site on its own is something every agency sells. A site that is the address of your entity is the foundation everything else rests on.
You, wired into the graph.
This is the layer nobody else sells, and the one everything depends on. An author page that is the canonical you. Person schema that says which profiles are yours. An ORCID iD, free and recognised. LinkedIn rewritten as an entity rather than a CV, linked back to the site. The same name, the same role line, the same photograph, everywhere. Wikidata only where the notability is genuinely there.
Nothing here is invented. It is your real history, made consistent and readable by machines. The single cheapest win in the whole build is consistency.
What you are known for, with demand behind it.
Up to 150 questions and terms with real search demand, grouped into three to five pillars. For each one we capture whether an AI answer already exists and who it cites today. That tells you where the door is open and where someone already holds the citation. The first ten briefs come out of this, in the order they are worth writing.
Pages an answer can quote.
A page gets cited when a machine can lift a claim from it and attribute it to you: a clear answer near the top, a named author with markup, sources, dates, structure. Twenty-three checks test exactly that, before anything is published, every time. Your tone of voice, derived from your own writing, keeps the pages sounding like you.
Content that keeps coming, in your voice.
A research engine configured to your topics, your tone and your author entity. It researches from the questions with demand, drafts in your voice, runs the publish checks, and queues the result for your approval. Under the set-up it is configured and loaded with your first ten briefs. Producing the articles is a separate line, self-served in your login area or managed for you, so you only pay for content you want.