Run the notification through one sentence

“Because this changed, the subscriber can do this now on this exact page.”

A strong push notification turns that sentence into one honest promise, enough context to evaluate it, and a destination that fulfills it. It should still make sense if the operating system truncates part of the message.

Write the destination first

Open the page, account screen, article, product, or report that the notification will link to. Identify the action available there and any condition the subscriber needs to know before clicking. The message should summarize that reality, not create a more exciting version of it.

Alignment test

Read the notification, click the destination, and ask whether the first screen immediately continues the same promise. If not, change the destination or rewrite the message.

Give the title one job

Use the title for the subject or outcome: “Your November report is ready,” “Price dropped on your saved item,” or “Kickoff moved to 7:30.” Generic titles such as “Important update” force the body to do all the work. Test the finished hierarchy in the push notification designer and preview.

Use the body for decision context

The body can explain what changed, which saved item is involved, when a deadline ends, or what action is available. Remove greetings, throat-clearing, and repeated brand names when the notification interface already shows the site or app identity.

Use urgency only when it is real

“Today,” “last chance,” and countdown language require a genuine deadline visible on the destination page. False scarcity may increase a short-term click while weakening the permission relationship that makes future delivery possible.

Personalize from reliable fields

Useful personalization is often contextual rather than personal. Refer to the saved route, followed topic, watched item, account task, or selected location. Always define a fallback when a field is missing, stale, unexpectedly long, or unsafe to display.

Examples with clear reasons

Publication alert

Title: New guide to Web Push permissions
Body: Compare prompt timing, denial recovery, and iPhone requirements.
Why it works: The topic and value are visible before the click.

Account event

Title: Your export is ready
Body: Download the completed CSV from the reports page.
Why it works: It identifies the completed task and exact destination.

Saved-item change

Title: Price changed on a saved watch
Body: The listed price is now $420. Review the seller and condition.
Why it works: It states the change without inventing urgency.

Final review

  • The message describes one primary action.
  • Names, dates, prices, and availability are current.
  • The title works if the body is shortened.
  • The copy does not depend on an image or emoji.
  • The destination is HTTPS and matches the promise.
  • Tracking parameters contain no secrets or subscriber identifiers.
  • The audience follows an explainable segmentation rule and the recent-send exclusions are correct.

Design for truncation and accessibility

Operating systems control layout and may shorten text differently by device, language, settings, and notification grouping. Put the subject and changed fact early. Do not hide the meaning in an emoji, image, action button, or final clause. Use plain words that a screen reader can pronounce and avoid decorative character sequences that create noise.

Localization is more than translation. Names, dates, prices, sentence order, and safe length can change by locale. Review the composed message in each supported language and use the frequency-cap policy to keep overlapping localized campaigns from creating excess volume.

Use a message worksheet before scheduling

QuestionRequired answer
Why this subscriber?The declared preference, saved object, account event, or current behavior that makes the message relevant.
Why now?The real change or deadline that creates present value.
What next?The exact action available after the click.
When does it expire?The point after which the text or action would be stale.

Keep the medium’s ethical boundary visible

After the copy passes this workshop, compare it with the notification composer and service workflow so the selected website, destination, schedule, and delivery limits still fulfill the written promise.

MDN’s Web Push notification best practices recommends useful, time-sensitive messages and easy opt-out. Use that as a release condition: if the team cannot explain the utility and timing in one sentence, the message is not ready.