google-search-console
When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search…
When the user wants to add, optimize, or audit breadcrumb navigation. Also use when the user mentions "breadcrumbs," "breadcrumb trail," "breadcrumb nav," "breadcrumb links," "path navigation," "site breadcrumb," "BreadcrumbList schema," "location-based breadcrumb,"
$ npx -y skills add kostja94/marketing-skills --skill breadcrumb --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/breadcrumbContext preview
The summary Claude sees to decide when to auto-load this skill.
When the user wants to add, optimize, or audit breadcrumb navigation. Also use when the user mentions "breadcrumbs," "breadcrumb trail," "breadcrumb nav," "breadcrumb links," "path navigation," "site breadcrumb," "BreadcrumbList schema," "location-based breadcrumb,"
name: breadcrumb-generator description: When the user wants to add, optimize, or audit breadcrumb navigation. Also use when the user mentions "breadcrumbs," "breadcrumb trail," "breadcrumb nav," "breadcrumb links," "path navigation," "site breadcrumb," "BreadcrumbList schema," "location-based breadcrumb," "attribute-based breadcrumb," "site hierarchy display," "add breadcrumbs," or "breadcrumb SEO." For BreadcrumbList JSON-LD, use schema-markup. For main nav, use navigation-menu-generator. metadata: version: 1.2.0
Guides breadcrumb implementation for SEO, UX, and GEO. Breadcrumbs show users their location in the site hierarchy and help search engines understand content taxonomy. Well-implemented breadcrumbs can increase CTR by 20–30%, reduce bounce rates by up to 30%, and strengthen internal linking.
**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.
| Type | Use case | Recommendation | |------|----------|----------------| | **Location-based** | Reflects site hierarchy (Home > Blog > SEO > Page) | **Recommended** — most SEO-friendly; clear structure | | **Attribute-based** | Shows product attributes (Home > Electronics > Phone > iPhone 15) | E-commerce; product classification | | **Path-based** | Shows user's browsing path | **Avoid** — different users, different paths; can cause confusion |
**Default**: Use location-based for most sites. Use attribute-based for e-commerce product pages.
**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for site structure and key pages.
Identify: 1. **Site structure**: Hierarchy depth (e.g., Home > Category > Subcategory > Product) 2. **Page types**: Blog, e-commerce, docs, etc. 3. **Multi-category**: Products in multiple categories—need canonical path
| Practice | Guideline | |----------|-----------| | **Depth** | 3–5 levels optimal; avoid very long trails | | **Anchor text** | Keyword-rich, human-readable; descriptive | | **Consistency** | Same pattern across all pages (blog, category, product) | | **Canonical path** | For items in multiple categories, define one canonical breadcrumb to avoid diluted link equity |
See **schema-markup** for BreadcrumbList requirements, JSON-LD example, and multiple paths. Schema must match visible breadcrumbs exactly.
| Practice | Guideline | |----------|-----------| | **Position** | Below nav bar or above page title; top of content area | | **Visual** | Smaller font, lighter color; avoid competing with main content | | **Separator** | Clear separator (>, /, ›); consistent across site | | **Naming** | Match page title or nav menu; concise, descriptive |
| Practice | Guideline | |----------|-----------| | **Mobile** | Tappable; short, readable text; high contrast | | **Long trails** | Horizontal scroll container rather than truncating | | **Current page** | Last item non-linked; use `aria-current="page"` | | **Screen readers** | `nav` with `aria-label="Breadcrumb"`; proper landmark |
<nav aria-label="Breadcrumb">
<ol itemscope itemtype="https://schema.org/BreadcrumbList">
<li itemprop="itemListElement" itemscope itemtype="https://schema.org/ListItem">
<a itemprop="item" href="https://example.com/"><span itemprop="name">Home</span></a>
<meta itemprop="position" content="1" />
</li>
<li itemprop="itemListElement" itemscope itemtype="https://schema.org/ListItem">
<a itemprop="item" href="https://example.com/category/"><span itemprop="name">Category</span></a>
<meta itemprop="position" content="2" />
</li>
<li itemprop="itemListElement" itemscope itemtype="https://schema.org/ListItem" aria-current="page">
<span itemprop="name">Current Page</span>
<meta itemprop="position" content="3" />
</li>
</ol>
</nav>**Implementation**: Generate BreadcrumbList from route segments or page metadata. Ensure `item` URLs are absolute. Use `next-seo` BreadcrumbJsonLd or custom component. See **schema-markup** for JSON-LD structure.
| Site type | Use case | |-----------|----------| | **E-commerce** | Category > Subcategory > Product | | **Blog** | Home > Blog > Category > Post (see **article-page-generator** for article page structure) | | **Docs** | Home > Docs > Section > Page | | **Large sites** | Any site with 3+ level hierarchy |
**Skip** on flat sites (e.g., single-page, 1–2 level depth).
**Deep pages**: For 6+ levels, consider omitting middle levels; show only the most important categories to avoid clutter.
| Platform | Options | |----------|---------| | **WordPress** | Yoast SEO, Rank Math, Breadcrumb NavXT | | **Next.js** | next-seo BreadcrumbJsonLd, custom from route segments | | **Shopify, Drupal, Joomla** | Built-in or plugin support |
| Error | Fix | |-------|-----| | Relative URLs in schema | Use absolute URLs (https://) | | Schema doesn't match visible trail | Keep schema
Markdown skill library for AI agents - SEO, content, pages, paid ads, channels, strategies. Add project context + skills; your agent delivers tailored, production-ready output. Works with Cursor, Claude Code, OpenClaw, Lovable, and any AI that reads markdown.
Repo: kostja94/marketing-skills
When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search…
When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions…
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI…
When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic,"…
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4,"…
When the user wants to promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker,"…