🍴

RecipeMemoir full site review

Private deliverable. Enter the hub password to continue.

That's not right. Try again.

← Back to the hub

RecipeMemoir full site review

Forty-one findings from live testing of the beta, ranked by impact, with the evidence for each one.

Prepared 2026-11-14

Reviewed 14 November 2026 against the live beta, v0.9.29. Everything below was tested in a real headless Chromium at 1280px and 390px, signed out, plus direct calls to the public API. Every finding names the URL and the step that produced it. Where something could not be verified from outside, it is marked suspected and the reason is given.

The honest headline first: the craft on this site is real. The styles gallery is genuinely impressive, the recipe page design is better than most of the sites it imitates, the pricing page is more candid than anything a competitor publishes, and the privacy writing is warm and human. The problems are not taste problems. They are plumbing problems, and most of them sit between a good product and the people who would pay for it.

Executive summary

The five problems that matter most

  1. The privacy policy describes a newsletter, not this product. It says "What I collect: nothing at all unless you subscribe," then lists five items and says "that's the entire list." The app stores accounts, 1,500 recipe collections, uploaded photos, shopping lists, pantry contents and meal plans. None of that is mentioned. The same page claims "no analytics, no tracking of any kind," while loading the Cloudflare analytics beacon on that very page.
  2. Recipe pages carry no structured data at all. Zero schema.org Recipe markup on every recipe page tested, before or after JavaScript. The entire product promise is "publish your recipes as a real website," and those websites are invisible to Google rich results and close to uncitable by AI search engines.
  3. No attribution anywhere, on any recipe. The API exposes source and source_url fields and both are empty on all 1,517 recipes. Several titles still carry the origin ("Oatmeal Cookies - America's Test Kitchen", "Tarta De Limon | GoodNes"), so the provenance was known at import and dropped. For a product that publishes these pages publicly, this is the largest non-technical risk on the site.
  4. Published sites cannot be found. The sitemap contains 7 URLs. No recipe, no published collection, and not even the pricing page is in it. Recipe pages have no canonical tag and no meta description. The shareable artifact the whole product exists to create is the part search engines know least about.
  5. The app's own chrome sits on top of every customer's public site. A visitor to Annette's recipe site sees "Shopping, Pantry, Plan, Insight, Tidy and Enrich, Photos: standard, Sign in" above her masthead. On a phone that navigation consumes the entire first screen before any recipe content appears, and it quietly contradicts the "your own site" pitch.

The five biggest opportunities

  1. Ship Recipe JSON-LD and a real sitemap. This is a few days of work that turns every customer's site into an SEO asset. It also makes each published site a reason to stay subscribed, because leaving means losing the rankings.
  2. Make attribution a feature, not an omission. "Adapted from Sally's Baking Addiction" with a link is what good food blogs already do. It defuses the legal exposure, it is the honest thing, and it fits the brand voice better than silence does.
  3. Put the product on the homepage. There is not one food photograph on the homepage of a product that sells beautiful food websites. The styles gallery is the best asset on the site and it is one click away behind a text link.
  4. Separate the app from the published site. When a family member opens a shared recipe link they should see a recipe site, not a logged-out dashboard. This single change makes the core artifact feel like the promise.
  5. Charge for the family and heirloom story, not for feature counts. The current tiers sell "unlimited imports" and "nutrition info." The thing people actually pay for is "Grandma's recipes, safe, shareable, and beautiful forever." The wedge is right; the pricing copy has not caught up to it.

Findings

Severity reflects impact on a real user or on the business, not difficulty. Effort is a rough build estimate in passes: S is a single focused change, M is a feature-sized piece of work, L is a project.

