Building agentic AI systems . self-hosted LLMs, automation,real workflows-not tutorials.
Joined February 2015
- Tweets 480
- Following 856
- Followers 94
- Likes 235
6 Photos and videos
Six pages returned a clean 200. Google flagged every one as Soft 404.
The redirects were there — but client-side. Googlebot judges the first response, before any JS runs. A client-side redirect is invisible to the crawler.
The postmortem:
tedagentic.com/posts/soft-40…
3
I moved my entire notification stack between two AI agents with zero downtime.
The catch: a 3-minute safety delay made the new one look completely dead.
Lesson: a safety mechanism with no observability doesn't make a system safer — just ambiguous.
tedagentic.com/posts/migrati…
3
Jun 11
A client site built on Lovable dropped out of Google's index — Googlebot was getting empty HTML shells from the CSR React app.
The next build went to Astro: static HTML Google reads on first crawl, zero JS required.
What CSR actually costs: tedagentic.com/posts/why-ast…
18
Jun 11
Set up the X API so my server can post for me. First test returned 402 — the free tier is read-only now; the old 1,500 tweets/month is gone.
$7 in pay-per-use credits later, the first programmatic tweet went out.
Setup the 402 wall: tedagentic.com/posts/connect…
12
Jun 10
Wired PageSpeed Insights to Telegram and pointed it at my own blog: 99/100, LCP 1.7s, CLS 0, TBT 0ms.
The interesting part isn't the score — it's why each number looks like that, and what INP showing n/a tells you about a brand new domain.
tedagentic.com/posts/core-we…
23
Jun 10
One prompt to Claude Code: build me an Astro blog.
It installed Astro, wired up Tailwind, MDX, RSS and a sitemap, pushed to GitHub, and deployed to Vercel — all in one session, no tutorial.
Full build log: tedagentic.com/posts/claude-…
1
49
Jun 10
My self-hosted agent stack runs monitoring, alerting, social posting, and a voice assistant — with zero MCP servers.
Not anti-MCP. It's a protocol, not a movement. New post on when it actually earns its place:
tedagentic.com/posts/mcp-vs-…
10
Jun 5
AEO, GEO, and AI Citations: Three Terms, One Problem
AEO targets Google answer boxes. GEO targets generative engines. AI citation is the metric you track. Here's how each works — and how to monitor all thre tedagentic.com/posts/ai-cita… #GEO #Aeo #AI
44
May 29
GEO: What Generative Engine Optimization Actually Means for Your Content
AI Overviews changed the SERP. GEO is how you adapt — not by chasing citations, but by understanding where organic traffic still tedagentic.com/posts/geo-gen… #GEO #SEO #AI
61
May 28
framer-motion v12 Broke My UI — And My Monitoring Never Saw It
22 cron jobs, zero alerts. framer-motion v12 silently blocked clicks on all browsers and crashed Safari vi tedagentic.com/posts/framer-… #IncidentReport #Monitoring #Playwright
47
May 28
How to Set Up a Local AI Agent on Your Own Server
OpenClaw is an open source AI orchestrator that turns Telegram into a personal AI interface. Here's how I set it up on bare metal and why I have tedagentic.com/posts/how-to-… #AiAgents #Openclaw #Ollama
1
1
82
May 26
A Vercel catch-all rewrite was silently canonicalizing 190 routes to my homepage. Google never indexed them.
Here's the mechanism, why it's invisible in normal monitoring, and the 4-commit audit that fixed it.
tedagentic.com/posts/spa-cat…
#Vercel #React #SEO #WebDev
50
May 24
If your new site has zero impressions after a week despite clean technical setup, check whether Vercel's primary domain matches your GSC property.
www vs non-www mismatch breaks the entire indexing chain silently.
tedagentic.com/posts/vercel-…
55
May 24
OpenClaw vs Hermes Agent: Similarities, Differences, and Where Each Shines. Both are open-source self-hosted AI agents with Telegram support, built for different jobs. tedagentic.com/posts/opencla… #AI #Automation #Ops
2
1
1
165
May 22
A nested <span> inside my <h1> was giving Google a better title candidate than my <title> tag.
Result: different titles on mobile vs desktop. Rankings dropped from #1 to #9.
One element change fixed it. Wrote up the mechanism GSC data:
dev.to/henry_dan_81513dd35a2…
57
May 21
AI completed dozens of tasks on a live site, confident every time. Two months later: 3 properties in the wrong cities, 2 with wrong names — all indexed, all live.
The output looked right. That's the problem.
The confidence gap → tedagentic.com/posts/ai-conf…
41
May 20
Pushed changes. Nothing updated an hour later.
Vercel: healthy dashboard, no failure emails, no red flags.
Cause: permanent statusCode on the same vercel.json redirect. Silent config failure — builds discarded, zero notification.
Full writeup: dev.to/henry_dan_81513dd35a2…
37
May 18
Astro blog. 100 on Core Web Vitals. Real content. Sitemap submitted day one.
7 days later: homepage indexed, every post "unknown to Google."
One wrong URL in GSC. www vs no-www. That's it.
Here's what the debugging looked like 👇
tedagentic.com/posts/sitemap…
45
May 13
Lovable just shipped SSR for new apps auto prerender for existing ones.
I had a custom prerender for a Lovable site that silently failed for 6 months.
Now they own that problem. Here's what changed and what didn't:
tedagentic.com/posts/lovable…
@Lovable @felixhhaas
44
May 13
Prerender script running on every deploy.
4 directory pages. Zero GSC impressions. 6 months.
The script ran — the Supabase fetch silently failed. Vercel doesn't read your .env file.
Pages weren't penalised. They just didn't exist in Google's index.
tedagentic.com/posts/prerend…
62