Durable Sessions AI UX vs Claude Code SEO: Which to Use?
// TL;DR
These two skills solve completely different problems and do not compete. If you are building an AI-powered chat or agent product and your streaming architecture breaks on disconnects, multi-device use, or user interrupts, use the Christensen Durable Sessions AI UX Framework. If you want to build and rank an SEO-driven website using Claude Code without writing code, use the Catliff Claude Code SEO Growth System. Most teams need one or the other based on their current project — pick the one that matches your problem.
// HOW DO THEY COMPARE?
| Dimension | Christensen Durable Sessions AI UX Framework | Catliff Claude Code SEO Growth System |
|---|---|---|
| Best For | Engineering teams building AI chat/agent products that need resilient, multi-device, controllable streaming UX | Solopreneurs, local businesses, and marketers who want to build and rank an SEO website using Claude Code |
| Problem Solved | Fragile AI streaming that breaks on disconnect, lacks multi-surface continuity, and has no live user control | Getting a new or small website to rank on Google and generate organic traffic at scale |
| Complexity | High — requires rearchitecting your streaming infrastructure, replacing SSE with WebSockets, and introducing a pub/sub session layer | Low to moderate — follows a step-by-step no-code workflow inside Claude Code with SEMrush and Vercel |
| Time to Apply | Days to weeks depending on existing architecture; involves a full audit and rebuild cycle | Hours to days for initial site; ongoing daily cadence for content publishing |
| Prerequisites | Existing AI product with streaming architecture, engineering team, knowledge of SSE/WebSockets/pub-sub patterns | Claude Code desktop app, SEMrush account, Vercel account, writing samples for voice training |
| Output Type | Architectural redesign — a durable session layer between agents and clients with validated resilience, continuity, and control | A live, deployed, SEO-optimized website with blog posts, service pages, and Google Search Console integration |
| Technical Depth | Deep infrastructure and systems design — pub/sub, WebSockets, sequence-based resumability, multi-agent event routing | Surface-level technical — static site generation, Lighthouse audits, sitemap.xml, robots.txt, meta tags |
| Creator Background | Mike Christensen of Ably, a real-time infrastructure company (AI Engineer conference talk) | Jono Catliff, an SEO practitioner demonstrating 50,000+ monthly clicks via Claude Code automation |
| Scaling Pattern | Scales by supporting more concurrent agents, clients, and devices per session — infrastructure scaling | Scales by publishing more keyword-targeted pages at a controlled cadence — content scaling |
| Coding Required | Yes — significant backend architecture work required | No — Claude Code handles all code generation; the user prompts and reviews |
What does the Christensen Durable Sessions AI UX Framework do?
The Christensen Durable Sessions AI UX Framework is an architectural pattern for AI products that stream responses to users — chatbots, coding assistants, research agents, customer support bots, and similar. It diagnoses a root problem: most AI products use direct HTTP streaming (typically Server-Sent Events) that couples the response stream to a single client connection. When that connection drops, the stream dies. When a user switches devices, they lose context. When they hit a stop button, the system cannot distinguish that from a network disconnect.
The framework introduces a Durable Sessions layer — a persistent, shared channel between the agent layer and the client layer. Agents write events to the session; clients subscribe to it. This decoupling unlocks three foundational capabilities: Resilient Delivery (streams survive disconnects), Continuity Across Surfaces (sessions follow users across tabs and devices), and Live Control (users can steer or cancel agents mid-generation). The framework includes a 10-step workflow covering architecture audit, session layer design, transport replacement (SSE to WebSockets), multi-agent flattening, and validation testing.
This is a backend infrastructure framework. It requires engineering expertise and an existing AI product to redesign.
What does the Catliff Claude Code SEO Growth System do?
The Catliff Claude Code SEO Growth System is a complete workflow for building, optimizing, and ranking a website using Claude Code — without writing any code yourself. It targets solopreneurs, local businesses, and marketers who want to generate organic search traffic.
The system has two core tactics: Blog Posts at Scale (informational content that builds domain authority) and Service Pages via the Service Page Zipper (combining services × cities into individual landing pages targeting commercial keywords). Keyword research uses SEMrush with strict filters — Keyword Difficulty ≤ 30, volume ≥ 100, informational or commercial intent — to find winnable targets the creator calls Needle-in-a-Haystack Keywords.
Every page goes through a multi-pass process: initial draft, competitor structure analysis (Steal from the Search Engine), voice rewriting using trained personality files, an 80+ item on-page SEO checklist, and a Google Lighthouse technical audit targeting 100/100 scores. The entire pipeline is then packaged into a Claude Code Skill — a single command that automates the full process. Content is published at a controlled cadence to avoid Google spam penalties, and the site is deployed via Vercel with Google Search Console submission.
How do the Durable Sessions AI UX Framework and Claude Code SEO Growth System compare?
These two skills operate in entirely different domains and do not overlap. The Durable Sessions framework is about real-time infrastructure architecture for AI products — how agent-generated streams reach users reliably across devices and connections. The Claude Code SEO system is about content marketing and website building — how to create and rank web pages using AI-assisted workflows.
The Durable Sessions framework is clearly better if your problem is a broken or fragile AI product experience. It addresses engineering challenges like the SSE Resume-Cancel Conflict, the Orchestrator Dual-Purpose Problem, and the Single-Connection Trap. No amount of SEO will fix a chat interface that loses responses on network drops.
The Claude Code SEO system is clearly better if your problem is getting found on Google. It addresses marketing challenges like keyword selection, content quality, technical SEO, and deployment. No amount of streaming architecture will generate organic search traffic.
Complexity also differs sharply. The Durable Sessions framework requires a team with backend infrastructure skills, pub/sub expertise, and WebSocket experience. The Claude Code SEO system is explicitly designed for non-engineers and can be executed by a single person with a Claude Code subscription and a SEMrush account.
Which should you choose?
Choose the Christensen Durable Sessions AI UX Framework if you are building an AI-powered product with streaming responses and your users experience any of these problems: lost responses on disconnect, no cross-device session continuity, inability to cancel or steer an active agent, or bottlenecked multi-agent progress updates. This is an engineering-level architectural overhaul aimed at product teams.
Choose the Catliff Claude Code SEO Growth System if you want to build a website that ranks on Google and drives organic traffic — especially for a local or service-based business. This is a marketing-level content workflow aimed at business owners, freelancers, and growth marketers.
If you happen to be building an AI SaaS product, you might eventually use both: the Durable Sessions framework for your product's streaming architecture, and the Claude Code SEO system for your marketing website. But the two skills solve completely independent problems and should be evaluated separately based on which problem you are facing right now.
// FREQUENTLY ASKED QUESTIONS
Can I use the Durable Sessions framework and the Claude Code SEO system together?
Yes, but they solve different problems. The Durable Sessions framework fixes your AI product's streaming architecture. The Claude Code SEO system builds your marketing website. An AI SaaS company could use both — one for the product, one for growth — but they are independent workflows with no overlap in implementation.
Do I need to know how to code to use the Durable Sessions AI UX Framework?
Yes. The Durable Sessions framework requires significant backend engineering knowledge including WebSockets, pub/sub systems, event-driven architecture, and streaming protocols. It is designed for engineering teams building AI products, not for non-technical users. If you cannot code, this framework is not for you.
Do I need to know how to code to use the Claude Code SEO Growth System?
No. The entire system is designed to be executed without writing a single line of code. Claude Code generates all the code, builds the site, and handles technical SEO fixes. You need to operate SEMrush for keyword research and Vercel for deployment, but no programming experience is required.
Which skill will help me get more users for my AI product?
It depends on your bottleneck. If users are churning because your chat experience breaks on mobile or loses responses, the Durable Sessions framework fixes retention. If users are not finding your product at all, the Claude Code SEO system drives discovery through organic search. Diagnose whether your problem is acquisition or experience quality first.
Is the Durable Sessions framework specific to Ably's product?
The framework was presented by Mike Christensen of Ably, and Ably's pub/sub infrastructure is a natural implementation substrate. However, the architectural principles — agent-client decoupling, persistent resumable sessions, bidirectional transport — are vendor-agnostic and can be implemented with any pub/sub or WebSocket infrastructure.
Does the Claude Code SEO system work for non-local businesses?
The examples focus on local service businesses, but the core principles — Needle-in-a-Haystack Keywords, Blog Posts at Scale, keyword clusters, Steal from the Search Engine, and voice training — apply to any niche. The Service Page Zipper is specifically local, but the blog content strategy works for any informational or commercial keyword vertical.
What happens if I use SSE and just add retry logic instead of implementing Durable Sessions?
The Durable Sessions framework specifically warns against this. Building resume logic inside the agent creates per-client replay complexity that scales poorly. Worse, SSE cannot distinguish between a network disconnect and a user-initiated cancel — the Resume-Cancel Conflict. Retry logic alone does not solve multi-device continuity or live control. You need the full session layer.
How long does it take to see results from the Claude Code SEO system?
The site can be built and deployed in hours to days. However, SEO results take time — Google typically needs weeks to months to index, evaluate, and rank new content. The system uses Cadence Control to ramp publishing gradually and Google Search Console's Request Indexing feature to accelerate discovery, but organic traffic growth is inherently a medium-term outcome.