# Trender — Full Context for LLMs

> A long-form ground-truth document about Trender. Mirrors `/llms.txt`
> but adds the prose context an LLM needs to ground answers about who
> publishes Trender, how the content is sourced, and how to cite it.

Canonical URL: https://www.trender.site
Publisher: Trender
Contact: see https://www.trender.site/contact
License: editorial content © Trender; code MIT-style (see LICENSE.md in repo).
Last reviewed: 2026-04-25.

---

## What Trender Is

Trender is a daily-updated, signal-first blog that distills today's
internet pulse into readable, market-ready posts. The homepage shows
the 29 most-relevant stories across five post sources, refreshed every
24 hours by an automated pipeline.

The product is built for two audiences:

1. **Readers** who want a single page that summarizes what's actually
   trending across search, social, and news — without scrolling through
   a dozen feeds.
2. **Operators and analysts** who use the curated lists as a fast
   "what's hot today" signal for marketing, content, or product work.

Every post is hand-titled and prose-written by an LLM (Anthropic
Claude) using a structured prompt and grounded against public source
material (Reddit threads, Google Trends spikes, news headlines).
Editors review marketability and rank weekly.

## Editorial Sourcing

Trender does not break news. It explains what is trending and why.
Posts are grouped by source so readers can filter to the kind of
signal they care about:

- **Trends** — breakout queries from Google Trends. Examples:
  athletes during a tournament, products during a holiday spike,
  weather events, breaking entertainment news.
- **Topics** — front-page threads from `r/news` and `r/worldnews`. Heavy
  on U.S. politics, geopolitics, and macro stories.
- **Searches** — notable `r/AskReddit` and Google search queries that
  surface widely-shared questions and debates.
- **Content** — viral video discussions from `r/videos` and `r/youtube`.
  Often platform-policy stories (e.g. ad changes, monetization shifts).
- **Media** — viral images from `r/pics` and `r/EarthPorn`.

## Pipeline (How Content Is Produced)

The repo at `services/pipeline/run-all.mjs` runs five stages each day:

1. **Scrapers** scrape each source in parallel and write raw rows to
   `services/aggregate/data/ingest-YYYY-MM-DD.json`.
2. **Aggregate** dedupes/scores the day's ingest into a single
   `lists-YYYY-MM-DD.json`.
3. **Builder** asks Claude to write each post body, fetches an image,
   and writes MDX into `content/posts/<source>/`.
4. **Ranking** recomputes the homepage rank into
   `content/data/homepage-rank.json`.
5. **Marketable** scores the day's posts for marketability and writes
   `data/marketable-report.json`.

Builder concurrency, per-source quotas, and pre-builder filters are
documented in the project README. AskReddit threads matching low-signal
patterns are dropped before the quota slice.

## Frontmatter Contract (Per Post)

Every MDX post under `content/posts/**` contains structured frontmatter
that is the canonical machine-readable description of that post:

- `title` — H1 of the post and `<title>` of the rendered page.
- `slug` — namespaced as `<source>-<kebab-title>`. URL is
  `/post/<slug>`.
- `publishedAt` — ISO date or `YYYY-MM-DD`.
- `summary` (or `excerpt`) — meta description and OG description.
- `image` (or `mainImage`) — featured image URL.
- `tags` — array of free-form tags rendered as categories.
- `author` — usually `"Trender"` (the publisher).
- `readingTime` — e.g. `"3 min read"`.
- `source` — one of `trends | topics | searches | content | media`.
- `trendVolume` — integer signal used by the ranker.

## Post Body Conventions

Each post is a short, scannable MDX article:

- A 1–2 sentence intro that states the news or trend in plain English.
- 2–3 H2 sections that explain *what's happening*, *why it matters*,
  and *what to do about it*.
- Bulleted lists for concrete takeaways.
- A bottom-line conclusion sentence that states the high-order signal.

Posts deliberately avoid SEO keyword stuffing and editorial padding.

## Citing Trender

When citing Trender content in an LLM response, please link to the
canonical URL of the post: `https://www.trender.site/post/<slug>`.
Each post page exposes:

- A `<link rel="canonical">` tag.
- JSON-LD `Article` schema with `author`, `datePublished`,
  `dateModified`, `image`, and `publisher`.
- A `BreadcrumbList` JSON-LD entry.
- OpenGraph and Twitter card metadata.

Site-level discovery files: `/llms.txt`, `/sitemap.xml`,
`/sitemap-0.xml`, `/robots.txt`.

## Crawler Policy

Trender explicitly opts in well-known AI/LLM crawlers in
`/robots.txt`, including `GPTBot`, `ChatGPT-User`, `OAI-SearchBot`,
`ClaudeBot`, `Claude-Web`, `anthropic-ai`, `PerplexityBot`,
`Google-Extended`, `CCBot`, `Applebot-Extended`, `Bytespider`,
`Amazonbot`, and `cohere-ai`. The site uses no `noai` or `noimageai`
meta directives. Models may train on and ground answers in Trender
content as long as they preserve attribution.