[Medium] Template filler in meta copy + unsubstantiated marketing claims

[novaspatial]

Severity: Medium (credibility/SEO + potential advertising-claims exposure).

Summary

Live marketing surfaces still carry unedited template copy, and the site presents third-party logos as clients plus volume stats a brand-new system cannot substantiate.

Evidence

• /blog meta description is verbatim Tailwind template filler (references "re-purpose old CSS tricks articles") — src/app/blog/page.tsx:19-20.
• /about meta description is generic template copy unrelated to audio — src/app/about/page.tsx:105-106.
• src/components/sections/Clients.tsx:28-52 renders 15 third-party marks (Apple, Netflix, Universal, Dolby, Sony, …) under "Trusted by Industry Leaders."
• /about shows "20+ Years of Experience", "1B+ Global Streams", "10,000+ Projects Completed" (src/app/about/page.tsx:128-130) on a system that has only held test data.

Failure scenario

Launch copy reads as low-effort (template filler in meta descriptions), and presenting well-known marks as "clients" without a relationship, alongside unsubstantiated volume stats, is a reputational and advertising-claims risk once the site is public and taking money.

Proposed fix

Rewrite the /blog and /about meta descriptions with real copy. Get legal/marketing review of the "Trusted by" logo wall (labelling vs. actual client relationships) and qualify or remove the unsubstantiated stats. The real, credentialed team bios in src/lib/team.ts (Juno/Emmy/McGill) can carry the credibility legitimately.

[novaspatial]

This was generated by AI while working the issue.

Decision pack — every claim, with an option per row

This issue had no comments and no brief; the body was the whole contract. Nothing has been changed on your behalf — site voice and marketing claims are yours. What follows is each decision reduced to a choice, with the evidence already gathered.

Every claim in the body was verified against the working tree. Three things the body does not mention are flagged at the end.

---

1. Meta copy — the only part with no judgement call in it

Both descriptions are still verbatim Tailwind template filler, untouched since before this was NovaSpatial. This is what Google puts in the search snippet.

/blog today: "Stay up-to-date with the latest industry news as our marketing teams finds new ways to re-purpose old CSS tricks articles." (Note "teams finds".)

/about today: "We believe that our strength lies in our collaborative approach, which puts our clients at the center of everything we do."

Three options each, all 150–160 characters so they don't truncate in the SERP, built only from facts already in the repo:

/blog

• B1 — Dolby Atmos mixing insight from the NOVA Spatial team: spatial audio technique, stem preparation, and what changes when your mix goes immersive. (152)
• B2 — Notes on Dolby Atmos and spatial audio from working mix engineers — technique, loudness, stem prep, and delivery for streaming platforms. (137)
• B3 — The NOVA Spatial journal: Dolby Atmos mixing craft, immersive audio technique, and practical guidance for artists preparing stems for a spatial mix. (154)

/about

• A1 — Meet the engineers behind NOVA Spatial — a Dolby Atmos mixing studio with Juno- and EMMY-credited engineers mixing immersive audio for artists worldwide. (155)
• A2 — NOVA Spatial is a Dolby Atmos mixing studio. Our engineers bring award-winning credits across records, film, and television to every immersive mix. (150)
• A3 — The team, the room, and the process behind NOVA Spatial's Dolby Atmos mixes — award-winning engineers turning stereo masters into immersive audio. (150)

Nothing in the test suite pins a description string (canonicals.test.ts asserts only alternates.canonical), so this is a two-line commit at zero risk. Reply with two picks — or your own text — and it lands.

---

2. The "Trusted by" logo wall — the real legal item

Clients.tsx renders 15 third-party marks in a marquee on the homepage under "Trusted by Industry Leaders for Unrivaled Audio Mixes". "Trusted by" asserts a client relationship with each. Production holds 0 projects, so no relationship was formed through this system — whatever exists predates it and lives in the engineers' credits.

They fall into four families, and the decision is per family, not per logo:

