I remember exactly where I was when the rejection email landed — sitting in my kitchen, actually testing a recipe for the blog, flour literally on my hands, when my phone buzzed. I wiped my hands on a towel, opened the email, and read the word “unable to approve” while a pot of something was still simmering behind me.
The blog was about home cooking, mostly simple weeknight recipes, stuff I actually made for my own family. I’d put a decent amount of care into it, or so I thought. Fifteen recipes, decent photos I’d taken myself, a clean-ish free theme. The rejection just said the usual line about content not meeting the required standard.
I only got rejected once, which I know is fewer times than a lot of people go through, but it still took me a solid month of confused tinkering before I actually figured out what was wrong and fixed it properly.
What I Assumed the Problem Was (Wrong, As It Turns Out)
My first guess was photos. I figured maybe my food photography wasn’t polished enough, so I spent a weekend re-shooting several dishes with better lighting near my kitchen window, cleaning up backgrounds, all of that. Genuinely nicer photos afterward.
I didn’t reapply immediately, thankfully, because a friend who blogs in a completely different niche looked at my site when I mentioned the rejection and pointed out something I’d completely missed — my actual recipe content was thin. Like, really thin.
What Was Actually Wrong
Going back through my own posts with fresh eyes, I saw it pretty quickly once someone pointed it out. My typical recipe post looked like this: a short intro paragraph, an ingredient list, numbered steps, done. Maybe 300-400 words total per post.
Functional, technically complete, but missing basically everything that makes a recipe post actually useful beyond the bare mechanics. No notes on substitutions, no explanation of why a step mattered, no mention of common mistakes, nothing about how to store leftovers or what to serve it alongside.
It read like an index card, not an article.
How I Actually Fixed It
I want to walk through exactly what changed on one specific post, because I think the “before and after” makes this clearer than just describing it abstractly.
Before: My garlic butter pasta post was a four-sentence intro, an ingredient list, six numbered steps, and that was it. Maybe 380 words.
After: I added a section on why I use pasta water in the sauce and what happens if you skip it (it separates, learned that one the hard way early on). I added ingredient substitution notes for people who don’t have fresh garlic on hand. I included a short bit about which pasta shapes work best and why, based on ones I’d tested myself. I added a storage and reheating section, since leftover pasta dishes can get gummy if reheated wrong. Ended up around 950 words, and every added section was something I actually knew from cooking it multiple times, not filler.
I did this same rewrite across my ten strongest recipes and quietly retired the five weakest ones that didn’t have enough behind them to expand properly.
The Other Things I Fixed Alongside the Content
The content rewrite was the biggest piece, but I also cleaned up a few other things while I was at it, since I figured I might as well fix everything at once instead of reapplying repeatedly.
Added a real About page. Mine had literally said “Hi, I’m a home cook, welcome to my blog!” I rewrote it to actually talk about why I started cooking seriously, what kind of recipes people could expect, and a bit of personality instead of a one-liner.
Fixed my Contact page, which had a contact form plugin I’d installed once and never actually tested. Sent myself a test message and realized it wasn’t even working.
Added a Privacy Policy, which I hadn’t had at all. Used a free generator from PrivacyPolicies.com and edited the wording so it matched my actual site instead of leaving it generic.
Checked my site on my phone, since I’d built the whole thing on my laptop. Found that my recipe cards were overflowing off the screen on mobile, which I fixed by switching to a lighter, more mobile-friendly theme (I went with GeneratePress).
Compressed my images. My re-shot food photos were beautiful but huge, some over 4MB each straight off my camera. Ran them all through TinyPNG, which cut the file sizes down significantly without any visible quality loss.
Step-by-Step: What I’d Actually Recommend
If you’re in a similar spot — one rejection, decent-looking site, not totally sure what’s wrong — here’s the order I’d go through based on what actually worked for me:
- Reread your weakest posts as a stranger would. Not the ones you’re proud of, the mediocre ones you kind of glossed over when building the site.
- Ask what’s missing beyond the bare mechanics. For a recipe blog, that meant substitutions, common mistakes, storage tips. For other niches it’ll look different, but the idea’s the same — go beyond the surface-level steps.
- Fix or remove the thinnest content, rather than leaving it there hoping it won’t count against you.
- Check your About, Contact, and Privacy Policy pages, and make sure they’re real, not placeholder text.
- Test your site on an actual phone, not just your laptop screen.
- Compress your images if they’re large — run them through something like TinyPNG before uploading.
- Give the site a couple weeks to settle after making changes before reapplying, ideally after submitting your sitemap through Google Search Console.
A Small Detail That Surprised Me
I genuinely thought photos were going to be the fix, and while nicer photos didn’t hurt, they clearly weren’t the actual issue, since my first instinct (better photography) did nothing on its own until I also fixed the actual writing. It’s a good reminder that the most visible thing about your site isn’t always the thing that’s actually holding it back.
Common Mistakes I’d Flag From My Own Experience
- Assuming the visual stuff (photos, design) is the problem when it’s often the writing itself that’s too thin.
- Leaving weak posts up instead of either fixing or removing them.
- Skipping the About/Contact/Privacy Policy pages because they feel separate from your “real” content.
- Never checking mobile layout, especially if you build primarily on a laptop like I did.
- Uploading unedited, oversized images without compressing them first.
- Reapplying too quickly after changes, without giving the site time to reflect them.
Final Thoughts
One rejection was enough to make me second-guess the whole project for a while, standing there in my kitchen rereading that email a few too many times. But looking back, the fix wasn’t dramatic. It was going back through my own content honestly, adding the depth that was genuinely missing, and cleaning up a handful of small things I’d overlooked while I was excited to just get the site launched.
If you’re staring at a similar rejection right now, it’s worth checking whether your content is actually thorough, not just whether it looks nice. That was the real gap for me, and once I closed it, everything else fell into place pretty quickly.
