Press Release Brand Name Typo — Blue Sky Capital

Overview

A typo in Blue Sky Capital's brand name was published in a press release and went undetected through multiple review stages — including client approval. The error was caught after publication and cannot be corrected retroactively.

What Happened

The press release contained a misspelling of the Blue Sky Capital brand name. The document had been reviewed and approved by the client (Jim) before going out, and at least two people on the Asymmetric side should have caught it. Melissa acknowledged the error directly to Jim and took responsibility.

"Shame on me. It won't matter in the end because what matters in a press release are the links." — Melissa

Impact Assessment

Brand: This is a brand reputation issue, not an SEO one. The client was understandably grumbling, and it contributed to an already tense relationship at a sensitive moment (Jim had just moved to month-to-month).

SEO: Minimal. Press release SEO value comes from backlinks, not the text content of the release itself. The two links back to the Blue Sky Capital website remain intact and functional. No SEO value is derived from the words on the press release page, as that content lives off-site.

"You don't get any SEO value for the words on the press release because they're actually not on your website." — Mark

Root Cause

The press release was drafted early in the project and was not re-reviewed before final distribution
The client approved the document with the error present
Multiple reviewers (client + at least two agency-side) missed it

Lessons / Process Notes

Press releases should receive a final proofread immediately before distribution, regardless of prior approval status — especially for brand names, URLs, and proper nouns
Client approval does not substitute for agency-side quality control; the agency is expected to catch brand-level errors
Consider a dedicated pre-publish checklist item: verify brand name spelling against the client's official materials

^[1] — Blue Sky Capital client overview
^[2] — Concurrent ad performance issue affecting the same client relationship