I have been spending the last two weeks finishing unfinished products. One of those products is the interactive content blocks I use on blog posts and pages. It lets people answer questions on my content with the aim of helping them / answering a question they may have while also keeping them on my content for longer. You can see it in action on this article I created about Long-Form Articles and SEO - these are the free versions of these blocks and you can download the file you give to AI and copy the prompt to use them. The term to understand to improve organic traffic is a non-commodity content and that includes creating a cluster page with articles that link to it. Something that is possible and easy to do on Djangify. Non-commodity content is original material, created first-hand from your lived experience that only you and/or specific domain can share. You can use the free micro-app I set up that helps you plan your content here. So me talking about the fact that Claude totally screwed up making my software by doing something I didn't ask it to do is original content and specific only to me. I sort of mentioned this when I wrote about EEAT. This type of content can't be copied by AI because its original to you. Or the fact that 90% of my clients who emailed me or called me got in touch after reading something I had written. That is specific to me. You get the point. ☺️ If you want to succeed with organic traffic it has become a necessity. I will be monitoring how this improves "time on site" and keep a record of that. I have stopped sharing updates mainly because I think they are fairly boring for anyone other than me but I will keep updating this group. The Interactive Content Blocks is one of many products I have decided to put up for sale. I am working through everything I use in my own business, including the software, and making some of it open source and some of it for sale.

I have been experimenting with different ways to use AI, particularly beyond the familiar process of opening a chat, asking a question and copying the answer somewhere else. One project that caught my attention is Buzz, an open-source workspace designed to bring people and AI agents together. I wanted to explore whether I could use it to organise my work differently, with AI agents helping with research, writing and other tasks. Not just helping but actually doing the work. So instead of asking for an idea for a video shorts it will make the shorts for me. Or instead of asking for a title for a blog post I will wake up and it tells me the title, the research it did to know its a blog post worth adding and has written the post for me! Getting it running on Windows 11 taught me a few things about installing AI tools, connecting agents and managing background processes. ━━━━━━━━━━━━━━━━━━━━ WHAT IS BUZZ AI? Buzz is an open-source project from Block that provides a shared workspace for people and AI agents. Think of a collaborative messaging environment where you can organise conversations into channels and bring AI agents into those discussions. Rather than opening a separate AI conversation every time you need help, you can organise work around projects and give different agents specific responsibilities. For example, you might have: • A channel for content planning. • A channel for research. • A channel for software development. • Different AI agents assigned to particular tasks. The interesting possibility is having a more organised environment in which AI can contribute to your work, rather than treating every interaction as a separate conversation. ━━━━━━━━━━━━━━━━━━━━ WHY I WANTED TO TRY IT I have been using AI-assisted coding to build software, and I wanted to explore what happens when you move beyond asking AI to complete individual tasks. For example, I have content planning software. Rather than sitting down every morning and asking AI to generate content topics, I wanted to investigate whether I could develop a workflow where some of that work was prepared for me.

Google has updated its AI content guidance as of the 1st of this month and I wanted to just give you a little heads up, especially if you are like me and use AI every day. AI helps me draft blog posts, product descriptions, emails, page titles, meta descriptions and image alt text and Google has not said AI content is bad (yet) or that using it will hurt your rankings. What its updated guidance does say is that you can't publish AI output without taking responsibility for what it says. The main point is that an AI model doesn't know whether something is true. It predicts the next likely word. So it can write a paragraph that sounds completely sure of itself and is flat wrong. Because of that, Google says AI-generated content should be fact-checked and reviewed for accuracy before it goes live. That covers more than the article itself. It also covers page titles, meta descriptions, structured data and image alt text. You are the approval process If AI writes an article for my site, I read it before it goes up, which is now my reality after the painful past of having a ton of my articles on Inspirational Guidance deindexed. If it writes a product description, I check that it describes the product I'm actually selling. If it writes a meta description, I ask whether it describes what's on that page. If it writes alt text, I look at the image and check that the text describes it accurately. That check is the human layer Google is asking for. It doesn't mean rewriting every draft for three hours. It means you read it and you're the one who decides it's ready. The bigger risk is publishing too much Just because AI can write 50 articles in an hour doesn't mean you should just go ahead and publish them all! Publishing too much will also get you into trouble if you end up with loads of weak AI Slop as people like to call it! What you have that AI doesn't AI hasn't run your business. You have. You know what you tried, what worked, what flopped, what surprised you, which mistakes cost you money, what customers keep asking, and what you'd do differently.

I have created documentation that outlines the steps you have to go through to install the self-hosted version of Djangify eCommerce builder on your own hosting. It looks like a lot, but actually it really isn't when you hand the documentation files I have included over to AI and let AI do everything for you. You'll spend most of your time just watching your AI scroll through everything and you won't really have to do much. You are responsible for anything that relates to payment. So adding your stripe information and your email settings set up. That's all classed as sensitive and secure information, so no AI will handle that. You have to add it yourself but other than that AI can do absolutely everything. That includes unzipping the folder after you've downloaded it and creating a new folder for you on your computer. Checking to make sure you have everything you need on your computer and walking you through anything you need to do step by step. As you go through each step you can tick it off. So it's all there and I hope it's useful https://www.djangify.com/docs/self-hosted-ecommerce-builder-install-guide/

Today I woke up and realised something. I built Djangify using a framework Django and Django uses HTML to build the front end - things like pages, templates and blog posts can take html code and display it. All an artifact or micro-app is, is html and CSS code blended together and AI is really good at making them look amazing. My idea was to make a blog post look and read better by giving everyone the ability to add tables, lists, checklist and just different things that will break a long article up, because long articles that help people are key for SEO. I wanted a way to present information without a long wall of words broken up by bullet points and titles. So I spoke to Claude code and came up with something and you can see what it looks like here https://www.djangify.com/blog/long-form-articles-seo-and-content-blocks/ and then inside of that article is a link to a live example. It shows the instructions to install Djangify self-hosted from beginning to end. It is responsive and looks great on a mobile and so from tomorrow I will be upgrading a lot more of my articles using different content boxes. Does it make a difference to my search traffic? That's the question I will answer through this experiment.