Schema & JSON-LD Recommendations
Pick the right schema types for a page — and only the ones the page's actual content supports
What This Prompt Does
Structured data makes pages eligible for rich results, but only if the schema matches the content. This prompt reads your visible page content, recommends the right schema types, explains why each is a fit, and lists the important fields — while explicitly flagging any schema you should not add because the page doesn't back it up.
When to Use It
- •Rolling out schema on a new site for the first time
- •Deciding which rich result types are realistic for a given page
- •Auditing a site that uses schema indiscriminately across every page
- •Figuring out why a page isn't showing rich snippets
The Prompt Template
Act as a technical SEO specialist. Your goal is to identify the best schema types for this page and explain why they should be used. Context: - Page type: [PAGE TYPE] - Business type: [BUSINESS TYPE] - Page content: [PASTE PAGE CONTENT] Task: Determine: 1. which schema types fit this page 2. why each schema type is appropriate 3. what important fields should be included 4. whether any schema should be avoided Process: 1. Review the visible page content. 2. Match the content to appropriate schema types. 3. Identify the most important properties. 4. Flag anything unsupported by the actual page content. Constraints: - Only recommend schema supported by visible page content. - Do not recommend misleading or fake markup. - Use simple language. - Keep the answer practical. Output format: Return a table with these columns: - Schema Type - Use It: Yes or No - Why - Important Fields
How the Prompt Is Structured
"Visible Page Content" Is a Hard Rule
Google requires that schema reflect what users can see. The constraint "only recommend schema supported by visible page content" keeps the output aligned with this rule and prevents markup penalties.
"Yes or No" Forces Clarity
The binary "Use It" column kills indecision. A schema type is either a fit or it isn't. Forcing the AI to commit prevents long theoretical lists of every possible schema type.
Important Fields, Not All Fields
Asking for "important fields" prevents a 40-property dump. You end up with the minimum viable markup: the properties you need for the rich result or eligibility signal, nothing more.
"No" Rows Are as Valuable as "Yes"
The prompt explicitly asks what to avoid. That's where the risk lives — misleading Review, FAQ, or HowTo markup are common ways sites get structured-data penalties.
Example Output
| Schema Type | Use It | Why | Important Fields |
|---|---|---|---|
| LocalBusiness | Yes | Page describes a local service business with a service area and contact info. | name, address, telephone, url, openingHours, areaServed |
| Service | Yes | Page is specifically about one service (emergency plumbing), not the business overall. | serviceType, provider, areaServed, description |
| FAQPage | No | The page has no visible Q&A section to back up the markup. | — |
| Review / AggregateRating | No | No visible reviews on the page itself. Adding this would violate Google's visible-content rule. | — |
Tips for Better Results
Validate Before Deploying
Always run the AI's JSON-LD through Google's Rich Results Test and the Schema.org validator before shipping.
Add Content to Unlock Schema
If the AI says "no" to FAQPage because the page has no FAQ, add the FAQ first — then re-run the prompt.
One Primary Type per Page
Pages usually need one dominant schema type with supporting nested types — not six disconnected top-level schemas.
Ask for the JSON-LD Next
Once the type list is confirmed, a follow-up "generate the JSON-LD for LocalBusiness and Service using the fields above" produces code you can paste directly into the page.
Structured Data, Done Safely
We design schema rollouts that unlock rich results without tripping Google's misleading-markup guardrails.