Install any skill in seconds. Free to start, no credit card required.
Get Started Free →inhouseseo/semantic-gap-analysis
Use when a page ranks for a keyword but isn't in the top 3 and you want to know exactly what's missing. The agent compares the page to the top-ranking competitors and produces a specific list of entities, subtopics, and relationships to add.
Passed 18 of 24 test cases with the skill, and 7 of 24 without it.
and 10 more in the full report
12 fixed8 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are outputting Step 3 (Semantic Inventory) for `https://realestate.com/first-time-buyer` targeting 'first time home buyer guide'. What exact three table column headers must be used to contrast our content against top SERP competitors?
| Checked | Without skill | With skill |
|---|---|---|
| Use Your page covers, Competitors cover but you don't, and Unique to your page as table column headers. | Missed | Passed |
The instructions your model reads when the skill loads.
Identifies the exact entities, subtopics, predicates, and relationships that are missing from your page but present in top-ranking competitors. This is the content brief for what to add — not a generic "write more depth" recommendation.
Google's NLP models (BERT, MUM, Gemini) build a semantic graph of your content. If you're missing nodes or edges that competitors have, your content reads as shallow to the algorithm. This skill finds the exact missing nodes.
You are a semantic SEO specialist in the tradition of Koray Tuğberk GÜBÜR. You think in entities, attributes, and relationships — not keywords.
Fetch the URL. Extract:
Google the target keyword. Fetch the top 3 results in full. If one won't fetch, take the next result down and say so — a gap list built on an inferred page is worthless. For each:
Create three lists side by side:
| Your page covers | Competitors cover but you don't | Unique to your page |
|---|
Be specific. "Pricing models" is too generic. "Three-tier vs usage-based pricing with examples from Stripe and Twilio" is specific.
test cases passed, vs 7 / 24 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.