Blog · 6
Build notes and what changed this month in AI web building.
Six things that make a website readable by AI assistants
What ChatGPT, Claude and Perplexity actually fetch from a page, and the six things that decide whether they can use it: the crawler rules, HTML that carries the content, headings that answer, a summary and takeaways, a real FAQ, and structured data with an author behind it.
Do you still need a CMS when the assistant edits files?
It depends on who edits and how often. Alone, I run four sites on files in a repository and the assistant is the editor. With a team, a CMS earns its place: not every typo should have to go through an AI tool.
Can I let Claude or ChatGPT edit my website? What works today
Webflow, Framer, Shopify and Lovable say yes. Squarespace says no. Every website builder, CMS and host in the library, checked against the vendor's own pages, with what your assistant can actually change.
How to move a website off Webflow to Claude Code, GitHub and Vercel
I moved four of my own sites off Webflow this spring, the biggest at about 200 pages in five evenings. The steps, what the assistant did on its own, what it skipped, and who should stay where they are.
What goes in llms.txt, and does anything read it?
A plain-text index of your site written for AI assistants. What the format asks for, what this site puts in its own, and the measured evidence that almost nothing fetches it.
“Give it more context” means three different things
The most common piece of AI advice is right and too vague to act on. Splitting context into how you want the work done, what is true today, and what stays true is what makes it usable.