Have something to say?

Tell us how we could make the product more useful to you.

On Roadmap πŸ‘

Allow Custom HTML IDs (Stable Selectors) for Sections/Rows/Elements in GemPages v7

Please add the ability to set a custom, human-readable HTML ID for any Section/Row/Element (e.g., #cds-contact-form). Right now GemPages auto-generates internal IDs/classes, which makes it hard to create reliable anchor links, custom CSS/JS, and tracking. A built-in β€œCustom ID” field would be a huge workflow + UX win. Use case example: I want my contact section to have a stable ID like: #cds-contact-form So I can: Link from buttons/menus: /pages/contact-us#cds-contact-form Create β€œScroll to contact form” CTAs reliably Target the section with CSS/JS without depending on auto-generated selectors that are hard to maintain Current problem: GemPages assigns internal auto-generated selectors (e.g., .i2le03ff99d82) which are not human-readable. These selectors can become painful when: duplicating blocks/pages rebuilding sections collaborating with teammates maintaining custom CSS/JS over time We often end up using custom code or third-party apps just to achieve stable anchors and reliable targeting. Requested feature: Add an β€œHTML ID” field (and ideally also a β€œCustom selector” helper) in Advanced settings for: Section Row Column Element Requirements / behaviour: Custom ID field User can set an ID like: cds-contact-form GemPages outputs it as: id="cds-contact-form" Provide validation + auto-sanitization (lowercase, hyphens, remove invalid characters) Warn if duplicate ID exists on the same page Easy usage in the editor Show the custom ID in Layers panel (next to the element name) One-click β€œCopy selector” (copies #cds-contact-form) Optional: search/filter layers by ID Anchor link & UX improvements Support smooth scrolling (optional toggle) Allow interactions β€œScroll to element” to target custom IDs easily Improves accessibility (clear skip links / deep linking) Why this is valuable (UX + SEO + maintenance): Better UX: deep links and clear navigation paths inside long landing pages (FAQ, specs, contact form). Better maintainability: stable selectors for custom CSS/JS and analytics events. Less reliance on custom apps/code for basic site structure features. Aligns GemPages with common website-builder/editor capabilities. Note (clarity): CSS Class (.class) is great for styling groups. HTML ID (#id) is essential for anchors and unique targeting. Both are useful β€” but the missing piece is a dedicated, stable β€œCustom ID” feature.

Dima Chernyshov 2 months ago

2

πŸ’‘ Feature Requests

Dynamic Breadcrumbs (Supports Subcategories + Customizable + SEO Rich Snippets)

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.

Dima Chernyshov 2 months ago

1

πŸ’‘ Feature Requests

Improve Blog Posts for SEO with Categories, Pagination, and Social Sharing

For website and e-shop owners, having a properly structured blog is extremely important for SEO and achieving better Google rankings. However, your current blogging functionality is not presented properly. At the moment, you only offer the possibility to create a single article page, but there is no complete blog structure. 1. You should create a proper blog article list page. This page should allow categories to be added, so visitors can either β€œView All Articles” or filter and view articles under specific topics. 2. Please add a pagination feature for the blog list. The page should not rely on endless scrolling. For example, visitors could view 9 articles per page and navigate by selecting page numbers (1, 2, 3, etc.). Alternatively, at minimum, a β€œLoad More” button could be added - but pagination would be much more desirable. 3. Articles should also include built-in social sharing options and the ability to copy the article link. This feature was created for me upon request by your support team, but it should not be treated as a custom request. Social sharing is a standard feature that is expected on blog articles 4. As a nice-to-have (lower priority) feature, it would also be beneficial to allow readers to leave comments under articles and to react with likes or hearts. 5. Also, under each article there should be the possibility to add a carousel featuring suggested content - for example, a β€œRelated Articles” section encouraging readers to continue reading, or a product carousel highlighting relevant products from the e-shop.

GutBrush 2 months ago

12

πŸ’‘ Feature Requests