
I’ve discovered that AI agents heavily rely on structured data to understand and interact with my content. Embracing schema markup is essential to thriving in the emerging agentic web.
Schema markup has become pivotal in SEO and Generative Engine Optimization (GEO) conversations. I learned that both Google and Bing utilize structured data to fuel AI overviews, and platforms like ChatGPT incorporate it for product suggestions.
The evolution towards the agentic web means AI systems interact directly with websites on our behalf. It’s not just about understanding content; they need schema markup to interpret and act on it. This makes it clear why schema is becoming an integral part of the agentic web’s infrastructure.

In the traditional search landscape, schema markup enhances visibility by making my content eligible for search engine results page (SERP) features. It aids search engines in understanding entities better, thereby influencing how results are presented to users.
AI agents go beyond by leveraging schema markup to understand relationships and relevance. They assess if content is actionable enough to be recommended or used for task completion. This knowledge helps them determine if my content is trustworthy.
With structured data, my website becomes easier and cheaper for AI systems to process. Parsing unstructured HTML is more costly compared to clean, structured data, especially as large language models (LLMs) work within finite context windows and escalating inference costs.

Sites that simplify content interpretation are more attractive to AI agents as these systems expand. This simplification becomes critical for ensuring my content is accessed and utilized effectively.
I understand that NLWeb, built on schema markup, plays a vital role in the agentic web’s infrastructure. Microsoft’s open-source initiative, NLWeb, enables websites to integrate AI-powered conversational interfaces, transforming them into AI apps for natural language queries.
Developed by R.V. Guha, NLWeb connects with my existing schema markup, leveraging structured formats like Schema.org. This allows both humans and AI agents to interact seamlessly with the web.

Incorporating structured data like RSS with NLWeb ensures a real-time, interactive experience for AI agents, making my site truly ‘agentic’. The transition from humans browsing to AI agents querying underlines the significance of these initiatives.
For someone like me aiming to optimize for the agentic web, schema markup is a game-changer. It enables my site to be more than just readable, allowing for direct, real-time interactions through NLWeb’s capabilities.
NLWeb uses AI tools to create natural language interfaces, enhancing how my content can be queried and interacted with. It doesn’t require a complete rebuild of my existing content structure, just good order in my schema markup.
By prioritizing completeness, automating processes where possible, and utilizing JSON-LD, I can make steady progress in schema optimization. It’s crucial that I view schema as a comprehensive graph across my site, improving reliability and trust for AI agents.
Ultimately, adopting schema markup and understanding its evolving role in the agentic web is vital. As AI systems evolve, content that aligns with their preferences will reap ongoing benefits.
Inspired by this post on Search Engine Land.


Leave a Reply