schema-markup
Schema.org Structured Data
The general shape of JSON-LD and the common @type vocabulary is assumed knowledge. This skill captures only the things that are easy to get wrong: recent Google rich-result deprecations, exact magic strings, numeric constraints, and implementation gotchas.
Recent Google deprecations
Do not promise rich results for these types:
- FAQPage rich results — For Google Search, these are now limited to well-known, authoritative government and health websites. For most other sites, FAQ markup will not usually produce visible FAQ rich results.
- HowTo rich results — Deprecated in Google Search and no longer shown on desktop or mobile. Don't add HowTo markup just to chase Google rich results.
- sameAs for Knowledge Panels — Still a valid structured-data property for disambiguation and linking to official profiles, but it is not a "claim or control your Knowledge Panel" lever.
When users ask for FAQ or HowTo schema, explain these limits first so they can decide whether the markup is still worth adding.
Choosing the right type
LLMs commonly pick the wrong @type:
- Listicles / "best of" / "top 10" posts →
ItemListwith numberedListItementries (optionally wrappingProduct,Review, orSoftwareApplicationnodes). This is what triggers the numbered/carousel rich result. Defaulting toArticleorBlogPostingon a listicle is a missed opportunity.
More from rankearly/rankearly-skills
blog-creator
Umbrella skill for ANY blog-related task — research, outline, write, audit, humanize, illustrate. Use when the user mentions blog posts, outlines, drafts, blog images, or wants to audit/humanize/rewrite blog content.
14blog-image
Generate a Nanobanana Pro prompt for blog images - either a scroll-stopping cover or an explanatory in-post illustration. Use when the user asks for a "blog cover", "blog image", "post thumbnail", "illustration for my blog", "header image", or wants to create a visual for a blog post or article section.
12blog-title-generator
Generate SEO blog titles, title tags, and H1 variations for an SEO blog. Use when the user wants blog title ideas, headline options, title tag suggestions, H1 variants, or SEO/CTR title optimization for a planned or drafted blog post.
12seo-memory
Maintain a project knowledge file for SEO content creation. Use when the user shares critical context about their project — product renames, new/removed features, service changes, subproduct launches, pricing updates, audience shifts, or any factual change that SEO content should reflect. Also triggers on "update seo memory", "remember this for content", "initialize seo memory from domain", or when the user corrects a factual detail about their product/service. Even small updates matter — stale project facts in published content erode trust.
10topic-research
Expand topics into keywords or cluster a keyword library into topics and keyword clusters using RankEarly. Use when the user asks for keyword expansion, topic clustering, content clusters, topic maps, keyword research, or content planning tied to a keyword library.
10serp-gap-analysis
Analyze a live Google SERP for keyword winnability and competitor gaps. Use when the user asks for SERP analysis, real-result keyword difficulty, SEO competitor analysis, content gap analysis, or a brief or content plan for a specific keyword or query.
10