Schema markup is one of the few SEO tactics with real enforcement risk: mark up content that isn’t visible to users and Google can issue a manual action, not just ignore the tags. This prompt only proposes schema for what’s demonstrably on the page. Consider cross-checking structured data support in Rank Math Content AI before publishing.
SEO
Recommend schema markup for a page
A prompt that inspects a page's actual content before prescribing FAQ, Product, or Review schema, since applying the wrong schema type risks a manual spam action.
Works with Claude / GPT1,780 uses★ 4.4
The prompt
seo-schema-markup-recommendation
A client sells a $340 standing desk on a WooCommerce product page at [yourdomain.com/products/standing-desk-pro/] and wants "the rich snippet with stars" to show up in search. The page has 47 verified customer reviews averaging 4.6 stars, a comparison table against two competitor models, and a short Q&A section with 5 questions. PAGE URL: [yourdomain.com/products/standing-desk-pro/] PAGE CONTENT SUMMARY: [paste the actual visible page content or a detailed description] EXISTING SCHEMA (if any, paste JSON-LD): [paste here or say "none"] Reason through this like someone who has seen sites get manual actions for schema misuse: 1. Confirm which schema types are actually justified by content that's visibly on the page. Product and AggregateRating are justified here because reviews are real and visible; only recommend FAQPage if the Q&A content is genuinely visible to users on the page, not injected purely for the snippet, since Google has penalized invisible FAQ markup before. 2. Draft the Product schema JSON-LD including price, availability, and aggregateRating, using the real numbers given, not placeholder values. 3. Draft FAQPage schema only for the questions that appear as visible text, and explicitly exclude any I might be tempted to invent to pad the count. 4. Warn if this page is missing anything schema.org would need to actually be eligible (e.g. a visible price, a return policy link) rather than assuming compliance. 5. Output valid JSON-LD ready to paste into a custom HTML block, and note it should be tested in Google's Rich Results Test before publishing, since a single malformed field can invalidate the whole block.