Your blog is probably invisible to AI right now, and you wouldn’t know it because you’ve never looked. Getting your blog visible to AI starts with one move, and it is not writing more posts. It is looking at what sits underneath the writing.
Most people haven’t looked because they’re either scared of AI or they think it costs money.
We’re at the beginning of what AI can do, the same way we were at the beginning of social media. The people who learned it then have the advantage now.
You don’t need to be an expert. You just need to start using it as a tool for your own business.
There’s a way to see exactly what’s happening underneath your site, and it doesn’t cost you anything. Gemini will look at your blog and tell you what it can read and what it can’t.
That’s the first move.
You have been publishing without ever looking underneath. I am opening mine up, one piece at a time, every Tuesday.
Send me the Tuesday letterI built my blog the way most people build one. Write the post, hit publish, hope Google finds it.
It worked. Traffic came in, people read, I was making sales. I never questioned what was underneath it.
Then AI answers started taking a real chunk of search traffic and I went looking at my own site the way I would look at a client’s. It took about three months to raise the hood and actually see what was happening.
How do you know if your blog is visible to AI?
You ask an AI tool to read your site and tell you what it can and cannot see. Your traffic numbers won’t tell you, your plugin dashboard won’t tell you, and nobody sends you a warning. You have to set it up for this data.
Search engines and AI engines do not read a page the same way. Google is forgiving and fills in gaps from context. AI engines use what is explicitly declared and ignore the rest.
It also matters which crawler you are talking about. The AI companies run separate bots for separate jobs, and OpenAI’s own documentation spells out that the search crawler and the training crawler are controlled independently. Blocking one does not block the other, and blocking the wrong one takes you out of answers you could have been in.
How do you use Gemini to check if your blog is visible to AI?
Go to gemini.google.com, sign in with your Google account, and start a new conversation.
Opening Gemini and saying “look at my blog” will not give you the answers you need. AI is only as good as the question you ask it.
Ask specific questions instead. Open your blog and go to your plugins ask to look and “Analyze my SEO plugin. Does it have all the core settings filled in?” Then go through each plugin one at a time. “Check my structured data setup. What fields am I missing?” “Look at my indexing settings. Is there a layer I’m not using?”
The better the question, the better the answer. You’re not asking AI to guess. You’re asking it to audit each component so you can see what’s actually broken instead of what you assume is broken.
Gemini doesn’t crawl your site on its own. You share your page with it, it looks at what’s there, then it tells you what to change. After you make each change, you come back and tell AI what you did and ask what to look for next.
Each time it gives you an instruction, you go turn that button on or fix that setting. Then you report back. It’s a conversation, not a one-time scan. You ask, you fix, you ask again.
This is not a quick fix. Depending on how deep you go and how steady you are with the changes, this could take you days or weeks.
It took me several days and several hours, going piece by piece, updating everything that needed updating. It’s worth taking the time to do it right, but I want you to know upfront that if you’ve never done this before, you’re not finishing it in an afternoon.
What did I find when I audited my own blog?
My plugins were doing less than I assumed. I thought my SEO plugin covered the technical side. It covered maybe half, and the half it skipped was the half that decides how well an AI engine can read the page and is protected.
My structured data was incomplete. Google is forgiving about that and fills in the gaps from context. AI engines are not. They use what is explicitly declared and ignore the rest.
My content was written for skimming, not for lifting. A direct answer in the first two or three sentences of a section is what gets pulled into an answer. Long warmups bury it where nothing can reach it.
My indexing was slower than it needed to be. There’s a whole layer of getting a new post noticed in hours instead of days, and I had none of it turned on.
And I had no way of knowing whether any of it was working. That was the real problem. I guessed for years. I had traffic, so I assumed everything underneath was fine.
What changed after I fixed it?
Since the first of May, about 2,700 people have come through the blog and they’re averaging two pages each.
That second part is what I actually care about. They land and they keep going instead of bouncing off.
That started after I fixed the setup, not after I changed anything about the writing.
None of this is writing advice. The writing was fine. It was everything under the writing that I had never looked at.
What makes a blog visible to AI in the first place?
Does my blog need to be on WordPress to be visible to AI?
No. The platform matters far less than what your pages declare about themselves. A blog on any platform can be read well or read poorly. What decides it is whether your structured data is complete, whether your settings allow the right crawlers through, and whether your answers sit near the top of each section.
How long does an audit like this take?
The looking part takes about an hour. The fixing part took me several days spread over three months, working piece by piece. If you have never opened these settings before, plan on weeks rather than an afternoon. There is no version of this that finishes in one sitting, and rushing it is how things get missed.
Do I have to pay for Gemini to run this audit?
No. A standard Google account gets you in at gemini.google.com at no cost. The paid tiers give you more capacity and longer conversations, but nothing in this audit requires them. Cost is the reason most people skip this, and it is not actually a reason.
Will my traffic tell me if AI can read my blog?
Not reliably. My traffic looked fine the entire time my setup was incomplete, which is exactly why I never questioned it. Search traffic and AI visibility are separate things. You can rank on Google, sell from your posts, and still be missing from the answers people get when they ask an AI the same question.
Should I block AI from my blog instead?
That is a real choice, and it is worth understanding before you make it. Each AI company runs separate crawlers for search and for training, controlled separately. Blocking training and blocking citation are two different decisions, and people who block everything often lose visibility they never meant to give up.
What do I do first if I have never looked at any of this?
Pick one page, paste it into Gemini, and ask what it can and cannot read on that page. One page, one conversation. You are not fixing anything yet. You are replacing what you assume about your blog with what is actually true, and that is the part everybody skips.
Where to start
Tonight, pick one page on your blog. Paste the link into Gemini and ask it what it can read on that page and what it can’t. Twenty minutes, one page, no fixing yet.
Over the next few weeks I’m breaking down each of these pieces so you can see what to look for and what actually matters. But first you have to raise the hood and look.
If you’ve never audited your own setup, that’s not a knock. Most people haven’t. I only did it because the search landscape changed enough that I wanted to know where I stood.
Your blog might be fine. It might also be invisible, and you wouldn’t know it yet.
If you’d rather not do this part alone, I’ll sit down with you for forty-five minutes and go through your blog with you. We look at what’s actually there, and you leave knowing what to fix first.
Book a 45-minute audit callBe unpolished, Angela