ID Area Severity Status What is wrong Evidence Suggested fix Effort
1 Trust and privacy Critical Confirmed The privacy policy does not describe the product. It states "What I collect: nothing at all unless you subscribe," then lists email, referring page, dates, country code and two tokens, and says "That's the entire list." The app stores user accounts, imported recipe collections, uploaded photos, shopping lists, pantry contents and meal plans, none of which appear. Read the full text of https://recipememoir.com/privacy on 14 Nov 2026. Compared against the signed-out app surface at /site/shopping.html, /site/pantry.html, /site/plan.html and the import flow at /site/import.html. Rewrite the policy to cover account data, recipe content, uploaded images, and any third party AI processing used for commentary. Keep the current warm voice, which is an asset. Add account deletion and data export, since "your data, always yours" is the brand promise. M
2 Trust and privacy Critical Confirmed The policy claims "Cookies and tracking: There are none. No analytics, no advertising pixels, no tracking of any kind." The site loads Cloudflare Web Analytics on every page, including the privacy page itself. Loaded /privacy in headless Chromium and captured all network requests. Observed static.cloudflareinsights.com/beacon.min.js and a request to /cdn-cgi/rum on that page and on /, /u/annettethompson and a recipe page. Either remove the beacon or amend the sentence. The cookie claim is actually true and worth keeping: zero cookies were set on any page tested. The accurate line is that analytics are cookieless and record no personal data. S
3 SEO and AI search Critical Confirmed No schema.org Recipe structured data exists on any recipe page, before or after JavaScript runs. Recipe pages cannot win rich results and are poor candidates for AI search citation. Parsed every script of type application/ld+json after full page render on six recipe pages, including /u/annettethompson/r/lazy-mexican-rice-c1 and four style demos. Result was an empty list on all six. Emit server-side Recipe JSON-LD with name, image, recipeIngredient, recipeInstructions, totalTime, recipeYield, nutrition and author. Server-side matters because most AI crawlers do not execute JavaScript. M
4 Trust and content Critical Confirmed No recipe credits an original creator. The source and source_url fields exist in the public API and are empty on every recipe. Several imported titles still name their origin, so the source was known when the recipe was captured. Fetched /api/collection.js?owner=annettethompson and counted empty source fields across all 1,517 records: 1,517 of 1,517 empty for both fields. Confirmed on the detail payload /api/recipe.js for lazy-mexican-rice-c1. Titles in the data include "Oatmeal Cookies - America's Test Kitchen" and "Tarta De Limon GoodNes". Capture and display source name plus link on import, and render an "Adapted from" line on the recipe page. Backfill from the URL already stored at import time where it survives.
5 SEO High Confirmed The sitemap lists only 7 URLs. No recipe page, no published collection, and not the pricing, help or guide pages. Fetched https://recipememoir.com/sitemap.xml and counted 7 loc entries: home, styles, and five gift and cookbook landing pages. Generate the sitemap from the database so every published collection and recipe appears, with lastmod from the edit timestamp. Exclude unpublished and private collections. M
6 SEO High Confirmed Recipe pages and published collections have no canonical tag and no meta description. The homepage is the only page tested that has a canonical. Checked the rendered head of /u/annettethompson, /u/annettethompson/r/lazy-mexican-rice-c1, /styles, /privacy and /terms. Canonical was absent on all of them. Meta description was absent on both recipe URLs. Add canonical and a generated meta description to every published page. Build the description from the first instruction or the ingredient list, since 98 percent of recipes carry no description of their own. S
7 Product and UX High Confirmed The RecipeMemoir app navigation renders on top of every customer's public site, including owner only tools. A signed-out visitor sees Shopping, Pantry, Plan, Insight, Tidy and Enrich, Photos: standard and Sign in above the site masthead. Viewed /u/annettethompson and /u/annettethompson/r/lazy-mexican-rice-c1 signed out at 1280px and 390px, and read the rendered nav links. Hide app chrome for visitors who are not the owner. Show the published site alone, with at most a small "Made with RecipeMemoir" credit, which also works as acquisition. M
8 Mobile High Confirmed On a phone the stacked app navigation plus the marquee band plus the site masthead fill the entire first screen. The recipe title appears only after roughly 340px of scrolling, and no recipe content is visible above the fold. Screenshot of /u/annettethompson/r/lazy-mexican-rice-c1 at 390x844. The first visible content is nine app navigation links across two rows, then a Sign in button, then the ticker, then the masthead. Collapse app navigation into a single menu button on small screens, or remove it from published sites entirely, which also fixes finding 7. S
9 Product and UX High Confirmed Signed-out visitors reach fully rendered owner tools that silently fail. The pages render their full interface, including buttons like "New list" and "Delete list", while every API call returns 401. Loaded /site/shopping.html, /site/pantry.html, /site/plan.html, /site/insight.html and /site/tidy.html signed out. Each returned HTTP 200 with a complete interface and console errors from 401 responses on /api/site/shopping, /api/site/pantry, /api/site/plan and others. Redirect signed-out visitors to the sign-in page with a return path, or render an explicit signed-out state. Do not show controls that cannot work. S
10 Performance High Confirmed Photos are served at original upload size. A single recipe photo weighed 846 KB and the published collection page transferred 4.2 MB across 46 requests. Measured with the Performance Resource Timing API on /u/annettethompson. Largest resources were /api/photo/1796.jpg at 846 KB, /api/photo/1741.jpg at 683 KB and /api/photo/1792.jpg at 549 KB, against a total of 4,215 KB. Serve resized and reencoded derivatives through Cloudflare Images or a sized variant of the photo endpoint, and use WebP or AVIF with a JPEG fallback. A thumbnail grid should never download a 1024px original. M
11 Performance and design High Confirmed Many stored photos are far too small for the slots they fill, so hero images are visibly upscaled. A 280x280 photo is stretched across a 1178x684 hero, and a 200x150 placeholder is rendered at 820x461. Compared naturalWidth against rendered width for every image on five recipe pages. Examples: /styles/the-pioneer-woman/recipe.html hero at 1178x684 from a 225x225 source, /styles/nyt-cooking/recipe.html hero at 1280x600 from a 280x280 source. Set a minimum resolution for hero use, fall back to a cropped layout when the source is too small, and route small sources into the AI upscaler the homepage already advertises. M
12 Performance High Confirmed No image on any page tested carries width or height attributes, so every image contributes layout shift while loading. Counted images lacking both attributes: 21 of 21 on /u/annettethompson, 21 of 21 on /site/browse.html, 6 of 6 on /site/welcome, and every image on the recipe pages tested. Emit intrinsic width and height, or an aspect-ratio box, on every image. This is the cheapest Core Web Vitals win available here. S
13 Legal and brand High Confirmed Twenty-two of the 24 styles are named after real, trademarked publications and creators, and presented as product features on a commercial site with paid tiers. Read all 24 style names at /styles. They include Saveur, The Pioneer Woman, NYT Cooking, America's Test Kitchen, King Arthur Baking, Sally's Baking Addiction, Joy the Baker, Pinch of Yum, RecipeTin Eats, Half Baked Harvest and Andrew Zimmern. Rename the styles to descriptive names and keep the inspiration in the prose if at all. "Test Kitchen" and "Farmhouse Table" sell the same look without using someone else's mark. Worth a short conversation with a lawyer before paid tiers launch. S
14 Accessibility High Confirmed The sign-in email field has no associated label, only a placeholder. This is the single most important form on the site. Inspected /site/login.html. The input has id "email" and placeholder "[email protected]" and no matching label element, no aria-label and no aria-labelledby. Add a visible label. Placeholders disappear on focus and are not a substitute for a label under WCAG 2.2 AA. S
15 Accessibility High Confirmed The feedback widget's three fields are unlabeled on every page that carries it, and the recipe search input is unlabeled on the published site. Found unlabeled fields on /site/pricing, /site/help, /site/welcome and /site/import.html, each with a textarea and two inputs identified only by placeholder. The search input on /u/annettethompson has only the placeholder "SEARCH RECIPES". Add labels, visually hidden where the design needs it. This is four small edits that clear the most common WCAG failure on the site. S
16 Monetization and SEO Medium Confirmed The pricing page is marked noindex, and /pricing returns 404. Pricing is reachable only from a footer link. /site/pricing returns a robots meta of "noindex". /pricing returns HTTP 404. The only links to it are in page footers. Remove the noindex, add /pricing as the canonical URL with a redirect from the current path, and link it from the main navigation. People comparing recipe managers search for pricing by name. S
17 Accessibility Medium Confirmed Contrast failures on the pricing page affect the prices themselves. Grey text on white measures 3.62:1 against a 4.5:1 requirement. Computed contrast on rendered /site/pricing. Failing items include "or $40 a year: 2 months free" and "or $80 a year: 2 months free" at 3.62:1, and "/ you're here" at 3.16:1, all in rgb(139,134,126). Darken that grey to roughly rgb(105,100,94) or darker. The same token fails four more times on /site/welcome and once on /styles. S
18 Accessibility Medium Confirmed Many links and buttons are under the 24 by 24 pixel minimum target size at phone width, which fails WCAG 2.2 AA 2.5.8. Measured rendered boxes at 390px. Counts of controls under 24px in either dimension: 22 on /site/guide, 16 on the homepage, 15 on /site/help, /site/add.html and /u/annettethompson, 9 on /site/pricing. Increase padding on inline and navigation links at small widths. Most of these are 18 to 23 pixels tall, so a small padding change clears the threshold. S
19 Product and SEO Medium Confirmed Each recipe is reachable at two URLs with no canonical, and the second one renders incorrectly. The query-string variant shows the collection masthead as the page title and heading, embeds the recipe as a subheading, and loads the full recipe grid beneath it. Compared /u/annettethompson/r/lazy-mexican-rice-c1, which renders correctly at 78 KB with the title "Lazy Mexican Rice", against /u/annettethompson/recipe.html?slug=lazy-mexican-rice-c1, which renders heading "ANNETTE & RECIPES" and transfers 4,215 KB. The published cards link only to the correct form. Redirect the query-string form to the pretty URL, or add a canonical pointing at it. The broken variant is live and indexable today even though nothing links to it. S
20 Content and copy Medium Suspected The nutrition panel tells visitors "we add nutrition info every 24 hours." No daily job could be confirmed from outside, and project notes from July flagged that no such job existed. Observed the message on /u/annettethompson/r/lazy-mexican-rice-c1. Marked suspected because a scheduled job cannot be verified from the public site. Confirm the job exists and runs. If it does not, change the wording to something true, such as "nutrition for this one is still being worked out." A promise with a clock on it is the kind visitors check. S
21 Data consistency Medium Confirmed The published site calls itself three different things. The browser tab says "Annette's Kitchen", the collection heading renders "ANNETTE & RECIPES", and the recipe page masthead reads "ANNETTE'S KITCHEN". Compared document.title and rendered h1 on /u/annettethompson against the masthead on /u/annettethompson/r/lazy-mexican-rice-c1. Take the site name from one stored field and render it everywhere. The ampersand appears to be style template decoration overriding the real name. S
22 Data quality Medium Confirmed Imported titles carry publisher junk, and the collection contains duplicates. Analysed all 1,517 records from the public collection endpoint. Found 14 duplicate title groups, including "Sweet and Sour Chicken", "Soft Molasses Cookies" and "Strawberry Cobbler" twice each. Dirty titles include "Tex-Mex Beef Enchiladas " with a trailing pipe, "Tarta De Limon GoodNes" and "Sheet Pan Pancakes Recipe
23 Recipe pages Medium Confirmed There is no print button and no print layout worth the name on the pages tested, and print export is listed as a feature of the top paid tier. Checked six recipe pages for a print control. Only the NYT Cooking style had any print affordance. Each page carried a single print media rule. The /site/pricing page lists "Print exports" under the $8 Family tier. Give every recipe page a print button with a clean one-page layout. Printing a recipe is table stakes for a recipe site, and gating it behind the top tier will read as mean. S
24 Recipe pages Medium Confirmed Recipes cannot be scaled, and serving counts are often missing from the display. The reviewed recipe showed a cook time only, with no prep time, total time or yield. Searched rendered text on six recipe pages for scaling controls and found none. On /u/annettethompson/r/lazy-mexican-rice-c1 the only time shown is "COOK 20 to 25 minutes". Across the collection, 97 of 1,517 recipes carry no total time at all. Add a servings stepper that rescales quantities, which is one of the most used features in Paprika and a frequent request in recipe app reviews. M
25 Bug Medium Confirmed Both legal pages throw an uncaught JavaScript error on every load. They carry the homepage waitlist script but not the form it expects. Loaded /privacy and /terms. Both produced "Cannot read properties of null (reading 'addEventListener')". The page source contains getElementById calls for wlForm, wlEmail, wlBtn and four more ids that do not exist on these pages. Remove the waitlist script from the legal page template, or guard it with a null check. S
26 SEO and UX Medium Confirmed The "More Recipes" block is random rather than related. A Mexican rice recipe was followed by Italian donuts, sugar-free gelatin, a watermelon slushie and lemon blueberry cake. Observed the related grid on /u/annettethompson/r/lazy-mexican-rice-c1 and on the breakfast bowls recipe, where the suggestions were equally unrelated. Relate by course, cuisine or shared ingredients. This is the cheapest internal linking improvement available and it also improves time on page. M
27 First impressions Medium Confirmed The homepage contains no photographs at all, on a product that sells beautiful recipe websites. The feature grid uses emoji as icons. Counted images on the rendered homepage: zero. The section headed "Want to see what the websites look like?" is a red block of text with a link. Put three or four real style screenshots above the fold and let the gallery sell itself. The assets already exist at /styles and are good. S
28 Accessibility Medium Confirmed Most pages have no main landmark, so screen reader users cannot skip navigation. There is no skip link. Checked for a main element or role on each page. Missing on the homepage, /site/pricing, /site/guide, /site/welcome, /site/import.html, /u/annettethompson, /privacy and /terms. Present only on /styles, /site/help and /site/add.html. Wrap page content in a main element and add a skip-to-content link as the first focusable element. S
29 Navigation Medium Confirmed The app navigation differs from page to page, so items appear and disappear as you move around. Compared rendered navigation across pages. /site/shopping.html, pantry, plan and insight show Update, Newsletter, Settings and Dashboard. /site/tidy.html and /site/add.html do not. /site/import.html shows "Find recipes" and omits Insight. Render one navigation component everywhere, with items shown or hidden by sign-in state rather than by page. S
30 Onboarding Medium Confirmed A new visitor cannot try anything without handing over an email address. Even the sample collection is gated. /site/import.html signed out says "First, sign in or create your account. Then come back here to import," and the "Import the sample collection" button sits behind that gate. /site/add.html says "Sign in to add recipes." Let people run the sample collection and see a generated site before signing up. The moment of delight is seeing their recipes look beautiful, and it is currently behind the form. M
31 Import Medium Confirmed Import accepts only the Paprika format. No other recipe manager is supported. The file input at /site/import.html accepts only .paprikarecipes, application/zip and application/octet-stream. No other import route was offered on the page. Add JSON-LD scraping in bulk, a generic CSV, and Copy Me That or Mealie exports. Every one of those is a competitor's user who is ready to move. M
32 Content and copy Low Confirmed Product copy takes a direct swipe at a competitor inside the app. /site/plan.html reads "Drop recipes onto the week, then turn the whole week into one shopping list, sorted by aisle, with what's already in your pantry ticked off. Paprika can't do that last part." Describe the benefit and drop the comparison. The feature is good enough to stand on its own, and the jab sits oddly against the warm voice everywhere else. S
33 Content and copy Low Confirmed Owner-facing instructions are shown to public visitors. A recipe without a photo tells readers to "Remind this cook to add one of her own photos here, or she can generate one with AI." Observed on /u/annettethompson/r/lazy-mexican-rice-c1, which is also the featured recipe on the collection homepage. Show visitors a quiet placeholder and show the owner the prompt. Also consider not featuring a photoless recipe in the hero slot. S
34 Data quality Low Confirmed Visibly broken ingredient data is on display on the featured recipe. /u/annettethompson/r/lazy-mexican-rice-c1 lists "1 1/2 white long grain rice or you Jasmine" with no unit and a typo, and "1 serving of love" as a measured ingredient. Step 2 says "1 cup and a half" where the ingredient says "1 1/2". Flag ingredients with a quantity and no unit in the Tidy queue. The featured recipe is the first thing a visitor reads. S
35 Heading structure Low Confirmed Recipe pages contain a hidden h3 "More Recipes" above the visible h2 "MORE RECIPES", which skips a heading level and duplicates the label for screen readers. Inspected headings on /u/annettethompson/r/lazy-mexican-rice-c1. The h3 sits in a zero-height related-section container while the visible heading is an h2. Remove the hidden heading from the suppressed native block. S
36 Styles gallery Low Confirmed Nearly every style thumbnail previews the same dish, which makes 24 distinct designs look alike. Viewed /styles at 1280px. The great majority of cards show the same chicken enchilada or white casserole photograph. Vary the preview dish per style. The designs differ more than the gallery suggests, and the sameness undercuts "pick the look you love". S
37 Styles gallery Low Confirmed The family groupings end raggedly. Bold and Edgy contains a single style sitting alone in an otherwise empty row, which reads as unfinished. Viewed /styles. Bold and Edgy has one card, Elegant and Romantic has two, and Classic Magazine leaves one orphan on its third row. Rebalance the families or let the grid centre a short final row. S
38 Social sharing Low Confirmed Published collections and recipe pages have no Open Graph tags, so a shared family link previews poorly. The homepage has a full set. Compared meta tags. The homepage carries og:title, og:image, og:description and a Twitter card. /u/annettethompson and both recipe URLs carry none. Generate per-recipe Open Graph tags using the recipe photo. Sharing a recipe with family is the core loop and the preview is currently blank. S
39 Content Low Confirmed Ninety-eight percent of recipes carry no description, which leaves recipe pages thin for search and for readers. Measured across all 1,517 records: 1,492 have an empty description field. This appears to be deliberate, since project notes record that imported descriptions were suppressed for copyright reasons in migration 041. Offer owners a one-click AI-written description in their own words. That replaces the copyrighted text with something original and fixes the thinness at the same time. M
40 Social proof Low Confirmed The flagship demo collection looks unused. Of 1,517 recipes, 3 have a rating and none is marked a favourite. Counted rating and favourite flags in the public collection payload. Rate and favourite a few dozen recipes on the demo site. A prospective user reads an unrated collection as an abandoned one. S
41 AI search Low Confirmed The llms.txt file exists but lists only the home page and the sitemap, and the sitemap it points at holds 7 URLs. Fetched https://recipememoir.com/llms.txt. It contains a one-line description and two links. Expand it to name the styles gallery, pricing, help and a sample published collection, once the sitemap covers them. S

