Google sent people searching for
a Norwegian landscaper
to an AI article from Cape Town.
Agaia.no is Norway's largest landscape contractor. Founded 1981. Builds outdoor spaces in Buskerud. Has nothing to do with AI, software, or Cape Town. AGIA is an AI development methodology coined here in September 2026. Google has been sending Agaia's search traffic our way. Here is why that happened, what it proves about GEO, and the real comparison everyone should read — vibe coder, traditional developer, or AGIA?
Google Search Console shows every query that landed someone on your site. Most of them make sense — you wrote about a topic, someone searched for it, they found you. Occasionally one appears that makes you stop and stare at the screen for a moment.
"agaia.no founded" — 48 impressions, position 9.85. "Who is the CEO of agaia.no" — 43 impressions, position 6.77. People looking for a Norwegian construction company and ending up on a Forge Vertical article about AGIA — Artificial General Intelligence Architect.
Agaia AS and AGIA are not the same thing. One is a 45-year-old landscape contractor in Buskerud, Norway. The other is an AI development methodology coined in Cape Town on 17 September 2026. Google's entity disambiguation engine is still catching up — it sees similar character sequences, no strong entity separation yet, and routes the traffic accordingly. The result is that Agaia's customers are finding Forge Vertical, and Forge Vertical is appearing in searches it had no intention of targeting.
Before anything else — a free mention for Agaia AS, because they deserve the traffic back and this is genuinely one of the more unusual free advertisements a Norwegian landscaper has ever received from a Cape Town developer.
Why Google made this mistake — and why it matters for your business
// Chapter 01 — Entity disambiguation in plain EnglishGoogle does not just index words. It tries to understand entities — the real-world things that words refer to. "Apple" the company versus "apple" the fruit. "Paris" the city versus "Paris" the person. When a new entity enters the web, Google has to decide where it sits in its knowledge graph and how it relates to existing entities.
AGIA was coined on 17 September 2026. Agaia AS has been indexed since at least the early 2000s. When someone searches "agaia" or "agaia.no" today, Google's entity model has forty years of Agaia AS data and about eleven days of AGIA data. The character sequences are similar enough — four letters, A-G-I-A versus A-G-A-I-A — that the disambiguation is genuinely difficult until enough distinct entity signals accumulate to pull them apart cleanly.
The Agaia confusion will resolve itself as AGIA accumulates more indexed content. In the meantime — 91 impressions from people searching for a Norwegian landscape contractor is 91 more impressions than would have existed without the overlap. The internet rewards the well-positioned.
The actual comparison — vibe coder, traditional developer, AGIA
// Chapter 02 — Three types of builder, one production systemThe Agaia/AGIA mix-up is a useful hook for the comparison that actually matters. Not between a Norwegian landscaper and a Cape Town developer, but between the three types of person currently building software in 2026 — and what happens when each of them hands you a production system.
The thing that separates the three is not the output — it is what happens next
// Chapter 03 — The production momentA vibe-coded app and an AGIA-built app can look identical in a demo. The same screens, the same flows, the same features ticked off the list. The difference becomes visible at the production moment — when real users arrive, when a payment fails at 2am, when a client needs a feature the original build did not anticipate, or when someone finds a security gap and decides to use it.
The vibe coder in that situation opens the codebase and finds something they cannot reliably navigate — because it was generated in pieces without a coherent architecture holding it together. The traditional developer navigates it but takes longer than the situation allows. The AGIA knows exactly where the problem is, because they specified the architecture before a single line was written and can trace any failure back to a known component.
This is what the Facebook group post was actually about — the developer who responded to a beginner's question with rage rather than guidance. That rage comes from having cleaned up too many vibe-coded systems that looked like products and behaved like accidents. It is understandable. It is not useful. The better response — and the AGIA response — is the same one given in that group: show me what you tried. Tell me what you understand. We go from there.
What the Agaia accident proves about GEO
// Chapter 04 — The methodology in practiceThe practical takeaway for any South African business: your competitors are not doing this. They have a website, maybe some Google Ads, possibly a Facebook page. They do not have Wikidata entity nodes, structured schema on every page, llms.txt files telling AI models exactly what their business does, or articles that create entity connections to adjacent concepts in their industry.
The gap between a business with GEO infrastructure and one without it is the same gap between a vibe-coded app and an AGIA-built one. Both exist. Only one works reliably at scale.