Submitting Recipes
There are three ways to get your recipes into Platebreaker. Sitemap submission and batch URLs are available to verified domain owners through the creators portal. Single URL submission is open to any authenticated user.
Sitemap Submission
Section titled “Sitemap Submission”Submit your sitemap URL and Platebreaker handles the rest. It fetches the sitemap XML, extracts all the URLs, filters out non-recipe pages and blacklisted patterns, checks for duplicates, and queues valid URLs for processing.
The sitemap must be hosted on the same domain you have verified. Platebreaker accepts standard XML sitemaps with <loc> tags. After submission you get a summary: how many URLs were found, how many were queued, and how many were filtered out. Processing happens in the background, and the portal’s status page shows progress as URLs move through the pipeline.
Batch URL Submission
Section titled “Batch URL Submission”If you want to submit specific pages rather than an entire sitemap, you can provide a list of up to 5,000 URLs at once. Each URL gets validated, checked against your verified domain, and deduplicated before being queued.
This works well when you have added a batch of new recipes and want them indexed without waiting for the next scheduled indexing run. It is also useful if your sitemap includes non-recipe pages that you would rather skip. Like sitemap submission, processing is asynchronous.
Single URL Submission
Section titled “Single URL Submission”Any authenticated Platebreaker user can submit a single recipe URL for indexing. No domain ownership required. The system fetches the page right away, extracts the JSON-LD recipe metadata, and stages the recipe for processing.
The initial fetch is synchronous, so you get immediate confirmation that the page was found and contains recipe data. The full nutritional analysis runs asynchronously through the same background pipeline as the other methods.
If the URL has already been indexed, the response tells you and returns the existing recipe information instead of re-processing it.
How Indexing Works
Section titled “How Indexing Works”Every URL goes through the same pipeline regardless of how it was submitted. Platebreaker fetches the page and looks for a <script type="application/ld+json"> tag containing schema.org/Recipe structured data. If it finds valid recipe metadata, the URL is staged for full processing: ingredient matching against USDA nutritional data, per-recipe nutrient profile calculation, and then the recipe becomes available in search results.
Pages without valid recipe JSON-LD are marked as having no recipe and are not processed further.
Monitoring Progress
Section titled “Monitoring Progress”Verified domain owners can check indexing progress from the creators portal. The status page shows total URLs submitted, how many have been successfully indexed, how many are still pending, how many failed, and when the most recent successful indexing happened.
Failed URLs usually mean the page didn’t contain valid recipe metadata, was unreachable, or was blocked by the site’s firewall (WAF). If your URLs are showing as WAF blocked, see the firewall allowlisting guide for instructions on allowing Platebreaker through your firewall. Failed pages are not automatically retried, but you can resubmit them after resolving the issue.
Re-indexing
Section titled “Re-indexing”Platebreaker periodically re-indexes recipes based on the indexing frequency in your domain settings (1 to 90 days, default 30). This picks up changes to your recipes and recalculates the nutritional profile. You do not need to resubmit URLs for re-indexing to happen.