glossary page generator
When the user wants to create, optimize, or audit glossary page content and structure. Also use when the user mentions "glossary," "definitions," "terminology," "industry terms," "glossary page," "term definitions," "vocabulary," "glossary SEO," or "definition page." For definitions at scale, use programmatic-seo.
Becerinin kendisi
# Pages: Glossary Guides glossary page structure, content, and internal linking for SEO. **When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Initial Assessment **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for industry terms and customer language. Identify: 1. **Domain**: SEO, marketing, tech, industry-specific 2. **Audience**: Beginners, practitioners, both 3. **Content volume**: Number of terms ## Best Practices ### Structure | Element | Purpose | |---------|---------| | **Alphabetical index** | A-Z or by category | | **Term + definition** | Clear, concise explanation | | **Related terms** | Cross-links within glossary | | **Internal links** | Link to relevant blog/content | | **Search** | Help users find terms | ### Definition Quality - **Clear**: Jargon-free where possible - **Concise**: One paragraph typical - **Context**: How term is used in your domain - **Examples**: When helpful ### Internal Linking Strategy - **Anchor text**: Descriptive, keyword-rich; avoid "click here" - **Variation**: Mix anchor phrases; don't repeat identical text - **Placement**: Higher on page = more valuable - **Relevance**: Link to most valuable next content - **Avoid orphans**: Ensure every term page has inbound links ### SEO Benefits - **Topic clusters**: Glossary as hub; links to and from pillar content; see **content-strategy** - **Long-tail**: Definition queries, "what is X" - **Crawlability**: Reduces depth; distributes authority - **User engagement**: Helps users understand; keeps them on site ### Maintenance - **New terms**: Add as content expands - **Audit links**: Periodically check internal links - **Update**: Keep definitions current ## Output Format - **Structure** (index, layout) - **Term** template (definition format) - **Internal linking** plan - **SEO** metadata - **Schema**: DefinedTerm or similar if applicable ## Related Skills - **url-slug-generator**: URL slug for glossary terms (e.g. /glossary/term-slug); 3-5 words - **internal-links**: Glossary is internal linking hub - **content-strategy**: Glossary supports content clusters - **blog-page-generator**: Link between glossary and blog - **title-tag, meta-description, page-metadata**: Glossary page metadata
Nasıl kurulur
Claude Code / Claude Desktop 1. Create a folder named after the skill inside your skills directory: - Claude Code: `~/.claude/skills/<skill-name>/` - A project-local skill: `<project>/.claude/skills/<skill-name>/` 2. Save the text below as `SKILL.md` in that folder, keeping the `---` frontmatter block at the top — the `name` and `description` fields are what make the skill discoverable. 3. Restart Claude Code, or run `/skills` to confirm it is listed. The skill loads only when its `description` matches what you are doing, so a precise description matters more than a long body.
Sende işe yaradı mı?
Buraya yazmak için giriş yapın.Nereden geldi
2025 kostja94