Marketing & Store Pages Prompts

Steam short descriptions have 30 words to convert browsers. The five-variation approach lets you A/B test and the recommendation forces a specific choice rather than paralysis.

Steam long descriptions that address the reader as "you" convert significantly better than third-person descriptions. The features-as-feelings rule prevents bullet-point feature lists that read like patch notes.

Steam tag strategy is one of the highest-leverage discoverability tools available for free. Wrong tags send mismatched players to your page, destroying conversion rate.

Steam capsule art is the most important pixel on your store page. The movie poster reference forces a clear tonal choice that designers can execute consistently.

EA announcements that acknowledge skepticism directly perform better because they preempt the negative comment that kills store page conversion.

Tag strategy is the highest-leverage discoverability lever on Steam. The traffic vs conversion distinction in tag selection is a nuance most devs miss.

Steam capsule briefs that don't account for size variations produce art that looks great at large size and illegible at small. Size-specific composition rules fix this.

EA page copy that overpromises destroys review scores. The FAQ section alone prevents the most common refund trigger: players not knowing what they were buying.

Update posts that read like patch notes lose readers. This template keeps the human developer voice that builds community loyalty.

Developer review responses are marketing. Defensive or generic responses hurt more than no response. These templates create the genuine developer voice that builds community trust.

Wishlisting campaigns need message variation by audience — a message that works for existing genre fans is alienating to cold audiences. This creates the three variants needed for paid and organic distribution.

Next Fest without a post-festival plan misses the wishlist conversion window. The demo sunset decision alone — keeping vs removing — has significant long-term conversion implications.

Featured spot pitches that lead with "our game is amazing" are rejected immediately. Leading with "here's why your audience wants this" is what gets the response.

Localized store pages that are just translations miss the cultural resonance that drives wishlists in specific markets. Japanese players' genre expectations differ from German players' — this brief captures that.

Over-tagging to maximum genre breadth attracts wrong-fit players who refund and leave negative reviews. Tag discipline — defining what the game is NOT as carefully as what it is — protects review score.

Press releases with journalist-focused opening paragraphs get better coverage because editors can lift them directly. The "sounds like a human" quote requirement prevents the PR-speak that journalists mock.

Press kit one-pagers that include targeted review terms help journalists understand what kind of coverage to write. Sending the right mental frame increases positive framing.

Streamer pitches under 150 words with a specific content reference get far more responses than long press-release style emails. The "one sentence they can paste" shows respect for their time.

Press email pitches that lead with the developer's story instead of the game's news angle get deleted. This template forces journalist-first thinking.

Media kits with marketing language are ignored because journalists can't use them. Pure factual clarity is the format journalists actually want.

Dev diaries that're just feature announcements miss the audience-building opportunity. Honest failure-then-solution posts generate significantly more organic shares.

Influencer pitches sent without audience-size calibration waste relationships. Large creators get 100+ pitches daily — the large-tier template is radically shorter for a reason.

Award submissions that describe the game generically rather than arguing specifically for the category get skipped. This forces category-specific argumentation that reviewers actually read.

Developers who prepare talking points tell stories; those who don't give feature lists. The "honest answer to the hardest question" preparation prevents the moment that becomes a negative clip.

Press databases used for aggregators require specific length variants. Having all sizes pre-written prevents the "just copy the Steam page" mistake that results in inconsistent descriptions across the web.

Press screenshots without specific moment direction produce generic "guy fighting in dark area" images. The "impression for someone who hasn't played" requirement focuses capture on marketing utility rather than technical showcase.

Post-mortems that don't name specific data or incidents become generic lessons that help no one. The "specific, with data or anecdote" requirement is what makes a post-mortem worth publishing.

Award submission strategies without honest competitiveness assessment waste submission fees and developer time. Identifying the 2 categories where the game has a genuine shot and concentrating effort there is more effective than mass submission.

Launch week content calendars prevent the panic-posting that produces inconsistent messaging. Day-by-day variety keeps the algorithm happy without burning the audience.

Reddit hates marketing posts but loves developer stories. The "one specific honest challenge" requirement produces the authenticity that transforms a post from "ad" to "interesting developer story".

Short-form video scripts that front-load the payoff retain viewers past the 3-second drop-off. The authentic developer voice consistently outperforms polished brand content for indie games.

Devlogs that start with the problem or result rather than background info retain readers long enough to build an audience. The specific question CTA drives comment engagement that the algorithm rewards.

Content calendars without platform-specific timing and content mix ratios get abandoned within a week. This structure keeps posting sustainable while covering all audience-building bases.

Launch threads written as marketing copy perform worse than developer authenticity. The "secret discovery" tweet rewards thread readers and drives shares.

Reddit promotional posts that lead with the product pitch get downvoted. The "story behind one feature" opener performs significantly better in game subreddits.

TikTok game promotion fails when it's just trailer clips with text. The five content archetypes here perform across different discovery algorithms without looking like ads.

Discord servers that grow without structure become unusable. Channel architecture designed before launch prevents the chaotic retroactive reorganization that always breaks community.

Game reveals that aren't coordinated across platforms waste the momentum spike. The 100-amplifier seeding list is the most underused tool in indie announcement strategy.

Templated community responses are obvious and damaging to trust. But unprepared responses under launch pressure are worse. This balances the two with explicit "never template" exceptions.

Pre-launch strategies without a week-by-week arc reveal too much too early (burnout) or save everything for launch week (zero momentum). This paced structure builds compound interest on community attention.

Short-form content without a "satisfying loop" anchor performs inconsistently. The mechanic that looks great on repeat is the engine of organic sharing — identifying it before production saves months of guesswork.

Announcement trailers that save gameplay for the gameplay trailer perform better because they build desire before explaining mechanics. The "wanting a second trailer" end requirement forces a deliberate tease.

Gameplay trailers need the mechanic-showcase sequence planned before filming begins — recording the wrong footage wastes production time. The UI visibility decision per scene is the detail editors always ask about.

Mobile trailers with muted-first design perform better because they're built for how people actually consume them. The 2-inch readability requirement forces legibility decisions often made too late.

Demo trailers that end with "wishlist" miss the conversion opportunity. The CTA pivot from wishlist to download is a simple change with major impact on demo uptake.

Story trailers with narration voice-over are a dying format. Character-driven emotional storytelling without spoken exposition is what drives modern trailer shares.

Update trailers that lead with the logo and title card waste the first 5 seconds — the algorithm decides relevance in the first 3. Opening with the beloved base-game moment anchors returning players immediately.

Accolades trailers with 15 quotes and tiny logos don't convert. Two quotes paired with the gameplay that earned them do. This brief forces selective quality over quantity.

Multiplayer trailers that show solo gameplay with another character added miss the point. The "genuinely different gameplay" requirement forces the trailer to sell co-op, not just co-presence.

Announcement trailers that open on studio logos and title cards lose 30% of viewers before showing the game. The first 5 seconds must earn the next 85 — briefing the hook before any other element sets the production priority correctly.