Defines how Hibu One supports catalogs of products, rentals, or inventory using blog-based listing pages. Covers client management, tag-based filtering, template restrictions, and limits such as external checkout only and locked listing layouts. Search terms: product listings, inventory pages, catalog listings.

Meta description tags define the supporting summary that appears beneath a page title in search results. This guideline explains Hibu One standards for writing effective meta descriptions, including recommended length, front-loading key messaging, sentence-case formatting, and page-type variations.

Title tags define the primary headline of a page and serve as the clickable title in search results. This guideline outlines Hibu One standards for writing titles, including the 55-character target, keyword placement, business name rules, and page-type formatting variations.

Header Background Imagery: The header must remain clean, readable, and brand-forward. Solid colors, subtle gradients, and low-detail textures are supported. Busy photos, people, text, or high-contrast imagery that interfere with logo or navigation are not allowed. Readability and usability always come first.

Taglines (brand slogans or statements) are not permitted in the header to protect layout clarity and mobile performance. They may be placed in the hero, section headlines, image captions, or integrated naturally within body copy across homepage, service, about, and service area pages.

Additional Header Phone Numbers replace the single header number with a Contact/Call button that opens the pre-built Multi-Phone Pop. It supports up to 10 numbers, displays in two columns on desktop/tablet and one column on mobile.

Hibu One supports one button in the top right of the desktop header. The default CTA may be swapped for a client-requested action or HTML embed. It does not appear on tablet and is not shown on mobile by default. Third-party code may not match site styling and will not be modified by Hibu.

Hibu One Homepage and CAT Layout Standards

Hibu One Website Design & Rebuild Policy defines how sites are rebuilt using proven, mobile-first layouts that prioritize conversion, SEO, and page speed. It explains why custom or legacy designs aren’t replicated and outlines the standards that protect performance, consistency, and long-term results.

Page Removal & Deactivation (Post-Launch) outlines the required process for retiring live pages without deleting them. Pages must be renamed, removed from navigation, set to draft, moved within the root structure, and redirected to prevent 404 errors and protect SEO integrity.

During site build, unused template pages must be moved to XTRA Pages and unpublished or deleted if unsupported. FAQs and Request Form pages must be set to Draft to prevent indexing. SAPs must be nested under Serving Area. The live page tree should reflect only intentional, approved structure.

Every Hibu One Smart Site includes a Social Image (Open Graph or OG image) that controls how links appear when shared on social media and messaging apps. Images must meet size and ratio standards and clearly represent the business for consistent, professional previews.

Text-heavy promotional images often fail on mobile when scaled from desktop widths. Landscape graphics become unreadable, and portrait layouts still reduce clarity. Mobile-friendly versions are required for hero use; otherwise, images must be hidden or placed in supporting sections.

This definition explains how third-party apps integrate into Hibu One Smart Sites using Duda’s client-side capabilities. It outlines supported embed methods, code types, and platform constraints to clarify what is technically possible without backend or plugin-based integrations.

This definition outlines commonly recommended third-party widgets that embed cleanly with Hibu One Smart Sites. It provides Sales and teams with a centralized reference for scheduling, chat, forms, maps, calculators, reviews, and limited real estate tools, with clear ownership expectations.

Clarifies the differences between Catalog Overview Pages and Inventory Pages, including when to use each, how they work together, and the shared 50-card site limit. Helps teams choose the right structure and avoid misusing categories or item listings.

Defines required introduction content for homepage, category, About Us, location profile, and service area pages. Establishes purpose, scope, placement, and intent to support SEO, clarity, and trust without duplicating deeper page content.

Defines how BBB logos, text references, and accreditation seals may be used on Hibu One Smart Sites. Covers verified accreditation requirements, allowed placements, linking rules, use of dynamic seal code, and restrictions to prevent misleading endorsement or ratings.

Google Tools connect a Hibu One Smart Site to services like Analytics, Ads, Tag Manager, and Search Console for tracking and performance insights. Clients provide their own IDs, which are added through the Google Tools tab in Duda. Hibu does not create or manage Google accounts but supports multiple tracking codes runn

Widgets are small code-based tools that add interactive features like chats, reviews, or forms to a Hibu One Smart Site. Hibu supports client-supplied code through approved HTML areas but does not create, debug, or manage third-party widgets. Only secure, HTTPS-based scripts are allowed, and full IDX/MLS integrations a

Password-protected pages restrict access using a single shared password and are available by request. These pages count toward total page limits, must be set to no index, do not support unique logins, and cannot be applied to dynamic or anchored pages.

