Download, FAQ, privacy and terms pages have no meta description

Open Beginner friendly
#3,675 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@patrickballard is already working on this.

Since Nov 3, 2026.

  • #3676 by @patrickballard — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
nextjs, react, typescript

Research direction

The four affected pages build metadata through buildMarketingMetadata in apps/web/lib/og/url.ts, which always sets the description key, so an undefined value overrides the root layout's description. Start by reading that helper and one page that passes a description, such as the pricing page. Run the curl check from the issue against a local build and confirm the four pages emit description, og:description and twitter:description meta tags. Done when those tags appear on /download, /faq, /privacy and /terms.

Written by the indexing model from the issue text.

Description

Description

cap.so/download, /faq, /privacy and /terms serve no meta description, and no og:description or twitter:description either, so search results and link previews for them fall back to whatever text the crawler picks.

The root layout sets a site-wide description, but these four pages build their metadata with buildMarketingMetadata (apps/web/lib/og/url.ts) without passing one. The helper always sets the description key, so undefined overrides the layout's description instead of inheriting it. The other 23 pages that use the helper pass a description and are fine.

Reproduction
curl -s https://cap.so/download | grep -cE '<meta (name|property)="(description|og:description|twitter:description)"'

This prints 0 for /download, /faq, /privacy and /terms, and 3 for /pricing.

Expected

Each page has its own description in its page, Open Graph and Twitter metadata.

Dominant language
Rust
Stars
24.2k
Forks
2.2k
Avg merge
1d 9h
Merged PRs (30d)
731

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CapSoftware/Cap

All issues in CapSoftware/Cap

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.