Newest first · RSS
Field notes
Rule changes at AI engines and platforms, experiments measured on live sites, and release notes.
MeasurementProduct launch metrics: seven numbers to read at week 1 and week 4
Product launch metrics are the seven numbers that answer different questions at week 1 and week 4: reach, intent, activation, retention, mentions, corrections and hours. Here is the ledger, the read dates and the decision each number supports.
ImplementationProduct launch plan: six phases, one owner each, a gate before every step
A product launch plan is the one-page sequence that says who does what, which week it is due, and what must be true before the next phase starts. Here are six phases, a copyable table, and the gates that stop a launch from becoming a task list.
ImplementationEditorial calendar vs content calendar: what a product launch actually needs
An editorial calendar vs content calendar split decides two different jobs: what each piece must prove and when it ships. Here is the four-week launch table that holds both.
ImplementationProduct one pager: the eight blocks a buyer reads in two minutes
A product one pager is a single buyer-facing page that answers what it is, who it is for, and what to do next. Here are the eight blocks, a fill-in template, and the checks before you send it.
Crawling & Indexingupgrade-insecure-requests: upgrade every insecure request before it fires
upgrade-insecure-requests is a CSP directive that rewrites http:// URLs to https:// before the browser sends them. Add the header, find the insecure URLs first, and keep HSTS for the links this directive cannot touch.
ImplementationAI content workflow: five approval gates before an agent publishes
An AI content workflow needs five approval gates: input, evidence, draft, publish, and verification. Here is the handoff table for API or MCP agents, the pass condition for each gate, and what stays human.
Link click tracking after a listing goes live: which number counts
Link click tracking after a directory listing goes live answers three questions: did the link exist, did someone click it, and did that click become a customer. This chapter gives a metric table, a five-step check, and the point where the numbers stop proving anything.
ImplementationProduct launch email: the six-block template that gets read
A product launch email is six blocks and one link. Here is the copyable template, the subject-line test, and the five send checks that decide whether anyone reads it.
ImplementationPress kit checklist: eight assets a product press kit needs
A press kit checklist for product teams: eight assets to assemble, the boilerplate block that carries the facts, and the four places a press kit quietly goes stale.
ImplementationDirectory submission checklist: review the form before you send it
A directory submission checklist for the minute before you press send: 12 fields to verify, six review steps and the four cases where the honest answer is to skip the directory.
ImplementationFact check AI-generated content: a claim ledger that catches what a reread misses
To fact check AI-generated content, log every checkable claim and verify each one against a primary source before editing for voice. This five-step review and claim ledger catch invented numbers, stale features and false quotes.
ImplementationHow to collect testimonials that are specific enough to publish
How to collect testimonials in six steps: ask for one specific moment, record permission for name and logo, and place each quote beside the doubt it answers.
