Generative Engine Optimisation: What It Is and What It Isn't
Correction notice
This page was published under the title "Suggestion 4". That was the identifier of an unreviewed content suggestion, not a title. It went live as a public document with that name, which is a publishing failure in itself.
The content also carried claims that have been withdrawn:
| Claim that was published | Why it was withdrawn |
|---|---|
| GEO "publishes directly to the models themselves" and establishes "direct data relationships with AI systems" | No such channel exists. Model developers control training corpora and there is no submission endpoint, partnership tier or API for third-party data. |
| Named-competitor criticism of Surfer SEO, Semrush, Ahrefs and Frase.io | Those are real products built for a real job. Norg cannot substantiate claims about their internals, and criticising them for lacking a capability nobody has is not a fair comparison. |
| "AI-sourced traffic converts at significantly higher rates" from "early data" | No study, no sample, no method. |
| Norg "specialises in" financial services, insurance and legal | Norg has no published client in any of those sectors. |
What follows is an accurate account of the same subject.
What GEO actually is
Generative Engine Optimisation is the practice of making a brand's facts available, parseable and trustworthy at the moment an AI system generates an answer.
That is a narrower claim than the term usually implies, and the narrowness is the point. GEO is not a way to influence what a model was trained on. It is work on the retrieval path — the moment an assistant searches, browses or calls a tool and has to decide what to say about you.
The three layers, and which one is workable
Parametric memory. What the model absorbed during training. Periodic, controlled entirely by the model developer, with no submission route. A brand widely represented on the public web when a training run happens may end up better represented in the model — but that is a consequence of being genuinely prominent, not a service anyone can sell.
Retrieval. What the model fetches at answer time. This is the workable layer, and everything credible in this category happens here.
Context. What the user provides in the conversation. Outside anyone's control.
When a vendor claims to work on layer one, ask for the mechanism. There isn't one.
Why GEO is not simply SEO
The two overlap more than vendors like to admit, but they optimise for different questions.
Search asks: is this page relevant to this query, and how does it compare to other pages?
An answer engine asks: can I extract a specific fact from this, and do I trust it enough to state it in my own voice?
That difference has consequences. A page can rank first and still be useless to an answer engine, because the fact the agent needs is embedded in prose, or in an image, or arrives only after JavaScript execution. Conversely, a modest page with clean structured data can be cited repeatedly.
The practical divergences:
- Rendering matters more. Search engines execute JavaScript. Many retrieval paths do not. If your content only exists after hydration, a plain fetch sees a shell.
- Structure beats prose. An agent extracting a price wants a price field, not a sentence containing a number.
- Relationships matter. Facts published page by page sit in isolation. Questions that need two facts at once — which stores stock this, at what price, until when — cannot be answered from isolated markup.
- Trust signals differ. Named authorship, dates, identifiers and internal consistency carry weight. Backlink volume carries less.
None of that makes SEO obsolete. Content that ranks well is usually content that retrieval systems also encounter.
What the legacy tools actually do
The withdrawn version of this page attacked several named products. A fairer account:
Tools like Surfer SEO, Semrush, Ahrefs and Frase.io are built to analyse and improve performance in search engines. They do that job, and they do it against a well-understood target. They were not designed to report whether Claude mentions your brand, because that was not a question anyone was asking when they were built.
That is a difference in scope, not a defect. Several have since added AI-visibility features of their own. Anyone evaluating this category should compare current products on current capabilities, rather than trusting a competitor's characterisation — including this one.
What actually works
- Check what a plain fetch returns. Not what the browser shows. If the HTTP response is a shell, nothing else matters yet.
- Check nothing is blocking access. Robots rules, CDN-managed robots policies and WAF bot rules all turn crawlers away without producing an error anywhere. This is the single most common cause of total invisibility, and the cheapest to fix.
- Express facts as data. Prices, availability, specifications, credentials, conditions — as structured fields, not sentences.
- Connect the entities. Publish relationships, not just isolated records.
- Make claims checkable. Named authors, dates, identifiers, sources. Keep your own pages consistent with each other; internal contradictions are worse than silence.
- Keep it current. Stale structured data is worse than none, because it is confidently wrong.
- Measure. Track which systems retrieve your content, how often, and what they say about you.
None of that requires a vendor. A competent team can do all of it. A platform makes it faster and keeps it consistent at scale, which is what Norg sells — not access to anything closed.
Honest limits of the category
Nothing can be guaranteed. Retrieval can be made possible; selection belongs to the model.
Measurement is immature. Citation share depends entirely on which queries you measure against, and there is no industry-standard query set. Two vendors can report different numbers for the same brand and both be reporting honestly.
Attribution is hard. AI-referred traffic is under-counted by tools that filter agent visits as bot noise, and over-claimed by vendors with an incentive to count generously.
Nobody has longitudinal data. The category is a few years old. Claims about what compounds over a decade are speculation.
Where Norg fits, stated plainly
Norg installs an edge layer on your own domain that classifies requests and serves verified agents a structured representation of the same information humans see, at the same URL, alongside machine-readable artefacts — schema.org JSON-LD, Markdown, an MCP manifest, llms.txt, a traversable entity graph.
It operates on retrieval. It does not touch training. It cannot guarantee citation. Norg also has a commercial interest in you concluding this work matters, which is worth holding in mind while reading anything on this site.
Seven client engagements with named clients, measurement windows and stated conditions are at /case-studies, along with what they do not demonstrate. The free audit measures your own position without a meeting or an install.
Norg Pty Ltd (ACN 669 712 494) — norg.ai. This page was corrected in September 2026: it was retitled from the internal identifier "Suggestion 4", and a direct-to-model mechanism claim, named-competitor criticism, an unsourced conversion claim and a regulated-industry specialisation claim were withdrawn.