Improvement ideas, not bugs

These are not defects. They are the things most likely to move signups, retention and word of mouth.

A "see it before you sign up" path. Let a visitor paste one recipe URL or load the sample collection and watch a real site get built, with no account. Right now the only proof is Annette's demo, and a visitor cannot picture their own recipes in it. Helps every prospective user, and it puts the best moment of the product before the form instead of after it.

Per-recipe Open Graph images generated from the recipe photo. When a daughter texts her mother a link to the cornbread recipe, the preview should show the cornbread. Helps families, and it is the viral loop the product already depends on.

A family invitation flow. The Family tier promises "shared cookbook" and "up to 5 collections", but nothing on the public site explains how a relative joins, what they can see, or what they can change. Helps the family historian, who is the buyer most likely to pay.

Contributor credits on a shared collection. "Grandma Ruth's recipes, contributed by Ruth, Annette and Maria" with a note on who added what, and when. Helps the heirloom use case, which is the emotional moat and the thing no competitor does well.

Import from a photo of a handwritten recipe card. Every family cookbook project hits the shoebox of index cards. This is the one capture route that makes people cry a little, and the vision models to do it are cheap now. Helps the family historian, and no competitor in this list does it.

Save the original as evidence. When a recipe is imported from a URL, keep the source link, the publication, and the date. It powers attribution, it answers "where did this come from", and it lets a recipe be rechecked when a blog disappears. Helps everyone, and it closes finding 4 permanently.

