اطبخ الحكاية.
تخلّص من ثِقَل الإضافات.

Does VeloCMS support Recipe JSON-LD / schema.org/Recipe?

Yes — VeloCMS emits a full schema.org/Recipe block on any post tagged with recipe:. The schema includes cookTime, prepTime, recipeYield, recipeIngredient, and recipeInstructions extracted automatically from your post content. If you connect a Spoonacular API key, NutritionInformation is also populated. The JSON-LD is rendered server-side and ships in the page head, so Google and Bing pick it up on first crawl without requiring any client-side JavaScript to run.

How does the jump-to-recipe button work?

VeloCMS automatically injects a sticky jump-to-recipe anchor button at the top of every post tagged with recipe:. The button appears above the fold and stays pinned as the reader scrolls through the intro. Clicking it jumps directly to the recipe card section — the <div> containing the structured recipe fields. The button is excluded from the print stylesheet so it doesn't appear when a reader prints the recipe. No shortcode, no plugin, no manual HTML required.

Can VeloCMS auto-compute nutrition info?

Yes, with an optional Spoonacular API key. Add your key in Admin → Settings → Integrations and VeloCMS sends your ingredient list to the Spoonacular API on publish. The per-serving nutrition data (calories, fat, protein, carbohydrates) populates the NutritionInformation schema property and displays as a nutrition label on the recipe card. If you don't add a Spoonacular key, the nutrition fields are simply omitted from the schema without affecting anything else. The free Spoonacular tier covers 150 requests per day.

How do I import my existing WordPress recipe blog?

Export your WordPress site via Tools → Export → All Content and drag the XML into Admin → Import in VeloCMS. The importer strips Tasty Recipes and WP Recipe Maker shortcodes, converts recipe card data to VeloCMS Recipe metadata fields, and queues all posts as drafts. Posts that contained plugin-generated recipe cards are automatically tagged with recipe: so you don't need to re-tag them manually. The process takes around 15–30 minutes for a typical recipe blog of 200–500 posts.

Will my recipes still appear in Google Search Generative Experience?

Yes — valid schema.org/Recipe markup with a complete ingredient list and instructions is one of the strongest signals for Google's AI-powered recipe cards. VeloCMS emits this markup server-side on every recipe-tagged post. Google SGE eligibility also depends on your domain's crawl history, content quality, and whether your recipe passes Google's E-E-A-T guidelines — schema alone isn't a guarantee, but missing schema is a guaranteed disqualifier. VeloCMS handles the schema; the rest is up to the recipe.

Does VeloCMS have a recipe-specific theme?

The Restaurant preset ships free on all plans and is the closest to a recipe-blog aesthetic — warm serif typography, clean recipe card layout, generous whitespace, food-friendly color palette. It's designed for long-form blog-style writing in the Smitten Kitchen / Food52 / Serious Eats tradition, not a menu-card format. You can apply the Restaurant theme in Admin → Themes in one click; all content re-flows immediately. VeloCMS has 13 other themes if you prefer a different visual direction.

What happens if Pinterest decides to deprioritize recipe pins next year?

Nothing — if your recipe blog runs on VeloCMS, your audience is on your email list, not on Pinterest's platform. VeloCMS membership features let you collect email subscribers directly on your site; you own and can export that list at any time. Pinterest, Instagram, and TikTok are traffic channels, not audience containers. When you publish to your VeloCMS blog and collect emails there, a Pinterest algorithm change is an SEO inconvenience, not an existential crisis.

Is VeloCMS faster than WordPress + Tasty Recipes for recipe sites?

Substantially. WordPress + Tasty Recipes typically ships 400–600KB of JavaScript per recipe page — the plugin alone accounts for 200–400KB. VeloCMS recipe pages average 80–90KB gzipped. In independent Lighthouse testing on equivalent recipe content, VeloCMS achieves LCP under 800ms; WordPress + Tasty Recipes on shared hosting averages 3.2–4.8s LCP. The difference is architectural: VeloCMS pre-renders recipe pages as static HTML with no client-side plugin runtime, while WordPress re-runs PHP and plugin hooks on every request.