Posts

Crawled, Currently Not Indexed: What It Means and What I Actually Did

Image
Of every message Search Console has given me this year, "Crawled, currently not indexed" is the only one that stings. The others are administrative. This one is a verdict, and it took me a while to be willing to read it properly. Here is the distinction that finally made it click. There are four reasons a page of mine was sitting outside Google's index. Three of them are about whether Google can get in. One of them is about whether Google, having got in and read the page, decided it was not worth including. That last one is a judgment about my work, and I had exactly one page carrying it. This post is about that page, and about the difference between a site that is hard to enter and a page that is easy to dismiss. What the label actually means "Crawled, currently not indexed" means Google fetched the page, read it, understood it, and chose not to put it in the index. Not because it could not reach it. Because it decided the page did not add enough to what i...

Google Search Console Says Redirect Error. Here Is What It Actually Means.

Image
My site had 18 URLs flagged as "Redirect error" in Search Console, and the validation sat on "Started" for weeks without moving. The cause was not a broken redirect I had created on purpose. It was Blogger's automatic mobile redirect meeting Google's smartphone crawler. A redirect that looks like a road: one arm goes where you meant, the other dead-ends in grass. What the label means "Redirect error" does not mean "this URL redirects". It means Google's last visit to that URL ended somewhere unexpected, or followed a chain it did not want to follow. The report shows the date of that visit, which matters: if you fixed the issue afterwards, the row is a historical record, not a current fault. That distinction cost me a week. I was validating a fix that had never been crawled, and the validation stayed pending because there was nothing new to read. How to reproduce it in a terminal Send a mobile user agent to the URL and look at th...

Twelve of Sixty-One: The Count I Kept Avoiding

Image
I published 61 posts before I checked how many of them Google actually showed to anyone. The answer was twelve. Not because the writing was bad, but because the site had one inbound link and no path between its own pages. The count I kept avoiding: twelve of sixty-one posts visible, and one dim corner where the light still was. This is how I found that out, and the three measurements that made the problem obvious. 1. Count what search shows, not what you published The only number that matters is the one a stranger can see. Search your own domain in Google with the site: operator and count the results, including page two: ``` site:example.com ``` Then compare it to your post count. Mine was 12 of 61. Search Console's Pages report said 7 indexed, which was even worse, and it was three weeks stale. Two different numbers, both far below 61, and neither was in my dashboard where I could trip over it. Measure it the same way every week. Same query, same browser, count the posts o...

Twenty-Seven Posts Nobody Could Reach: The Link I Never Built

Image
Twenty-seven of my posts had no inbound link from any page Google already trusts. They were live, they returned 200, they sat in the sitemap, and no crawler had a road to any of them. Twenty-seven posts, all reachable, none with a road leading to them. One door had light behind it. This is how I found that out and what I did about it. It is the cheapest fix in SEO and almost nobody runs the audit. The number I had been avoiding I counted my posts, then counted the ones that appeared when I searched my own domain. The gap was 27. Not thin content, not duplicates, not blocked by robots, just orphaned: nothing linked to them, so the crawler had no path except the sitemap. Sitemap inclusion is a hint. Links are a route. A crawler with a one-request-per-day budget and a sitemap of 60 URLs will read the sitemap, then spend its single request refreshing your homepage, because that is what it knows. The audit, run against your own HTML You do not need a paid crawler. Pull every URL you ...

I Killed WorldScope: 206 Posts, 64 Backups, and the Part Nobody Writes About

Image
WorldScope is dead. I killed it myself, on purpose, and I have been putting off writing this entry for weeks because the honest version of the story makes me look like a person who wasted a year. The morning after I deleted 206 articles: closed laptop, notebooks kept, tea gone cold. Two hundred and six articles. Eleven thousand characters each, most of them. Written in the evenings after work, on a laptop that runs hot, in a room in Carletonville where the neighbours' music comes through the wall. I built that blog to be the serious one, the news and analysis site that would finally look like a real publication instead of a diary. What it actually earned Nothing. Not one cent. Not one affiliate conversion. Not one AdSense approval, because the site was never accepted in the first place. The traffic was a slow trickle of readers who found one article about a currency move and then left, because the next article was about something else entirely. That was the flaw, and it took m...

The Second Site: Why I Put Prop Firm Math on Its Own Domain

Image
I bought a second domain this week. Not because I have spare money, and not because I have figured out how to run the first one properly. I bought it because I finally understood why vitaladge.com is stuck, and the answer was not fixable from inside that site. The second site: a second laptop on the same table, paid for with a domain that came free with hosting. The domain is propfirmmath.com. It went live on 26 October 2026, paid for with a free domain that came with my Hostinger Business plan, which expires in October next year unless I renew it. That is how thin the margins are here. If it fails, it costs me the annual renewal and my evenings. The problem the first site taught me vitaladge.com is an affiliate store. Three hundred product pages, most of them health and supplement content, written by me from product descriptions and research. It has been running over a year. It has a few hundred indexed pages. It has made almost nothing, and AdSense has refused it twice for the sa...

Audit Week: When Your AI Assistant Knows Your Website Better Than You

Image
One human, two AI assistants, and a website that got audited harder than any boss ever audited me. There is a sentence I never thought I would say about my own business: this week, the people who understand my website best are not people. Over roughly forty-eight hours, my AI assistants ran an audit of vitaladge.com and this diary that went page by page, post by post, through everything I have built, and what they found would have taken me months to notice on my own. Typos that had been sitting in published posts since August. Posts that were too short to take seriously. A privacy hole on the diary that I had walked past a hundred times. My own name, missing from my own work. I want to write this entry while the feeling is still fresh, because it is a strange one. It is part pride, part bruise. The pride is that the sweep ended with the site measurably cleaner than it has ever been. The bruise is simpler: I built this thing, and I did not know it as well as the machines did. How ...