If GemPages released a built-in Breadcrumbs element that supports multi-level “subcategory/hub” navigation and outputs proper structured data (JSON-LD), it would be a killer feature for UX + SEO.
Today, most stores need custom code/apps to get good breadcrumbs—especially when using landing pages/hubs + Shopify collections—while GemPages pages would benefit from a native solution.
Use case example:
Home → All Building Materials (GemPages landing page / hub) → Decking (Shopify Collection) → Product page / Article / etc.
Why this matters:
UX / Navigation:
Breadcrumbs reduce bounce rate and help users orient quickly in large catalogs.
They add a clean “back to broader category” path without relying on the main menu.
Especially important for stores with hubs, guides, and multiple entry points (beginner vs advanced shoppers).
SEO / Rich Results:
Proper breadcrumb structured data can generate Breadcrumb rich snippets in Google.
Better internal linking structure and clearer site hierarchy signals.
Current problem:
To achieve this today we need custom code or third-party apps (e.g., “Breadcrumbs & Categories” type apps).
Those solutions often don’t work well (or require extra dev work) specifically for GemPages landing pages/hubs.
The result: breadcrumbs become inconsistent, fragile, and harder to maintain.
Requested solution:
A) New “Breadcrumbs” element in GemPages v7:
Works on Home / Landing / Page / Product / Collection templates (where applicable)
Automatically detects context:
Product page: Home → Collection/Hub → Product
Collection page: Home → Hub → Collection
Landing hub page: Home → Hub (and optionally deeper levels)
B) Subcategory / Hub support (critical):
Allow defining a hierarchy that includes GemPages landing pages as “category hubs”
Ability to manually map:
Hub page → related Shopify collections
Collection → parent hub
Product → preferred collection + parent hub
C) Customization options:
Separator style
Show/hide Home, current page, etc.
Custom labels per node
Design controls (typography, spacing, responsive behavior)
D) SEO requirements (must-have):
Output valid BreadcrumbList schema (JSON-LD)
Ensure it’s index-safe and consistent across pages
Avoid duplicate/conflicting structured data if theme/app already outputs breadcrumbs (toggle to enable/disable)
Bonus (nice-to-have):
Option to choose the “primary collection” for a product’s breadcrumb when a product belongs to multiple collections.
Integration with Shopify metaobjects/metafields for defining parent/child relationships at scale.
Why this is a competitive advantage:
A robust, SEO-friendly breadcrumbs system that works seamlessly with GemPages hubs + Shopify collections would reduce reliance on apps/custom code and make GemPages more “full-stack” for serious stores focused on SEO and information architecture.
Please authenticate to join the conversation.
In Review
💡 Feature Requests
About 5 hours ago

Dima Chernyshov
Get notified by email when there are changes.
In Review
💡 Feature Requests
About 5 hours ago

Dima Chernyshov
Get notified by email when there are changes.