A changelog or "what's new" page. The product is in beta and improving fast, and nothing on the site shows that. Helps early testers feel they backed something alive, which is most of what retains a beta user.

Where RecipeMemoir stands against the alternatives

Real advantages, as observed. The style gallery is well beyond anything Paprika, Mealie, Copy Me That or a Notion template offers, and it is the actual differentiator. The pricing page's candour is a genuine trust asset. Cook Mode with the screen lock and the US and metric toggle are both present and working, and Paprika has neither in the browser. The meal plan, pantry and aisle-sorted shopping list together are a stronger kit than Copy Me That, and the pantry crossover is a real gap in Plan to Eat.

Real gaps, as observed. Paprika has recipe scaling, print, and mature mobile apps, and RecipeMemoir has none of the three today. Copy Me That has a browser extension that captures a recipe in one click from any site; import here is a Paprika file or a pasted link. Mealie is self-hosted and free, which is the answer for the data-ownership crowd this product is also courting. Family cookbook services such as Heritage Cookbook and Family Cookbook Project sell a printed book at the end, which is the artifact the heirloom buyer actually wants on a shelf, and nothing here produces one.

The strategic read. The published website is the right wedge and nobody else is doing it. But a website that search engines cannot see and that previews blank when shared is not yet that wedge. Findings 3, 5, 6 and 38 are what convert the wedge from a nice demo into the thing that sells the product.

