Recipe page visibility & SEO

Every published recipe gets a public page at a short /r/… link. This page explains what search engines and AI tools see there — and how to change it.

What indexable pages get

When indexing is on (the default), each published recipe page carries:

  • Recipe structured data — ingredients, steps, times, servings, and your byline in machine-readable form, which makes pages eligible for Google's recipe rich results (the cards with photo and cook time).
  • A canonical URL and Open Graph tags — clean previews when shared anywhere.
  • A place in the recipe sitemap — so search engines discover new recipes quickly.

Over time this makes your recipe library findable by people searching for the dish — an audience channel that compounds independently of the Instagram algorithm.

Turning indexing off

Some creators prefer recipes to be reachable only by people who got the link — from a DM, a share, or their profile. In Settings → Recipe pages, switch off "Allow search engines and AI tools to index my recipe pages." From then on your pages:

  • send a noindex robots directive to all crawlers (Google, Bing, and the AI crawlers that respect robots directives — see noindex),
  • are removed from the recipe sitemap,
  • stop emitting Recipe structured data, so there's nothing structured to lift.

Pages stay public in the practical sense: anyone with the link can open, read, save, and share them. Delivery is unaffected.

Timing

The switch applies to your pages within a minute. Removal from search results isn't instant — engines drop a page when they next recrawl it, typically days to a few weeks. Turning indexing back on restores everything (structured data, sitemap, canonical) immediately, and pages reappear as they're recrawled.

Scope

The setting is per account and covers all your recipe pages at once. It doesn't affect Cookping's own marketing or documentation pages — only /r/… pages you publish.