Issue No 131
I thought bots were attacking my site (it was me)
by Paul Seal
Every filter, sort option, and page of results is a real URL as far as a crawler is concerned, and they combine fast. Paul tells us about a bandwidth spike he spent weeks blaming on bots before realizing his own search feature had handed every crawler a map to an infinite crawl space, then shows us the small fix that solved it.
Issue 130 :: August 2026
Issue 129 :: July 2026
Stay Plugged in to the Community!
A curated collection of Umbraco and industry related tools, tips, tricks, and tutorials from around the web.
Building a QR-Code Walking Route App with Umbraco, Next.js and AI
Johan built a QR-code walking route app on Umbraco 18 and Next.js, with an AI coding agent doing much of the heavy lifting. He walks through the content model, how MCP configured Umbraco along the way, and the guardrails that kept the AI-generated code on the rails!
Read the blog postInitials.AutoLink
Tired of manually re-linking old articles every time a new keyword becomes relevant? Owain built Initials.AutoLink for Umbraco 17+ so now you can add a keyword once, and every past article that mentions it links itself. There's no editor work required so you can do more important things with your day!
Read the blog postCheck out the package
The First Umbraco India Festival
From a hackathon by the backwaters to a Kathakali welcome and a room-wide #H5YR, Nikhil takes us inside an emotional and touching look at the first-ever Umbraco India Festival in Kochi and how Umbraco, the sponsors, and the community made it truly a cultural event all of their own.
Read the blog postUmbraDesktop
Ever wanted a real desktop environment inside the Umbraco backoffice? Luuk built exactly that — windows you can keep open and switch between, side-by-side content editors, and nine background images to choose from, including a wonderfully retro Umbraco 4 throwback!
Check out the packageRetiring Named Pipes: A Simpler Fix for Dev Port Conflicts
Parallel Claude Code sessions in separate git worktrees each need their own port, so Matt built a named-pipes solution to track them — then realized git config --worktree did the same job for free, with automatic cleanup built right in!
Read the blog post