{"id":3720,"date":"2026-06-18T10:12:55","date_gmt":"2026-06-18T08:12:55","guid":{"rendered":"https:\/\/isla-stud.io\/?p=3720"},"modified":"2026-06-19T01:16:18","modified_gmt":"2026-06-18T23:16:18","slug":"schema-ai-visibility-llms-txt","status":"publish","type":"post","link":"https:\/\/isla-stud.io\/en\/yoast-seo\/schema-ai-visibility-llms-txt\/","title":{"rendered":"Yoast, Schema, llms.txt, and AI Visibility"},"content":{"rendered":"<p class=\"wp-block-paragraph\"><strong>As of June 2026.<\/strong> Yoast SEO can make your WordPress website more machine-readable. That\u2019s valuable. However, it doesn\u2019t automatically mean that ChatGPT, Claude, Perplexity, Gemini, or Google AI will find your content, categorize it correctly, and cite it.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This article is part of a series on <a href=\"https:\/\/isla-stud.io\/en\/yoast-seo-1176\/yoast-seo-plugin-optimal-settings-how-it-works\/\">How to Set Up Yoast SEO Correctly<\/a>. If you want to understand the basic concept first, on its own, without relying on Yoast, start by reading <a href=\"https:\/\/isla-stud.io\/en\/ai-visibility\/what-is-ai-visibility\/\">What is AI Visibility?<\/a>. This section covers a topic that\u2019s particularly prone to misunderstanding in 2026: Schema, llms.txt, and AI Visibility. In short: Yoast lays the groundwork. But visibility in AI response systems is more than just a plugin toggle.<\/p>\n\n\n\n<div class=\"wp-block-rank-math-toc-block\" id=\"rank-math-toc\"><h2>Table of contents<\/h2><nav><ul><li><a href=\"#kurzfassung\">The Summary<\/a><\/li><li><a href=\"#yoast-liefert\">What Yoast Actually Delivers from a Technical Perspective<\/a><\/li><li><a href=\"#schema\">Outline: A Guide, Not a Citation Spell<\/a><\/li><li><a href=\"#llms-txt\">llms.txt: good map, no ranking guarantee<\/a><\/li><li><a href=\"#crawler\">Not all AI crawlers are the same<\/a><\/li><li><a href=\"#ai-visibility\">Why AI Visibility Goes Beyond Traditional SEO<\/a><\/li><li><a href=\"#citelayer-research\">What I now view differently based on my own work with citelayer\u00ae<\/a><\/li><li><a href=\"#wordpress-praxis\">WordPress in Practice: What You Should Decide Now<\/a><\/li><li><a href=\"#citelayer\">Where citelayer\u00ae Comes In<\/a><\/li><li><a href=\"#naechste-schritte\">How to Move Forward Effectively After Yoast<\/a><\/li><li><a href=\"#faq\">FAQ<\/a><\/li><li><a href=\"#quellen\">Sources and Verification<\/a><\/li><\/ul><\/nav><\/div>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"kurzfassung\">The Summary<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Yoast Schema is useful<\/strong>, because it helps search engines and other systems categorize content, organizations, people, articles, and products more accurately.<\/li>\n<li><strong>A framework is not a magic solution<\/strong>, which suddenly turns a weak piece of content into a cited source.<\/li>\n<li><strong>llms.txt is a map<\/strong>: It can display important content and machine-readable versions. However, it is not an access control mechanism, nor does it guarantee a high ranking.<\/li>\n<li><strong>AI crawlers have different tasks<\/strong>: Training, search, user-initiated queries, and agent-based use are not the same thing.<\/li>\n<li><strong>AI Visibility is bigger than Yoast<\/strong>: It's about content, entities, reputation, technical accessibility, platform differences, and measurement.<\/li>\n<li><strong>citelayer\u00ae complements traditional SEO plugins<\/strong>, rather than replacing Yoast: with AI-specific signals, Markdown output, bot context, and audit methodology.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If there's just one takeaway from this article, let it be this: Make a conscious effort to apply technical fundamentals, but don't expect a technical file format to replace your subject matter expertise.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"yoast-liefert\">What Yoast Actually Delivers from a Technical Perspective<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Yoast SEO handles many elements in WordPress that make a website easier for search engines to understand: SEO titles, meta descriptions, canonical URLs, XML sitemaps, social metadata, and structured data. In the current interface, you\u2019ll also find AI-related features such as llms.txt under the website features.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" src=\"https:\/\/isla-stud.io\/wp-content\/uploads\/2026\/06\/yoast-settings-site-features.png\" alt=\"Yoast SEO Einstellungen mit Website-Funktionen, Schema und llms.txt\" data-no-translation=\"\" data-no-auto-translation=\"\"\/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">This is a positive development. Search engines don\u2019t read like humans. AI systems don\u2019t read like humans either. They break down content, verify sources, identify entities, compare statements, and retrieve additional web data depending on the platform. The cleaner your website is from a technical standpoint, the less a system has to guess.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">But: Yoast describes and organizes what\u2019s already there. It doesn\u2019t create expertise, clear positioning, or a reputation. If an article doesn\u2019t provide a clear answer, even perfectly implemented Schema markup is of limited help.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"schema\">Outline: A Guide, Not a Citation Spell<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Schema.org data consists of structured information. For example, it tells machines: This is an article. This is the organization behind it. This is a product. This is a person. This is a breadcrumb trail. Google explicitly describes structured data as a tool to help better understand content and elements on a page and, where appropriate, use them for Rich Results.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is important for WordPress because many websites provide very little machine-readable meaning without an SEO plugin. Yoast lays a solid foundation here. In particular, the \u201cOrganization,\u201d \u201cWebsite,\u201d \u201cArticle,\u201d and \u201cBreadcrumbs\u201d sections\u2014as well as product data when using compatible extensions\u2014can help make a website more clearly defined.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Nevertheless, \u201eimplementing schema\u201c is not the same as \u201eappearing in AI responses.\u201c A 2026 Ahrefs study examined 1,885 pages that had added JSON-LD schema and compared them with approximately 4,000 control pages. Result: For pages already cited by AI, there was no significant increase in citations. That doesn\u2019t mean Schema is useless. It means Schema isn\u2019t a quick fix\u2014you can\u2019t just flip a switch and expect ChatGPT and the like to dutifully cite your website.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">My take: Schema remains important for entity clarity, rich results capability, and machine understanding. However, it is only one component. If content, authority, recency, internal structure, and external mentions are missing, Schema cannot magically fill those gaps.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"llms-txt\">llms.txt: good map, no ranking guarantee<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">llms.txt is a proposed file format for websites. The idea: Under <code>\/llms.txt<\/code> There is a Markdown file that provides AI systems with a kind of table of contents. Important pages, documentation, products, guidelines, or machine-readable versions can be linked there.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Yoast can generate this file in WordPress and, according to its own documentation, update it regularly. You can enable and customize this feature in the settings. This is convenient, especially for people who don't want to create files in the web root themselves or maintain them via code.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">What matters is the expectation. llms.txt is not a robots.txt file. A robots.txt file tells crawlers which areas they are allowed to access or should not access. llms.txt is more like a curated invitation: \u201eHere is the content that matters, and here it is in a format that\u2019s easy for you to read.\u201c<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The current data is sobering. SE Ranking analyzed approximately 300,000 domains and found no clear correlation between llms.txt and AI citation frequency. In a dataset of 94,614 AI-cited URLs, ALLMO found only a single reference to a <code>\/llms.txt<\/code>-URL. OtterlyAI also concluded in a 90-day experiment that llms.txt is not currently a reliable GEO lever.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Why I still don't copy llms.txt: Infrastructure standards rarely catch on the very day they're proposed. A well-maintained llms.txt can be useful in the long run, especially if it doesn\u2019t just list everything indiscriminately but curates the truly relevant content. But it shouldn\u2019t be marketed as a substitute for content quality.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"crawler\">Not all AI crawlers are the same<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A common misconception: \u201eAI crawler\u201c sounds like a single type of bot. In reality, providers themselves distinguish between multiple purposes. OpenAI, for example, documents different user agents for training, search, and user-initiated queries. Anthropic distinguishes between ClaudeBot, Claude-User, and Claude-SearchBot. Perplexity also describes its own crawlers and user agents.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is important from a practical standpoint. If you block everything across the board, you might end up blocking not only training but also search queries or user-initiated responses. Allowing everything is also a decision. Both approaches can be correct. The only mistake is not knowing what your own website is actually serving up.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Google also illustrates just how subtle these differences can be: According to Google, \"Google-Extended\" is not a separate HTTP user-agent, but rather a robots.txt token used to control certain types of usage. Google also emphasizes that \"Google-Extended\" does not affect inclusion in Google Search and is not a ranking signal in search.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For regular website owners, this means: Please don\u2019t just copy and paste robots.txt block lists simply because they sounded dramatic in a LinkedIn post. First, ask yourself: What do you want to allow? What do you want to prevent? What kind of visibility would you be losing? What kind of use do you really want to block?<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"ai-visibility\">Why AI Visibility Goes Beyond Traditional SEO<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Traditional SEO often asks: Is the page being crawled, indexed, and ranked for relevant search queries? AI Visibility also asks: Is the brand mentioned in AI responses? Is it described accurately? Which sources are cited? Which competitors appear? Is the tone positive, neutral, or problematic? And does this vary by platform?<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That\u2019s no small difference. An article can rank well on Google and still not appear in ChatGPT. A brand can be visible in Perplexity but missing from Claude. A website can be technically sound but still seem too thin as a source because it lacks external mentions, clear author attribution, or up-to-date evidence.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Furthermore, AI systems often don\u2019t work with a single search query. This is why the concept of \u201cquery fan-out\u201d is important: A seemingly simple question can be broken down into several sub-questions. If you optimize only for a single main keyword, you may miss out on precisely those sub-questions that will later be used to construct an AI response.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This explains why AI Visibility isn\u2019t something you can just \u201einstall Yoast and activate llms.txt\u201c to get done. These steps can be helpful, but the real work lies in determining whether your website actually provides the relevant sub-questions, entities, supporting evidence, and decision-making information.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"citelayer-research\">What I now view differently based on my own work with citelayer\u00ae<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">As I\u2019ve worked on citelayer\u00ae, my priorities have shifted. In the past, it made sense to treat AI Visibility primarily as a technical checklist: Is there an llms.txt file? Is there a schema? Are AI crawlers allowed? Those factors remain important, but they\u2019re not the core of the matter.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This assessment isn\u2019t based solely on what others are currently publishing about GEO, LLMO, or AI Search. I base it on my own citelayer\u00ae audit and product work: recurring patterns from platform tests, WordPress signals, Schema\/llms.txt checks, and the question of what content AI systems can actually classify as citable.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That\u2019s exactly why I want to break this topic down for regular WordPress users. Not as a battle of buzzwords, but as a practical question: What can you do to improve your website today so that AI systems have to guess less and people get better, more complete answers?<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The stronger signals today tend to be in these areas:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Content Quality:<\/strong> Does the content answer the actual question directly, in a timely manner, and with supporting evidence?<\/li>\n<li><strong>Entity Clarity:<\/strong> Is it clear who is speaking, what the brand stands for, and which services or products are being referred to?<\/li>\n<li><strong>Authority and Reputation:<\/strong> Are there external mentions, a platform presence, author signals, and consistent brand information?<\/li>\n<li><strong>Structure:<\/strong> Are headings, sections, tables, lists, internal links, and sources structured in a way that allows both machines and humans to quickly grasp the content?<\/li>\n<li><strong>AI Presence:<\/strong> Does the brand actually appear in AI responses, or does the website just look technically polished?<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">That\u2019s the point where I start to get skeptical about many \u201eGEO tips.\u201c A technical standard can be useful, but it\u2019s no substitute for a source that really has something to say. A plugin can generate signals, but it can\u2019t create expertise, trust, or mentions in the market for you.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"wordpress-praxis\">WordPress in Practice: What You Should Decide Now<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Master the basics of Yoast:<\/strong> Website name, organization or person, logo, social media profiles, sitemap, canonical tags, SEO titles, and meta descriptions.<\/li>\n<li><strong>Activate the schema intentionally:<\/strong> Not because it promises miracles, but so that your content and entities are described accurately.<\/li>\n<li><strong>Enable llms.txt only for quality purposes:<\/strong> Check which pages appear there. A list of random, thin posts doesn't help anyone.<\/li>\n<li><strong>Check noindex and robots.txt:<\/strong> A page that you want to make visible to both people and AI systems should not be accidentally blocked or excluded from the sitemap.<\/li>\n<li><strong>Write your answer early:<\/strong> If an article answers a question, the answer shouldn't appear only after six paragraphs.<\/li>\n<li><strong>Build internal clusters:<\/strong> A single article is rarely enough. Clearly link foundational information, in-depth content, examples, and next steps to one another.<\/li>\n<li><strong>Cross-platform trade show:<\/strong> ChatGPT, Claude, Perplexity, Gemini, and Google AI may interpret the same brand differently.<\/li>\n<li><strong>Think of AI Visibility as a combination of editorial and technical expertise:<\/strong> The technical aspects must be correct. However, the content must also be citable.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"citelayer\">Where citelayer\u00ae Comes In<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/citelayer.ai\/\" target=\"_blank\" rel=\"noopener\">citelayer\u00ae for WordPress<\/a> fills exactly this gap between a traditional SEO plugin and AI Visibility. Yoast does a great job of covering many SEO basics. citelayer\u00ae adds the AI-specific layer: llms.txt and llms-full.txt, Markdown outputs, AI bot context, content signals, Schema\/API interfaces, and compatibility with existing SEO plugins.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The distinction is important: I don\u2019t want to \u201ereplace\u201c Yoast just because AI Visibility is the hot topic right now. Solid search engine fundamentals remain valuable. But if you want to know whether your brand is visible, accurate, and citable in AI systems, you\u2019ll need additional metrics and methodology.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That's why the <a href=\"https:\/\/citelayer-ai.com\/services\/ai-visibility-audit\/\" target=\"_blank\" rel=\"noopener\">citelayer\u00ae AI Visibility Audit<\/a> The idea is not to treat this as just another plugin toggle, but rather as an analysis of platforms, competitors, entities, content, schema, crawler accessibility, and concrete action steps. The question isn\u2019t \u201eDo we have a file?\u201c The question is: \u201eWhat do AI systems say about us, on what basis, and what\u2019s missing?\u201c<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"naechste-schritte\">How to Move Forward Effectively After Yoast<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Once the Yoast basics are set up properly, the next step isn\u2019t just to flip another switch. It makes more sense to take an honest look at where you stand: What content is meant to explain your brand, what questions does it actually answer, and where do AI systems still have to guess today?<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Clarifying AI Visibility:<\/strong> Check whether your brand appears at all in AI responses and whether it is described correctly.<\/li>\n<li><strong>Maintain llms.txt intentionally:<\/strong> Decide which content should appear there as key entry points.<\/li>\n<li><strong>Check the schema and entities:<\/strong> Are the organization, authors, services, products, and sources described clearly enough?<\/li>\n<li><strong>Handling AI crawlers strategically:<\/strong> Decide what you want to allow, limit, or consciously block.<\/li>\n<li><strong>Thinking Through Query Fan-Out:<\/strong> What specific questions would an AI system need to answer before it could make a meaningful recommendation for you?<\/li>\n<li><strong>Measure instead of guess:<\/strong> Test multiple platforms, not just a single ChatGPT test prompt.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">So Yoast remains the technical foundation. AI Visibility is the strategic work that builds on top of that: making content easier to understand, explaining entities more clearly, strengthening sources, and regularly checking what AI systems actually do with the content.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"faq\">FAQ<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Does Yoast automatically make my website appear in AI responses?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. Yoast can provide technical insights and describe content more clearly. Whether AI systems mention or cite your website also depends on content, recency, reputation, platform logic, external sources, and metrics.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Should I enable llms.txt in Yoast?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">In many cases, yes\u2014as long as you treat the file as a guide and review the content it contains. It\u2019s not a ranking factor. However, it can serve as a useful, search engine-friendly roadmap.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Is llms.txt the same as robots.txt?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. robots.txt controls which crawlers should or should not access certain areas. llms.txt recommends important content and machine-readable versions. It is not an access control mechanism.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Is there any way to guarantee that ChatGPT or Google AI will quote me?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. Schema helps with understanding. There is no citation guarantee. Recent studies in particular show that Schema should not be treated as the sole AI citation lever.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Should I block AI crawlers?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">That's a strategic decision. If you want to prevent the content from being used for training, that's a different issue than visibility in AI search or user-initiated searches. Blocking everything across the board can cost you visibility. Allowing everything across the board is also a conscious decision.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Does citelayer\u00ae replace Yoast?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. Yoast remains a powerful tool for classic SEO fundamentals in WordPress. citelayer\u00ae adds an AI visibility layer: machine-friendly output, AI bot context, content signals, audit methodology, and visibility considerations that go beyond Yoast.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"quellen\">Sources and Verification<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">For this article, I reviewed public primary sources, product documentation, and my own citelayer\u00ae audit and product work. It is important to me to make this distinction: External sources substantiate public facts, while my own work data provide technical context and address practical questions.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Our Own Research Data and Practical Foundations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>In-house citelayer\u00ae audit and product development:<\/strong> recurring patterns from platform tests, WordPress signal checks, query fan-out vulnerabilities, llms.txt\/schema checks, and editorial prioritization.<\/li>\n<li><strong>citelayer\u00ae for WordPress:<\/strong> Product work on llms.txt, llms-full.txt, Markdown outputs, AI bot context, content signals, schema\/API interfaces, and SEO plugin compatibility.<\/li>\n<li><strong>citelayer\u00ae AI Visibility Audit:<\/strong> A public audit perspective on platform responses, competitors, entities, content, structured data, and specific action steps.<\/li>\n<li><strong>Our own market and topic analysis:<\/strong> Positioning, topic radar, and translating technical research findings into accessible articles.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">I am not using my own work data here as external evidence, but rather as a technical basis for my work. Public statements of fact can also be verified using the following sources.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Public sources for cross-checking<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Yoast: llms.txt function: <a href=\"https:\/\/yoast.com\/features\/llms-txt\/\" target=\"_blank\" rel=\"noopener\">https:\/\/yoast.com\/features\/llms-txt\/<\/a><\/li>\n<li>Yoast: Enable and Customize llms.txt: <a href=\"https:\/\/yoast.com\/help\/enable-llmstxt\/\" target=\"_blank\" rel=\"noopener\">https:\/\/yoast.com\/help\/enable-llmstxt\/<\/a><\/li>\n<li>Yoast Developer Docs: llms.txt Functional Specification: <a href=\"https:\/\/developer.yoast.com\/features\/llms-txt\/functional-specification\/\" target=\"_blank\" rel=\"noopener\">https:\/\/developer.yoast.com\/features\/llms-txt\/functional-specification\/<\/a><\/li>\n<li>llms.txt Proposal: <a href=\"https:\/\/llmstxt.org\/\" target=\"_blank\" rel=\"noopener\">https:\/\/llmstxt.org\/<\/a><\/li>\n<li>Google Search Central: Structured Data: <a href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/structured-data\/intro-structured-data\" target=\"_blank\" rel=\"noopener\">https:\/\/developers.google.com\/search\/docs\/appearance\/structured-data\/intro-structured-data<\/a><\/li>\n<li>Google Search Central: robots.txt: <a href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/robots\/intro\" target=\"_blank\" rel=\"noopener\">https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/robots\/intro<\/a><\/li>\n<li>Google Crawlers: Google Extended and Other Crawlers: <a href=\"https:\/\/developers.google.com\/crawling\/docs\/crawlers-fetchers\/google-common-crawlers\" target=\"_blank\" rel=\"noopener\">https:\/\/developers.google.com\/crawling\/docs\/crawlers-fetchers\/google-common-crawlers<\/a><\/li>\n<li>OpenAI: Crawlers and User Agents: <a href=\"https:\/\/developers.openai.com\/api\/docs\/bots\" target=\"_blank\" rel=\"noopener\">https:\/\/developers.openai.com\/api\/docs\/bots<\/a><\/li>\n<li>Anthropic: ClaudeBot, Claude-User, and Claude-SearchBot: <a href=\"https:\/\/support.claude.com\/en\/articles\/8896518-does-anthropic-crawl-data-from-the-web-and-how-can-site-owners-block-the-crawler\" target=\"_blank\" rel=\"noopener\">https:\/\/support.claude.com\/en\/articles\/8896518-does-anthropic-crawl-data-from-the-web-and-how-can-site-owners-block-the-crawler<\/a><\/li>\n<li>Perplexity: Crawlers: <a href=\"https:\/\/docs.perplexity.ai\/docs\/resources\/perplexity-crawlers\" target=\"_blank\" rel=\"noopener\">https:\/\/docs.perplexity.ai\/docs\/resources\/perplexity-crawlers<\/a><\/li>\n<li>Ahrefs: Schema and AI Citations: <a href=\"https:\/\/ahrefs.com\/blog\/schema-ai-citations\/\" target=\"_blank\" rel=\"noopener\">https:\/\/ahrefs.com\/blog\/schema-ai-citations\/<\/a><\/li>\n<li>Ahrefs: AI Overview, Citations, and Top 10 Overlap: <a href=\"https:\/\/ahrefs.com\/blog\/ai-overview-citations-top-10\/\" target=\"_blank\" rel=\"noopener\">https:\/\/ahrefs.com\/blog\/ai-overview-citations-top-10\/<\/a><\/li>\n<li>Ahrefs: Query Fan-Out: <a href=\"https:\/\/ahrefs.com\/blog\/query-fan-out\/\" target=\"_blank\" rel=\"noopener\">https:\/\/ahrefs.com\/blog\/query-fan-out\/<\/a><\/li>\n<li>SE Ranking: llms.txt Analysis: <a href=\"https:\/\/seranking.com\/blog\/llms-txt\/\" target=\"_blank\" rel=\"noopener\">https:\/\/seranking.com\/blog\/llms-txt\/<\/a><\/li>\n<li>ALLMO: llms.txt for AI Search Report: <a href=\"https:\/\/allmo.ai\/articles\/llms-txt\" target=\"_blank\" rel=\"noopener\">https:\/\/allmo.ai\/articles\/llms-txt<\/a><\/li>\n<li>OtterlyAI: llms.txt Experiment: <a href=\"https:\/\/otterly.ai\/blog\/the-llms-txt-experiment\/\" target=\"_blank\" rel=\"noopener\">https:\/\/otterly.ai\/blog\/the-llms-txt-experiment\/<\/a><\/li>\n<li>Yoast SEO AI+: <a href=\"https:\/\/yoast.com\/product\/yoast-seo-ai-plus\/\" target=\"_blank\" rel=\"noopener\">https:\/\/yoast.com\/product\/yoast-seo-ai-plus\/<\/a><\/li>\n<li>citelayer\u00ae WordPress Plugin: <a href=\"https:\/\/citelayer.ai\/\" target=\"_blank\" rel=\"noopener\">https:\/\/citelayer.ai\/<\/a><\/li>\n<li>citelayer\u00ae AI Visibility Audit: <a href=\"https:\/\/citelayer-ai.com\/services\/ai-visibility-audit\/\" target=\"_blank\" rel=\"noopener\">https:\/\/citelayer-ai.com\/services\/ai-visibility-audit\/<\/a><\/li>\n<\/ul>","protected":false},"excerpt":{"rendered":"<p>Yoast lays an important foundation with Schema and llms.txt. However, AI Visibility also requires clear content, entities, a crawler strategy, and accurate metrics.<\/p>","protected":false},"author":1,"featured_media":3741,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","footnotes":""},"categories":[647,763,13],"tags":[],"dipi_cpt_category":[],"class_list":["post-3720","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-yoast-seo","category-howtos","category-ratgeber"],"acf":[],"_links":{"self":[{"href":"https:\/\/isla-stud.io\/en\/wp-json\/wp\/v2\/posts\/3720","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/isla-stud.io\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/isla-stud.io\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/isla-stud.io\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/isla-stud.io\/en\/wp-json\/wp\/v2\/comments?post=3720"}],"version-history":[{"count":5,"href":"https:\/\/isla-stud.io\/en\/wp-json\/wp\/v2\/posts\/3720\/revisions"}],"predecessor-version":[{"id":3828,"href":"https:\/\/isla-stud.io\/en\/wp-json\/wp\/v2\/posts\/3720\/revisions\/3828"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/isla-stud.io\/en\/wp-json\/wp\/v2\/media\/3741"}],"wp:attachment":[{"href":"https:\/\/isla-stud.io\/en\/wp-json\/wp\/v2\/media?parent=3720"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/isla-stud.io\/en\/wp-json\/wp\/v2\/categories?post=3720"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/isla-stud.io\/en\/wp-json\/wp\/v2\/tags?post=3720"},{"taxonomy":"dipi_cpt_category","embeddable":true,"href":"https:\/\/isla-stud.io\/en\/wp-json\/wp\/v2\/dipi_cpt_category?post=3720"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}