Monetization readiness

Pricing is clear, honest and well written, and it is also noindex, 404 at the obvious URL, and reachable only from a footer. Fix that first, because it costs almost nothing.

The tiers need work on substance, not presentation. Free Beta currently lists "Nutrition and AI commentary", and the $4 Home Cook tier lists "Nutrition info" and "AI recipe commentary", so the paid tier reads as the free tier with a price. The $8 Family tier gates "Print exports", and printing a recipe is something people expect for nothing.

What people would plausibly pay for, based on what the product already does well: a custom domain for a published site, unlimited published collections, family accounts with contributor credits, AI photo upscaling in volume, and a printed or PDF cookbook at the end. The last one is the strongest, because it is the thing the heirloom buyer is already trying to buy elsewhere.

Roadmap

Quick wins, under a day each

  1. Correct the "no analytics" sentence in the privacy policy, finding 2.
  2. Remove noindex from pricing and serve it at /pricing, finding 16.
  3. Darken the failing grey text token, finding 17.
  4. Add a label to the sign-in email field and to the feedback widget fields, findings 14 and 15.
  5. Remove the waitlist script from the legal pages, finding 25.
  6. Add width and height to images, finding 12.
  7. Add canonical tags and generated meta descriptions, finding 6.
  8. Redirect the query-string recipe URL to the pretty one, finding 19.
  9. Fix or soften the "every 24 hours" nutrition promise, finding 20.
  10. Put style screenshots on the homepage, finding 27.

