{"id":3775,"date":"2026-06-18T13:37:06","date_gmt":"2026-06-18T11:37:06","guid":{"rendered":"https:\/\/isla-stud.io\/?p=3775"},"modified":"2026-06-18T17:19:51","modified_gmt":"2026-06-18T15:19:51","slug":"llms-txt-wordpress","status":"publish","type":"post","link":"https:\/\/isla-stud.io\/en\/ratgeber\/llms-txt-wordpress\/","title":{"rendered":"llms.txt for WordPress: Useful, Overrated, or Both?"},"content":{"rendered":"<p class=\"wp-block-paragraph\"><strong>As of June 2026.<\/strong> llms.txt is a small Markdown file located in a website\u2019s root directory. Its purpose is to show AI systems which content is important and where they can find machine-readable versions of it. In WordPress, you can now easily generate such a file using a plugin, such as Yoast SEO.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The key question, however, isn't whether you can create a file. The question is: What does it actually accomplish? This is where it gets interesting. llms.txt is more useful than many people instinctively assume, but significantly less powerful than some tool websites promise.<\/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=\"#was-ist-llms-txt\">What is llms.txt?<\/a><\/li><li><a href=\"#nicht-ist\">What llms.txt Is Not<\/a><\/li><li><a href=\"#google\">What Google is currently saying about this<\/a><\/li><li><a href=\"#google-praxis\">Double standards or two levels?<\/a><\/li><li><a href=\"#yoast\">What Yoast Does in WordPress<\/a><\/li><li><a href=\"#datenlage\">What the data shows<\/a><\/li><li><a href=\"#sinnvoll\">When llms.txt Is Useful<\/a><\/li><li><a href=\"#wordpress-checkliste\">WordPress Checklist<\/a><\/li><li><a href=\"#citelayer\">How I Think About llms.txt Using citelayer\u00ae<\/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>llms.txt is a table of contents<\/strong>: It can bundle important pages, documents, and machine-readable versions.<\/li>\n<li><strong>llms.txt is not a robots.txt file<\/strong>: It does not control access and does not replace crawler rules.<\/li>\n<li><strong>llms.txt is not a Google ranking signal<\/strong>: Google explicitly states that Google Search ignores these files for search visibility.<\/li>\n<li><strong>Google's own approach is still fascinating, though<\/strong>: Google Developer Docs also provides many pages in Markdown format; Chrome has a Lighthouse test for llms.txt; and Chrome for Developers provides a large llms.txt file.<\/li>\n<li><strong>Yoast makes implementation easy<\/strong>: The file can be generated automatically, updated weekly, and partially adjusted manually.<\/li>\n<li><strong>The data is sobering<\/strong>: Recent studies have not yet shown a reliable correlation between llms.txt and AI citations.<\/li>\n<li><strong>It can still be useful, though<\/strong>: particularly as a curated context for other systems, agents, documentation, products, and its own AI visibility infrastructure.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">My recommendation: Treat llms.txt as a well-maintained side street, not as a highway to AI visibility. If the file is maintained quickly and properly, there\u2019s little reason not to use it. But it\u2019s no substitute for a clear brand, quality content, a good reputation, or metrics.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"was-ist-llms-txt\">What is llms.txt?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The proposal behind llms.txt originated from the circle around Jeremy Howard and Answer.AI. The idea is simple: Under <code>\/llms.txt<\/code> contains a Markdown file that provides large language models with a condensed, easy-to-read overview of a website.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Why Markdown? Because many websites are quite \u201cnoisy\u201d for machines. Navigation, cookie banners, tracking scripts, layout code, and dynamic elements are all mixed in with the actual content. A curated Markdown file can convey the message more clearly: This is the website; this content is important; here are the clean, readable versions.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For a WordPress site, for example, this could mean grouping together key service pages, central guides, product documentation, API documentation, pricing or policy pages, author information, and selected categories.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"nicht-ist\">What llms.txt Is Not<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The most common mistake is having the wrong expectations. llms.txt is not an access control mechanism. If you <a href=\"https:\/\/isla-stud.io\/en\/ai-visibility\/ai-crawlers-robots-txt-content-signals\/\">Controlling AI crawlers and robots.txt rules<\/a> If you want to do that, you'll need robots.txt, HTTP headers, meta-robots, login barriers, or technical access controls. An llms.txt file doesn't say, \u201eYou're not allowed to do that.\u201c It's more like, \u201eIf you're looking for context, start here.\u201c<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It\u2019s also not a sitemap in the traditional SEO sense. An XML sitemap helps search engines find URLs that can be indexed. llms.txt is more of a curated content map for systems that need context quickly. That can be useful, but it serves a different purpose.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">And above all: llms.txt is not a magic citation tool. A file in the root directory does not turn thin, contradictory, or outdated content into a reliable source.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"google\">What Google is currently saying about this<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">As far as Google Search is concerned, the situation is currently surprisingly clear. In its current documentation on optimizing for generative AI features, Google states that you do not need to create new machine-readable AI files, such as llms.txt, for Google Search. Google Search does not use these files as specific signals for visibility or ranking.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This does not mean that \u201ellms.txt is prohibited\u201c or \u201ellms.txt is harmful.\u201c Google explicitly states that such files can be maintained for other services or systems. It is only with regard to Google Search itself that website operators should not base any expectations regarding rankings or visibility on them.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is important because Google AI Search, AI Overviews, and AI Mode have become the most visible AI context for many websites. Anyone creating an llms.txt file with Google in mind alone should keep a level head. For Google, discoverable, helpful, technically sound, and trustworthy content remains what counts.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"google-praxis\">Double standards or two levels?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Now things are getting quite contradictory. Because while Google Search says you don\u2019t need llms.txt files or special Markdown files for Google Search, Google itself provides machine-readable versions on its developer platforms. The page for the Google Guide to Generative AI Features, for example, is available under a <code>.md.txt<\/code>-URL available as Markdown. This also applies to other Search Central pages, such as the SEO Starter Guide or the robots.txt documentation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In addition, Chrome for Developers has its own <code>\/docs\/llms.txt<\/code>, which references many Markdown versions of the Chrome documentation. And Lighthouse documents an llms.txt audit in the \u201eAgentic browsing\u201c section: If the file is missing, the current status is only \u201eNot Applicable,\u201c but the direction is clear. For search engines, a machine-readable summary of a website can be useful because it helps them understand the site\u2019s structure, purpose, and important links more quickly.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Is that a double standard? A little bit, at least in terms of communication. But from a technical standpoint, it\u2019s more accurate to distinguish between two levels:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Google Search:<\/strong> According to Google, llms.txt should not be treated as having special status for ranking, indexing, and visibility in Google Search.<\/li>\n<li><strong>Agents and Documentation:<\/strong> Markdown files and llms.txt can be very useful for tools, browser agents, developer documentation, and small context windows.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">That\u2019s exactly the point that many short posts fail to mention. \u201eNot necessary for Google Search\u201c doesn\u2019t automatically mean \u201euseless for AI systems.\u201c And \u201eGoogle uses such formats itself in its documentation infrastructure\u201c doesn\u2019t automatically mean \u201eGoogle Search rewards your llms.txt.\u201c Both can be true at the same time.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">My critical take: Google understandably wants to prevent every new file from immediately turning into an SEO gold rush. At the same time, its own developer infrastructure is clearly paving the way for a world in which agents no longer have to laboriously parse away HTML, navigation, JavaScript, and UI noise when the content is also available directly as Markdown. This eliminates the need for context windows, reduces parsing friction, and gets agents to the actual information faster.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For WordPress, this means: I wouldn\u2019t market llms.txt as a ranking trick. But I wouldn\u2019t dismiss machine-readable formats either. They\u2019re more a part of the next layer of technical readability: not an \u201eSEO hack,\u201c but infrastructure for bots, documentation, product knowledge, and your own AI visibility workflows.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"yoast\">What Yoast Does in WordPress<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Yoast SEO can generate an llms.txt file in WordPress. According to Yoast, it is created in the website\u2019s root directory and updated weekly via a scheduled task. Yoast automatically selects content for this, including recent posts and cornerstone content. For individual pages, you can manually override the selection.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In the interface, the feature is located under \"Website Features\" or \"AI Tools.\" You can enable and customize it there. This is convenient because many website owners don't want to\u2014or aren't able to\u2014upload files to the root directory themselves.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Important: If there is already a custom llms.txt file in the file system, this may conflict with plugin outputs. Yoast also documents technical details such as the file path, encoding prefix, and filters. For most websites, this is usually invisible. For developers and agencies, this is exactly where a clear decision must be made: plugin output, a custom file, or a custom dynamic solution?<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"datenlage\">What the data shows<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The current data does not support grand claims. SE Ranking analyzed approximately 300,000 domains and found no clear correlation between llms.txt and AI citation frequency. Only about one in ten domains in the dataset had such a file at all.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">ALLMO examined whether llms.txt plays a visible role in its own dataset of more than 94,000 cited URLs from over 11,000 AI responses. Here, too, the conclusion is cautious: no demonstrable advantage, no clear confirmation that it serves as an AI search lever.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">OtterlyAI also analyzed server logs covering a 90-day period. Of more than 62,000 AI bot visits, only 84 were directed to the llms.txt file. This is not proof that the file is never read. But it does cast significant doubt on the claim that AI bots check there first and on a regular basis.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">My takeaway from the citelayer\u00ae project: llms.txt is currently more of an infrastructure component than a performance lever. It can bring order, highlight priorities, and make machine-readable versions discoverable. However, it is no substitute for content quality, entity clarity, external signals, and genuine AI visibility measurement.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"sinnvoll\">When llms.txt Is Useful<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">I wouldn't reject llms.txt outright. Google's own developer practices actually provide a good argument in its favor: not as a ranking signal, but as a practical aid for systems that need to quickly and accurately capture context. There are situations in which a well-maintained file can be useful:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>You have a lot of important content and want to offer a curated starter pack.<\/li>\n<li>You maintain documentation, a plugin, a SaaS product, a store, or many technical help pages.<\/li>\n<li>You also generate clean Markdown versions of your content.<\/li>\n<li>You want to provide AI agents, internal tools, or your own workflows with a clear context path.<\/li>\n<li>You're intentionally using llms.txt as part of a broader AI visibility strategy, not as the sole lever.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">It's less useful if the website itself is disorganized. If your most important pages are out of date, product names are spelled inconsistently, or the content doesn't provide clear answers, llms.txt will mostly just add to the confusion.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"wordpress-checkliste\">WordPress Checklist<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>First, check the content:<\/strong> Which pages should explain your brand, your services, and your products?<\/li>\n<li><strong>Remove weak candidates:<\/strong> An llms.txt file should not recommend just any archive site.<\/li>\n<li><strong>Provide clear excerpts:<\/strong> If a plugin includes descriptions, they should not be empty, cryptic, or overly promotional.<\/li>\n<li><strong>Check noindex and sitemaps:<\/strong> Important content should not be both hidden and recommended at the same time.<\/li>\n<li><strong>Check the file yourself:<\/strong> Calls <code>https:\/\/deine-domain.de\/llms.txt<\/code> Open it and read it as if you were a stranger.<\/li>\n<li><strong>Decide between a plugin or a custom solution:<\/strong> Yoast is often sufficient for simple websites. For product documentation or AI visibility workflows, a more targeted solution may be more appropriate.<\/li>\n<li><strong>Measure separately:<\/strong> Keep an eye on mentions, sources, and platform differences. The mere existence of the file is not proof of visibility.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"citelayer\">How I Think About llms.txt Using citelayer\u00ae<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/citelayer.ai\/\" target=\"_blank\" rel=\"noopener\">citelayer\u00ae for WordPress<\/a> It does not treat llms.txt as a \"magic file,\" but rather as a building block in a larger AI visibility layer: machine-readable output, Markdown, bot context, <a href=\"https:\/\/isla-stud.io\/en\/advisor\/schema-entities-quotable-content\/\">Schema and Entities<\/a>, content signals, and compatibility with existing SEO plugins.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For me, that difference is crucial. An llms.txt file might say, \u201eHere is important content.\u201c But an AI visibility audit must check: Is this content actually being understood? Does the brand appear in the responses? Which sources are being used? Which competitors are mentioned? Where is evidence missing?<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you want to do more than just activate a file\u2014if you want to check your brand's visibility in AI systems\u2014the <a href=\"https:\/\/citelayer-ai.com\/services\/ai-visibility-audit\/\" target=\"_blank\" rel=\"noopener\">citelayer\u00ae AI Visibility Audit<\/a> the more appropriate next step.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"faq\">FAQ<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Do I need llms.txt for Google AI Overviews or AI Mode?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No, not for Google Search. Google says that Google Search does not use llms.txt or similar specialized AI files to determine visibility or rankings. The file may still be useful for other services or your own agent workflows.<\/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\">If the file is generated properly and contains meaningful content: sure, why not? But don't expect an immediate jump in rankings or citations. Read through the file after activating it and check to make sure it really does showcase your most important content.<\/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 is a control signal for crawler access. llms.txt is a curated content map. It can provide guidance, but it does not block anything and does not replace access control.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What should be included in an llms.txt file?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The most important, up-to-date, and informative content: key service pages, product pages, documentation, author or company information, guidelines, help pages, and well-maintained guides. Outdated, sparse, or contradictory pages do not belong here.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Could llms.txt harm my website?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Technically, the risk is usually low. The problem tends to be editorial: If the file prominently recommends incorrect, outdated, or irrelevant content, it can reinforce a negative perception of your website.<\/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\">This classification is based on my work with citelayer\u00ae products and audits, as well as on publicly available primary and product sources. I use my own analyses as a basis for technical classification; publicly available factual claims can be verified through the following sources.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>llms.txt Proposal: <a href=\"https:\/\/llmstxt.org\/\" target=\"_blank\" rel=\"noopener\">https:\/\/llmstxt.org\/<\/a><\/li>\n<li>Google Search Central: Optimizing Your Website for Generative AI Features on Google Search: <a href=\"https:\/\/developers.google.com\/search\/docs\/fundamentals\/ai-optimization-guide\" target=\"_blank\" rel=\"noopener\">https:\/\/developers.google.com\/search\/docs\/fundamentals\/ai-optimization-guide<\/a><\/li>\n<li>Google Search Documentation Updates: Clarifying guidance on llms.txt files: <a href=\"https:\/\/developers.google.com\/search\/updates\" target=\"_blank\" rel=\"noopener\">https:\/\/developers.google.com\/search\/updates<\/a><\/li>\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>SE Ranking: LLMs.txt and AI Citations: <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 the 2026 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>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<li>Google Search Central: AI Optimization Guide as Markdown: <a href=\"https:\/\/developers.google.com\/search\/docs\/fundamentals\/ai-optimization-guide.md.txt\" target=\"_blank\" rel=\"noopener\">https:\/\/developers.google.com\/search\/docs\/fundamentals\/ai-optimization-guide.md.txt<\/a><\/li>\n<li>Google Search Central: SEO Starter Guide as Markdown: <a href=\"https:\/\/developers.google.com\/search\/docs\/fundamentals\/seo-starter-guide.md.txt\" target=\"_blank\" rel=\"noopener\">https:\/\/developers.google.com\/search\/docs\/fundamentals\/seo-starter-guide.md.txt<\/a><\/li>\n<li>Google Search Central: robots.txt documentation in Markdown: <a href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/robots\/intro.md.txt\" target=\"_blank\" rel=\"noopener\">https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/robots\/intro.md.txt<\/a><\/li>\n<li>Chrome for Developers: llms.txt: <a href=\"https:\/\/developer.chrome.com\/docs\/llms.txt\" target=\"_blank\" rel=\"noopener\">https:\/\/developer.chrome.com\/docs\/llms.txt<\/a><\/li>\n<li>Chrome for Developers: Lighthouse llms.txt audit: <a href=\"https:\/\/developer.chrome.com\/docs\/lighthouse\/agentic-browsing\/llms-txt\" target=\"_blank\" rel=\"noopener\">https:\/\/developer.chrome.com\/docs\/lighthouse\/agentic-browsing\/llms-txt<\/a><\/li>\n<\/ul>","protected":false},"excerpt":{"rendered":"<p>llms.txt can provide AI systems with a machine-readable table of contents. It is not a ranking factor for Google Search. However, it can still be useful for agents and documentation.<\/p>","protected":false},"author":1,"featured_media":3776,"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":[13,764,754],"tags":[],"dipi_cpt_category":[],"class_list":["post-3775","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ratgeber","category-ai-visibility","category-ki-b2b"],"acf":[],"_links":{"self":[{"href":"https:\/\/isla-stud.io\/en\/wp-json\/wp\/v2\/posts\/3775","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=3775"}],"version-history":[{"count":5,"href":"https:\/\/isla-stud.io\/en\/wp-json\/wp\/v2\/posts\/3775\/revisions"}],"predecessor-version":[{"id":3807,"href":"https:\/\/isla-stud.io\/en\/wp-json\/wp\/v2\/posts\/3775\/revisions\/3807"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/isla-stud.io\/en\/wp-json\/wp\/v2\/media\/3776"}],"wp:attachment":[{"href":"https:\/\/isla-stud.io\/en\/wp-json\/wp\/v2\/media?parent=3775"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/isla-stud.io\/en\/wp-json\/wp\/v2\/categories?post=3775"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/isla-stud.io\/en\/wp-json\/wp\/v2\/tags?post=3775"},{"taxonomy":"dipi_cpt_category","embeddable":true,"href":"https:\/\/isla-stud.io\/en\/wp-json\/wp\/v2\/dipi_cpt_category?post=3775"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}