Guide
Recipe SEO: how to get your recipes found on Google
Recipe SEO for food creators who'd rather be cooking: how Google finds a recipe, how to name it the way cooks search, how long it really takes, and what AI Overviews change.
You posted your lemon chickpea soup three weeks ago. It's one of your best. You called it "The soup I make on Sundays," your regulars loved it, and when you search Google for "lemon chickpea soup" it's nowhere to be seen.
Recipe SEO (search engine optimization) is the work of putting a recipe like that in front of the people looking for it. Google has to be able to find the page, understand which dish it is, and trust that it'll help the cook who searched. When a recipe goes missing, one of those three has broken, and each has its own fix.
Make sure Google can reach the recipe
Google finds pages mostly by following links, then crawls them, stores them and picks which to show for a search. When your soups collection links to the lemon chickpea soup, Google finds it the same way a reader does, which is one more reason to organize your recipes into collections. A sitemap, the list of every page on your website, is the other route. Most recipe platforms create one; submit it once in Search Console.
Then open the recipe in a private browser window, signed out. If you hit a login screen or a "coming soon" page, so does Google. A members-only recipe can stay private; just don't expect it to rank. If your website isn't public yet, the setup guide covers going live.
Ask Google what it knows about the page
Google Search Console is the free tool Google gives website owners. Add your website once, then paste the soup's full address into URL Inspection. Here's what to read:
- Is the page on Google? If it's indexed, your problem is wording or competition, covered below. If it isn't, the details tell you why.
- Crawl details. Whether Google could fetch the page, or something blocked it.
- Google-selected canonical. When several addresses show similar content, Google picks one to represent them. If it picked another version of your soup, like an old URL or a print page, look there first.
- robots.txt and noindex. Either one keeps a page out of results. If you find one on a recipe you want found, ask who set it and why before removing it.
One thing trips people up. The report first shows Google's recorded version of the page, which may be weeks old. If you've just fixed something, click Test live URL to check the page as it is now, then Request indexing. A clean live test means the page can be indexed, not that it will be soon.
How long recipe SEO takes on a new website
Nobody can give you a date, and Google doesn't try. Its page on asking Google to recrawl says crawling "can take anywhere from a few days to a few weeks," and asking twice won't speed it up. Its SEO Starter Guide says some changes show up in hours and others take several months, and suggests waiting a few weeks before judging whether a change worked.
So for a new recipe website: submit the sitemap and inspect your three most important recipes in week one. A few weeks later, check URL Inspection for "URL is on Google." After a month or so, see which searches they appear for in the Performance report. Indexed isn't ranking, and a new website has few links pointing at it, so share your recipes where your readers already are, Instagram included.
Recipe keyword research: name the dish people search for
Say the soup is indexed and still invisible. Look at the title. "The soup I make on Sundays" means something to your regulars and nothing to a stranger typing into Google. "Lemon chickpea soup" names the dish, the main ingredient and the flavor. Keep the Sunday story in the intro, where it's lovely.
That's most of recipe keyword research: picking the plain words a cook would type for the dish you actually made. The catch is that every word in the name is a promise. Little Spice Jar's pasta al limone is made with heavy cream; Billy Parisi's has none. Same name, different dinners. Before you pick a phrase:
- Describe your dish in one plain sentence. "Spaghetti with lemon, lots of garlic and a cream sauce, ready in 25 minutes."
- Search two or three phrases a cook might use and open the top recipes. What do people expect from those words?
- Pick the phrase your recipe fully delivers. Creamy lemon garlic pasta is honest here; "dairy-free" or "15-minute" wouldn't be. Use nearby phrases like "lemon pasta" naturally in the text.
A genuinely different dish deserves its own page, after you've tested it. A different keyword for the same pasta doesn't.
Google builds its result from your page title and your page text or meta description, and may rewrite both. So write them plainly:
Bright, lemony chickpea soup made in one pot, with spinach stirred in at the end. Ready in 40 minutes and even better the next day.
Food blog SEO starts with a recipe that works
Google's guidance on helpful content asks whether readers leave having learned enough to reach their goal. For a recipe, the goal is dinner. "Simmer until ready" doesn't get them there. "Simmer until the chickpeas crush easily against the side of the pot, about 15 minutes" does. The full checklist is in how to write a recipe.
Recipe schema, the code that labels your ingredients, steps and times for Google, can make the page eligible for a recipe rich result with a photo and cook time. Recipe plugins and platforms generate it from your recipe fields (Crumb does this for every public recipe), so your job is checking that it matches the page. The recipe schema walkthrough shows how.
What AI Overviews and AI Mode change for recipes
Less than the panic suggests. Google's page on AI features and your website says there are no additional requirements to appear in AI Overviews or AI Mode. A supporting link has to be indexed and eligible to show with a snippet: the page you just checked in URL Inspection. Also from that page:
- No special file or schema. You don't need AI text files or extra structured data. Ignore anyone selling one.
- Your recipe schema has to match the page. It's on Google's short list of practices that still count.
- AI Overviews often don't appear. Google shows them only when it judges they add something to the usual results.
Google doesn't say how recipe searches in particular are treated, so judge by your own numbers. Clicks from AI features are counted in the Performance report with ordinary web results, with no separate filter.
Read your Search Console numbers
Once the soup has been live a few weeks, open the Performance report. Pick a date range, click the soup's row under Pages to filter the report to it, then switch to Queries to see what people searched before they saw it.
| Measure | What it means |
|---|---|
| Clicks | Times someone clicked through to your page from Google |
| Impressions | Times the page appeared in results (not unique people) |
| CTR | Clicks divided by impressions |
| Average position | Roughly where the page showed for those searches. It moves around. |
Here's how to use them. Say a butter-and-Parmesan lemon pasta with no cream gets 1,000 impressions and 20 clicks for "lemon pasta no cream" over three months. That's a 2% CTR (20 ÷ 1,000). People are seeing the page for a question it answers, but the title doesn't say so. Mention "no cream" in the title or opening and explain how the sauce gets creamy without it. Nobody can promise the extra clicks, but the page will finally answer what people are asking.
The query list is incomplete, since Google leaves some queries out for privacy, and your own searches won't match what others see.
When to update an old recipe post
Update a recipe when you have something specific to fix: a reader question, a mismatch with your notes, a query the page doesn't answer. "It's two years old" isn't a reason. A new version, like an almond flour swap, needs testing first and goes in as a labeled variation. A correction, say 2 tablespoons of oil where the post said 2 teaspoons, has to reach every copy: ingredients, method, print view, any PDF and the schema, which you can confirm in the Rich Results Test. Then leave a note for readers with a saved copy:
Updated October 3, 2026: Corrected the oil from 2 teaspoons to 2 tablespoons to match the original recipe notes.
Edit the existing page rather than publishing a duplicate. Keep the URL, the original publish date and any credits for adapted recipes, and show an "updated" date that matches your structured data, as Google's byline date guidance asks. On Crumb, saving a published recipe updates the live page right away, so finish the edit before you hit save.
Where to start this week
Pick the one recipe you most want found. Open it signed out, look it up in URL Inspection, and read its title as a stranger would. Whichever check fails first is this week's job. If all three pass, check its recipe schema and come back to the Performance report in a month.