The Siftr newsletter is must-read material for an ambitious food blogger.
Month after month, the newsletter delivers reliable SEO insights that are useful for new and seasoned food bloggers alike.
At Foodie Digital, we practice semantic search. And wisely, so does the Siftr team, which is probably why I like their SEO newsletters so much.
The moment each issue hits my inbox, I’m in. I might even be the first open (lol 😂).
Even as someone who spends all day thinking about semantic SEO, each newsletter still gives me plenty to think about. And not just about where things are headed, but what needs fixing too. I also like how practical the recipe-specific examples are.
After reading every single Siftr issue, here are 10 major mic-drop moments 🎤🎤🎤 that I think every food blogger (and every Foodie Digital member) needs to hear:
Issue 40: The era of SEO page formulas is over (read the newsletter)
It’s no secret that following a page template can help reduce writing friction, keep the writer organized and on topic, and ensure the basics of a recipe are covered.
But, the problem starts when filling in the sections of the page template becomes the goal instead of the guide. Each time the same post structure is reused, originality gets quietly squeezed out because the writing becomes easy, rather than inventive.
Instead of focusing on what the recipe needs, the urge to fill every predefined section takes over — a major cause of filler text in recipe posts!
Worse, cookie-cutter templates dampen personality, recipe testing insights get omitted, and every post begins to sound the same.
Over time, this creates a bigger SEO issue for food blogs: sameness at scale. When thousands of recipes follow the same formula — same intro, same headers, same FAQ blocks — the collective value drops. 👎
Issue 45: An easy framework for writing better recipe titles (read the newsletter)
Writing a recipe title used to be pretty straightforward:
- Develop a recipe
- Find and use the applicable keyword
- Publish the post
- Move on
And honestly, that approach still works fine. Nothing is technically “broken” about it.
But working isn’t the same as performing.
A recipe title does a few important things. It can act as a ranking signal, reinforce branding and context, and summarize the page.
But its most important job is driving clicks while setting the right expectations.
Issue 36: How to boost views with no new recipes (read the newsletter)
Simplistic internal linking “formulas” have wreaked havoc on food blogs.
Today, to boost views, the real SEO impact comes from consistently internally linking the way people actually cook. Linking like people cook — LLPC — isn’t some kind of SEO magic trick. It’s a mindset shift. ⭐
An LLPC approach to internal linking can lift views (and ad revenue $$) without any new recipes because it increases chances of earning multiple views per session.
Issue 42: 10 tech SEO priorities to audit on your food blog (read the newsletter)
Tech SEO audits are great at uncovering a mountain of issues, but they often treat every finding with the same level of urgency. They give you no sense of what you should tackle first, second, and third.
With SEO, food bloggers rarely stay stuck because they aren’t trying hard enough. Food bloggers are some of the most tenacious, savvy, advanced SEO pros out there!
It’s usually a problem of prioritization.
Issue 44: 10 recipe structured data priorities to audit (read the newsletter)
When it comes to recipe structured data, prioritize accuracy first, then completeness. But ideally, you want both.
If a field (like “Cuisine”) naturally applies to the recipe, include it. If it doesn’t (like “Diet”), it’s perfectly fine to leave it blank. Forcing fields to be filled in can create more confusion for crawlers than simply leaving them empty.
Issue 35: SEO lessons from 2025’s only spam update (read the newsletter)
With AI-generated recipe content spreading fast, it’s not surprising that Google is tightening the reins for recipes — and, in particular, for structured data violations.
For many food blogs caught by the August 2025 spam update, the issue wasn’t a one-off mistake — it was repeated spam violations across 1 or more of 3 major areas, spread across big portions of their recipe index, including:
- Recipe structured data violations
- Review snippet structured data violations
- Link spam violations
Issue 32: Natural language processing for recipes (part 1) (read the newsletter)
Writing in an NLP-friendly way isn’t about adding more words.
It’s about choosing better ones.
And it’s not a separate tactic (you don’t “optimize for NLP” directly) but the clearer and more meaningful your sentences, the easier it is for Google (and other search engines) to understand what your recipe is about, and reward it with rankings.
It’s these words that help Google connect the dots on what your recipe is about, and just as importantly, what it’s not. Because here’s the SEO truth:
Vague writing isn’t just unhelpful for readers: it’s unhelpful for NLP.
Issue 33: Natural language processing for recipes (part 2) (read the newsletter)
How people search is changing fast and Google knows it.
More and more, people are skipping Google search and using visual search tools like AI Mode to find the recipes they want.
With multimodal NLP, Google’s basically learning to see your recipes the way humans do, picking up on clues from words, photos, and videos instantly and all at once.
Issue 34: The “type” keyword research trick (read the newsletter)
After finding a focus keyword for a recipe, a lot of food bloggers think their keyword research session is finished. When really, it’s just getting warmed up!
It’s really hard for one main keyword per post to:
- Reinforce your brand identity
- Match your right reader’s search intent
- Give semantic context to a recipe
- Meet natural language processing requirements
Issue 41: Reader Q: When and how should I update posts? (read the newsletter)
A lot of food bloggers only update posts after organic traffic starts to decline, or when they notice a recipe drop a position or two in the search rankings.
And, the instinct is always to make quick changes, like tweaking wording, shortening instruction steps, or adding new process photos or a video to stop the slide. 🫠
While well-intentioned, these reactive updates are busywork, not SEO work.
Updating only after a post loses traffic is like fixing a leaky roof during a flood! 💦
This last one is my personal favorite. ☝️



