<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Nabil Asofi — Journal</title><description>What&apos;s actually changing in AI and search, and what to do about it. Written to be read, structured so answer engines can cite it.</description><link>https://nasofi.com/</link><language>en-gb</language><copyright>Nabil Asofi</copyright><item><title>Agent or Workflow? A Ten-Minute Test</title><link>https://nasofi.com/blog/agent-or-workflow/</link><guid isPermaLink="true">https://nasofi.com/blog/agent-or-workflow/</guid><description>Most products sold as AI agents are fixed pipelines with a model bolted on. Run this ten-minute test before you buy or build one.</description><pubDate>Tue, 22 Sep 2026 00:00:00 GMT</pubDate><content:encoded>An agent decides which steps to take and in what order, based on the state of the world. A workflow follows a fixed sequence with a model filling in some blanks. Ask whether removing a single step changes the path taken, not just the content produced. If the sequence never changes, you have a workflow with a language model in it — fine, but sell it and buy it as that.</content:encoded><category>systems</category><category>agentic ai</category><category>workflows</category><category>automation</category><category>systems design</category></item><item><title>The four ways agent pilots die in production</title><link>https://nasofi.com/blog/how-agent-pilots-die/</link><guid isPermaLink="true">https://nasofi.com/blog/how-agent-pilots-die/</guid><description>Most agent pilots don&apos;t fail loudly. They stall on unattributed errors, missing owners, and cost overruns nobody tracked from day one.</description><pubDate>Tue, 22 Sep 2026 00:00:00 GMT</pubDate><content:encoded>Agent pilots usually die from one of four causes: the demo-to-production gap (a clean demo hides the messy inputs production actually has), unattributed failure (nobody can say which step broke), no clear owner once the builder moves on, and cost surprise (token spend nobody modelled before launch). Each is preventable with basic logging, ownership, and a cost ceiling set before go-live, not after.</content:encoded><category>systems</category><category>agentic ai</category><category>production</category><category>reliability</category><category>ai ops</category><category>cost management</category></item><item><title>What &quot;agentic&quot; actually means, and where the word does no work</title><link>https://nasofi.com/blog/what-agentic-actually-means/</link><guid isPermaLink="true">https://nasofi.com/blog/what-agentic-actually-means/</guid><description>Most products sold as agentic are deterministic pipelines with a model inside. A ten-minute test for telling the two apart, and why it changes your budget.</description><pubDate>Tue, 22 Sep 2026 00:00:00 GMT</pubDate><content:encoded>An agentic system decides its own next step at runtime; a workflow follows steps you defined in advance. Most products sold as agentic are workflows with a language model inside, which is usually the right engineering choice. The test is whether the system can choose an action you did not enumerate — and what happens when it chooses wrong.</content:encoded><category>systems</category><category>agentic ai</category><category>automation</category><category>evaluation</category></item><item><title>AI Overviews and your traffic mix: what to measure when clicks stop being the story</title><link>https://nasofi.com/blog/ai-overviews-traffic-mix/</link><guid isPermaLink="true">https://nasofi.com/blog/ai-overviews-traffic-mix/</guid><description>AI Overviews appear in roughly 45% of searches and can cut clicks to a page by more than half. Rank tracking alone cannot tell you whether that is happening to you.</description><pubDate>Wed, 16 Sep 2026 00:00:00 GMT</pubDate><content:encoded>AI Overviews appear in roughly 45% of Google searches and are associated with click reductions of up to 58% on affected queries. Impression counts fall less than clicks, so a widening gap between the two is the practical early signal. Track impressions, clicks and AI citation separately — a single ranking position no longer describes your visibility.</content:encoded><category>ai-news</category><category>ai overviews</category><category>measurement</category><category>search</category></item><item><title>The five workflows I rebuild for almost every client</title><link>https://nasofi.com/blog/five-workflows-i-rebuild-every-time/</link><guid isPermaLink="true">https://nasofi.com/blog/five-workflows-i-rebuild-every-time/</guid><description>Not the interesting automations — the boring ones. These five appear in nearly every engagement because they address the same handful of failure points.</description><pubDate>Tue, 08 Sep 2026 00:00:00 GMT</pubDate><content:encoded>The five workflows that recur across most engagements are a Search Console anomaly watchdog, an inbound lead triage router, a review-mining pipeline, a content brief engine, and a feed integrity checker. They share a shape: each one watches a system that fails silently and reports the failure before a human would have noticed it.</content:encoded><category>systems</category><category>automation</category><category>operations</category><category>workflows</category></item><item><title>Cited, not ranked: the split that broke old reporting</title><link>https://nasofi.com/blog/cited-not-ranked/</link><guid isPermaLink="true">https://nasofi.com/blog/cited-not-ranked/</guid><description>A page can rank fifth and get cited, or rank first and be skipped. Once you accept that, most visibility reporting stops making sense and something better replaces it.</description><pubDate>Wed, 26 Aug 2026 00:00:00 GMT</pubDate><content:encoded>Ranking and citation are now separate outcomes. AI answer engines select sources for extractability, authority and consensus rather than position, so a page outside the top three can be cited while the top result is skipped. Track them as two metrics, because improving one does not reliably improve the other.</content:encoded><category>ai-news</category><category>ai search</category><category>citations</category><category>strategy</category></item><item><title>Google retired FAQ rich results. What to do with your FAQ markup now.</title><link>https://nasofi.com/blog/faq-rich-results-retired/</link><guid isPermaLink="true">https://nasofi.com/blog/faq-rich-results-retired/</guid><description>FAQPage stopped producing rich results for every site on 7 May 2026. The markup is not harmful — but if it was your reason for writing FAQs, that reason is gone.</description><pubDate>Thu, 14 May 2026 00:00:00 GMT</pubDate><content:encoded>FAQPage rich results were retired for all sites on 7 May 2026, so the markup no longer produces an enhanced SERP appearance. It does not cause harm, and non-Google AI engines still parse the structure. Keep the markup if you want it, but write FAQs because your readers have the questions — not because you wanted the expanded listing.</content:encoded><category>seo</category><category>schema</category><category>structured data</category><category>faq</category></item></channel></rss>