If your domain is new, the honest read is that you cannot win the terms you want for a long time. The sites holding them have been accumulating authority for years and have people whose job is keeping them there.
The useful question is what moves faster than domain authority. The answer turns out to be the surfaces answer engines pull from, which is why demand for generative engine optimisation has gone from almost nothing to a real search category in about two years, along with the related searches for AI visibility and AI search optimisation.
This is written from the position of running a new domain, not from having finished. Take it as a plan with reasoning attached rather than a report of results.
Why citation is the faster game
Ranking rewards accumulated trust in a domain. That is a stock, you build it slowly, and a new site has none.
Citation works differently. When an engine assembles an answer it is looking for passages that address the question directly and can be attributed to something. Authority still matters, but so do things a new site can control immediately: whether your claim is stated plainly enough to lift, whether it appears anywhere the engine already trusts, and whether it exists anywhere else at all.
The last one is the leverage. If the information exists in ten places, an engine has no reason to name any of them. If it exists in one, naming it is the only option.
Most of the work is not on your site
This is the uncomfortable part for anyone who would rather be writing.
Answer engines lean heavily on third-party surfaces — review platforms, comparison listicles, community threads, directories. Those surfaces have the authority you lack, and unlike your domain age you can appear on them in weeks. Getting listed where your category gets compared, and being present in the places your buyers actually ask questions, does more in the first months than another post will.
The order that follows from this is uncomfortable but clear: the off-site work outranks the on-site work early, and it costs time rather than engineering. If you are choosing between publishing a fifth article and claiming your profiles on the surfaces that already rank, claim the profiles.
Write only what a model cannot already say
The rule that survives contact with this: if a competent model can answer the question without you, writing the answer is volunteering to be summarised without attribution.
That rules out the explainer content most new blogs start with. Nobody needs the thousand-and-first description of what an AI agent is, least of all a model that has read the other thousand.
What it leaves is narrower and better. Things you measured. Methods you used and can describe precisely. Decisions you made with the reasoning intact, including the ones that turned out badly. Constraints you hit that are not documented anywhere because nobody else built the thing.
Original data is the strongest version of this, because a number that exists in one place must be attributed to that place. It is also the hardest, since it requires having enough of something to count. It is worth gating honestly: numbers computed from too small a sample are noise dressed as research, and publishing them is worse than publishing nothing, because the whole point was to be citable rather than dismissible.
The mechanics that matter on the page
Less than people think, but not nothing.
Put the answer first. A meaningful share of citations come from the early part of a page, and an argument that arrives in the sixth paragraph has wasted the position that was doing the work.
Make passages self-contained. Retrieval operates on passages, not documents, so a section that only makes sense after the three before it is a section that cannot be lifted.
Mark up what you actually have. Article metadata with a real modification date, and question markup only where the questions are genuinely rendered and genuinely answered. Marking up questions you did not answer is the kind of thing that stops working and then counts against you.
Keep dates honest. Restamping a file changes nothing about the content and the engines are not the audience being fooled — you are, about whether the post is still true.
You cannot measure any of this by default
The part most easily skipped: without the property verified in the search consoles, none of the above is measurable. You will not know which pages are indexed, what they surface for, or whether anything changed.
There are two consoles worth having rather than one. The second matters because one major assistant's retrieval runs on that index, which makes it the closest thing to a direct readout of AI answer visibility.
And the cheapest honest measurement is manual: once a month, ask the assistants the ten questions your buyer would actually ask, and write down whether you appear. Ten minutes, no tooling, and it is the only thing that directly measures the outcome you are chasing.
What this adds up to
Expect little from your own domain for months. Spend that time on the surfaces that already have authority, publish only what could not have been written without you, and verify the properties so you can tell the difference between working and waiting.
Our own attempt at the third category is what we hit implementing a compliance requirement, which is the kind of thing that only exists because we did it. The free tools are the other half of the same idea: utility that cannot be summarised, because you have to run it.
Last reviewed 18 September 2026.
