Why is blog.schema.org blocking my Claude @danbri ?

A bit of a "personal" work announcement: we're joining Your . Online! joost.blog/progress-planner-…

This week I shipped an MCP so AI agents could read my new specification .website. Also this week, one of my hosts shipped a CAPTCHA on another of my sites. To keep the agents out. Only one of us is reading the room. joost.blog/block-the-abuse/

Launching specification.website. A platform-agnostic spec of what a good website does: SEO, accessibility, security, agent-readiness, performance, privacy, i18n. Every claim cites a source. Ships with a checklist, llms.txt, MCP server, and Agent Skill. Free. Open Source.

I spent over a year on FAIR (the federated WordPress alternative). The lesson: Open Source First in procurement isn't enough without funding the commons it depends on. Why I'm signing the SUSE letter to the EU, and what's missing from it: joost.blog/open-source-first…

I built cocktail.glass/for-agents/ Because you all need a cocktail MCP server. #TGIF

I recently built a bot tracking dashboard for my blog. Then when I looked at it today, I realized that it was reporting "visitors" that my (Plausible) analytics was not showing me... Which led me to think: what is a visitor, these days? joost.blog/what-is-a-visitor…

Read. And please. Don't be stupid.

FAQ schema died twice from spam. The second time was last Wednesday. The fix is a new schema .org type: FAQSection. I filed it. joost.blog/faq-schema-cycle/

Vol. XV: the 15th version of my blog since June 2004 (following pretty quickly after the previous one). I got rid of the AI-generated post images, picked Klim's Domaine and Pitch fonts to do the work instead, and built proper plumbing for longer writing. joost.blog/vol-xv/

I tweeted "how long before we get this for custom fields too?" when Custom Post Type UI landed in Gutenberg 23.1. Here's why custom fields are the half that matters, and what they should look like when Core finally ships them. joost.blog/wordpress-custom-…

WordPress 7.0 ships with AI, without real-time collaboration. The right call, just five weeks too late. The same answer was visible on March 31, when the cycle was extended for RTC. 7.0 could have shipped on its original April 9 date with the much needed AI features.

Devin Walker (@innerwebs) has a smart post on what he'd build in WordPress today. The vertical-SaaS prescription is mostly right. My issue is with the internal consistency of how he gets there. The framing: "WordPress users are not a market. They're a distribution channel." But the companies built around him in the 2010-2018 window (Yoast, Gravity Forms, WooThemes, BackupBuddy, iThemes, and even, although maybe to a lesser degree, GiveWP itself) were all selling to WP users as buyers. Real CAC, real LTV, real exits. If WP users were never a market, what exactly were their customers? The retroactive framing flatters the past. The honest version is: WP users were a market, GiveWP was a successful play in that market, and what he'd build today is different because the conditions are different. That's a more interesting story than "we always knew it wasn't really the market." A few other places where the story doesn't quite hold together: Maps Builder Pro as a "distraction." He frames shipping a second focused plugin in 2014 as a strategic error. But that was the standard portfolio play at the time: most successful WP plugin shops shipped multiple products. Calling it a distraction in 2026 makes him sound disciplined in retrospect; at the time it was normal behavior in a market that rewarded it. The mentor's advice. His mentor said "focus on one plugin instead of six." That's a focus lesson. Devin grafts his current vertical-SaaS thesis onto that 2014 advice and presents them as the same insight. They aren't. "Pick one plugin and double down" and "abandon plugins entirely for vertical SaaS" are different lessons separated by twelve years of ecosystem change. The prescription doesn't quite match the diagnosis. He proposes vertical SaaS for mobile car detailers, pool service companies, restaurant groups, with a WP plugin as the customer-acquisition wedge. But what if those buyers mostly aren't on WordPress? What if they're on Squarespace, GoDaddy, or no website at all? If WP is your wedge, it has to wedge where your buyer actually lives. For most of the verticals he names, that isn't WP, which means the plugin part of his thesis doesn't work the way he says it does. The post I'd find more interesting: "The model that built GiveWP worked because of where WordPress was when we built it. Here's what's different now, and here's what I'd build because of those changes, not in spite of them." That version would force Devin to name what actually changed, instead of treating the past as if it was always already the present.

One of our portfolio companies asked me for help on a domain migration, and when I sent them my input, I realized I had never written about this, even though I've spoken about this a lot. So, here it is, my guide to how to do SEO domain migrations: joost.blog/seo-domain-migrat…