Find a gap in the search results before you write
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Methods
Paste into a general LLM and find a gap in the search results before you write.
LLMPrompt
Prompt
Copied 0
Act as an expert SEO strategist and Google SERP analyst. Target keyword: [KEYWORD] My website: [URL] Google’s top 10 results: [PASTE URLS] Analyze the search results and identify opportunities for a smaller niche website to compete. Your analysis should include: Search Intent: What exactly is the searcher trying to accomplish? Are the ranking pages satisfying that intent? Competitor Weaknesses: Examine each ranking page. Identify missing information, outdated content, shallow explanations, and unanswered questions. Content Gaps: Find 5–10 specific things a new article could provide that existing results don’t adequately cover. SERP Opportunities: Identify weaker results, forums, Reddit threads, or pages that don’t fully address the query. Explain what they reveal about the opportunity. Unique Angle: Recommend 3 differentiated article angles with a realistic reason someone would prefer each over existing results. Original Value: Identify what firsthand research, photos, measurements, comparisons, or tools would make the article genuinely more useful. Ranking Feasibility: Score the opportunity out of 20 based on search intent, competition, content gaps, original advantages, and relevance to my website. Article Blueprint: Recommend a title, structure, key questions to answer, and the evidence needed before publishing. Final Verdict: Should I pursue this keyword, target a narrower variation, or skip it entirely? Explain why. Important: Use actual search results and page content you can access. Don’t invent traffic estimates, rankings, competitor weaknesses, or keyword data. Clearly identify anything you couldn’t verify.
No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/find-a-serp-gap-before-writing - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "find-a-serp-gap-before-writing",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}