My approach has been methodical: bookmark authoritative archives and follow a few active constructors. 'Cruciverb' and 'Crossword Compiler' forum threads are especially rich because they include back-and-forth about why a clue failed editorial muster — sometimes a perfectly clever idea flops because it creates an unfair crossing, or because the reference is uncheckable for the average solver. 'XWordInfo' and 'Crossword Fiend' provide historical comparisons where you can often see an original clue and the later accepted version, effectively giving you a rejected example.
Beyond forums, university puzzle clubs and the 'American Crossword Puzzle Tournament' write-ups occasionally surface rejected clues in contest discussions. I like to catalogue these into categories — offensiveness, obscurity, duplication, ambiguous grammar — because it helps me when I'm crafting clues. Reading through the rejects sharpens my own instincts and keeps me humbler about the ones I think are clever.
I've spent a lot of late nights hunting down rejected clues and my go-to is community discussion. 'Puzzling Stack Exchange' and subreddits like 'r/crosswords' or 'r/crossword' frequently have threads where constructors post a grid and then readers point out which clues got axed and why. Constructors also sometimes write postmortems on their own sites explaining which clues were rejected for being too vague or for repeating synonyms elsewhere in the puzzle.
For archival material, check 'XWordInfo' for New York Times clue histories — it often shows older and newer versions of clues, which is a neat way to see edits that may have been rejected in drafts. I also search for phrases like "editor changed clue" or "clue rejected" plus the constructor's name; you can find really specific examples that way. I get a kick out of comparing the drafts and seeing how small wording changes completely shift solvability, and I often save the funniest rejects in a folder for inspiration.
If you want quick, concrete examples then look where constructors hang out: their blogs, 'Crossword Compiler' forums, and Twitter/X threads. People will literally post "Here were my rejected clues" or show the before-and-after of edits. Reddit threads in 'r/crosswords' and posts on 'Crossword Fiend' are full of real-life rejected clues and explanations, like clues tossed for being obscure or unintentionally offensive.
A short tip: search for "rejected clue" and "postmortem" together — you'll find long lists and the rationale behind rejections. I always learn a trick or two from each post and it makes me appreciate how tight a good clue has to be.
I've dug around a ton of places when I've wanted to see the weird bits editors toss aside, and there are some really satisfying rabbit holes.
Start with constructors' personal blogs and Twitter/X threads — many builders will post a grid and then a follow-up listing clues that got Cut or rewritten. Sites like 'Crossword Fiend' and the 'Wordplay' column archives often post write-ups where editors or constructors discuss clue edits. For a more technical dive, the 'Cruciverb' mailing list archives and the 'Crossword Compiler' forums have long discussions where people share rejected clues and the reasoning behind decisions.
If you want searchable examples, try Google with site-specific queries such as site:reddit.com "rejected clue" or site:crosswordfiend.com "rejected". Rejected clues often fall into categories — too-obscure factual references, duplicative wordplay, ambiguous grammar, or potentially offensive language — so when you read those posts you'll start to recognize patterns. I always enjoy seeing the attempts that almost worked; it's like peeking into a workshop and I come away with new clue-writing tricks and some laughs.
I've found the most entertaining rejections in social spaces where constructors are relaxed about their failures. People will drop a list of cut clues on Twitter/X or in a 'Crossword Fiend' comment and you get raw, human reasons: "too local," "too edgy," or "forced wordplay." Reddit's puzzle communities are full of screenshots and constructor commentary, which is a goldmine for seeing real rejected clues and the exact phrasing that provoked the cut.
If you prefer curated examples, some puzzle bloggers create "rejected clues" posts that compile the funniest or strangest ones, often with a note on why they didn't pass muster. I always laugh and learn from those collections — they make me braver to try weirder ideas next time.
2026-02-07 01:43:23
30
Tingnan ang Lahat ng Sagot
I-scan ang code upang i-download ang App
Kaugnay na Mga Aklat
Rejected
Ellie Scott
9.7
317.7K
"I reject you, Alpha! I reject you!".
Elizabeth is an Omega ranked wolf; however, she does not realize she is an Alpha by birth. She has been rejected by her family, and her Pack, having suffered years of abuse from them. She is about to be given to the Pack Beta as his chosen mate when her fated mate finds her. Will her fated mate reject her as well?
“I, Alpha Logan of the Crystal Moon Pack rejects you, Myra. A very useless and worthless omega to ever be my mate, and my future Luna.” He spewed with primal disgust, eyes void of any regret.
“And I, Myra De Vries accepts your rejection.”
The brewing bond shattered and I felt no pain, however I couldn’t say the same for him when he held his heart, hurt flashing through his eyes.
___________
Enslaved and mistreated by the Alpha’s Family who took her in when she was ten and a surviving rogue.
Myra’s world was trudged early into a dark world filled with miseries and monsters in form of werewolves.
That was until she turned eighteen and was mated to the pack’s new Alpha, who rejected her at the sniff of her mystical scent.
She was instantly blessed with a second chance mate that turned out to be the most feared man in the wolf-verse who took an interest the moment his eyes laid on her.
However, his interest held secrets. And her first mate wanted back the gem he once threw away.
It is now left to Myra to navigate her new world of rejection, betrayal, love, and fate.
*Not suitable for readers under the age of eighteen*
I am an Omega, the lowest rank in the wolf packs, the rejected, the despised. I never bother about being an Omega or serving my fellow wolves as long as my family is right beside me.
My bed of roses turned into a bed of thorns when I clocked eighteen. I discovered that my mate is the beta, and he has pronounced rejection upon me. My heart is torn and my life has turned complicated. Is this how it feels to be rejected by your mate?
*****
Being an Omega is bad, isn't it? Getting rejected is worse, is it not? And getting accepted by a cursed Alpha is the worst of all, don't you think?
After Elena gets rejected by the Beta because of her status, she accepts her fate and decides to move on despite knowing how painful it will be, she crosses paths with the Alpha and he declares acceptance upon her.
When Elena uncovers the mask behind the acceptance by the Alpha, will she choose to remain rejected by the Beta or accepted by the Alpha?
“I, Alpha Xavier Grayson, reject you, Karen Denmark, as my mate and Luna,” he said with a smirk. “I don’t need to make you accept the rejection, because you’ll be gone in what seems like a couple of minutes.” He smiled evilly.
“I, Karen Denmark, accept your rejection,” I whispered, though each word tore through me like pieces of glass.
******
She thought the mate bond would be her salvation but instead, it became her curse.
Framed for a crime she didn’t commit, she was cast aside, rejected by the one fate had first chosen for her. Left broken, unwanted, and betrayed, she was certain her life was over.
Until the bond pulled her to another.
Will he be the one to heal her brokenness, or will her presence only tear them both apart? And when the truth of her past begins to unravel, when shadows stir and hidden enemies rise… will their bond be strong enough to survive what’s coming?
Alpha James who is known to be cold-hearted, ruthless and arrogant is feared by all. Rumors say he is totally cruel and leaves no enemy behind. His reputation does him no justice in the social department as he was rejected three times by his mates. A secret he intends to keep to himself. Convinced he doesn't need love, he takes it upon himself to reject his forth chance mate to preserve his pride.
"I Alpha James Tyler Carter of black mist pack, reject you Zoe Chloe Anderson of White mist pack as my mate and Luna."
"But.....why?"
"I don't need a mate. I'm fine on my own! I don't want some she-wolf up in my business!" He roared arrogantly.
"I Zoe Chloe Anderson of white mist pack, reject your rejection, humph!" She scoffed.
Zoe is an arrogant, egotistic Alpha's Daughter who doesn't take no for an answer. What happens when she meets the most ruthless Alpha in the world and he rejects her as his mate?
They say opposites attract but similarities bind. Will these two look past all their shortcomings and accept each other? Or will their pride lead them to separate ways?
Maya is riding high after finally becoming a member of the pack. On that fateful night, the best and worst things happen to her. Not only does she turn into a wolf, but she finds her mate. None other than the pack’s nomad alpha, Luke. He doesn’t want her as his mate.
All he's ever needed was his bike and the freedom of the open road—until Maya. Luke knows he's made a mistake by rejecting Maya. Nothing else matters to him. Each time he visits the pack he hopes to see her, but she's perfected the art of avoiding him—until he decides to stay.
Maya wants to stay mad at Luke to protect herself, but with every passing day she learns more about their aloof alpha. She wants to give herself to him completely, but will she be risking more than her body?
He left once. He rejected her once. He’d been cruel. Is there any chance that he's really changed?
There are a few predictable traps that turn perfectly good entries into rejects, and I can’t help but rant about them a little because they’re so avoidable. Editors often dump clues for being factually wrong (a date, a chemical symbol, a name that’s been misremembered), or for using wildly obscure vocabulary that only a handful of grad students would know. Then there’s the tone problem — clues that are unintentionally rude, needlessly sexual, or culturally insensitive get cut fast. Beyond ethics and accuracy, technical issues matter: wrong enumeration, inconsistent use of abbreviations, or clues that don’t actually match the entry when you parse them cleanly will fail a sanity check.
Another big category is crosswordese and stale fill. If your grid relies on a stack of ancient fillers and a new, clever clue would require two of them to be replaced, editors sometimes reject the clue to preserve overall quality. Theme misfires are brutal too — a themed entry that breaks the revealed pattern or betrays the puzzle’s internal logic gets rejected. I try to think like a solver: fair surfaces, clean grammar, solvable crossings, and mainstream knowledge usually keep clues in the puzzle. It’s a balancing act, and when a clue survives the editor’s knife it’s a small victory I never take for granted.
Got a clue that feels flat-out wrong? Here's my go-to approach that usually gets editors to listen. First, note the essentials: puzzle title or publication, date, puzzle ID (if there is one), the exact clue text, the grid entry it produced, and the crossing letters. I always take a screenshot of the grid and the offending clue so there’s no ambiguity about which puzzle I mean. Then I check quick reference sources—dictionary definitions, style guides, or original-language sources if it’s a translation issue—to gather evidence.
Next I write a short, polite message. I lead with the exact puzzle details, paste the clue and fill, explain why it’s misleading or incorrect, and include links or quotes from references. If I can, I suggest an alternative clue or explain how the current clue violates a rule (ambiguity, incorrect facts, offensive language, etc.). I send this through the publication’s official feedback channel—website form, puzzle email, or the app’s feedback option—and I copy the constructor or post on their social account if that’s customary. Editors aren’t adversaries; they appreciate precise, civil reports. I usually sign off with a friendly line and a quick note that I enjoy the puzzles, which seems to help the message land. I’ve had a few rejections reversed this way, so it feels worth the effort.