# Bluesky topic feed keyword before generic broadcast

> Design a topic-specific feed or posting keyword before you broadcast generically, so people can find the stream that matches the job instead of only the account.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/bluesky-topic-feed-keyword-before-generic-broadcast/
- Source: [bsky.social](https://bsky.social/about/blog/7-27-2023-custom-feeds)
- GrowthDex source hub: [Bluesky Blog: Algorithmic Choice with Custom Feeds](/sources/bluesky-blog-algorithmic-choice-with-custom-feeds-bsky-social/)
- Last checked: 2026-06-09T09:09:03.000Z
- Rarity: epic
- Budget: medium
- Channels: Community-led Growth, Social, Product-led Growth
- Stages: topic feed, custom feed, keyword convention, event stream, algorithmic choice


## Why this can grow

One of Bluesky's strongest differences is that discovery does not have to center on the profile. It can center on a feed. The custom-feeds post gives several concrete examples: event feeds, science feeds keyed off an emoji, and shopping or artist-submission feeds built for a narrow purpose. That is useful growth design because it matches how demand often arrives. People do not always want to follow a founder forever. Sometimes they want the best posts about one topic, event, or use case right now. If the team creates a feed, keyword convention, or feed generator that collects that demand, the community surface can grow beyond one personality. That makes the distribution asset more durable and easier to share in starter packs, launch posts, and niche communities.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where bluesky topic feed keyword before generic broadcast can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Community-led Growth and Social channel.
3. Use the evidence from bsky.social to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Bluesky's custom-feeds post says the vast majority of feeds on the network are built by independent third-party developers and highlights examples like science feeds keyed off the test-tube emoji and event-specific feeds.

## Adjacent tactics in the same lane

- [Notion owned-domain link preview before generic embed](/growth-ideas/notion-owned-domain-link-preview-before-generic-embed/) - 2 shared channels
- [Devvit app-centric subreddit before broader promo](/growth-ideas/devvit-app-centric-subreddit-before-broader-promo/) - 2 shared channels
- [Bluesky starter pack before open-ended posting](/growth-ideas/bluesky-starter-pack-before-open-ended-posting/) - 2 shared channels
- [Bluesky shareable pack link before algorithmic hope](/growth-ideas/bluesky-shareable-pack-link-before-algorithmic-hope/) - 2 shared channels

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The social account should arrive with a map](/blog/the-social-account-should-arrive-with-a-map/) - social growth, community-led growth, brand trust

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.