TITLE: Why Pure Technical Articles Don’t Work in the AI Era? Reclaiming E-E-A-T and Reshaping the Moat of ‘Personal Entity’ DESCRIPTION: This led me to re-examine Google’s consistently emphasized E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), and I was surprised to realize that in my pursuit of technical depth, I had inadvertently lost the most important ‘soul’ of my articles. What should I do? BODY:

Recently, while reviewing the backend data for datafox.tw, I discovered a harsh reality: some of the hardcore technical articles I spent a lot of time writing were almost invisible to search engines and AI crawlers. In 2026, an era where AI SEO and GEO (Generative Engine Optimization) dominate attention, forgetting to center my content around E-E-A-T was a fatal strategic error.

🔍 The Root Problem: I’m Trying to Compete with the World’s Strongest Giants for the Same Keywords

I previously wrote an article discussing flash vs thinking kv cache test time compute. I thought this article, being highly technical, should have attracted decent organic traffic. The result? The data was utterly silent.

The reason is simple: this is a purely “topic-based” keyword. When users or AI search for this term, who are the competitors my newly established datafox.tw domain has to face? They are top papers on arXiv, official technical blogs from Pure Storage, and senior AI researchers on Substack who have accumulated a massive number of backlinks. In front of these highly authoritative giants, no matter how well-written my article is, it will simply be drowned out.

In contrast, for searches with my personal tags, such as datafox llm or datafox ntu, I consistently hold the top spot. This reveals a harsh truth: if an article isn’t tied to “who you are,” it’s merely a generic popular science article that can be replaced at any time.

🦊 Information is Replaceable, but a “Personal Entity” is Not

In the AI era, the cost of acquiring knowledge has approached zero. If I only write an article on “How to Automate Website Updates with GitHub Actions,” AI can easily generate dozens of perfect versions for you.

But what can AI not learn, even through brute force? It’s context and personal experience.

Take automated updates, for instance. If I write: “How did this fox named Datafox, while studying data science at NTU and interning at Google, manage his weekly reports using this automation system?” This kind of authentic, lived experience cannot be taken away by AI.

In the future AI knowledge graph, I don’t need to be the person who understands GitHub Actions best on the entire internet, but I can precisely claim the unique tag intersection of “automation + master’s in data science.”

🎤 Monday’s AI Club Lecture: A Self-Inflicted Awakening

I profoundly realized this because I happened to lead an AI club lecture this past Monday.

I spoke on stage for a full two hours, teaching everyone the importance of building a personal brand in 2026 and how to use AI Agents for marketing. But when I stepped off the stage and re-examined my own website, I realized with a wry smile: although I sounded eloquent on stage, my recently produced technical articles closely resembled impersonal AI-generated content.

I taught everyone to become “mountain-shaped talents” in this era—meaning, take skills that AI can easily boost to a 60 (like writing basic Code, generating marketing copy) as a broad foundation, and then refine two to three unique experiences that only you possess, converging into a “mountain peak” that others cannot brute-force with AI.

In my case, this mountain peak should be the chemical reaction of “AI technical prowess × financial background × public speaking and team leadership.”

But I forgot to showcase this “mountain peak” of mine on my own digital territory. I wrote a bunch of purely technical analyses that AI could also generate, trying to compete with global giants in SEO, but completely obscured the most important aspects: “who I am” and “why I encountered this problem.”

(Regarding the concept of “mountain-shaped talents” and how to build a career moat that won’t be eroded by inflation in the AI era, there’s a wealth of hard-earned insights to discuss. I’ll dedicate a separate article to a deep dive into this topic later, so please stay tuned.)

🛠️ Future Correction Strategy: Weaving “Me” into Every Technical Article

After much reflection, to reclaim the soul of my articles and the weight of E-E-A-T, I’ve decided to thoroughly Refactor my future technical writing strategy:

1. Short Term: Abandoning Topic-Based Titles, Binding Unique Tags

I will no longer use generic titles like Flash vs Thinking 模式的 KV Cache 實測. Future titles must incorporate my Entity perspective. For example:

  • “From a GenAI Intern’s Perspective: Flash vs Thinking Mode KV Cache Real-World Test”
  • “Test-Time Compute Trade-offs I Encountered in the Google Pixels Team”

This way, when someone searches for “GenAI intern KV cache,” the sole and most authoritative answer will be me.

2. Mid Term: Letting Technology Become an Extension of My Personal Brand

The end of every technical article must anchor back to my real experiences. No longer just cold conclusions; for example, I need to add:

  • “This architectural problem is precisely where students most often get stuck when I teach at the NTU AI Club…”
  • “This real-world test, in fact, was the most painful pitfall I personally encountered when deploying LLMOps at Cathay United Bank…”

This will allow AI, when building its index, to firmly bind these hardcore technologies with the entity “Kuo Yu-Chi.”

3. Long Term: Revitalizing Historical Assets on Medium

My old articles written on Medium have actually accumulated decent traffic and Domain Authority. I will start adding backlinks to datafox.tw within those articles, gradually transferring the accumulated authority to this digital sovereign territory that truly belongs to me.

In summary: No matter how good the content of a technical article is, if it lacks a soul, it will merely be an “anonymous article about a certain technology” in the eyes of AI and search engines. From today onwards, I will unreservedly weave my blood, sweat, tears, and stumbling experiences into every technical article. After all, this is the truest reflection of a fox constantly debugging its life in beta.