Content Strategy

This piece is a thought experiment conducted through simulated interviews. The interviewees are composed of social psychology, editorial practice, and creator research perspectives and do not represent any real person’s original words. In November 2025, I recorded the phrase: “The creator’s loss: the scarcity of positive feedback.” In April 2026, I wrote: “Understanding generates positive feedback.” Together, these two sentences shift the question. Do creators truly seek only praise? When one hundred people like a piece but none articulate the contradictions it addresses, that void persists. Conversely, a single reader who precisely identifies how a detail altered their judgment—without public dissemination—might reignite the creator’s resolve to continue. ...

This is the sixth essay in Reckoning with Reality. The previous essay separated fast feedback from slow results. This one turns to a question that technological progress makes easy to neglect: when an old bottleneck disappears, where does the new one appear? Whenever a new tool arrives, people first imagine what it will eliminate. AI makes writing faster, code cheaper, translation nearly instantaneous, and video production possible without a full team. Work that once took days can now be completed in minutes. ...

This is the fifth essay in Reckoning with Reality. The previous essay asked what kind of action can produce evidence. This one examines the speed at which evidence arrives—and how speed quietly changes our goals. A friend told me that content and retail have one enormous advantage: fast feedback. Change the opening today and the view count responds within hours. Adjust the price or the page and clicks or sales may change at once. Compared with spending months building a product in private, only to receive a faint response at launch, this rhythm does make it easier to preserve morale. ...

Last winter I ran a very ugly set of numbers. I’d spent an entire afternoon in a café, writing code and shooting footage in between — about forty minutes of material across phone and screen recording. I started editing that evening and exported at 1:30 in the morning. The finished cut was fifty-eight seconds. Forty minutes of footage. Six hours of editing. Fifty-eight seconds of output. And the numbers on it were mediocre. ...

I wasted years on this one sentence “If the product is good enough, people will come.” I believed that line for years. It fits the engineer’s worldview: code is verifiable, performance is measurable, and there’s an objective difference between good and bad. If the difference is objective, then the good thing winning is just a matter of time — the market is efficient, it just needs a while. That was my logic through my open-source years. Write the project well, keep test coverage high, take the docs seriously, and then wait. Wait for stars, wait for issues, wait for someone to mention it in a blog post somewhere. Sometimes the wait paid off. More often it didn’t. And every time it didn’t, my first reaction was the same one: the thing isn’t good enough yet, go back and keep improving it. ...

The short answer: there is no single GEO score GEO measurement becomes misleading the moment four different events are compressed into one number. An answer may show your name without linking to you. It may link to a page without supporting the nearby claim. A reader may visit through an AI product but arrive with no referrer. A well-cited page may still produce no useful outcome. So I use a four-layer framework: ...

The answer first: a clean technical audit was not the same as demand In July 2026, I put the previous four chapters’ five-layer GEO model against my own blog. The useful result was not “technical SEO is perfect.” It was narrower: The tested homepage passed every Lighthouse SEO audit, while a three-month Search Console snapshot showed 878K impressions and only 852 clicks. Once I segmented the data, most clicks came from a small technical core, while many impressions came from unrelated long-tail queries. ...

The answer first: trust is evidence, not a platform trick A technically healthy page can be crawlable, clear, and quotable and still receive no visible citation from an answer engine. That does not prove a hidden “trust gate” rejected it. The page may never have been selected, another source may have matched the prompt better, the answer may have absorbed its facts without linking it, or the platform may have behaved differently on that run. ...

The answer first: structure is a promise to the reader Good structure reduces the amount of reconstruction a reader must do. A useful technical section makes its conclusion, evidence, limits, and next action easy to find. That also gives search and answer systems cleaner material to process, but no heading pattern, paragraph length, summary block, or schema type guarantees an AI citation. That distinction matters. It is tempting to turn GEO into a writing ritual: put the answer first, keep the paragraph within a magic range, add FAQ schema, and wait for citations. Google explicitly says its AI search features use the same foundational SEO requirements as ordinary Search and require no special AI markup or content format. The safer order is: ...

The answer first: there is no universal citation algorithm AI search does not expose one shared pipeline that publishers can reverse-engineer into a recipe. Google documents retrieval-augmented generation and query fan-out for AI Overviews and AI Mode. Perplexity documents real-time web search, synthesis, and source links. OpenAI says ChatGPT search uses third-party search providers and content supplied directly by partners. None of those statements proves that the products share the same index, chunker, lexical retriever, vector store, reranker, prompt assembly, or citation policy. ...

The Short Answer Generative engine optimization (GEO) is a useful name for the work of making content eligible, useful, well-supported, and attributable when an AI-assisted search system builds an answer. It is not one ranking algorithm, and it is not a bag of markup tricks. For Google, the official position is deliberately unexciting: AI Overviews and AI Mode are rooted in the same core Search ranking and quality systems, and there are no additional technical requirements or special optimizations for inclusion. Other products have different retrieval stacks and crawler controls, so a responsible GEO practice begins by naming the system rather than speaking about “the AI” as if it were one machine. ...

In March 2024, this page was a long collection of Sora prompts. It belonged to the brief season when a research preview could become a small open-source movement before most people had touched the product. We copied examples, named camera movements, and tried to infer a grammar from a handful of remarkable clips. That guide can no longer honestly call itself a guide to “mastering Sora.” The Sora web and app experiences closed on April 26, 2026. OpenAI says its Sora API will be discontinued on September 24, 2026. A page that still teaches Sora as a growing platform would turn search traffic into misinformation. ...

Status update, July 2026: The Sora website and app shut down on April 26, 2026. The Sora API is scheduled to shut down on September 24, 2026. This is no longer a guide to getting started; it is a record of what the technology, the product, and their ending can teach us. When I first wrote about Sora in February 2024, the irresistible detail was the one-minute video. Two years later, the more useful story is about boundaries: a research result is not a product specification, a better model does not guarantee a permanent service, safeguards do not erase risk, and generated media does not arrive with a simple answer to copyright. ...