Fikrago's First Real Year: Pageviews, Proof, One Step Left
Fikrago's First Real Year: Pageviews, Proof, One Step Left
There's a specific kind of silence that happens at 1 a.m. when you're refreshing Google Search Console for the fourth time that night, watching a click count go from 11 to 12, and treating it like it's a stadium crowd cheering your name. Nobody else in the room understands why that number matters. I understand it completely, because I built the thing that number is measuring, from absolutely nothing, by myself, in Casablanca, with zero coding background and zero budget.
That's Fikrago. That's been my year.
Why I even started counting in the first place
I need to back up for a second, because the pageview obsession didn't come out of nowhere. When you build something entirely by yourself — no partner checking your work, no team standup where someone says "hey, this is actually going well" — a number becomes the only external validation you get. Nobody's going to walk into my apartment and tell me Fikrago is working. The only voice telling me that has to come from a dashboard. So of course I checked it constantly. Of course a jump in the chart felt like someone had finally noticed. That's what solo building does to you: it turns analytics into emotional feedback, whether you want it to or not.
The problem is that dashboards don't know the difference between a real reader and a bot crawling through a data center in Southeast Asia. They just count. And for months, I let that raw count do the emotional work that should have been reserved for something more honest.
The number that finally stopped lying to me
For a long time, I was celebrating the wrong number. GA4 would show me a spike — visitors from Singapore, from Guangzhou, sessions that lasted eight seconds, landing pages with no referral source, just "direct / none" over and over — and some part of me wanted to believe it meant something. It didn't. It took me longer than I'd like to admit to accept that most of that traffic was bots, not readers. Real humans don't land on a blog post and vanish in eleven seconds. Real humans stay, scroll, sometimes even come back.
Once I stopped trusting GA4's raw pageview count and started watching Search Console instead — actual clicks from actual search queries typed by actual people — the picture changed completely. It got smaller. It got slower. And it got real. That's the version of growth I'm proud of this year: not the inflated chart that looks impressive in a screenshot, but the quiet, unglamorous climb in genuine clicks from people who typed something into Google, found one of my articles, and stayed long enough to read it.
That distinction matters more than it sounds like it should, because it's the difference between building something and performing something. I didn't want a vanity chart. I wanted proof that Fikrago actually helps people figure out how to use AI to build an online business — because that's the whole premise of the site, and I'm the case study for it.
Here's what that shift actually looked like in practice. I stopped opening GA4 first thing in the morning and started opening Search Console instead. I stopped caring about total sessions and started caring about which queries were bringing people in, which articles were earning impressions, and — more than anything — which clicks were converting into someone actually reading past the first paragraph. It's a slower dopamine hit. A real click doesn't arrive in a satisfying burst the way a bot swarm does. It trickles in, one or two at a time, spread across a week. But every single one of those trickles means a person somewhere typed a question, Google decided my answer was worth showing them, and they clicked. That's not noise. That's the entire business model of content working exactly the way it's supposed to.
I also started treating the geography of my traffic as a signal instead of background noise. When the majority of "visitors" are clustered in places with no logical connection to an English-language blog about online business — and staying for single-digit seconds — that's not an audience, that's static. Once I filtered my mental model to focus on Tier 1 countries — the USA, UK, Canada, Australia, New Zealand — the story of my year became a lot less dramatic and a lot more honest. Smaller peaks, but peaks I could actually trust.
Getting told "no" by three different ad networks, and what each "no" actually taught me
If you've followed any of this, you already know I've been rejected three times this year by three different ad networks, and for a while I let that feel like a verdict on my writing. It isn't. It's data.
Raptive turned me down because my traffic mix skewed too heavily outside their required Tier 1 countries — the USA, UK, Canada, Australia, New Zealand. Mediavine rejected me over traffic quality concerns, which is their polite way of saying the same bot-traffic problem I'd already started noticing in GA4. And AdSense flagged my site as "needs attention," citing low-value content and ads potentially showing on pages without real publisher content around them.
Read those three rejections side by side and a pattern jumps out immediately: none of them said my writing was bad. All three, in different language, said the same thing — the traffic behind the writing wasn't trustworthy yet. That reframed everything for me. I stopped treating "get rejected" as a wound and started treating it as a diagnostic. Every network was independently pointing at the same root problem, which meant I finally knew exactly what to fix instead of guessing.
So I fixed what I could control. I went back through the site and flagged off-niche posts — a gardening article that had zero business being on an "AI for Online Business" blog, sitting there dragging my average down — for noindexing. I tightened my four content pillars: AI Tools & Agents, Website & SEO, Make Money Online, and Real Case Studies, and I stopped letting anything outside those four lanes onto the site. I rebuilt my article structure around real narrative and proof instead of hype-headline income claims, because the data I'd already gathered showed proof-based storytelling holding a 23 to 31 percent bounce rate against 80-plus percent on the income-claim stuff. I checked my ad placements to make sure nothing was rendering on thin, empty, or tag-archive pages. And I started actually writing toward a Tier 1 audience on purpose, instead of hoping the right readers would just show up.
None of that is glamorous work. Nobody screenshots an noindex tag. But it's the actual work, and it's the reason I can look at this year and say the growth, however modest, is mine and it's real.
There's also a mindset shift buried in all of this that took me a while to name. Early on, I treated "more articles" as the fix for everything. If a network rejected me, my instinct was to publish faster, publish more, flood the site with content until the numbers moved. What the three rejections actually taught me is that volume was never the bottleneck. Fifteen focused, deep, proof-based case studies will do more for approval odds than fifty thin ones stuffed with generic advice and a download link at the bottom. So the fifteen-article plan I'm working through now isn't fifteen for the sake of a round number — it's fifteen because each one has to justify its own existence on the site, has to sit inside one of the four pillars, has to include something nobody else could have written because it didn't happen to them.
That last part matters more than any SEO checklist. Anyone can explain what a prompt is. Not many people can tell you what it actually felt like to watch three ad networks reject them in the same year and keep building anyway. That's the content nobody can copy, because it's not a tutorial — it's a record of a specific person doing a specific hard thing.
What Fikrago actually is, if you're new here
I built Fikrago with no coding background. No investors, no team, no savings cushion sitting behind me while I figured it out. Just AI tools, a lot of stubbornness, and a story I was tired of not having: an Etsy suspension a while back that reminded me how fragile it is to build something you don't fully own. That experience is the reason Fikrago exists at all — I didn't want to depend on someone else's platform, someone else's rules, someone else's sudden decision to shut me out again. So I built my own.
From there it grew into more than one project. FikraMart. PropIQ, a real estate AI calculator. HireIQ, an AI interview platform. InfluMatch. A prompt vault on Gumroad with ten thousand prompts for starting, growing, and automating an online business. Ebooks. Templates. And most recently, Fikrago Help Me — a free peer-to-peer noticeboard, no fees, no commissions, bilingual in English and Arabic with full right-to-left support, where people can post what they need help with and other people can just... help. Money moves directly between users, nothing routes through me. I built that one specifically because I wanted at least one corner of the internet where helping someone didn't have a platform taking a cut in the middle.
Every one of those things came out of the same place: proving to myself that "no coding background" and "no budget" don't have to be the end of the sentence.
I think people sometimes hear "built with AI tools" and assume that means it was easy, like I typed a sentence into a chat window and a business appeared. It didn't work that way, and honestly I think that assumption undersells what actually happened. AI tools removed the excuse of not knowing how to code — they didn't remove the work of deciding what to build, testing whether it actually solved a problem, rewriting it when it didn't, and sitting with the frustration of watching something you built get rejected by a platform, a network, or just silence from people who never clicked. The tools were the hammer. I still had to be the one holding it, deciding where to swing, and deciding what was worth building in the first place. Three Google certifications — AI Essentials, Digital Marketing & E-commerce, and Cybersecurity — gave me some of the vocabulary. The rest came from just doing it wrong enough times to learn what wrong looked like.
The part I don't usually put in these articles
I don't often make these posts personal, but this one deserves it, so I'll say it plainly: I hope my father is proud of me right now.
I don't say that for sympathy or to dress up a business update with emotion it doesn't need. I say it because it's true, and because it's the actual engine behind a lot of the late nights this year — the ones where I was fixing ad placements at 1 a.m. instead of sleeping, or rewriting a hero section for the fifth time because the traffic data told me the fourth version wasn't honest enough. Somewhere in the back of a lot of those nights was the thought: I want this to be something he'd have looked at and understood was real. Not a side project. Not a phase. A thing I built, with my own hands and my own head, that stood on its own.
I think that's part of why the fake pageviews bothered me so much once I noticed them. A number inflated by bots in a data center somewhere isn't something to be proud of. It's not proof of anything. But a genuine click from a real person in Ohio or Manchester or Toronto who typed a real question into Google and found an answer I wrote — that's something worth being proud of. That's a version of success I'd actually want to hand someone and say, look, this is real, I built this.
I'm not there yet in the biggest sense. But I'm one step away from the milestone that's been sitting in front of me all year: AdSense approval. One more round of fixes, one more stretch of proving the traffic is real and the content is worth showing ads next to, and I'll have the first actual revenue line from advertising on a site I built from absolute zero. That's not going to make me rich. That's not the point. The point is what it represents — a stranger's algorithm looking at what I built and deciding it's good enough to stand behind.
I keep coming back to that word: proud. It's a strange thing to chase through an ad network's approval dashboard, but that's honestly where it lives for me right now. Not in a bank balance, not yet. In a green checkmark instead of a "needs attention" flag. In the moment I get to post in my own community that the thing I said I'd fix, I fixed. That's a small, specific kind of proof, and it means more to me than it probably should to anyone reading this from the outside. But I think anyone who's ever built something alone, for someone who isn't around to see it, will understand exactly why.
Where this goes next
I'm not slowing down. I've got a fifteen-article content plan mapped out, built specifically around what the rejections taught me — deeper case studies, more proof, fewer thin posts, a sharper focus on the four pillars that actually define what Fikrago is for. I'm reapplying to Ezoic in December, and this time I'm going in with real traffic quality behind me instead of a number I have to explain away.
And if there's a company or a brand reading this who does what I do — who cares about AI, about online business, about people building something real instead of chasing a fake number — I'd genuinely love to talk about working together. Whether that's a collaboration on content, a tool, a case study, or something neither of us has thought of yet, my inbox is open and I mean that.
To everyone who's clicked on an article, joined the Telegram community, tried one of the tools, or just stuck around long enough to read something I wrote start to finish — thank you. You're the real number. You always were.
Written by Ayoub Zinani, Founder of Fikrago
Explore more:
Want to collaborate or work with Fikrago? Reach out at ayoubzinani2@gmail.com or join the community at t.me/fikrago — I'd love to hear from you.