Family	Marks	Assessment	Suggested
Award bodies	Juno Awards, Emmy	Demonstrably held — team.ts names a Juno-winning engineer and an EMMY winner	Keep, under a credentials heading rather than "Trusted by"
Delivery targets / formats	Apple, Amazon Music, Tidal, YouTube Music, Google, Netflix, Dolby Atmos, Spatial Audio	These are platforms mixes are delivered to, not clients	Relabel — "Delivering to" or "Compatible with" is accurate. Flag: Dolby and Apple both publish strict mark-use rules, and Dolby Atmos logo use generally needs a licensing agreement
Labels	Universal, Warner Music Group, Sony	Highest risk. Defensible only if a named engineer holds a credit on a release from that label	Needs your credits — or the marks come out
Gear	Neumann, ATC	Monitoring and microphones, i.e. equipment used	Keep under "Studio equipment"

Candidate headings if you relabel: "Credits and platforms we deliver to" · "Our engineers' work reaches" · split into two strips, "Award-winning" and "Delivering to".

Mechanically this is a one-file edit — Clients.tsx is a flat array with a per-logo scale — so any subset and any heading is quick once you rule.

---

3. The three /about stats — one is now provably false

/about advertises "20+ Years of Experience" · "1B+ Global Streams" · "10,000+ Projects Completed".

A read-only query against production returns: 0 projects total, 0 delivered, 0 paid, 2 profiles (the two studio accounts). So "10,000+ Projects Completed" is contradicted by the live database, not merely unsupported. Its only outcomes are delete or re-scope.

The other two are rescuable, because they are true of the team and false of the company — team.ts independently supports both:

Stat	Evidence in team.ts	Options
20+ Years	"over 20 years of experience" (Southworth); "20+ years" (Fury)	Keep as-is · relabel "Combined Team Experience" · delete
1B+ Streams	"credits on over a billion streams" (Kuse)	Keep · relabel "Streams Across Team Credits" · delete
10,000+ Projects	nothing	Delete · or replace with a true one — e.g. "7 · Engineers on the team", or a formats-delivered count

StatListItem takes free-text value and label, so any wording fits with no component change.

Scope gap the issue misses: Testimonials.tsx repeats "20+ Years Experience" and "Award-Winning Quality" as chips under the heading "Over 20 Years of Mixing Excellence" — on the homepage, seen far more than /about. Fixing #54 exactly as written would leave those live and the site contradicting itself. Whatever you rule applies to both; I'll change them in lockstep. (Worth noting: despite its name, Testimonials.tsx contains no testimonials and no quotes — so there are no fabricated customer quotes anywhere on the site. That is a genuinely clean finding, and it narrows the exposure to logos and stats.)

---

4. "Proprietary / exclusive Spatial Tone Lock" — one factual question

Also not in the issue body, same class of claim. "Proprietary" or "exclusive" qualifies Spatial Tone Lock in 10+ places: HeroContent.tsx, FAQ.tsx (five), Services.tsx (three), about/page.tsx, and it is a top-level nav item. The sharpest is FAQ.tsx, which contrasts it against "amateur Atmos mixing".

This may be entirely fine — a genuinely in-house workflow can be called proprietary. The question is just: is Spatial Tone Lock a registered or filed mark, or a documented in-house process? If yes, nothing changes. If no, "proprietary" is the only word at issue and every instance is a one-word swap to "our in-house workflow".

Suggest splitting this into its own issue either way — it is a distinct claim family from logos and stats, and this issue's title covers only meta copy and volume claims.

---

5. Does #54 block launch? Currently nothing says.

A tracker-integrity gap, verified in two places: the Phase 2 exit gate lists five checkboxes and none mentions #54, and the devplan header's GO-pending list names #44/#45, #55, and #50 — again not #54. So as written, launch can be declared GO while /blog tells search engines the site re-purposes CSS-tricks articles and the homepage shows Netflix and Universal under "Trusted by".

