How I write posts so answer engines can cite them
I write posts as one question, a direct answer, and the check I actually run. I do not invent a statistic to sound quotable.
Answer engines and search both quote pages that state a fact in the first lines, then show the work. I write posts that way on purpose. Here is the pattern I use on this site.
One question, one page
The title is the question a buyer or an engineer would type. The first paragraph is the answer. The rest is the check I actually run.
A post that opens with my biography does not get cited. The model has to read too far to find the claim.
Say what I do, not what the industry thinks
I am a full-stack engineer shipping GenAI products, including LinkAssist. The useful pages are the ones tied to that work: how I evaluate a bad AI feature, when an agent should stop and ask, and how a small SaaS turns into billing and queues.
Generic "what is an AI agent" posts already exist in the thousands. I do not need another one.
Make the page easy to extract
I use a short answer, then numbered checks, then a last section called what I do next. That shape is easy for a search result and for an answer engine.
I also keep the canonical URL on www.sahiltiwari.in, and I put the post in the sitemap with a lastmod. A good paragraph on the wrong host does not help.
What I will not do
I will not invent a statistic to sound quotable. A fake "90% of teams" line gets repeated, and then the page is a liability.
If I do not have the number, I write the decision rule instead.
What I do next
Each new post has to answer one question I have already had to answer for a product. If I cannot point at the product decision, I do not publish it.