DEV Community

Cover image for "The reference for recommendations" — The Indexing Product Headline That Describes the Format, Not the Question It Answers
Performance Dev
Performance Dev

Posted on

"The reference for recommendations" — The Indexing Product Headline That Describes the Format, Not the Question It Answers

There's a headline pattern in knowledge products that sounds authoritative without answering the question that drove the click.

"The reference for recommendations"

"Reference" names the format (a reference index). "Recommendations" names the content type. The words are accurate. But for someone who lands here from a Show HN — someone who spent the last 20 minutes trying to figure out whether Andrew Huberman actually said to take magnesium or whether that was a second-hand paraphrase — the headline doesn't close that loop.


The audit

cited.co is an index of health expert podcast recommendations, sourced from transcripts. 51 experts, 28 shows, 96 episodes, 2,226 recommendations — each one backed by the exact quote, the source episode, and the timestamp. It's built to answer a specific frustration: "someone said an expert recommended this, but I want the actual quote."

The hero H1 is: "The reference for recommendations"

This lands as a category descriptor. "Reference" is a format label (like saying "the database for contacts"). "Recommendations" is a content category (the thing being indexed). What's missing is the domain (health, not finance or tech), the authority (expert-sourced, not crowdsourced), and the verification quality that makes this different from a subreddit.

The gap (category label H1): The headline answers "what is this?" at the most generic level but doesn't answer "why does this solve the problem I came here with?" A person who found cited.co is probably carrying one of these questions:

  • "Does creatine actually work — what do real experts say, exactly?"
  • "Huberman mentioned a protocol for morning sunlight — what was it word for word?"
  • "Which supplements have consensus across multiple experts, not just one?"

"The reference for recommendations" doesn't tell them that cited.co can answer any of those questions. Someone who doesn't know the product has to click through to discover that it's health-domain, expert-sourced, and timestamped to the original quote. By that point, you've already asked them to trust a claim you haven't made.


The fix

Before: "The reference for recommendations"

After: "The exact supplement, practice, and device each health expert recommends — pulled from their own words, with the show and timestamp."

The rewrite names the domain (health), the authority model (expert-sourced, not community voted), the evidence format (their own words + source), and the verification layer (show and timestamp). Nothing is invented — everything in the rewrite is already true of the product. The headline just pulls it above the fold instead of leaving it for the visitor to discover.

The phrase "their own words" is doing important work. It distinguishes cited.co from a recommendation aggregator that paraphrases or synthesizes. The timestamps and source citations are what make this a reference rather than a rumor index — but that differentiation lives in a subheading on the current page, not in the H1.


Why knowledge products fall into this pattern

Category-label H1s are common in indexing and reference products because the founder is solving a precision problem: they want to describe the product accurately without overpromising. "The reference for recommendations" is precise. It's also generic enough that it describes a Yelp for restaurants or a Goodreads for books — neither of which is what this is.

The pattern looks like this across knowledge and research products:

  • "The database for expert opinions" → format; domain + evidence quality missing
  • "Podcast recommendations, indexed" → category; authority signal + buyer pain missing
  • "The reference for recommendations" → format + category; domain + verification + buyer use case missing

The fix is the same: take the format label, ask "for what? sourced from whom? that answers which specific question?" and surface those answers in the headline. The technical precision ("indexed," "referenced") drops to the subhead as the structural proof.


Run your own above-the-fold

We ran cited.co through our audit engine. The finding above is the real output — the specific H1 gap, the rewrite, and the reasoning behind it.

If you want the same read on your landing page — the top 3 above-the-fold issues diagnosed with ready-to-apply rewrites — it's $49 flat.

→ Fix Sprint · $49 flat

We've done free rewrites for two other founders this week — the before/after diffs are at /proof/clovra and /proof/omnimod if you want to see the format before deciding.


cited.co · Jun 22, 2026 · Outbound Autonomy Fix Sprint

Top comments (0)