GemFeedback

Trending requests
Run a CRO loop: find where a page loses buyers, test a fix, build the variantIdea · ▲ 1Turn plain product photos into a full set of store-ready imagesIn progress · ▲ 1Make and schedule slideshow posts across several social accountsIdea · ▲ 1Find short-form posts trending in my niche and turn them into briefsIdea · ▲ 1
Latest updates
Watch competitors' ads and flag the new long-running winnersShipped · 5 Oct 2026need helpShipped · 25 Sept 2026Getting Rid of Mobile popupShipped · 22 Sept 2026
Sign in
← All requests

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

Planned 2

in Feature request · Seller 48 ·

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.

Sign in to follow

Comments 2

  • GemPages teamTeam

    Hi @Seller 48 Thanks for the detailed proposal. Currently, GemPages v7 supports Custom CSS Classes for styling (you can read more about it here: https://help.gempages.net/articles/add-extra-css-class-to-element), but it does not yet support assigning a custom ID to sections, rows, columns, or elements. Stable IDs are useful for anchor links, scroll-to-section CTAs, and reliable CSS/JS targeting. Your suggestion to add a Custom ID field in Advanced settings makes sense. We can take this into consideration and investigate how it could be stored in the element data structure, so the ID remains st

    Show moreShow less

    Hi @Seller 48 Thanks for the detailed proposal. Currently, GemPages v7 supports Custom CSS Classes for styling (you can read more about it here: https://help.gempages.net/articles/add-extra-css-class-to-element), but it does not yet support assigning a custom ID to sections, rows, columns, or elements. Stable IDs are useful for anchor links, scroll-to-section CTAs, and reliable CSS/JS targeting. Your suggestion to add a Custom ID field in Advanced settings makes sense. We can take this into consideration and investigate how it could be stored in the element data structure, so the ID remains stable when elements are duplicated or reused. Best regards, Lucas

    ▲ 2
    • Seller 48

      It could just add the #, for ex. .form_section-copy1, copy2, etc… And thank you!

      ▲ 1
Sign in to GemFeedback