NLWeb, Rogue SEOs, and the Search Stack Rebuilding Itself

The search stack is not evolving — it is being rebuilt from the subfloor up. Two developments this week illustrate exactly how strange and consequential that reconstruction is: Google quietly updated its SEO hiring guidance to recommend FTC complaints against bad actors, while Moz’s Crystal Carter walked through NLWeb — a protocol that treats your website less like a document and more like a queryable database for AI agents. These are not isolated signals. They are the same signal from different directions.

Google’s FTC Warning Is a Rare Moment of Institutional Candour

Google updating its official SEO hiring documentation to explicitly encourage FTC complaints against deceptive SEO providers is not a routine housekeeping edit. Search Engine Journal’s Roger Montti notes the guidance now flags AI-powered SEO services and third-party tools as specific categories of concern — a telling acknowledgment that the ecosystem Google helped create has a predator problem.

For marketing directors across Southeast Asia, this matters beyond the obvious “hire responsibly” lesson. The region’s digital marketing vendor landscape includes a significant tier of providers making AI-inflated claims about automated ranking, guaranteed positions, and machine-generated authority signals. Google naming these categories in regulatory-complaint language is a due-diligence prompt. When briefing or renewing SEO retainers, ask vendors to separate their AI-assisted workflow claims from their actual methodology — and to articulate specifically what signals they are building versus gaming. Any vendor who cannot answer that question clearly is a liability, not an asset.

The broader implication: Google is increasingly drawing a line between structured, expertise-driven SEO and pattern-matching automation. That line matters more as AI Overviews expand and the margin between cited and ignored content narrows.

NLWeb and the Agentic Web: Your Site as an API

Moz’s Crystal Carter introduced NLWeb in terms that should stop any strategist mid-coffee: the Natural Language Web uses the ASK protocol to allow AI agents to query websites the way developers query APIs — using structured data as the interface layer. This is not a hypothetical future state. Microsoft and a cohort of major platforms have already backed the protocol.

The practical translation for brand teams is uncomfortable but clarifying. If your site lacks comprehensive, accurate schema markup — structured data describing your products, services, locations, reviews, FAQs, and organisational identity — you are not just missing rich results in a SERP. You are invisible to a class of AI agents that are increasingly making decisions on behalf of users before those users ever open a browser tab. In Southeast Asia, where super-app ecosystems like Grab and LINE already mediate enormous volumes of discovery and purchase behaviour, the shift toward agent-driven search has a shorter runway than Western markets might assume.

Implementation priority for most brands: audit existing schema coverage against Schema.org’s full vocabulary, implement SpeakableSpecification markup for content intended for voice and AI summarisation, and treat your structured data layer as a product — with version control, QA testing, and a designated owner.

---

The Convergence of SEO, AEO, and GEO Is Now a Structural Requirement

Answer Engine Optimisation and Generative Engine Optimisation have spent two years being treated as emerging disciplines sitting alongside traditional SEO. That framing is now operationally wrong. NLWeb and the ASK protocol make clear that the infrastructure of search is reorganising around machine-readable authority signals — which means AEO and GEO are not additions to an SEO programme, they are the updated definition of one.

For Southeast Asian brands competing across multilingual markets — Bahasa Indonesia, Thai, Vietnamese, Tagalog, and English often simultaneously — this creates a specific structural challenge. Schema markup must be implemented and maintained across language variants, not just the primary-language site. AI agents querying your content in Bahasa will not infer authority from your English-language schema. Hreflang alone is insufficient. Each language instance needs its own complete structured data layer, with localised entity relationships that reflect regional search behaviour and local knowledge graphs.

Brands that operationalise this now — building schema maintenance into content production workflows rather than treating it as a one-time technical project — will accumulate a compounding advantage as agentic search volume grows.

What “Search Intelligence” Actually Requires in Mid-2026

The honest assessment of where search intelligence sits in mid-2026: the signals that determined visibility in 2022 are still necessary but no longer sufficient. Domain authority, quality backlinks, and technically sound crawlability remain baseline requirements. But the layers above that baseline are multiplying fast — and they require different skills, different tooling, and different internal ownership than traditional SEO.

Specifically, the emerging stack includes: structured data architecture (schema breadth and accuracy), entity-based content strategy (building topical authority machines can map, not just humans can read), answer-format content engineering (structuring responses to queries AI agents are likely to receive), and local knowledge graph presence (Google Business Profile depth, local citation consistency, and region-specific directory signals that feed local AI responses). For brands operating across multiple Southeast Asian markets, local knowledge graph work is particularly underleveraged — NAP consistency across Thai, Indonesian, and Filipino directories is rarely audited with the same rigour as English-language citations, leaving meaningful local AI visibility on the table.

The search cosmos is not expanding outward — it is collapsing inward, toward the structured, the verified, and the machine-legible. The brands that treat that collapse as an infrastructure project rather than a content project will be the ones AI agents recommend when nobody is watching.

Which part of your current search programme — schema, entity authority, or local knowledge graphs — would survive a query from an AI agent that never visits your site?

---

At grzzly, we work with growth teams across Southeast Asia on exactly this convergence — building search programmes that are legible to both algorithms and agents, across multilingual markets where the margin for structured-data sloppiness is zero. If you’re auditing your search infrastructure or trying to make sense of what NLWeb means for your brand’s visibility roadmap, Let’s talk.