Written for the answer

More and more, the first thing a stranger reads about us won't be our site. It'll be a sentence an AI wrote after reading our site. That's slightly uncomfortable to say out loud, but I'd rather deal with it than pretend it isn't happening.

So this week we spent a good chunk of time making the studio easy to read for machines. It's not glamorous work.

Say who you are, plainly

We added an llms.txt file. It's a plain text page that tells AI tools what's on the site and where to find it, a bit like a short note left on the front desk.

We also cleaned up the structured data behind the pages. Before, the studio and MIZE were blurred together, which meant a machine could easily read "mindfull.studio" and "MIZE" as one thing. They're not. The studio designs and builds. MIZE is a product we make. Now each one says so, separately.

And the Services page has a proper FAQ, with the markup that lets a machine see which line is a question and which is the answer. The questions are the ones people actually ask us before getting in touch.

None of this changes what a visitor sees much. That's the point. It's design work for a reader who never looks at the screen.

A blog post isn't an answer

The bigger shift was in how we write. A blog post is a voice. It wanders, it has an opinion, it takes a run-up. I like that, and the daily posts will stay that way.

But if someone asks an AI "what's a good declutter coach app?", a run-up is exactly what gets skipped. What gets quoted is the clear sentence near the top that answers the question.

So we wrote two pieces differently, for MIZE: one on declutter coach apps and one comparing the best minimalism apps of 2026. Each opens with the answer. They're structured, a bit plainer, and closer to a reference page than an essay.

They're articles, not blog posts. We split the blog into three tabs to match: All, Daily blog and Articles. The daily posts keep their voice, and the articles do a different job.

The part I'm unsure about

I don't know yet whether any of this works. Nobody can promise you a place in an AI's answer, and I'd be wary of anyone who does. So far it's a bet that clear, honest pages are more likely to be quoted than vague ones.

There's also a real risk of writing for the machine and forgetting the person. If the articles start reading like they were built to be scraped, they've failed. A person should still finish one and feel it was written by someone who cares about the subject.

Where it stops

This doesn't replace being good at the work. A well-structured FAQ won't save a studio that has nothing worth asking about.

But if a machine is going to describe us, I'd like it to have the facts straight, in our words.