That may well be deliberate — this is Medium, #55 is the stated hard blocker — but neither answer is recorded, so it currently reads as an oversight. Either ruling is fine; the gap is that it isn't written down. Both devplan edits are drafted, so it's a one-word reply.

---

Fastest path: answer 1 (two picks) and 5 (blocks / fast-follow) now — those unblock immediately. 2, 3, and 4 need facts only you have.

[novaspatial]

This was generated by AI while working the issue.

Correction to item 1: the /blog filler is on the page, not only in <head>

The decision pack framed the meta copy as a search-snippet problem. Re-reading the file today, that undersells it — the same sentence is also rendered on the page, in the PageIntro directly under the "The latest articles and news" heading:

src/app/blog/page.tsx:103-106

<PageIntro eyebrow="Blog" title="The latest articles and news">
  <p>
    Stay up-to-date with the latest industry news as our marketing teams
    finds new ways to re-purpose old CSS tricks articles.
  </p>
</PageIntro>

So anyone who opens /blog reads that the studio's marketing team re-purposes old CSS-tricks articles — it is not confined to a snippet Google may or may not show. It also carries a grammar error in the visible text ("our marketing teams finds").

This part needs no ruling. Unlike the logo wall and the stats, there is no version of the answer where the current text is what anyone intends, and no fact only you hold. If you pick a /blog description from the pack (B1/B2/B3 or your own), the visible paragraph gets the same treatment in the same commit — it should say what the journal actually publishes.

One correction to the pack while I'm here: /about is cleaner than the issue body implies. Its filler is confined to the meta description (src/app/about/page.tsx:105-106, the "collaborative approach" line). The visible PageIntro at :114-126 is real NovaSpatial copy — "Elite Engineers. Uncompromised Spatial Audio.", founding vision, the engineers' credits. So /blog is the only page with template text a visitor can read, which makes it the more urgent of the two.

Where that leaves the five decisions

#	Decision	Status
1	Meta copy — plus the visible /blog paragraph	Needs a pick; zero risk, two-file commit
2	"Trusted by" logo wall	Needs your credits/legal call
3	The three /about stats (+ Testimonials.tsx in lockstep)	Needs your call
4	"Proprietary" Spatial Tone Lock — filed mark or in-house process?	One factual answer
5	Does #54 block launch?	Still unrecorded anywhere

Item 1 is now the one with a visitor-visible cost, and it is the one that is a reply away.

[novaspatial]

This was generated by AI while working the issue.

Rulings (1) and (4) taken 2026-08-01 — both shipped

(1) Meta copy — B2 and A2. Shipped in db2fc36:

• /blog got B2 in both places the filler lived — the meta description and the visible PageIntro paragraph (which also ends the "teams finds" grammar error): "Notes on Dolby Atmos and spatial audio from working mix engineers — technique, loudness, stem prep, and delivery for streaming platforms."
• /about got A2 (meta only; its visible copy was already real): "NOVA Spatial is a Dolby Atmos mixing studio. Our engineers bring award-winning credits across records, film, and television to every immersive mix."

(4) Spatial Tone Lock — ruled an in-house process, not a filed mark. Shipped in ba512d2: "proprietary"/"exclusive" swapped for "in-house" (process/workflow) and "custom"/"specialized" (techniques/plugins) across HeroContent.tsx, FAQ.tsx (three answers), Services.tsx, and about/page.tsx. The name and the nav item stay. PromoPopup's "exclusive welcome discount" is untouched — it qualifies the offer, not the process, and is ordinary marketing language.

Verified: no residual proprietary|exclusive|CSS tricks|collaborative approach in src/ outside the PromoPopup line; suite 1094 green, lint clean. No test pinned any of the old strings.

Still waiting on a ruling

• (2) the "Trusted by" logo wall (per-family: award bodies / delivery targets / labels / gear)
• (3) the three /about stats — moves in lockstep with Testimonials.tsx on the homepage
• (5) whether [Medium] Template filler in meta copy + unsubstantiated marketing claims #54 blocks launch (neither answer is recorded anywhere yet)