SEO & AI Search

Do We Still Need Our Own Blog in the Age of ChatGPT?

If AI can answer almost any question, why still write? That's exactly why. Your own site is a source, a context and an archive no algorithm controls. Compared with LinkedIn, social networks, newsletters and AI search.

Diagram: author, own site and archive, channels Google, AI search and social media, reader
Owned content is the source; channels are paths to the reader.

I'm asking this question on a blog I opened only recently, which is probably the most honest place for it. If AI can answer almost any question someone might type into a search engine, why would anyone still write their own posts? And why would anyone read them?

My answer is: that's exactly why. But not out of defiance. For quite practical reasons, which I'll try to explain without promising that a blog will make anyone visible.

What an AI answer is and isn't

An AI answer is a summary. It's assembled from sources the system finds, evaluates and combines into a text that sounds final. That's useful for many questions, and I use it every day myself.

What an AI answer isn't is a source. Somewhere there has to be a text the summary came from: documentation, experience, an opinion, an example. If nobody writes those texts anymore, systems summarise summaries, and after a few rounds not much is left. My own post is one of the sources, not a competitor to the summary.

Something follows from that which seems important to me: if I want my view to be part of the answer, it has to exist somewhere in a form that can be found, read and cited. A post on a social network isn't that, or only for a short while.

I notice one more thing. When a system summarises, the tone disappears. The answer is balanced, careful, without an edge. If my opinion is sharp, in the summary it becomes "some believe". That's not a flaw in the system; that's how summaries work. But it means that for the sharpness, the context and the reason I think something, only one place remains: the original. And that has to exist somewhere.

What my own site gives me

When I think about why I made this site at all, a few things keep recurring. I wrote about some of them in the first post; here I look at them from the angle of AI search.

It's my source. When someone, a person or a system, looks for what I think about a topic, there's a place where it's written with my name and a date. Not in a comment under someone else's post, not in a conversation that can't be found.

It's my context. Posts link to each other, projects are presented in their own place, the author is clearly identified. Whoever lands on one post can understand who wrote it and where the view comes from. That's something a single post on a network can never give.

It's my archive. A post from two years ago is still at the same address, still readable, still mine. I can correct it, add to it or mark it as outdated. On a platform I don't control, a post from two years ago practically doesn't exist.

It's also my place for corrections. When I find I was wrong, or that something has changed, I can update a post and mark what's new. On a network an old post is frozen; nobody reads the comment underneath. Here the history of my thinking stays in one place, with the right date, which seems fair to the reader and to me.

They're my views. A blog lets me say what I think without worrying whether an algorithm will show it to anyone. The reach is smaller, but it's mine.

Owned content, not borrowed

There's a term for this that I find useful: owned content. Content on a medium I own, at an address I determine, in a form nobody else dictates.

The opposite is borrowed content: a post on a platform that decides the reach, the lifespan, the format and the rules. The platform isn't bad; it's just not mine. When it changes its algorithm, my posts get lost. When it changes its rules, my content adapts to them. When it shuts down or becomes irrelevant, everything I wrote there goes with it.

My own site doesn't replace the platforms. It's the starting point from which paths lead to the reader. Google, AI search, social networks and a newsletter are channels. The source is one.

The comparison I make myself

Let me try an honest comparison of the options I choose between when I want to say something.

A LinkedIn post reaches people who know me, and occasionally someone new. It lives a few days. It can't be found a year later, can't be linked to, can't be corrected. It's good for conversation, bad for an archive.

Facebook and Instagram are even more fleeting for my topics. A photo from a trip belongs there; a reflection on a website finds no audience there that would read it.

A newsletter has an advantage nothing else has: direct contact with people who asked for it. But it has no archive that someone who doesn't know me yet could find. I don't have one at the moment, and I may start one when it makes sense.

AI search is a new channel in which I decide nothing. But I can make sure my site is understandable, clearly authored and accessible to the systems that look for sources. I wrote about that in the post on SEO: I don't promise myself inclusion, but I take care of the conditions.

My own site is the only one of these options that combines permanence, context and control. For reach it relies on the others. That seems a fair deal to me.

What a blog doesn't do

I don't want this post to sound like a promise. A blog by itself doesn't bring visibility. Most posts in the world go unread. A search engine doesn't reward the fact that something exists, and AI systems don't cite pages just because they're tidy.

What a blog does is less: it makes it possible for my view to exist at all, in a form that can be found and cited. Whether it's found depends on whether it's worth reading, whether it answers a question someone has, and whether it's written so that a person and a system can understand it. That's work the blog doesn't do for me.

What I actually do to make the site a source

If my own site is a source, it also has to be built as one. That's a few concrete things I take care of on this site, and they aren't tricks; they're basic tidiness.

Every post has a clear author with a link to the profile, a publication date and a date of last change. Addresses are stable and don't change for the sake of keywords. Claims that rely on documentation have a source. Opinion is marked as opinion. Posts link to each other when it helps the reader. The site has an RSS feed, a sitemap and a description of its content for the systems that read it. None of that guarantees the site will be used; it does make sure it isn't excluded for being a mess.

For a small business the list is similar, only shorter. A clear name, a clear description of services, clear contact details, a few pages that answer real customer questions, and tidy information that matches everywhere. That's what a system can assemble an answer from, and what a person actually needs after clicking.

What about reach

The question that remains is reach. A blog without readers is a diary. I have no magic answer here and won't invent one.

What I do is simple. I publish a post on my own site. On the networks where I am, I share the link with a few sentences, not the whole text, so that the conversation happens there and the archive stays here. I make sure the site is understandable to search engines and AI systems. And I write things I'd want to read myself, because that's the only method I know of that brings readers who come back in the long run.

If that works slowly, that's fine. My own site has time. That's one of its advantages a platform doesn't have.

Why write when you can ask

There's one personal reason left, and it may be the most important. Writing forces me to think something through to the end. When I ask AI, I get an answer. When I write, I find out what I think, and I often find I didn't know yet.

A post I publish is therefore less a result than a process. If someone reads it and finds it useful, good. If some system cites it, also good. But the writing itself has already done its work.

The answer to the question in the title

Do we still need our own blog in the age of ChatGPT? If the question is whether everyone needs one, the answer is no. If the question is whether someone who has something to say, and wants it to remain findable, linkable and theirs, needs one, the answer is yes. More than before.

AI isn't a reason to stop writing. It's a reason to write the things a summary can't replace: a concrete view, a concrete experience, a clear "no". No system will write that for me, because it has nowhere to take it from.

Photo of the author

I build web solutions and digital products. At GE-KO I work on web design, development and SEO; with Bizko I look for simpler ways through everyday business. I am interested in how technology saves people work, and in how AI is changing the web.

One step further.