Page types define how a site’s content is structured and accessed through navigation tiers. Tier 1 holds primary pages like Home, Category Landing Pages, key Core, and Utility pages. Tier 2 contains supporting Core or Utility subpages.

Beginning December 3, 2025, all new Hibu One Smart Sites use the dynamic Mega Menu widget, which reduces manual setup, enforces correct page structure, and supports up to five balanced columns. Older sites continue to use the legacy version, which requires manual curation of CATs, children, and standalone pages.

A hidden page is available only by direct URL and not linked in site navigation. These pages count toward the site’s total page count and must include full content and design. When hidden, they’re set to “no index” so they don’t appear in search results but remain part of the sitemap.

Defines how Hibu One Smart Sites handle inventory-style content, including page structure, item limits, naming rules, descriptions, images, CTAs, and when to use a catalog overview page instead of full inventory.

This guide explains how to write and format title tags and meta descriptions for pages that fall outside standard Hibu One Smart Site patterns, providing consistent templates, examples, and rules for accurate, compliant metadata across unique page types.

Hibu One sites in medical, healthcare, insurance, and regulated legal fields cannot use service drop-downs or message fields to prevent collecting sensitive data. See Sensitive Restrictions Data and Prohibitive and Restricted Verticals.

Auto-responder emails are optional, client-requested confirmations sent after form submissions. They require client-provided subject and message content, apply only to specific form types, use a no-reply sender address, and require updating the site’s hidden, no-index Thank You page.

This guideline defines how form emails are routed, how subject lines and titles are used, and when exceptions apply. It clarifies default dashboard routing, disconnected form behavior, and rules for one-off email recipients to ensure consistent, accurate submissions.

Defines what content belongs on Homepage and Category Landing Pages to support conversion, clarity, and AI discovery. Emphasizes company-level messaging, trust signals, and intentional placement while keeping service-specific detail on dedicated pages.

Springtime Cookies Widget — consent management tool that helps sites meet state privacy laws and build user trust. Provides cookie banners that let visitors manage consent for analytics, functional, and marketing cookies. Automatically included on all sites; removal requires a request.

Fair Use Policy — guidelines that define reasonable build limits for content included in a standard Hibu One Smart Site. Covers maximum quantities for inventory items, photo galleries, PDFs, and custom forms, along with image quality expectations and transparency requirements to ensure fairness, consistency, and high v

The Header Navigation is the main menu bar that guides visitors to a site’s key pages. Built with the Navigation Links widget, it follows Hibu’s global design and accessibility standards for clarity and consistency.

Defines the structure, layout types, and allowed elements for the Hibu One hero section, including standard heroes, heroes with forms, and thin heroes. Covers CTAs, layout variations (centered, left-aligned, offset), media rules, and conversion-focused design standards.

Dynamic Rows — previously used for rotating announcements or promotions — are no longer supported. All updates and alerts are now managed through a static Alert Banner, ensuring faster load times, stable layouts, and improved SEO performance.

Countdown Widget — used to display a real-time timer for upcoming events, promotions, or launches. Includes rules for appropriate use, placement, timing, and expiration handling to maintain accuracy, site performance, and visual consistency.

Buttons — primary interactive elements that guide users toward key actions like contacting a business or requesting a quote. Includes design, color, and accessibility standards, contrast and theme rules, corner radius options, and best practices for clear, action-oriented button text.

Before / After Widget — used to display side-by-side image comparisons that highlight visual transformations or project results. Includes best practices for image quality, setup, and labeling to ensure clear, professional comparisons that enhance credibility and support conversions.

Click-to-Call is supported on both desktop and mobile versions of Hibu One Smart Sites, allowing visitors to easily reach the business. Buttons may appear in Heroes, Callouts, Coupons, and Footers. Phone numbers must match the primary number in Business Information and connect through Yext.

Favicons and Open Graph images help strengthen a site’s branding and visibility. Each Hibu One Smart Site includes a favicon by default and a standard OG image for social sharing. Clients can supply their own icons or images if they meet size and format requirements.

This definition outlines how geographic information appears across headers, hero H2s, title tags, meta descriptions, and body copy. It defines rules by location count, service areas, and Additional Locations, with strict Yext alignment and clear examples for each scenario.

Text should use color combinations that produce a green contrast indicator. Designers may override red only when the contrast ratio is between 3.0 and 4.49 and still readable. Any text below 3.0 is not allowed under any circumstance.

