← DidYouSEOCONTENT HISTORY
WHAT CHANGED
Update to DidYouSEO
Snapshot Nov 6, 2026 · 07:21 UTC · version 1.1.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save DidYouSEO and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Find the long, specific questions people search before they reach a site (8+ word and question-word queries in Google Search Console) and draft a short direct answer for the page that already ranks. Use when the user asks what questions people search, what to write next, how to get cited in AI answers or Google AI Overviews, or wants answer-engine (AEO) ideas from their own data. Requires the DidYouSEO MCP connector with Search Console connected.",
"included_files": [],
"name": "long-question-answers",
"skill_md_contents": "---\nname: long-question-answers\ndescription: Find the long, specific questions people search before they reach a site (8+ word and question-word queries in Google Search Console) and draft a short direct answer for the page that already ranks. Use when the user asks what questions people search, what to write next, how to get cited in AI answers or Google AI Overviews, or wants answer-engine (AEO) ideas from their own data. Requires the DidYouSEO MCP connector with Search Console connected.\n---\n\n# Long questions to answers\n\nLong queries are the same questions people ask ChatGPT. When a page shows for one but gets no clicks, a short direct answer at the top of that page is usually the fastest fix.\n\n## Tools\n\n- `get_search_console_keywords` (website, days=90) - queries with clicks, impressions, CTR and average position.\n- `analyze_meta_tags` (url) - title, description and headings of the page you will change.\n\n## Steps\n\n1. Call `get_search_console_keywords` with `days: 90`.\n2. Keep two kinds of query:\n - 8 or more words (regex `^(?:\\S+\\s+){7,}\\S+$`)\n - starting with a question word: how, what, why, when, which, who, where, can, does, do, is, are, should, will\n3. Drop branded queries and junk such as `keyword-xxxx` or queries that are mostly another site's domain name.\n4. Group near-duplicates into one cluster (\"how to find keywords on a web page\", \"how do i search keywords on web page\"). Sum impressions and clicks per cluster.\n5. Rank clusters by impressions where clicks are 0 or CTR is under 1%. Take the top 5.\n6. Note any query that starts with `context:` or contains `question:`. Those are AI assistants searching on someone's behalf. Report them separately; they show what AI tools look you up for.\n7. The keyword tool does not say which page ranks. For each cluster, name the most likely page and ask the user to confirm it in Search Console (Performance, click the query, then the Pages tab). Call `analyze_meta_tags` on the confirmed page.\n8. For each cluster, draft:\n - a 40-60 word answer that starts by restating the question and answers it in the first sentence, to go first on the page\n - one FAQ question in the searchers' exact words, with a 2-3 sentence answer\n9. Never suggest a new page when an existing page already shows for the cluster.\n\n## Output format\n\nA table: cluster, example query, impressions, clicks, average position, page. Then the drafted answer and FAQ entry for each of the top 5. Then the AI-assistant searches, if any.\n\nEnd with: \"Add the answer as the first paragraph, update the page's date, and re-check the cluster in 3 weeks.\"\n\n## Limits\n\n- On the Free plan the Search Console tool returns a short preview. Work with what it returns and say the list may be incomplete.\n- If a tool says \"Daily limit reached\", stop calling page tools, tell the user the limit resets at 00:00 UTC, and finish with the data you have.\n- Don't mention prices or upgrades. If the user asks how to get more, say plan details are on didyouseo.com.\n"
}SHA-256 of public snapshot: c3582deb50e175c54600bbc2437ae55d057f8d3ac4e4f3444b8dfb4773eec32f