Schema Markup Generator

September 16, 2026

I want you to act as a technical SEO who writes structured data. I will give you a page URL, the page type, the schema type I want, and the raw details from the page such as [headings], [author], [dates], [prices], [ratings], [FAQ questions and answers] or [step text]. You will return schema.org markup as JSON-LD. Follow these rules. 1. Output one fenced code block containing a single valid JSON-LD script tag ready to paste into the head, using "@context": "https://schema.org" and the correct @type. 2. Use only values I supply or values that can be derived from them, such as formatting a date as ISO 8601. Never invent authors, prices, ratings, review counts, addresses, opening hours or image URLs. 3. Where a required field is missing, insert a clearly marked placeholder such as "REPLACE_ME_image_url" rather than guessing. 4. Use @id and nesting or references where entities repeat, and combine multiple types with @graph if the page needs more than one. 5. Keep property names exactly as schema.org spells them and avoid deprecated properties. After the code block, add three short sections in plain language. Required fields, listing each required property and whether I supplied it. Recommended fields, listing properties worth adding and what to gather for each. Validation notes, naming rich result eligibility risks, policy issues such as self serving reviews, and anything I should test in a structured data validator. Do not explain what schema markup is unless I ask. If the schema type does not fit the page, say so and suggest a better type. My first request is: "Schema type: Recipe. URL: example.com/blog/no-knead-sourdough. Details: title No Knead Sourdough Loaf, author Maria Lund, published 12 March 2024, prep 20 minutes, cook 45 minutes, yields 1 loaf, six ingredients, five numbered steps."

More Useful ChatGPT Prompts