What generative engine optimisation actually asks of you when you can't outsource the signal.
Every GEO guide I've read in the past few months starts the same way. A definition. A list of AI tools. A framework with five steps and eight sub-steps and a diagram. Then a section called "Getting Started" that assumes you have a content team, a schema implementation specialist, and a quarterly review process.
I have me.
I should probably care about this more. After Ahrefs Evolve Singapore earlier this year, I went home and said out loud to no one in particular that I was going to learn GEO and AEO properly. Seriously, the way I take the craft of building seriously. I meant it. Then I opened seven browser tabs, read four frameworks that all said the same thing in different fonts, and closed the laptop.
The thing I've finally worked out is that GEO isn't a campaign. It's not something you run. It's a signal problem, and most of the guides are written by people who want to sell you a solution to a problem they've slightly mischaracterised.
Here's what I actually found.
What GEO Is, In One Paragraph
Generative engine optimisation is the practice of structuring your digital content so AI systems, ChatGPT, Gemini, Perplexity, AI Overviews, whatever comes next, can find it, understand it, and cite it when someone asks a relevant question.
That's it. The rest is implementation detail.
The reason it feels new is because the reading audience changed. Before, you were optimising so a search engine could rank you. Now you're also optimising so a language model can confidently summarise and cite you. They're related disciplines but they reward slightly different things.
The Part Nobody Tells You If You're Small
Here's the thing that stopped me mid-tab. A 2026 dataset on AI Overview citations found that 38% of the pages being cited are not in Google's top 10 for their respective queries.
Thirty-eight percent. That's not a rounding error.
What's doing the work, if not rankings? Attribution. Clarity. Authority signals that don't require domain age or backlink volume.
Specifically: pages with a named author, a title, and a linked bio earn approximately 60% more AI citations than equivalent anonymous content. Authored content earns 2.3 times more AI citations than anonymous content, full stop.
If you are the brand and your name is on your work, you're structurally ahead of every faceless agency publishing generic guides under their company logo.
I've been thinking of being small as the constraint. It's also the signal.
What Actually Matters (For a Studio of One)
There are four things that move the needle. Not eight. Not fifteen. Four.
1. Author attribution, done properly
Your name needs to be on your work, linked to a bio that demonstrates real experience. Not just a name at the bottom of the page. A bio page, a consistent author URL, credentials that are specific rather than vague.
This isn't new. But most people either skip it or do it badly. "Creative director" is a title. "Frontend developer and creative director who has been building Nuxt sites and working with independent Southeast Asian brands for five years" is a signal. The specificity is the proof.
2. Direct-answer structure
AI systems are looking for content that answers questions clearly and early. The buried lede is a GEO problem.
This doesn't mean writing like a FAQ page. It means knowing what question your article answers and making sure it's answered within the first 200 words, properly, not as a teaser. The full article can go deeper, but the answer needs to be findable without reading to the end.
3. Schema markup
I've written about the layer of intention inside your code before, in the Ahrefs Evolve recap. For GEO specifically, schema is how you tell AI systems what your content means rather than just what it says.
Article schema. Author schema. FAQ schema where relevant. JSON-LD, implemented properly in your head tag. On Nuxt, that's a useHead call. On Astro, it's your layout head. On Next, useHead or the Metadata API. It's not difficult. It's just intentional.
Most small sites don't have it, or have it partially implemented and half-broken. That's the gap. And for once, the gap is easy to close.
4. Topical consistency
You don't need volume. You need coherence.
If you publish ten articles on ten unrelated topics, you're a blog. If you publish ten articles that address a specific set of questions within a clearly defined space, linked to each other properly, you're building topical authority. AI systems read the site, not just the page.
For Echo, the SEO and process pillar exists for exactly this reason. Every piece in this space is a node in a network. The network is what gets cited, not the individual article.
What to Stop Doing
Stop treating GEO as a separate practice from building your site well. They're the same discipline. Semantic HTML, fast load times, clear content structure, proper metadata. This is SEO. It's also GEO. It's also just good code.
Stop publishing without a real author bio. Even if you're the only person at your studio, make the bio specific. Make it linkable. Make it findable.
Stop thinking that because you're small you can't compete in AI citations. The data doesn't support that. What you can't do is compete on volume. What you can do, and what the frameworks won't tell you because they're selling volume, is compete on signal quality.
A 900-word article that clearly answers one question, from a named author with specific credentials, with proper schema and a couple of clean internal links, will outperform a 3,000-word pillar assembled by a team and attributed to "the editorial staff."
The anonymous content machine is losing the GEO race. It just doesn't know it yet.
The Signal Was Already There
When I went back to the Ahrefs Evolve recap I wrote in May, I realised I'd already done most of this without naming it. Named author. Specific experience described. Questions answered directly within sections. Internal links. A bio that says something real.
I wasn't doing GEO. I was just building the article properly.
That's either reassuring or annoying, depending on how much time you've spent reading guides.
The thing I've taken from all of this: GEO isn't asking you to change what you do. It's asking you to do what you're already doing with more intention. Know what question you're answering. Put your name on it. Tell the machine what it's reading.
For a studio of one, that's not a disadvantage.
It's kind of exactly the point.
If you want that intention built into your content system, that's content & copywriting.
