Home › For Authors › Sapphic Romance Tropes for Authors
Your sapphic romance may contain ten, fifteen or even twenty recognizable tropes. That does not mean you should market it with all of them.
For authors, tropes are more than fun labels. They help readers decide whether a book offers the kind of romantic experience they want.
Age gap. Ice queen. Enemies to lovers. Second chance. Slow burn. Workplace romance. Forced proximity. Friends to lovers. Fake dating. Bodyguard romance.
Each label creates an expectation. The challenge is deciding which ones genuinely define your book.
This guide helps you identify your primary and secondary sapphic romance tropes, separate tropes from genre, setting and tone, and build a simple positioning structure, the LRR Trope Stack, that you can use in book descriptions, retailer metadata, ARC requests, review submissions and promotion.
Key Takeaways
- Don’t market every trope that appears in your book. Choose the tropes that materially shape the central romance.
- Separate genre from trope. “Contemporary romance” describes the genre. “Age gap” describes a relationship dynamic.
- Choose two or three primary tropes first. Secondary tropes add detail without overwhelming the positioning.
- A trope is a promise to the reader. If you market a book as enemies to lovers, slow burn or dark romance, readers will expect the book to deliver that experience.
- Build a complete positioning stack. Tropes work better when combined with genre, relationship, tone, heat and other useful reader information.
Jump to: Genre vs trope | Primary vs secondary | The LRR Trope Test | The LRR Trope Stack | Where tropes go | Worksheet
What Is a Romance Trope?
A romance trope is a recognizable relationship, character or story pattern that helps readers understand the type of romantic experience a book offers. Examples include:
- Age gap
- Enemies to lovers
- Friends to lovers
- Second chance
- Fake dating
- Forced proximity
- Ice queen
- Workplace romance
- Boss/employee
- Bodyguard romance
- Marriage of convenience
- Opposites attract
- Slow burn
- Forbidden romance
Readers often actively search for books using these terms, which makes tropes useful for discovery. But a trope is not simply something that happens once in a novel.
For author positioning, a trope should be important enough that a reader choosing the book because of that trope is unlikely to feel misled.
Genre, Trope, Setting and Tone Are Not the Same Thing
One of the easiest ways to improve book positioning is to stop treating every characteristic as a trope. Consider this hypothetical description:
A spicy dark lesbian mafia age-gap enemies-to-lovers romance set in Chicago with an ice queen crime boss and a happy ending.
That sentence contains several different kinds of information:
| Element | Example |
|---|---|
| Genre | Romance |
| Subgenre | Dark romance / romantic suspense |
| Primary trope | Age gap |
| Relationship trope | Enemies to lovers |
| Character archetype | Ice queen |
| Setting / world | Organized crime / Chicago |
| Heat | Explicit |
| Tone | Dark, dangerous, intense |
| Ending | HEA |
All of this information can help position a book. But it should not all be placed into one giant list of “tropes.”
Primary vs Secondary Tropes
This is the distinction we recommend authors make first.
Primary tropes
A primary trope substantially shapes the central romantic relationship. Ask:
If I removed this trope, would the romance become a meaningfully different story?
If the answer is yes, it may be a primary trope.
Imagine a romance built around a 45-year-old executive falling for her 27-year-old employee. If their age difference repeatedly affects attraction, expectations, social dynamics and conflict, age gap is probably a primary trope. If their professional power relationship drives the story, workplace romance or boss/employee may also be primary.
Secondary tropes
A secondary trope is clearly present and relevant but does not define the entire romance.
Perhaps the older protagonist initially appears emotionally distant and intimidating. Ice queen may be an excellent secondary trope: it gives readers useful additional information without pretending that the entire story is fundamentally an ice-queen romance.
The LRR Trope Test
Before using a trope in your marketing, ask these four questions:
- Is it central? Does the trope meaningfully affect the main romantic relationship?
- Is it sustained? Does it exist through a meaningful portion of the story rather than appearing in one scene?
- Would trope readers recognize it? If someone specifically searches for this trope, would they reasonably agree that your book delivers it?
- Would removing it change the romance? If removing it would barely change the relationship or plot, it probably should not be one of your primary selling points.
A trope does not have to pass every question perfectly. But the more strongly it passes them, the more confidently you can position the book around it.
A Trope Is a Promise to the Reader
This is the principle behind the entire guide.
- When you label a book slow burn, a reader who loves slow-burn romance expects romantic development to take time.
- When you use enemies to lovers, readers expect genuine opposition or hostility, not two characters who disagree during their first conversation.
- When you use forced proximity, readers expect circumstances to repeatedly keep the protagonists together.
- When you use second chance, readers expect a meaningful previous romantic relationship or opportunity that is now being revisited.
- When you use dark romance, readers expect darkness to be part of the romantic experience rather than simply a thriller plot happening around an otherwise conventional romance.
Using a popular trope may attract a click. Delivering the trope is what protects reader trust.
Don’t Confuse a Scene With a Trope
- Your protagonists are trapped in an elevator for ten minutes. That does not automatically make the novel a forced-proximity romance.
- They argue intensely twice. That does not necessarily make them enemies to lovers.
- One protagonist is five years older. That does not automatically make age gap an important reader-facing trope.
- They take many chapters to say “I love you.” That alone does not make the romance a slow burn if the relationship itself develops quickly.
Look at the overall reader experience, not isolated plot events.
How Many Tropes Should You Use?
There is no universal number. For positioning, we suggest beginning with 2–3 primary tropes plus 1–3 secondary tropes or useful relationship characteristics. You can store more detailed tags on a website or in a database; your front-facing marketing needs more discipline.
Compare these two descriptions.
Version A: noise
Age gap • workplace romance • ice queen • slow burn • enemies to lovers • opposites attract • forced proximity • rich heroine • boss/employee • found family • angst • strong women • spicy • HEA
Version B: positioning
Primary: Age Gap + Workplace Romance
Secondary: Ice Queen
Relationship: Boss/Employee
Tone: Emotional, high tension
Heat: Explicit
Ending: HEA
The second version tells readers much more precisely what kind of book they are considering.
The LRR Trope Stack
At Lesbian Romance Reads, we recommend thinking beyond a simple list of tropes. We call our framework the LRR Trope Stack: a structured description of the reading experience, built in this order.
| Layer | The question it answers |
|---|---|
| 1. Genre | What broad kind of book is it? |
| 2. Subgenre | What more specific category describes it? |
| 3. Primary tropes | Which two or three tropes fundamentally shape the romance? |
| 4. Secondary tropes | Which additional dynamics meaningfully enrich it? |
| 5. Relationship dynamic | What is important about the relationship itself? |
| 6. Setting or world | Where, or within what environment, does the romance develop? |
| 7. Tone | How does the book feel? |
| 8. Heat level | How explicitly is sexual intimacy portrayed? |
| 9. Ending | What romantic resolution does the reader receive? |
| 10. Content information | What significant content may readers want to know about? |
Together, these layers give a much clearer picture than a long string of keywords. The order matters: the strongest information comes first.
Example: Building a Trope Stack
Consider a hypothetical sapphic romance. A successful 46-year-old executive hires a brilliant 29-year-old strategist. The executive is intimidating, emotionally guarded and accustomed to controlling every professional relationship around her. Their attraction develops slowly as the younger woman becomes one of the few people willing to challenge her.
You might position it like this:
| Positioning element | Classification |
|---|---|
| Genre | Romance |
| Subgenre | Contemporary romance |
| Primary trope | Age gap |
| Primary trope | Workplace romance |
| Secondary trope | Ice queen |
| Relationship dynamic | Boss/employee |
| Tone | Emotional, high tension |
| Heat | Explicit |
| Ending | HEA |
Notice what we did not do:
- We did not automatically call it enemies to lovers because they argue.
- We did not call it forbidden romance merely because dating a colleague creates complications.
- We did not call it slow burn until we established that the romantic development genuinely unfolds slowly enough to satisfy readers looking specifically for that experience.
Accuracy comes before quantity.
One Trope Stack, Five Uses
Once the stack is settled, the same positioning serves every place you present the book. Here is how our hypothetical example translates.
1. Retailer book description
The Trope Stack should not appear in your blurb as a mechanical list. Use it to decide what the blurb emphasizes:
Elena Ward built her company by never allowing emotion to interfere with control. At forty-six, she has little patience for anyone who challenges her decisions, until the new strategist assigned to her most important expansion refuses to be intimidated.
Twenty-nine-year-old Maya knows getting too close to her boss is a terrible career decision. Unfortunately, keeping her distance becomes harder every time the woman behind the ice begins to appear.
With careers, reputations and far more personal stakes caught between them, attraction is the one problem neither woman knows how to manage.
The words “age gap,” “workplace romance” and “ice queen” don’t need to be repeated unnaturally. The description demonstrates them. For the full method, see How to Write a Sapphic Romance Blurb.
2. ARC reader call
ARC readers wanted: an explicit contemporary sapphic romance. Age gap + workplace romance, with an ice-queen CEO, boss/employee tension and an HEA. Content notes available on request.
3. Review request
Reviewers need clarity faster than ordinary readers:
[Book Title] is an explicit contemporary sapphic romance built around an age-gap workplace relationship, with an ice-queen lead and a boss/employee dynamic. It follows…
Now the reviewer can immediately decide whether the book fits their interests and audience. For more help, see How to Get a Sapphic Romance Book Reviewed.
4. Social post or promotion
Looking for your next sapphic age-gap romance?
✓ Workplace romance
✓ Ice queen
✓ Boss/employee
✓ High tension
✓ Explicit heat
✓ HEA
Promo sites and newsletters often ask for exactly this information. Our sapphic book promotion directory lists which ones accept sapphic books.
5. LRR book submission
The LRR submission form asks for the same layers, so a finished stack maps straight onto it:
| Submission field | Answer from the stack |
|---|---|
| Genre and subgenre | Contemporary romance |
| Primary tropes (your top 2–3) | Age gap, workplace romance |
| Secondary tropes | Ice queen |
| Relationship dynamic | Boss/employee |
| Tone | Emotional, high tension |
| Heat level | High heat / explicit |
| Ending type | HEA |
Primary Tropes Lead; Secondary Tropes Support
Think of positioning as a hierarchy. Your strongest information should appear first.
Structured: Contemporary sapphic romance → Age Gap + Workplace → Ice Queen → Boss/Employee → High Tension → Explicit → HEA
Unstructured: Sapphic → spicy → emotional → age gap → women → workplace → contemporary → ice queen → romance → boss → HEA
Both contain similar information. Only one gives it structure.
Where Your Tropes Actually Go: What Authors Control
Before choosing tropes, it helps to know where trope information actually appears. Our September 2026 research found that authors control some trope signals directly, while many others are generated by readers.
| Place | Who controls it | What this means for you |
|---|---|---|
| Book description (blurb) | You | Your main tool. Let the story demonstrate the primary tropes. |
| Amazon KDP keywords (KDP guidance) | You | Up to seven keywords or short phrases. KDP suggests character types, character roles, plot themes and story tone; it prohibits misleading metadata, quality claims and other authors’ names. |
| Amazon categories (KDP guidance) | You | Up to three categories, including LGBTQ+ Romance and Lesbian Romance options. Categories describe genre, not tropes. |
| Title and subtitle (KDP rules) | You, within KDP rules | Some marketers recommend tropes in subtitles, but KDP’s title rules prohibit extra descriptive content and repeated keywords. Check the current rules before adding trope phrases. |
| Promo sites, ARC platforms, review requests | You | Most ask for genre and tropes directly. Use your stack. |
| Your website and publisher page | You or your publisher | Some sapphic publishers, such as Ylva and Bella Books, show trope tags on book pages. |
| Goodreads genres and shelves | Readers | Genre pages are built from readers’ shelves; authors cannot set them. |
| StoryGraph moods, pace and tags | Readers and StoryGraph | Authors cannot set moods or pace, but StoryGraph offers author-approved content warnings. |
| romance.io tags | Readers | Tropes, steam ratings and content tags are added by registered readers. |
The takeaway: the places you control are where accurate positioning pays off, and accurate positioning makes it more likely that reader-generated tags will match what you intended.
Common Sapphic Romance Tropes
LRR tracks many tropes and relationship dynamics used by sapphic romance readers. Some commonly encountered examples, with author-facing definitions:
- Age gap: a meaningful age difference forms part of the relationship dynamic.
- Ice queen: a protagonist initially presents as emotionally guarded, intimidating or difficult to approach.
- Enemies to lovers: opposition or hostility evolves into romance.
- Friends to lovers: an established friendship develops into a romantic relationship.
- Second chance: protagonists get another opportunity at a relationship or love they previously lost.
- Slow burn: romantic development unfolds gradually, and delayed payoff is part of the reading experience.
- Workplace romance: the relationship develops substantially within a shared professional environment.
- Boss/employee: workplace romance involving a professional power difference.
- Forced proximity: circumstances repeatedly require the protagonists to remain physically or situationally close.
- Fake dating: protagonists pretend to be romantically involved and the artificial relationship becomes real.
- Bodyguard romance: protection and proximity between a bodyguard and the protected character form a major part of the setup.
- Opposites attract: meaningful differences between the protagonists create attraction, conflict or both.
For a broader reader-facing exploration, see the LRR Sapphic Romance Trope Glossary, which includes frequency data from our reviews, and the Lesbian Romance Tropes directory.
Be Careful With Tropes That Carry Strong Expectations
Enemies to lovers
Conflict alone is not enough. Ask whether the protagonists genuinely begin on opposing sides or meaningfully dislike each other.
Slow burn
A long book is not automatically slow burn. The romantic development itself should unfold gradually.
Dark romance
A dark setting or villain does not necessarily make the central romance dark. The darkness should meaningfully affect the romantic dynamic or reading experience.
Age gap
There is no universal mathematical threshold that turns an age difference into an “age-gap romance.” Ask whether the difference is significant enough to affect the characters, relationship or reader experience.
Forbidden romance
Difficulty is not automatically prohibition. Something meaningful should make the relationship socially, professionally, culturally, legally or personally forbidden or seriously constrained.
Forced proximity
One shared room or one journey together may not be enough. Proximity should meaningfully drive romantic development.
Don’t Choose Tropes Only Because They’re Popular
A popular trope may attract more searches. That does not make it the right trope for your book. Mislabeling can attract the wrong readers: they may buy or download the book, but they are also more likely to be disappointed because they arrived expecting a different experience.
Good positioning isn’t about maximizing the number of people who see a book. It is about increasing the chance that the people who see it are the right readers for it.
Tropes and Search Keywords Are Related, but Not Identical
A trope can also be a search term. Readers search for phrases like “sapphic age gap romance,” “lesbian enemies to lovers books,” “sapphic ice queen romance” and “slow burn lesbian romance.” That makes accurate trope language useful for discoverability.
But don’t turn every description into a string of search phrases. Write for readers first. Use the terms naturally where they accurately describe the book: in descriptions, metadata, book pages and structured fields where appropriate.
Use the Same Positioning Consistently
Once you have your Trope Stack, keep the important elements consistent across:
- Your website
- Retailer description
- Book landing page
- ARC information
- Reviewer pitch
- Social promotion
- Media kit
- Goodreads information
- Promotional submissions
- LRR submission
Consistency makes the book easier to understand. It also reduces the chance that one platform calls your novel a dark romance while another markets it as a romantic comedy.
The LRR Sapphic Romance Positioning Worksheet
Before promoting your next book, fill this in:
| Field | Your answer |
|---|---|
| Book title | |
| Genre | |
| Subgenre | |
| Primary trope #1 | |
| Primary trope #2 | |
| Primary trope #3 (only if genuinely needed) | |
| Secondary tropes | |
| Relationship dynamic | |
| Setting / world | |
| Tone | |
| Heat level | |
| Ending | |
| Important content information |
Now write one sentence:
This is a __________ sapphic romance featuring __________ and __________, with __________.
If that sentence clearly describes the book, you have the foundation of your positioning. If it sounds confusing or contains eight different selling points, simplify it.
Before You Add a Trope: Final Checklist
- Is this trope actually present?
- Is it important to the central romance?
- Does it last long enough to shape the reader’s experience?
- Would readers specifically looking for this trope feel satisfied?
- Is it primary or secondary?
- Am I confusing a setting with a trope?
- Am I confusing tone with genre?
- Am I using the term because it describes my book, or because it is currently popular?
If you cannot confidently answer those questions, reconsider the label.
Submit Your Book’s Tropes to Lesbian Romance Reads
When you submit a sapphic romance to LRR, we ask for structured information about the book, including genre, primary and secondary tropes, relationship dynamic, tone, heat level, ending and other reader-facing details.
You don’t need to attach every possible trope. Give us the ones that best describe the book. That helps LRR classify it more accurately and helps readers discover books that fit what they actually want to read.
More Resources for Sapphic Romance Authors
- How to Get a Sapphic Romance Book Reviewed: how to find appropriate reviewers, prepare your request and approach them professionally.
- Where to Promote a Sapphic Romance Book: our maintained directory of free and paid promotion opportunities, review sites, ARC services, communities and discovery resources.
- Sapphic Romance Book Launch Checklist: a week-by-week plan from positioning to 90 days after release.
- How to Write a Sapphic Romance Blurb: turn your Trope Stack into a compelling book description.
Or return to the For Sapphic Romance Authors resource center.
Position the Book You Actually Wrote
Good book positioning doesn’t require inventing more tropes. It requires understanding the experience your story already offers.
Identify the genre. Choose the tropes that genuinely drive the romance. Add the relationship dynamics and reader information that matter. Then use that structure consistently when presenting the book.
The goal isn’t to make your book sound like every popular sapphic romance. The goal is to make the right reader recognize that this is the book they have been looking for.