{"id":12685,"date":"2026-07-28T22:46:37","date_gmt":"2026-07-28T14:46:37","guid":{"rendered":"http:\/\/longzhuplatform.com\/?p=12685"},"modified":"2026-07-28T22:46:37","modified_gmt":"2026-07-28T14:46:37","slug":"why-data-integrity-is-the-new-technical-seo-from-crawling-to-trust-via-sejournal-alexmoss","status":"publish","type":"post","link":"http:\/\/longzhuplatform.com\/?p=12685","title":{"rendered":"Why Data Integrity Is The New Technical SEO: From Crawling To Trust via @sejournal, @alexmoss"},"content":{"rendered":"<p><\/p> <div id=\"narrow-cont\"> <p>In the past two years, Google has dropped support for nine ItemTypes from its rich result search gallery. This has happened not too long after ChatGPT\u2019s launch and when mass adoption began:<\/p> <figure id=\"attachment_582192\" class=\"wp-caption aligncenter\" style=\"width: 2398px\"><img decoding=\"async\" src=\"https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/rich-results-types-chart-123.png\" alt=\"Rich results supported by Google search over time\" width=\"2398\" height=\"940\" class=\"wp-image-582192 size-full\" srcset=\"https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/rich-results-types-chart-123-384x151.png 384w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/rich-results-types-chart-123-425x167.png 425w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/rich-results-types-chart-123-480x188.png 480w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/rich-results-types-chart-123-680x267.png 680w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/rich-results-types-chart-123-768x301.png 768w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/rich-results-types-chart-123-850x333.png 850w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/rich-results-types-chart-123-1024x401.png 1024w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/rich-results-types-chart-123-1280x720.png 1280w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/rich-results-types-chart-123-1300x680.png 1300w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/rich-results-types-chart-123-1536x602.png 1536w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/rich-results-types-chart-123-1600x627.png 1600w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/rich-results-types-chart-123-1920x753.png 1920w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/rich-results-types-chart-123-2048x803.png 2048w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/rich-results-types-chart-123.png 2398w\" sizes=\"auto, (max-width: 2398px) 100vw, 2398px\" loading=\"lazy\" title=\"Why Data Integrity Is The New Technical SEO: From Crawling To Trust via @sejournal, @alexmoss\u63d2\u56fe\" \/><figcaption class=\"wp-caption-text\">Image from author, July 2026<\/figcaption><\/figure> <p>The question remains whether this decline will continue, but the most recent removal \u2013 FAQ\/FAQPage \u2013 has since caused some debate over the role of schema.org within the future of Search.<\/p> <h2>Schema Is Dead, Right?<\/h2> <p>While some perform tests and experiments to understand whether schema really makes a positive impact on being cited within platform responses, Gianluca Fiorelli notably observed that we may be performing these tests on limited datasets. With that in mind, let\u2019s remind ourselves of the wording of the deprecation message\u00a0for FAQ rich results:<\/p> <blockquote> <p><em>\u201c\u2026We will be dropping the FAQ search appearance, rich result report, and support in the Rich results test in June 2026.\u201d<\/em><\/p> <\/blockquote> <p><iframe class=\"sej-iframe-auto-height\" id=\"in-content-iframe\" scrolling=\"no\" src=\"https:\/\/www.searchenginejournal.com\/wp-json\/sscats\/v2\/tk\/Middle_Post_Text\"><\/iframe><\/p> <p>Notice here what they did not mention \u2013 which is that the use of FAQ schema is no longer required. This is because the deprecation is that of rich results only \u2013 a display feature. Schema itself is a comprehension layer \u2013 identifying entities and the relationships between them. Is schema dead? In my opinion, it is far from it. While some properties deprecate, others, such as Product,\u00a0are extended.<\/p> <p>That being said, I\u2019m also aware that adding schema isn\u2019t a magic bullet that contributes towards citation growth. However, that growth goes beyond the metrics we\u2019ve been accustomed to rely on such as citations, impressions, etc. Suganthan Mohanadasan wrote a great piece about how schema has three \u201clives\u201d:<\/p> <ol> <li>Google\u2019s index pipeline.<\/li> <li>LLM pretraining (indirect).<\/li> <li>LLM runtime retrieval.<\/li> <\/ol> <p>SEOs have been historically focused on No. 1 as something that can positively contribute towards success metrics. But schema goes beyond what we\u2019re used to, or accurately, report on. Schema isn\u2019t dying; one display feature it benefited from is diminishing instead.<\/p> <h2>An SEO\u2019s Biggest Threat: Ambiguity<\/h2> <p>Schema is an ontology that, as a web standard, can contribute towards data integrity. The risk to data integrity is ambiguity. Ambiguity leads to hallucinations. Hallucinations snowball. Eventually the result compounds, which could lead to inaccurate results or even incorrect LLM pre-training which could have longer-lasting effects.<\/p> <p>If an agent can misread you, at some point it will. LLMs can then risk traveling into \u201csemantic drift\u201d detracted from the facts and in favor of narrative. This was explored within a piece titled \u201cSangue e Grafi: Teaching a Small Model to Read the Bloodline\u201d\u00a0by\u00a0Andrea Volpini\u00a0and Chiara Carrozza\u00a0where\u00a0frontier models tended to fall for narrative over facts, while a small model given knowledge-graph tools drew level with them.<\/p> <figure id=\"attachment_582194\" class=\"wp-caption aligncenter\" style=\"width: 2424px\"><img decoding=\"async\" src=\"https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/sangue-e-grafi-wordlift-321.png\" alt=\"Sangue e Grafi, by WordLift\" width=\"2424\" height=\"1008\" class=\"wp-image-582194 size-full\" srcset=\"https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/sangue-e-grafi-wordlift-321-384x160.png 384w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/sangue-e-grafi-wordlift-321-425x177.png 425w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/sangue-e-grafi-wordlift-321-480x200.png 480w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/sangue-e-grafi-wordlift-321-680x283.png 680w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/sangue-e-grafi-wordlift-321-768x319.png 768w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/sangue-e-grafi-wordlift-321-850x353.png 850w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/sangue-e-grafi-wordlift-321-1024x426.png 1024w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/sangue-e-grafi-wordlift-321-1280x720.png 1280w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/sangue-e-grafi-wordlift-321-1300x680.png 1300w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/sangue-e-grafi-wordlift-321-1536x639.png 1536w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/sangue-e-grafi-wordlift-321-1600x665.png 1600w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/sangue-e-grafi-wordlift-321-1920x798.png 1920w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/sangue-e-grafi-wordlift-321-2048x852.png 2048w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/sangue-e-grafi-wordlift-321.png 2424w\" sizes=\"auto, (max-width: 2424px) 100vw, 2424px\" loading=\"lazy\" title=\"Why Data Integrity Is The New Technical SEO: From Crawling To Trust via @sejournal, @alexmoss\u63d2\u56fe1\" \/><figcaption class=\"wp-caption-text\">Image from author, July 2026<\/figcaption><\/figure> <p><em>\u2192 Further reading: Information Retrieval Part 1: Disambiguation<\/em><\/p> <h2>5 Layers Of Data Integrity<\/h2> <p>All this corroborates my belief that an SEO\u2019s role is to maximize data integrity, of which schema plays a role. Below, I illustrate five layers of what data integrity can include:<\/p> <figure id=\"attachment_582198\" class=\"wp-caption aligncenter\" style=\"width: 2210px\"><img decoding=\"async\" src=\"https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/5-layers-data-integrity-764.png\" alt=\"5 layers of data integrity\" width=\"2210\" height=\"886\" class=\"wp-image-582198 size-full\" srcset=\"https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/5-layers-data-integrity-764-384x154.png 384w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/5-layers-data-integrity-764-425x170.png 425w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/5-layers-data-integrity-764-480x192.png 480w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/5-layers-data-integrity-764-680x273.png 680w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/5-layers-data-integrity-764-768x308.png 768w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/5-layers-data-integrity-764-850x341.png 850w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/5-layers-data-integrity-764-1024x411.png 1024w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/5-layers-data-integrity-764-1280x720.png 1280w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/5-layers-data-integrity-764-1300x680.png 1300w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/5-layers-data-integrity-764-1536x616.png 1536w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/5-layers-data-integrity-764-1600x641.png 1600w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/5-layers-data-integrity-764-1920x770.png 1920w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/5-layers-data-integrity-764-2048x821.png 2048w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/5-layers-data-integrity-764.png 2210w\" sizes=\"auto, (max-width: 2210px) 100vw, 2210px\" loading=\"lazy\" title=\"Why Data Integrity Is The New Technical SEO: From Crawling To Trust via @sejournal, @alexmoss\u63d2\u56fe2\" \/><figcaption class=\"wp-caption-text\">Image from author, July 2026<\/figcaption><\/figure> <ol> <li><strong>Entities:\u00a0<\/strong>What exists, and what that thing is. Thing, Organization, and Person, stabilized with @ids and tied out to Wikidata, GS1, ISNI, or ORCID so an agent knows your \u201cApple\u201d from the fruit.<\/li> <li><strong>Relationships: <\/strong>How those things connect. @id and\u00a0sameAs, RDF.\u00a0Yoast SEO\u2019s schema aggregation feature\u00a0and\u00a0EntityMap\u00a0by Dixon Jones.<\/li> <li><strong>Format: <\/strong>How structure is serialized and served. JSON-LD, RDFa, and Microdata. Markdown, too (encompassing LLMs.txt, agents.md, OKF) and endpoints (content negotiation, ARD, MCP).<\/li> <li><strong>Actions:<\/strong> What can be done, declared to agents. Schema.org Actions such as BuyAction, plus the newer WebMCP, ACP, and UCP.<\/li> <li><strong>Perception:\u00a0<\/strong>Grounding, third-party perception, sentiment, etc.<\/li> <\/ol> <h2>Aggregation, Guidance, And Consumption<\/h2> <p>In\u00a0a\u00a0post I wrote in October last year, I said, \u201cSEOs will have to consider both sides of the web and how to serve both.\u201d The emerging protocols (all of which were launched in the past two years) show this to be true, where a new \u201cagentic grounding stack\u201d generally adopts one of three goals:<\/p> <div class=\"scrl-table\"> <table data-tablestyle=\"MsoNormalTable\" data-tablelook=\"1696\"> <tbody> <tr> <td data-celllook=\"69905\"><strong>Protocol\u00a0<\/strong><\/td> <td data-celllook=\"69905\"><strong>Goal\u00a0<\/strong><\/td> <td data-celllook=\"69905\"><strong>What It Does\u00a0<\/strong><\/td> <\/tr> <tr> <td data-celllook=\"69905\"><strong>sitemap.xml\u00a0<\/strong><\/td> <td data-celllook=\"69905\">Aggregation<\/td> <td data-celllook=\"69905\">Every canonical URL into a single XML index.<\/td> <\/tr> <tr> <td data-celllook=\"69905\"><strong>llms.txt\u00a0<\/strong><\/td> <td data-celllook=\"69905\">Aggregation<\/td> <td data-celllook=\"69905\">Summary of a site\u2019s content with important information and links to further reading.<\/td> <\/tr> <tr> <td data-celllook=\"69905\"><strong>Yoast Schema Aggregation\u00a0<\/strong><\/td> <td data-celllook=\"69905\">Aggregation<\/td> <td data-celllook=\"69905\">Page-level JSON-LD into one connected site-wide graph.<\/td> <\/tr> <tr> <td data-celllook=\"69905\"><strong>EntityMap\u00a0<\/strong><\/td> <td data-celllook=\"69905\">Aggregation<\/td> <td data-celllook=\"69905\">A site\u2019s entity declarations into one explicit map.<\/td> <\/tr> <tr> <td data-celllook=\"69905\"><strong>Knowledge Catalog\u00a0<\/strong><\/td> <td data-celllook=\"69905\">Aggregation<\/td> <td data-celllook=\"69905\">Structured, unstructured, and SaaS data into a governed context engine.<\/td> <\/tr> <tr> <td data-celllook=\"69905\"><strong>OKF\u00a0<\/strong><\/td> <td data-celllook=\"69905\">Aggregation<\/td> <td data-celllook=\"69905\">Site knowledge into a markdown bundle at \/okf\/.<\/td> <\/tr> <tr> <td data-celllook=\"69905\"><strong>ARD \u00b7 ai-catalog.json\u00a0<\/strong><\/td> <td data-celllook=\"69905\">Aggregation<\/td> <td data-celllook=\"69905\">A domain\u2019s tools and agents into a catalog; registries federate above it.<\/td> <\/tr> <tr> <td data-celllook=\"69905\"><strong>OpenKB\u00a0<\/strong><\/td> <td data-celllook=\"69905\">Aggregation<\/td> <td data-celllook=\"69905\">Source documents compiled into a markdown wiki.<\/td> <\/tr> <tr> <td data-celllook=\"69905\"><strong>Schema.org\u00a0<\/strong><\/td> <td data-celllook=\"69905\">Guidance<\/td> <td data-celllook=\"69905\">The shared vocabulary that tells machines what things mean.<\/td> <\/tr> <tr> <td data-celllook=\"69905\"><strong>agents.md\u00a0<\/strong><\/td> <td data-celllook=\"69905\">Guidance<\/td> <td data-celllook=\"69905\">How agents should represent and interact with you.<\/td> <\/tr> <tr> <td data-celllook=\"69905\"><strong>Markdown for Agents\u00a0<\/strong><\/td> <td data-celllook=\"69905\">Consumption<\/td> <td data-celllook=\"69905\">Same URL served as clean markdown via content negotiation.<\/td> <\/tr> <tr> <td data-celllook=\"69905\"><strong>Markdown\u00a0alternate\u00a0output\u00a0<\/strong><\/td> <td data-celllook=\"69905\">Consumption<\/td> <td data-celllook=\"69905\">A separate .md version linked with\u00a0rel=alternate.<\/td> <\/tr> <tr> <td data-celllook=\"69905\"><strong>\/crawl\u00a0endpoint\u00a0<\/strong><\/td> <td data-celllook=\"69905\">Consumption<\/td> <td data-celllook=\"69905\">Renders\u00a0a\u00a0page, or entire site,\u00a0as clean markdown on demand.<\/td> <\/tr> <tr> <td data-celllook=\"69905\"><strong>WebMCP\u00a0<\/strong><\/td> <td data-celllook=\"69905\">Consumption<\/td> <td data-celllook=\"69905\">Exposes a site\u2019s actions as tools an agent can invoke.<\/td> <\/tr> <tr> <td data-celllook=\"69905\"><strong>NLWeb\u00a0<\/strong><\/td> <td data-celllook=\"69905\">Consumption<\/td> <td data-celllook=\"69905\">Ingests schema, feeds , and sitemaps to answer natural-language queries.<\/td> <\/tr> <tr> <td data-celllook=\"69905\"><strong>ACP\u00a0<\/strong><\/td> <td data-celllook=\"69905\">Consumption<\/td> <td data-celllook=\"69905\">Agent checkout inside ChatGPT against merchant product data.<\/td> <\/tr> <tr> <td data-celllook=\"69905\"><strong>UCP\u00a0<\/strong><\/td> <td data-celllook=\"69905\">Consumption<\/td> <td data-celllook=\"69905\">A common language for agent commerce actions across surfaces.<\/td> <\/tr> <\/tbody> <\/table> <\/div> <p>These three goals help reduce the number of requests while increasing token efficiency. Some of the above protocols have been covered in more detail within Search Engine Journal, including my own on ACP and UCP\u00a0and\u00a0Emina Demiri-Watson\u2019s thorough article on OKF, ARD, and others earlier this month.<\/p> <p>But\u00a0there\u2019s\u00a0something none of these protocols have\u2026<\/p> <h2>There Is No Consensus Or Agreed Standard<\/h2> <p>Schema.org was\u00a0born out of consensus between Google, Microsoft\/Bing, and Yahoo! (Yandex joining later) who launched it under joint governance. The same happened five years earlier with the XML sitemap. When the search engines needed a standard, they simply sat down and created one \u2013 together.<\/p> <p>Nothing like this is happening now, and it comes\u00a0at\u00a0the detriment of SEOs who genuinely want clarity on what to implement and what not to implement\u00a0for sites they work on.\u00a0Even basic facts about consumption are contested, where the\u00a0debate over\u00a0markdown\u00a0is a\u00a0great\u00a0example\u00a0of this.<\/p> <p>While these debates continue, there\u2019s no room where platforms are convening and agreeing to one universal standard. The ecosystem has changed so dramatically that these companies are not in the business of Search and the good of the web, but must now navigate how their businesses affect jobs, economies, livelihoods, and the future of humanity as a whole. As such, I just don\u2019t believe questions posed by SEOs are at the top of their priorities.<\/p> <h2>What Can You Do About It Now?<\/h2> <p>Looking back at the five layers of data integrity, the four you have control over can be illustrated below when looking at what an agentic grounding stack can look like:<\/p> <figure id=\"attachment_582199\" class=\"wp-caption aligncenter\" style=\"width: 1942px\"><img decoding=\"async\" src=\"https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/agentic-grounding-stack-324.png\" alt=\"Agentic grounding stack options\" width=\"1942\" height=\"1436\" class=\"wp-image-582199 size-full\" srcset=\"https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/agentic-grounding-stack-324-384x284.png 384w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/agentic-grounding-stack-324-425x314.png 425w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/agentic-grounding-stack-324-480x355.png 480w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/agentic-grounding-stack-324-680x503.png 680w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/agentic-grounding-stack-324-768x568.png 768w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/agentic-grounding-stack-324-850x629.png 850w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/agentic-grounding-stack-324-1024x757.png 1024w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/agentic-grounding-stack-324-1280x720.png 1280w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/agentic-grounding-stack-324-1300x680.png 1300w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/agentic-grounding-stack-324-1536x1136.png 1536w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/agentic-grounding-stack-324-1600x1183.png 1600w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/agentic-grounding-stack-324-1920x1420.png 1920w, https:\/\/cdn.searchenginejournal.com\/wp-content\/uploads\/2026\/07\/agentic-grounding-stack-324.png 1942w\" sizes=\"auto, (max-width: 1942px) 100vw, 1942px\" loading=\"lazy\" title=\"Why Data Integrity Is The New Technical SEO: From Crawling To Trust via @sejournal, @alexmoss\u63d2\u56fe3\" \/><figcaption class=\"wp-caption-text\">Image from author, July 2026<\/figcaption><\/figure> <p>There\u2019s a lot to consider, and all have different goals and technical debt. Decide which are most applicable to you, as well as adopting anything that should not require too much technical debt.<\/p> <p>If I had to pick an order, it would be this.<\/p> <ul> <li>Stabilize your @ids and add sameAs links out to Wikidata and the other authorities first, because everything else stands on it.<\/li> <li>Then test how\u00a0you\u2019re\u00a0actually interpreted, with\u00a0NLWeb, rather than assuming the graph reads the way you intended.<\/li> <li>If\u00a0you\u2019re\u00a0in ecommerce, audit the product feed before touching anything shiny, and look at\u00a0BuyAction\u00a0while\u00a0you\u2019re\u00a0there: only\u00a0ReadAction\u00a0and\u00a0SearchAction\u00a0are deployed at any real scale today, so the field is genuinely open.\u00a0Look into the recent news about what has been\u00a0added to the Product schema.<\/li> <li>Attempt to implement WebMCP. It can be done on any website, and doesn\u2019t need to be ecommerce.<\/li> <li>Markdown serving and content negotiation can wait until you have engineering capacity to spare (unless\u00a0you can use Cloudflare\u2019s\u00a0Markdown for Agents).<\/li> <li>Look into OKF and ARD. When Google launches new protocols, I always take notice \u2013 especially when it comes to how an agent or LLM understands a site as a whole.<\/li> <\/ul> <p>None of this is a bet on a specific protocol. Implementing any of these reduces the risk that an LLM has to go \u201cthe long way round\u201d to form the answer it wants to respond with. By hedging bets to welcome\u00a0any\u00a0agent from<em>\u00a0any<\/em>\u00a0platform, this will also help you think more about exactly how your site may be interpreted by them, and how this improves when these protocols are adopted.<\/p> <p>Even if you want to make small experiments away from larger sites, it\u2019s worth exploring not only to see if there are positive results from it, but also to understand how they all work in practice. This is exactly what I have done recently, where I have rebuilt\u00a0my personal website, which\u00a0has several \u201cagentic ready\u201d protocols\u00a0running, including content negotiation, markdown alternate, llms.txt and\u00a0WebMCP.<\/p> <h2>Don\u2019t Chase The Protocol, Own The Layers Underneath<\/h2> <p>Right now,\u00a0it seems there\u00a0is no\u00a0single\u00a0\u201cwinner\u201d\u00a0that will progress from a proposal or protocol to a web standard.\u00a0There\u2019s\u00a0no\u00a0consortium\u00a0to repeat what was done with the XML sitemap and Schema.<\/p> <p>The stack is now big, but there\u2019s one thing they all share. Whether it aggregates, guides, or consumes, each one is fed by the same substrate: Accurate entities, explicit relationships, and content a machine can read without guessing or researching further.<\/p> <p>Rankings were the success metrics of the old web. Trust, integrity, accuracy, and validity. Earning this is still the role of an SEO.<\/p> <p><strong>More Resources:<\/strong><\/p> <hr\/> <p><em>Featured Image: hmorena\/Shutterstock<\/em><\/p> <\/div> <p>SEO,Technical SEO#Data #Integrity #Technical #SEO #Crawling #Trust #sejournal #alexmoss1785249997<\/p> ","protected":false},"excerpt":{"rendered":"<p>In the past two years, Google has dropped support for nine ItemTypes from its rich result search gallery. This has happened not too long after ChatGPT\u2019s launch and when mass adoption began: Image from author, July 2026 The question remains whether this decline will continue, but the most recent removal \u2013 FAQ\/FAQPage \u2013 has since [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":12686,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[16],"tags":[1899,4675,450,38483,80,97,341,2108],"class_list":["post-12685","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-accessibility","tag-alexmoss","tag-crawling","tag-data","tag-integrity","tag-sejournal","tag-seo","tag-technical","tag-trust"],"acf":[],"_links":{"self":[{"href":"http:\/\/longzhuplatform.com\/index.php?rest_route=\/wp\/v2\/posts\/12685","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/longzhuplatform.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/longzhuplatform.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/longzhuplatform.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/longzhuplatform.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=12685"}],"version-history":[{"count":0,"href":"http:\/\/longzhuplatform.com\/index.php?rest_route=\/wp\/v2\/posts\/12685\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/longzhuplatform.com\/index.php?rest_route=\/wp\/v2\/media\/12686"}],"wp:attachment":[{"href":"http:\/\/longzhuplatform.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=12685"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/longzhuplatform.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=12685"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/longzhuplatform.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=12685"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}