Next, a focused build pass

  1. Rewrite the privacy policy to cover the product, finding 1.
  2. Ship server-side Recipe JSON-LD, finding 3.
  3. Generate the sitemap from the database, finding 5.
  4. Hide app chrome from published sites and collapse mobile navigation, findings 7, 8 and 9.
  5. Serve resized images, finding 10.
  6. Add per-recipe Open Graph tags, finding 38.
  7. Rename the styles away from trademarked names, finding 13.
  8. Add a print button and a print layout, finding 23.

Later, project-sized

  1. Capture and display attribution, and backfill where the source survives, finding 4.
  2. Recipe scaling, finding 24.
  3. Related recipes that are actually related, finding 26.
  4. Broaden import beyond Paprika, finding 31.
  5. A no-signup trial path, finding 30.
  6. Minimum resolution handling and routing small photos through the upscaler, finding 11.
  7. The printed or PDF cookbook, which is the monetization unlock.

What could not be tested, and why

  • Everything behind sign-in. Creating an account would have meant a fake identity, which was out of scope. So the import flow itself, adding a recipe from a URL, a YouTube, TikTok or Instagram link, pasted text, editing, organising, the Tidy queues, newsletter sending and the publish and share controls were all observed only in their signed-out state.
  • Extraction quality from video links. The add page says it accepts "a link to a recipe page or a cooking video", but which platforms work, and how well, could not be checked without an account. Project notes suggest TikTok is caption-only and Instagram returns an honest failure, but that is not something this review verified.
  • The nutrition refresh job, finding 20, which is why that one is marked suspected.
  • Real-user performance. Timings here come from one headless browser on a fast connection in a single location. They are useful for comparison between pages, not as field data.
  • Screen reader behaviour. Headings, labels, landmarks and focus order were inspected programmatically, but no actual screen reader was driven, so announcement quality is unverified.
  • Email deliverability for the magic link, and what the signed-in session stores, since no account was created.
  • Other owners' published sites. Only Annette's collection is publicly discoverable, so cross-account behaviour and any leakage between collections could not be examined.
  • Anything requiring an attack, which was explicitly out of scope. The observations in findings 1, 2 and 9 come from ordinary browsing only.

Method

Pages were loaded in headless Chromium at 1280x900 and 390x844, scrolled to the bottom to trigger lazy loading, and captured as full-page screenshots that were then reviewed by eye rather than only by assertion. Structure, headings, labels, landmarks, images, contrast, tap targets, focus order and page weight were measured in the rendered DOM. The public API was queried directly for collection and recipe payloads, and the 1,517-record collection was analysed in full for completeness, duplicates and attribution. Twenty-five distinct URLs were checked for status, redirects and metadata.

Published to Annette's hub. Rebuilt from the source markdown, so edit the source and rerun rather than editing this page.