Images uploaded to Hibu One Smart Sites are automatically optimized by Duda to improve load speed, performance, and visual quality across devices. This includes resizing, compression, modern format delivery, and device-specific optimization, with no manual setup required.

Defines how PDFs and downloadable files are named in Hibu One to improve organization, usability, and search visibility. Filenames must lead with file subject, place the business name last, follow formatting standards, and align with Media Manager behavior for easy scanning.

Schema — structured data that helps search engines understand and display site content accurately. Includes default schema types for websites, local businesses, FAQs, breadcrumbs, blogs, videos, and reviews, with rules for optional client-supplied schema to ensure accuracy and relevance.

Page URLs (Slugs) — rules for creating clear, consistent, and search-friendly web addresses. Covers naming conventions, formatting standards, and structure for service area and GEO pages to ensure accuracy, readability, and alignment with site navigation.

Title tags and meta descriptions control how pages appear in search results and act as a mini ad for the page. This guideline defines 2026 character standards (55 ideal for titles, 150–160 for metas), front-loading strategy, uniqueness rules, and conversion-first expectations.

Copy, Tone, and Audience Fit — standards for refining AI-generated content to ensure accuracy, clarity, and conversion focus. Defines expectations for tone, formatting, and CTAs, along with editing best practices that align copy with the 3-30-3 Rule and each site’s brand voice.

Badges and accreditation logos are placed in the footer to maintain a consistent, professional look. Each must include alt text, use a uniform size, and meet quality standards. If a logo or badge is missing or low-quality, the best available version is used, or a note is added if unavailable.

Header Background Imagery: The header must remain clean, readable, and brand-forward. Solid colors, subtle gradients, and low-detail textures are supported. Busy photos, people, text, or high-contrast imagery that interfere with logo or navigation are not allowed. Readability and usability always come first.

Taglines (brand slogans or statements) are not permitted in the header to protect layout clarity and mobile performance. They may be placed in the hero, section headlines, image captions, or integrated naturally within body copy across homepage, service, about, and service area pages.

Additional Header Phone Numbers replace the single header number with a Contact/Call button that opens the pre-built Multi-Phone Pop. It supports up to 10 numbers, displays in two columns on desktop/tablet and one column on mobile.

Hibu One supports one button in the top right of the desktop header. The default CTA may be swapped for a client-requested action or HTML embed. It does not appear on tablet and is not shown on mobile by default. Third-party code may not match site styling and will not be modified by Hibu.

Defines the structure, layout types, and allowed elements for the Hibu One hero section, including standard heroes, heroes with forms, and thin heroes. Covers CTAs, layout variations (centered, left-aligned, offset), media rules, and conversion-focused design standards.

Dynamic Rows — previously used for rotating announcements or promotions — are no longer supported. All updates and alerts are now managed through a static Alert Banner, ensuring faster load times, stable layouts, and improved SEO performance.

Countdown Widget — used to display a real-time timer for upcoming events, promotions, or launches. Includes rules for appropriate use, placement, timing, and expiration handling to maintain accuracy, site performance, and visual consistency.

Buttons — primary interactive elements that guide users toward key actions like contacting a business or requesting a quote. Includes design, color, and accessibility standards, contrast and theme rules, corner radius options, and best practices for clear, action-oriented button text.

Before / After Widget — used to display side-by-side image comparisons that highlight visual transformations or project results. Includes best practices for image quality, setup, and labeling to ensure clear, professional comparisons that enhance credibility and support conversions.

Click-to-Call is supported on both desktop and mobile versions of Hibu One Smart Sites, allowing visitors to easily reach the business. Buttons may appear in Heroes, Callouts, Coupons, and Footers. Phone numbers must match the primary number in Business Information and connect through Yext.

Text should use color combinations that produce a green contrast indicator. Designers may override red only when the contrast ratio is between 3.0 and 4.49 and still readable. Any text below 3.0 is not allowed under any circumstance.

This guide defines how icon-based copy sections must remain visually balanced across layouts. It explains why incomplete rows create visual disruption and outlines rules for adjusting layouts so sections look intentional, consistent, and polished.

Definition The Call or Text feature (aka Textable RCF) is a Hibu One Smart Site conversion element that gives visitors a choice between calling the business or sending a text message. When activated, it opens a pop-up offering two clear paths — Call Us or Text Us —using the visitor’s native phone or messaging application. This functionality increases convenience, improves mobile engagement, and supports consumer preference for text-based interactions. Hibu One call-tracking numbers are textable only when texting is enabled for the RCF number at the time the number is provisioned. (updated 02/09/26)