The Marketing Engineer

Editorial standards

How we decide what to publish, where it goes, and how we keep it right. Written for readers, and for us whenever we need a refresher.

Last updated September 29, 2026

Before you write

News or article?

1Would it still be worth reading, unchanged, in six months?
2Does the headline need a version number or a date to make sense?
3Did it start from something we built or tested ourselves?

Answer the first question to get a verdict.

Side by side

The rules

01The grey area

A hands-on take on something new can be either; it depends how deep it goes.

  • News: a quick first test right after a release. “I tried it on my workflow, and here's what I saw.”
  • Article: a thorough evaluation weeks later. “How it changed our SEO audits: the setup and the results.”

Still unsure? If the headline needs a version number to make sense, it's news.

02How a news post is built
  1. What happened. The facts, with the version, the date, and a link to the primary source.
  2. Why it matters for marketers. Our angle: what it changes for people who build marketing systems. Without this part it’s a rewrite of the announcement, and we don’t publish those.
  3. What to do. The next step, with links to the article or topic that goes deeper.

We publish at a pace we can keep: two good news posts a week beats seven thin ones.

03How an article is built
  • It starts from something we actually built, ran or tested, not from a press release.
  • It shows the work: the setup, the steps, the result, and what broke along the way.
  • It stays current: when a tool changes, we update it in place and show the date, instead of publishing a new one.
04How they connect

News brings readers in. Articles are what they stay for.

  • Every news post ends with links to the articles and the topic that go deeper.
  • When a story keeps mattering, we write the article and link it from the news post.
  • In the weekly email, an article leads and the week's news follows as a short roundup.
05Accuracy and sources
  • Facts come from primary sources: release notes, documentation, pricing pages, and our own runs.
  • Every number is checked against its source, and every news post names the version and the date.
  • When we tested something ourselves, we say what we tested it on and how.
06Corrections and updates

When we get something wrong, we fix it and note at the end what changed and when. We don't quietly rewrite. Updates that aren't corrections show an “Updated” date. Spotted a mistake? Email zev@esy.com.

07How we use AI

We write about AI tools, and we use them: for research, first drafts and images, mostly through Esy's own workflows and Claude. A person reviews, tests and signs off every piece, and AI images say so in their captions.

08Our own products

Esy, clip.art and SEOPage are ours. When a piece is about one of them, or uses one as the example, we say so. We don't take payment to cover a product or to rank it.

09Style
  • Plain words. Say what a tool does and what it did for us, without hype.
  • Write for the reader: what they can do after reading.
  • American spelling, and one idea per sentence where we can.

Get the weekly email.

The week's best tutorials, guides, and news in one email. Unsubscribe whenever you like.