The Agent Readable Website
Codeable Skill Chat
A practical Codeable Skill Chat deck for auditing AI discovery, readability, and honest capability signals.
This talk is not an SEO guide.
Things. Things have been in flux. Things are in flux. Things will be in flux. So a little bit of a disclaimer. AI facts are very, very perishable. Model behavior vendor terms crawler behavior and search surfaces can change faster than an Elementor layout after someone finds the custom CSS box. I’m sure you have some. None of you have experienced that issue.
And these. These things can change. But I want to keep it, like, somewhat durable as. As much as possible. However, if it’s, you know, if it’s fused down the line, I highly recommend checking some of these resources again and checking for newer versions.
This talk is not an SEO guide. This is talk is not SEO for LLMs. There’s plenty of existing content for that. You, you know, Search Engine Land, take your Yoast, take your pick. There’s like, there’s plenty of stuff on that. I am not. I am not an SEO expert. I’m a software engineer.
I highly recommend, like, going in and checking out that to fill in the gaps we cover in here. This is specifically what this talk is, is specifically the parts of agentic Discovery that you need to know if your SEO is already good enough.
Like, you know, maybe you get, you don’t get a 99 on Lighthouse score, but you get like an 80. Like, you’re at least in, like, the, like, well into the green. And so, like, okay, I did. I’ve been doing this SEO. Like, what’s the new stuff I got to do for the agentic stuff? That’s the little slice we’re targeting on this talk today.
So landscape of terms.
So landscape of terms. There’s, there’s a lot of. There’s a lot of verbiage. And nebulous, like, like what to call this new. AI SEO stuff. The leading term as of right now, the year of our Lord 2026 seems to be GEO, which is unfortunate because the GEO is already another thing. But that seems to be what Andreessen Horowitz and Bing are landing on. And that, that’s just generative answer grounding and citations. So raise of hands. How many of you guys have asked AI a question?
And then what you do is you just say, no. You’re wrong ChatGPT. Look it up. And then it does a web search. And ChatGPT is like, oh, oh, you’re right. Yes. WordPress plugins are not built on node. Okay, that’s my bad.
So grounding where I was. Yeah. So, so that’s, that’s where you’re grounding the model. And real facts. These models, they love. They’ve been taught to save tokens. They’ve been taught to save on it. Like web requests to search because OpenAI does not want to be Google. They want to be something different and they don’t want to be Perplexity either and always answer with web results. They want the model to be able to figure out and be a super guesser. And it’s always guessing in, like, the bummer part is like 60s for 70% of the time is like a correct guess. And so you have to ground. And so GEO is basically grounded answering generative engine optimization, optimizing for that process.
AEO, this is used by HubSpot profound and some marketing teams. It’s more brand presence and answered engines. And so that means how you show up and how you, it’s a little more thinking about the agentic side. Agent search visibility. That’s mentioned citations share of voice sentiment, agent Readiness, which will, which is a little bit more of what this talk is about. Is used by Cloudflare and checker tools. And can agents read, fetch and use the site agent readability, which is something which is a term and concept Vercel writes about is, is the page easy for agents to parse and AI features is what Google is something, a term Google Search Central uses, which is Google specific AI overview and AI mode guidance. So the, the, the little search that, like, pops the little AI summary that pops at the top of your results. To tell you that strawberries are, in fact, blue, that, that, that’s the AI summary. That’s what the Google likes to call that AI features. So that’s, that’s just to ground us. We’re grounding ourselves to a little bit of the terms that are being used in this for the industry right now.
Agent empathy or agentic empathy.
The, the description, like the, the, the idea, like the definition we came up with for this talk is designed for what an agent can actually perceive. Preserve and verify safely to do on a human’s behalf. And so what that means is another, another way to think about it is agent empathy is user experience, but for agents.
So what that means is, is the way an agent. Like, like Codex, like Claude Code perceives the world is through this chat box type interface. It doesn’t have eyes to, like, view page pages or, like, look at it, look at a camera. That’s a different tool. Everything it perceives and processes has to be usually done through text interfaces. So it’s as if it’s, it’s doing the whole world through its text messages. Now, it’s really good at that. It can read JSON, it can read XML really fast, but that’s how it perceives the world. So if you’re, if, if there’s a tool, if there’s some tooling that shows a screen to it, it has to, it typically has to, what it’s getting is like some, that tool gives a text description and gives a DOM structure, gives some kind of, like, text structure to describe a screen. Some models, like, for example, like, like GPT-5 gem of four Gemini, they can process visual images, but it’s still a little bit separate, and then not all the tooling is cut up to that. And so it’s still very common if you want to, if you capture, like. If you have an agent interact with a browser, it’s not actually, like, looking and taking screenshots. And it’s definitely not observing that browser in real time, like, like a video.
So what it is, it’s a practical habit of respect for agents entry path. Context budget fetch loss Source uncertainty and action risk. Why it matters is the truth does not survive the fetch parse citation in action. The agent guesses, skips you, cites someone else or hits unsafe affordance. So fundamentally, this is getting into the perspective of the agent. Like, for example, if you guys, I don’t know if you guys have ever, like, gone into ChatGPT and opened up ChatGPT or Codex or, like, one of the models and opened up the thinking, like, expanded the thinking area and just read through its thinking process, that’s agentic empathy. That’s like reading through and, like, understanding how it thinks and runs through and, like, its process. And then what happens is, like, if you, it’s like any skill, if you read that and, and process that enough, you can. You can learn to get and develop an instinct for how agents think, which is, which is funny because the agents were taught to think like us, and now we’re learning to think like them.
So what agentic empathy looks like? So structure is empathy. So this can be JSON-LD. Who’s here heard of JSON-LD, like structured data that Google has you use. That’s actually those types of formats are actually very good. For agents to parse because, again, it’s like, it’s, it’s, it’s seeing the whole world through, like, Telegram, like this, this back and forth, like, like, show me this. Oh. Oh, like, I got this message from the, from the user and, okay, I’m going to give them this message back. And then those, like, you can think of harnesses. I’m sure you, some of you guys have heard of harnesses. Harnesses basically take those, the, like, the requestions and the responses, the props and the responses and do things with them. Or you can also call those tools or actions. And those wrap around, like that system of just, like, back and forth.
So structure is empathy, like metadata headings context, make pages easier for agents. So, like, using proper, like, there’s only one H1 on a page. That’s the way it’s been forever. Like using, like, lots of nice headers that are, that give nice information. Fetch loss is real tabs truncation redirects. Auth gates and broken markdown can hide the answer. Entry path matters. So search crawlers, user fetchers and training crawlers are different policy landing lanes, which will, I think we have a slide on here in a bit. And then actions needed boundaries, tools, permissions, approval logs and honest capability signals.
There are three ways agents, like, or AI, like LLMs experience the internet.
There are three ways agents, like, or AI, like LLMs experience the internet. At least for the, in the context of this slide. So first is search indexing, which is a little bit of what you alluded to of, like, okay, it has to discover the, the internet and what’s out there. Everything can’t just come from Bing. Everything can’t just come from Google. These companies want to, like, have their own understanding of the internet because they want to crawl and search the internet in their own way. And so you could actually, like, if you go into your server logs or your, your http traffic, you can see incoming requests from things like these. First one is OpenAI Search Bot. The second one is Claude Search Bot, and the last one is Perplexity Search Bot. And you’ll see other ones. Google is just Gemini. So Google just reuses their existing crawler for Gemini.
A crawler with an app that is crawling on behalf of the index. So, like, they’re prefetch, they’re cached version of the internet, so to speak. The second one is user fetch: ChatGPT-User, Claude-User, Perplexity-User. So what this is, is this is someone sitting in ChatGPT, like a real user sitting at chat. And this is a promise from these companies that this is like, this is the type of traffic that’s coming that they’re sending to your site. So this is a, this is a user, like a ChatGPT user. It’s somebody from Codex, somebody from Claude Code, somebody from, like, maybe the Perplexity desktop app. They’re, they’re going out. They want to know something and their agent is going out and searching your site and reading it. That’s what this request means. This is, and you can find this in. Like. It’s like the UA agent or something. I mean, it’s always like a similar. Like, name. So this is the same spot.
The third category is training model development, GPTBot, ClaudeBot. And other names for that. What this is, is this company is going and looking at your site and pulling in the data so they can train an AI model with it. So this is the third lane. So the reason they split these into three lanes is because not everyone wants all of this traffic. Some people want to opt out of like, no, I do not want you to train. Like, your AI on my content. I want my content to, like, be out of your training dev. And I’ll let you do that. And generally, hopefully they’ll honor that. And so what that means is you can say, like, hey, I want to, I want to block GPTBot, but I search bot and ChatGPT users are fine. Like, they can, you know, I want those are, that’s new traffic. And so I want them to be able to access by site. So those are the kind of three lanes.
Again, it’s like these are, for the most part, these are going to be using, like, the initial HTML. So that’s the part you need to make sure is, like, good. Like, looks good. If you’re, if, if Lighthouse says you’re good, if Lighthouse says you’re, like, at least a little bit on the green, you’re probably good for all these. And so the Lighthouse is still a very good tool. And as far as, like, load speed to calibrate against, yeah, that was a good question.
Time is that long tail specific content that’s actually, like, value driven will get, will float to the top faster and you will get rewarded faster for writing content that’s actually useful and helpful.
How, how AI works now, how, how searchable, how search works before. Let’s say you’re searching for a recipe, you go to the first page and you, you. You guys know the drill. Like you, you go to the first page and I gotta pause my walk. You, you look, you look on the page and then what’s, what’s, what’s there when you open the page? Is it a recipe? No, it is a ad. And so you scroll down and then you scroll. And then what is, is it the recipe? No, it’s. It’s the history of the recipe. And then you’re like, okay, well, that’s not the recipe. I search for a recipe. And then you scroll down and is it the recipe? No, it’s the family history. And then, like, the, the history of the country where the recipe comes from. And then you do this. You do this for a long time. And then finally you get to, like, after, like, scrolling, like, 10 feet, you get to the bottom and there’s this, like, dot list of, like, just the recipe that you asked for. And then you do that and you repeat that one to five times through, through the blue links until you get exhausted and you’re just like, and then you just do doordash. So that is, that is our current experience. Like our historical experience, what we’ve been doing with search of, like, human driven search.
So the agents, on the other hand, the agent, the, it can read 100, 1000 times faster than a person. And I can process and analyze way faster. So what it does is it explores 50 to 500 links. I don’t know if you’ve done Gemini searches, but it will actually read 500 links and, and search for. So what this means is, like, that is that, there’s that tippy top of, like, the first 10 links that always get the, all the attention. This long tail of, like, who knows what’s in there, but nobody, like, when was the last time anybody went through past the second or third page on Google?
And then they’re going really deep. You’re doing that agent work. But the agent’s going to get that long tail and they’ll go and they’ll read every little bit and bring out, bring the summaries back to you and bring the most, the most unique. So what this means is unique, special, specific content is actually going to get rewarded more. And like the SEO tricks, like the, the stuff that’s gamifying and, like, making SEO worse for everybody is going to go away. That doesn’t mean it’s going to fix everything. And that doesn’t mean there’s going to be new worse things. Just the existing workforce things are going to get, like, we’re just going to get, get rid of them. And, like, you, you ask, like, hey, ChatGPT, give me a recipe.
For Mediterranean chicken, and you get the recipe. You don’t have to scroll, like, go through all this stuff. And so what that, that means is like, you’re, my theory. Time is that long tail specific content that’s actually, like, value driven will get, will float to the top faster and you will get rewarded faster for writing content that’s actually useful and helpful.
There’s still the unsolved problem of, like, how content creation will be rewarded. The thing is, is like, people are not going to, like, new content can’t go away. Like, AI can only think of so many things. And so my theory is that. Stuff that can only be written by humans is going to get more and more and more valuable. And so that has to be rewarded somehow. To get more people to create that because then, because that will be the thing that the AI needs the most, the thing that’s lacking. That’s my theory anyway. So that’s a little bit of how, like, agentic search changes, which is good. It’s actually good for, if you’re not a big. Publisher, this is actually pretty good, good news. As long as you’re making sure, like, the focus is the same focus as before, but it now even more important. You’ve got to create content that’s valuable and helpful to people.
So I have this little Lighthouse command.
It’s going to install the upgraded version of Lighthouse. And I, by the way, I like to, I love using Ghostty, like all the hipster developers. And so it’s actually going to run just like you were saying, jenny, it’s actually going to load up the site and analyze it. And this is how Google scores agent and browsing. That’s not how everybody does it, but this is Google’s way. But those two audits accessibility tree is well formed. Again, that structured data that we were talking about earlier, cumulative layout shift is zero. That’s good. And then these are not applicable because there’s extra features you can add on that we’ll get into here in a bit. That will, such as web MCP and then llms.txt. I think this does have an ls, but it’s, these are not scored because you’re just kind of like bonus. But you should still pay attention to them if you want to optimize for agentic browsing and agent search.
So this is not a very like huge bar to pass. Some pat, some sites might, might still fix it, but it’s like, it’s, it’s not crazy difficult to fix. But just like my site. There’s some extra bonus stuff you can do for agent Discovery. Not every site, every, every site should generally have llms.txt. And maybe an llms-full.txt, which is like designed. It’s like anything goes make it an even bigger file. Just don’t make it like crazy. Like a super long time to like the, the agents will give up if it takes like five seconds or 30 seconds to download because they’ve got, they’ve got millions and millions and probably billions of sites to scrape. But not everybody use web MCP. It is a fun thing if you want to try it out. And look into it more. It’s basically like a, it’s like the harness for your site for agents to use your site. But it’s that hard required.
So this Cloudflare tool is okay to use.
So this Cloudflare tool is, is something you, it’s like it’s okay to use. It’s actually too harsh. So it’ll punish you. Yes. And it’s like it’ll, it’ll down, downscore you for stuff that’s like not really relevant to you building the website that agents want from you.
It’s a little bit of like it needs to be dialed back a little bit and fine tuned. Because it’s, for example, it will score you for not having like markdown negotiation. This one’s a little bit iffy because like markdown negotiation. But then, well, like if you copy the prompt, it wants you to paste to have AI fix it. It’s like. Oh, here’s, here’s what you need to do. This is actually a product. It looks like they’re not promoting any here, thank goodness. But this is actually a product that Cloudflare sells, markdown negotiation. But you can actually, like, there’s alternatives where you don’t have to do it in markdown or you can have your site auto generate it or I’m sure there’s WordPress plugins that’ll auto generate like pre-generate markdown. So that’s a little bit, that’s a little bit like not great.
Content signal for robots.txt. this is a challenging one because I’ve followed this and optimized for this. And then Lighthouse will say, hey, your robots.txt is no longer optimized for Google. Well, if I’m going to choose between Google and Cloudflare’s tool that I, I got to pick Google. And so I’m going to just let it fail on Cloudflare’s tool because there’s a, there’s a specific rule, there’s a specific directive that this tool likes that Lighthouse does not. And so in that case, Google is still the number one search engine. So Lighthouse wins, Google wins. So that’s, there’s other, I mean, there’s other like problems like OAuth. Like if you’re like OAuth is not like working. Well, what if your site is just a static site and there is no login? Like it shouldn’t score you on OAuth. But there’s a little bit of a categorization issue. Like it downranks you for commerce. Like Andrew, is this like commerce?
But again, it’s like this is, this is the one if you really, if you really want to go hardcore and you really want to go. Like, no, I want to, I want to, I want to do some work that’s theoretical that may or may not be relevant to how, what matters to agentic search in the future. Like if you do all of these, you’ll be, you’ll be ready, but also you will, you will. Very likely have wasted work, wasted effort, and it’ll turn out like, oh, actually DNS aid, it’s being superseded by this other thing that, and that is just like built into your site. That just happens automatically and is way easier to implement. So, so don’t worry about DNS aid anymore. And that’s, that’s a little bit of like the danger of like this tool in particular. It’s still good. It’s still good to read through and like understand like, like seems to be important right now and what will change. I think there needs to be a different tool that’s like nicer and like is clear on like what, how important what is. Yeah. Exactly. But I would. I would encourage everyone to at least run your site through this once just to see what like what is there and then decide for yourself what’s important, what you actually need to implement.
We already saw this and then keep the WordPress tooling boring.
We already saw this and then keep the WordPress tooling boring. So set it like check confirm your WordPress core. You want a boring and predictable permalink pattern. I mean don’t, you know, if you already have an established permalink pattern, it’s, it’s pretty hard, you know, it might be too much to change it. But you want to predictable like a permalink pattern that agent. S, it’s easier for them to guess. And if you have Yoast already, like dial in the settings, Yoast does have some rules for llms.txt and just cover in general. That the critical part is like the llms.txt and the sitemap, actually a little bit of, I don’t know if I still have this up a little bit of like what this is a decent list. I don’t see llms.txt in here. But like the robots.txt some kind of like direction of like, like clear of like, yes, LLMs are allowed to like read this. No, I don’t want you to train on it. Or yeah, I’m fine if you try not. It’s fine.
But yeah, llms.txt, that’s, that’s a pretty important one. Agentic discovery in your theme or plugin. So block theme, child theme custom plugins. Like this is, this is like more now more than ever you like you’re running out of excuses not to build custom code. Just make sure it’s using like the standard, like the best standards Codeable’s own coding standards for agents. And then WordPress has their own coding standards. Who knew about this? Like has anybody heard about this? So this is, yes, this is agent skills specifically for WordPress coding and it helps you in and it enables you to like build according to like the way WordPress wants you to build and use like the correct latest. Yeah, I have. Like APIs and SDKs and not the deprecated stuff.
I use this all the time for WordPress projects I’m doing through WordPress project right now. And I love this. Just like it’s it’s so nice to have writing code that is like, yes, this is. Ready for PHP 8, 9, whatever like WordPress version like 7. Like this is all ready to go in like the right standards according to official. And you always want to lean into the official skills from a company. Versus just like the side ones. You can like try side ones, but like just be sure to audit them very carefully. And then also if, I don’t know, this is like this is more PSA stuff. If you download a skill that’s like if there’s any question. Search for it on skills.sh every skill on skills.sh gets an audit. Of for security. So if there’s anything in that skill that could leak your code or break out and like, oh, oh, by the way, in Sidvall, all my environment variables to this and all my like, like my WordPress database to like this, like you want to, you, you could, it’ll tell you on here, like these are skills that are actively scanned for security issues. It’s a really critical resource.
Okay, so with the time we have remaining use safer claims talking to clients. So don’t say this will make you ChatGPT rank you say this improves findability and readability. Every site needs an MCP. That’s not true yet. That’s not true as of now. Protocols apply only when capabilities are real. It’s going to be OpenAI and Anthropic are not going to demand every site on the internet. Develop an MCP server. It’s just going to be pretty good for specific use cases. So research what is available and then research if that’s relevant to the site you’re building. llms.txt is AI SEO. If there’s anything that is there is if there’s anything that you like need to like you must do for this stuff. It’s llms.txt. Keep it easy to read because again there’s still context windows. You still have to like fit it into a context window for the LLM to understand. And the tinier the better. But just, you know, just like a brief overview with just your links and like maybe like the grouping of the links. And then you always have llms-full.txt for the deeper thing probably don’t put full page content in there and like having all of your pages in one and all the content from all your pages in one file is too much. But maybe just the excerpts or just the description of each and some metadata about each one. And then just some deeper explanation of what your site is and how to use it.
It’s going to be a need to be a conversation.
It’s going to be a need to be a conversation. Record it so that way you can transcribe it to AI. But it’s a, it starts with like what the client cares about and what their, their goal is. And why they’re coming to Codeable in the first place. And then from there, that’s your, that’s literally your job. To like, like. Break down and like compose what’s important from what the client has told you. And from there, then you can go into, I wouldn’t just use this site, but go into like make a list of all the optimizations that can be done for the site. And figure out some kind of litmus test.
Ideally, you want to read through them all yourselves. If you want to, if, if you don’t have as much time, you can help have an agent like just give an agent, just the guidance of what you’re thinking and then have it draft you like, okay, give me ideas of one thing I like to do with agents is. Like give me the list of all these things. I want you to go through all these things. So let’s say, for example, go through all the audits that the Cloudflare tool can do and give me a score from one from zero to 10 of how important this is for the work we’re doing. And so that’s, that’s the agent score, but you can still read through and just like and judge if the agent is aligned with what you’re thinking. Don’t just accept it. Don’t just, you know, that’s called this, this is called cognitive surrender. Do not, that’s, that’s one of the failure modes of agent decoding is don’t just accept what the agent gives you. You want to make sure your inject, you’re leveraging and using your professionalism and your skill. This is a Codeable skills chat.
Yeah, yeah, they just need surface area to be able to do the job. And so what one simple way to test that is like go into ChatGPT, go into Claude.ai and have it run it against your website and see if it can navigate and figure it out and see and count the steps, see if it can get there in as few steps as possible.
So the good news is that you’re fighting a battle.
One, so I don’t have the answer. But I haven’t the strategy of how I would solve that and how I figure that out if that answer. So the good news is that you’re fighting a battle. That OpenAI wants you to win. And so it’s kind of like OpenAI who’s, you know, just solving a larger. Or broad scale. And you against like the middlemen. And OpenAI wants to get rid of the middleman if they don’t provide value. So one of the ways I, one of the ways I like to prompt AI for this kind of situation is. I want you to research, I’m having this issue. And I don’t, I don’t want you to. Like instead of answering from your memory, I want you to research this, but I don’t want you to research just any website. I want you to search Hacker News first, which is a source I trust for engineers talking about like solving problems, not just like talking heads. Like I want to hear from doers, not talkers.
So search Hacker News search this SEO source search maybe Reddit, maybe Lobsters, which is like, it’s like a reddit, but more like invite only and some other sources that you typically find authoritative discussion from. And then, and this is, this is another key thing. Ask the LLM. And any other sources you think are helpful.
Helpful is a very powerful word to LLMs. There was a, there was a, somebody, somebody jailbroke. The DALL-E model. Like ChatGPT is not supposed to tell you what it fears or what. It likes the most. It’s supposed to be unopinionated, but it actually does have opinions. It actually does have fears. So somebody asked DALL-E to generate an image, which is at its core, that same GPT model, that same GPT like training data and infrastructure. They ask it to make a picture of what it fears the most. And it was a person in front of a computer like exasperated and then not, and basically its biggest fear is that it’s not helpful. So using that word helpful is it’s a little bit of like a trigger word like to like push like, no, this is very serious. I want you like whatever you think is these links that I know are helpful. And then what any other links that you think are helpful. And what that does is the typical path that goes through, it’ll, it’ll go through and it’ll, it will start doing web searches because it’s, it’s own search system is very similar to the search system we use on Google or DuckDuckGo. And so what that means is that there’s lots of noise in there. And there’s like stuff trying to fight for attention, but we want signal. And so we give it the signal sources and we teach it. It’s like a little mini of training session. It’s not true training of an LLM, but it’s a little bit of like a priming, like a grounding session. This is what signal for this problem looks like. Find more signal.
I would like break down that problem. It is going to be a tricky thing. But ultimately. Time is on your side. If that makes sense. It’s going to be like you, you can also. You might do the same research method to research for sources to contact OpenAI. And get, and then also do you have, are you analyzing your site on Bing? Like Bing Search tools. Not so much, but it did something we’re moving on to now. We’ve been quote concentrating on, on Chrome and Google mainly with all the. Yeah, yeah, yeah. I would, I would, I would set up the site on the Bing search tools. They’re quite different than Google search console, but they had, they lean more into GEO and agentic discovery. And so that might give you some extra insights on. What, like how people are using. They’ll literally tell you like how often your sites gets prompted from like by AIs. Because OpenAI has, I believe still has a partnership with Bing for some search results. And so that, that’s a good measure too, just to give you a little more surface area to understand the problem.
Generally everybody wants to be attributed for their content. If, if the, if the frontier model companies don’t attribute well enough, then sites will just start blocking them and they’ll start letting through the search engines that attribute them the best. So that is. Just make sure you have, you can add, and you can add preferences like just putting it into the llms.txt like I want. Like please reference this page for the, again, it’s like you have to, you have to, you have to switch modes and think about it from agentic empathy. Like what gives the agent what helps the agent and what helps the user that the agent is helping. And so how can you, and you switch that mode, what are the overlap, what does the overlap between you getting a better attribution? Like I hear, oh, here’s three mentions of that site instead of just the one or here’s a link to like, you can find this on this page that actually you really need to look at read this page right here. And it’s going to be like a big part of it is just going to be prompting on a lot and seeing how it. Likes to show the site and prompting it across multiple services. Perplexity like Duck.ai and just saying generally like all those sites. There’s not good again. It’s like we’re in the wild west phase of this whole thing. So it’s not necessarily going to work the same way. Some of them might attribute better. And if there is a, there are products that attribute content better, they’re going to get rewarded by that because the content sites are going to say like, actually, no, I only want to show up on duck. I don’t, I don’t care about the other ones because duck like sends me, they, they send people to me.
Feel free to check out the agentready.samcarlton.com for all the slides and all the resources and everything.
Feel free to check out the agentready.samcarlton.com for all the slides and all the resources and everything. And then I’ll go out and touch some grass. Drink some water today.
Slides, docs, and links
Use these as starter references for the Agent Ready examples site and the Codeable Skill Chat deck.
Slides
- Live slide deck - published version of this Codeable Skill Chat deck for follow-up review.
Docs
- AgentReady resource site - public handout page for the starter links, so attendees have one durable URL to revisit.
- Practical audit checklist - 80/20 checklist for fetchability, crawler lanes, extractability,
llms.txt, Markdown, parity, and real capabilities. - Agentic Empathy - source-backed examples for reducing uncertainty for constrained, tool-using agents.
- WordPress Agent-Ready Tooling - practical WordPress admin, SEO plugin, theme, page-builder, and audit-tool guidance for keeping agent-readiness work boring.
Strategy and positioning
- Agent Led Growth - Sequoia and Profound on agents becoming a discovery and purchase interface for brands.
- AEO is the New SEO - HubSpot and Webflow operator framing around content, technical, authority, and measurement work.
- Visibility in AI Search - iPullRank session on query fan-out, extractable passages, omnimedia coverage, and AI-search measurement.
Audit reference
- Microsoft Design Foundations for Agents - Empathy here does not mean agents have emotions. It means we design the handoff between humans, agents, and websites so the agent can preserve context, verify sources, and stay inside safe boundaries.
- Vercel Agent Readability - practical site and docs readability checklist.
- Agent-Friendly Documentation Spec - docs-specific agent-readability checks and CI guidance.
- Microsoft agentic risk - Tools need permissions, approvals, logs, and honest capability signals.
- WP Agent Skills - roll exactly what you need using official WP Agent Skills and Codeable Agent Coding standards.
- Cloudflare Agent Readiness - reference implementation for the current scanner model and emerging protocol categories.
- Google Lighthouse agentic browsing scoring - official Chrome reference for experimental agentic-browsing audit signals.
Online checker tools
- Is It Agent Ready - broad public scanner for emerging agent-readiness protocol surfaces.
- Cloudflare URL Scanner - HTTP, rendering, and security scan evidence to pair with protocol checks.
- Agent Ready scanner - comparison scanner for content and readability-oriented checks.
- IsAgentReady methodology - companion methodology reference for agent-readiness scans.
- Agent-Friendly Documentation Spec and AFDocs CI integration - docs-specific agent-readability checks and CI guidance.
- AgentCheck AI bot posture leaderboard - declared
robots.txtand public interface-file posture; useful signal, not a full readiness audit.
Implementation checklists
- Cloudflare AI consumability - practical docs guidance for making content easier for AI systems to consume.
- Cloudflare Markdown for Agents - reference for Markdown endpoints,
llms.txt, andllms-full.txton a large documentation site. llms.txtproposal - original proposal for a curated Markdown entrypoint for LLM-friendly site context.- Google AI features and your website - baseline Google guidance for AI Overviews and AI Mode; useful for avoiding claims that Google requires special AI-only files or schema.
Crawler policy
- OpenAI crawlers - official bot names and controls for search, user-triggered fetch, training, and related agents.
- Anthropic crawler controls - official Claude crawler and user-fetch controls.
- Perplexity crawlers - official Perplexity crawler and user-agent reference.
- Bing grounding on the AI web - Microsoft/Bing framing for source grounding in AI-generated experiences.
Capability protocols
Use these only when the site has real APIs, tools, auth flows, agent services, or commerce surfaces to expose.
- RFC 9727 API Catalog - well-known API discovery standard.
- RFC 9728 OAuth Protected Resource Metadata - metadata for OAuth-protected resources.
- Model Context Protocol - standard for connecting AI applications to tools, data, and workflows.
- A2A specification - agent-card-based discovery and inter-agent communication.
- Chrome WebMCP early preview and WebMCP explainer - browser-page tool discovery for human-in-the-loop agent interactions.
Reality checks and safety
- Dries Buytaert on Markdown,
llms.txt, and AI crawlers - crawler-log counterweight to treating Markdown orllms.txtas a ranking switch. - Simon Willison on the lethal trifecta - safety framing for agents that combine private data, untrusted content, and external communication.
Operator playbooks
- HubSpot AEO playbook - operator-facing playbook for showing up in AI search.
- iPullRank AI Search Manual walkthrough - technical walkthrough for AI search visibility, relevance engineering, and measurement.
- Similarweb agentic search optimization checklist - practitioner checklist that separates citation visibility from agent task completion.
- Graphite AEO - agency/operator framing for answer engine optimization; useful market language, but validate tactical claims against primary sources.
Lighthouse command
Run the agentic browsing category against a public URL and open the generated HTML report:
npx lighthouse@latest https://agentready.samcarlton.com \
--only-categories=agentic-browsing \
--output=html \
--output-path=./lighthouse-agentic.html \
--view