hibu-test

Blog Post Migration

Thu, 23 Apr 2026 18:27:07 GMT

Blog Post Migration

Definition

Blog Post Migration is the process of importing existing blog content from a client's previous website into Hibu One using an RSS feed or XML scrape. This is not a manual rebuild. Content is pulled from the source and imported into Hibu One's blog structure, where it conforms to Hibu One design standards automatically.

Import Methods

The following three methods must be attempted in order. Move to the next method only when the previous method fails. Do not combine methods.

Blog Overview: At-a-Glance

Effective Date: April 23, 2026 Last Updated: April 23, 202 6

Hibu Policy

When a client has an existing blog that needs to be brought into Hibu One, we will import the content using Duda's built-in Import Blog Post tool or, when that is not possible, through an Operations Support ticket for XML scrape.

We do not manually create or rebuild blog posts. All blog content must be imported through one of the three methods described in this article, tried in order.

There is no fixed limit on the number of posts we will import. We import whatever the feed or scrape returns. Some blog platforms cap the number of posts their feed exposes (Duda's import tool supports a maximum of 300 posts per import). If the source feed returns fewer posts than the client's blog contains, that is the final count. We will not supplement a partial import with a second method to capture remaining posts.

All imported content automatically conforms to Hibu One Smart Site design standards. The original blog's layout, styling, and visual presentation will not be recreated or matched. Every imported post will look like a Hibu One blog post.

All imported posts arrive in Hibu One in an unpublished (draft) state. They must be reviewed and published individually.

Method 1: Direct URL Import

Enter the client's blog URL directly into Duda's Import Blog Post tool. If Duda can locate and read a valid feed from the URL, the import will begin automatically.
This is the fastest path and must be attempted first.
If Method 1 fails , proceed to Method 2.

Method 2: Find the RSS or Blog Feed in Page Source

If the direct URL does not work, the feed URL may be embedded in the page source code. This method requires locating that URL manually.

How to find the feed URL (Chrome on Windows):

Open the client's blog page in Chrome.
Press Ctrl+U to open the page source.
Press Ctrl+F to open the search bar within the source code.
Type rss and press Enter.
If a match is found, look for a URL that contains "rss." It will appear inside the source code as part of a link reference. Examples of what an RSS feed URL looks like:
https://joeshvac.com/feed/rss2
https://joeshvac.com/blog/rss.xml
https://joeshvac.com/rss
If no results are found for "rss," clear the search and type feed instead. Press Enter.
If a match is found, look for a URL that contains "feed." Examples:
https://joeshvac.com/feed/
https://joeshvac.com/blog/feed
https://joeshvac.com/feed.xml
Copy the full feed URL and paste it into Duda's Import Blog Post tool.

If Method 2 fails (no feed URL is found in the source, or the URL found does not produce a successful import), proceed to Method 3.

Why Methods 1 and 2 Fail

There are specific reasons automated import methods do not work for every client site:

The client does not have a real blog. Some websites present standalone pages styled to look like blog posts, but there is no blog platform behind them. These pages do not generate an RSS or Atom feed because no feed exists. There is nothing to import.
The blog platform does not generate a standard feed. Not all platforms produce RSS or Atom feeds by default. Some require manual configuration that the client never enabled.
The feed is password-protected or blocked. Some hosting configurations restrict access to the feed URL, preventing external tools from reading it.
The feed is malformed or empty. The feed exists but contains errors, unsupported characters, or no content, causing the import to fail.

When any of these conditions exist, Method 3 (Operations Support ticket) is the required path.

What Imports

When importing blog content via RSS or scrape, the following elements are supported:
Text content (H1, H2, H3, paragraphs)
Post title, post URL/slug, author, and publish date
Meta titles and meta descriptions, when available
Content limitations:
Images, videos, and embedded HTML may not transfer correctly. Whether these elements import successfully depends on the source platform.
Styling, layout, and visual presentation from the original site will not carry over.
All imported content automatically conforms to Hibu One Smart Site design standards to ensure consistency, performance, accessibility, and mobile responsiveness.

Post-Import Review

All imported posts arrive in Hibu One in unpublished (draft) state. The person responsible for the import — or the person updating the site after a scrape — must review and publish each post individually.
Before publishing each post:
Check for broken or missing images. Imports and scrapes do not always bring in every image from the source. A missing image will display as a broken image indicator in the post editor.
If an image is missing or broken, remove it from the post. Do not attempt to source or re-upload the original image.
Confirm post content is intact and readable.

IMPORTANT - Do not bulk-publish imported posts. Each post must be reviewed individually before it is published.

Method 3: File a Ticket for XML Scrape

If Methods 1 and 2 both fail, file a ticket for Operations Support to scrape the content and push it into the site.
Ticket details:
Filed with: Operations Support
Topic: Website Build Concern
Required information: Business ID and the URL the blog content needs to be pulled from
Operations Support will scrape the content from the source site and push the posts into the Hibu One blog.
Posts will arrive in unpublished (draft) state.

Related Services (Right Gutter Element)

Wed, 01 Apr 2026 21:23:58 GMT

Internal Page Linking

Hibu Policy

The Related Services element is a standard component included by default on all core service pages. It appears within the right gutter and provides internal links to closely related services to support user navigation and on-page SEO.

This element must be included by default. It may only be removed or repositioned if explicitly requested by the client. Any deviation from the default must include clear communication of the impact to both user experience and search performance.

Definition

The Related Services element is a grouped list of internal service links displayed within the right gutter of a core service page, intended to connect users to relevant adjacent services.

Purpose / Why It Matters

This element serves two primary functions:

User Navigation Support - Provides immediate access to alternative or related services, allowing users to refine their intent without leaving the page or relying on primary navigation.
Internal Linking for SEO - Strengthens the internal linking structure across service pages, improving crawlability, topical relevance, and overall on-page optimization.

Together, these functions improve both usability and search performance.

Rules & Guidelines

Inclusion & Placement

Included by default on all core service pages
Positioned by default at the bottom of the right gutter
May be repositioned within the right gutter (e.g., above or below reviews) only if explicitly requested by the client
Must contain only internal service links relevant to the page and its associated category

Content Requirements

Links must be directly related to:
The current service page, or
The broader category service page it belongs to
Do not include unrelated or loosely associated services
Use clear, service-based naming aligned with page titles
Page/link names must remain concise:
Avoid long titles that wrap to multiple lines
If wrapping occurs, the name should be shortened for clarity and usability

Link Behavior

All links must point to internal pages within the same website
Do not link to external pages or non-service content

Client Requests (Removal or Repositioning)

The element may be repositioned within the right gutter only if explicitly requested
The element may be removed only if explicitly requested by the client
When removal or repositioning is requested, teams must communicate:
The loss or reduction of quick-access navigation for related services
The negative impact on internal linking and on-page SEO

Design Guidelines

Designers are encouraged to style the element using theme-aligned colors
Backgrounds should remain simple, using solid colors only
Link text must maintain strong contrast against the background for readability
Legibility and accessibility take priority over visual styling

Effective Date: April 1, 2026 Last Updated: April 1, 202 6

Best Practices for Link Styling

Tue, 24 Mar 2026 17:48:49 GMT

Best Practices for Link Styling

Effective Date: March 24, 2026 Last Updated: March 24, 202 6

Hibu Policy

Links must be easy to recognize, consistently styled, and clearly visible across all Hibu One websites. Users should be able to identify a link immediately—without needing to hover or interact with it.

If a theme’s default link color doesn’t provide enough contrast in a specific area (such as a footer or colored background), it must be adjusted. In those cases, designers are expected to override the default styling to ensure the link remains visible and usable. When color alone isn’t enough to distinguish a link, an underline must be applied.

The Hibu design team will rename all related assets and apply appropriate alt text where applicable.

Link Styling: At-Glance

Purpose / Why It Matters

Links are one of the primary ways users navigate a site. If they aren’t clear, users hesitate—or miss them entirely.

Consistent, accessible link styling helps users move through a site with confidence. It also supports accessibility standards, improves engagement, and reduces friction in key conversion paths.

Rules & Guidelines

Core Link Behavior

Links must stand out from surrounding text at all times.
Users should be able to recognize a link without hovering.
Hover states can enhance clarity, but should never be the only indicator.
Link styling should remain consistent across all states (default, hover, visited).
Avoid styles that make users guess what is clickable. The image must remain secondary to the header content at all times

Footer-Specific Rules

Footer links must be easy to read against the footer background.
Even when matching the overall footer style, links still need to stand out.
Underlines are required across all states in the footer to reinforce that the text is clickable.

Color & Contrast Requirements

Links must have strong contrast against both the background and surrounding text.
Do not use the same color as body text.
Avoid colors that are too similar to surrounding content.
Do not use red for links , as it is commonly associated with errors or warnings.

Theme & Background Overrides (Critical Rule)

If a link appears on a background where the default link color is difficult to see—such as a dark footer or a colored section—it needs to be adjusted.
In these situations, override the theme’s link color with one that improves visibility. White (#FFFFFF) can be used, even when surrounding text is also white, as long as the link is clearly differentiated by manually applying an underline.
If a link starts to blend in with nearby text or looks too similar in color, an underline should be applied—preferably across all states.
In areas where visibility is more likely to be an issue, such as footers or sections with strong background colors, links should combine high contrast with underlining to ensure they are easy to recognize.

Definition

Link styling is the visual treatment of clickable text—how links look, behave, and change across different states (default, hover, and visited) so users can easily recognize and interact with them.

Link State Consistency

Default, hover, and visited states should feel consistent and predictable.
Avoid dramatic color changes that could confuse users.
Hover states should support recognition—not define it.

Link Color Selection

When choosing link colors:

Start with brand colors, as long as they meet contrast requirements
Adjust those colors as needed to improve readability
If the brand includes a blue that meets contrast requirements, use that brand blue instead of a default blue
If necessary, fall back to a standard, highly recognizable link color ( such as Google blue - #0000FF )

At all times, clarity should take priority over strict adherence to brand colors.

Navigation Label Length

Tue, 17 Mar 2026 14:18:52 GMT

Navigation Label Length & Simplification

Effective Date: March 17, 2026 Last Updated: March 17, 2026

Hibu Policy

Navigation labels must be concise, scannable, and structured to maintain a single-line header layout across desktop breakpoints. Writers may shorten navigation labels and are not required to match full page or category names.

Definition

Navigation labels are the visible text links in the header navigation that direct users to primary pages or category landing pages.

These labels are designed for quick scanning and orientation — not for full keyword expression.

Purpose / Why It Matters

Navigation is one of the most frequently used elements on the site. Overly long labels:

Reduce scan speed
Cause wrapping that breaks layout consistency
Create visual clutter
Diminish perceived site quality

Concise labels improve usability while maintaining full SEO value through page-level content.

Rules & Guidelines

Label Length & Structure

Navigation labels must be short and scannable
Labels must avoid unnecessary qualifiers or repeated terms
Labels must not cause the navigation to wrap to multiple lines on desktop

Wrapping Validation Requirement

Navigation must be reviewed at 1366px desktop width in preview mode
If labels cause wrapping, they must be shortened
Labels must not be resized, compressed, or forced to fit
Simplification rules must be applied when resolving wrapping issues
Any label changes made to resolve wrapping must be documented with an assumption for QA review

Simplification Rules

Writers may shorten labels when context makes meaning clear
Industry or site context can replace repeated keyword
Examples:
“Commercial Fencing & Gates” → “Commercial”
“Residential Fencing & Gates” → “Residential”
“Decorative Accent Panels & Fencing” → “Decorative”

SEO Considerations

Navigation labels are not a primary SEO driver
Full keyword targeting must be handled on:
Page titles
Headings (H1, H2)
On-page content
Repeating keywords in navigation provides minimal SEO benefit

Design & Layout Constraints

Navigation must remain on a single line at standard desktop widths
Wrapping navigation is not permitted
If labels exceed available space, they must be shortened — not resized or forced to fit

Do / Do Not

Do:

Keep labels concise and intuitive
Use industry context to simplify wording
Prioritize readability over keyword inclusion

Do Not:

Force full page titles into navigation
Repeat obvious keywords (e.g., “Fencing” on a fencing site)
Allow navigation to wrap or compress unnaturally

Navigation Wrapping (Critical Consideration)

This guideline exists to prevent navigation wrapping, which occurs when labels are too long and force the header navigation onto a second line.

Navigation must remain on a single line at standard desktop widths. The primary checkpoint for this is 1366px desktop view in preview mode .

If navigation wraps:

Labels must be shortened
Simplification is required (not optional)

Writers are expected to adjust navigation labels when wrapping occurs and must document any changes using an assumption so QA can validate the decision.

For full rules governing navigation structure, behavior, and styling, refer to the Header Navigation definition.

Meta Description Tags

Mon, 02 Mar 2026 20:30:53 GMT

Meta Description Tags

Effective Date: March 2, 2026 Last Updated: March 6, 2026

Hibu Policy

Each visible page must include one unique meta description that:

Targets 150–160 characters
Prioritizes key messaging within the first 110–120 characters
Aligns directly with page content and intent
Encourages click-through from search results

Meta descriptions must be written in sentence case and must read as persuasive supporting copy to the title tag.

Definition

A meta description is the HTML <meta name="description"> element that provides a summary of a web page.

It appears beneath the title tag in search engine results and often serves as the supporting copy in link previews when a page is shared.

Example HTML structure:

The meta description represents the page’s value proposition before a user visits the site. It should clearly explain what the page offers and why it is relevant.

Unlike title tags, meta descriptions are not a direct ranking factor. However, they significantly influence click-through rate (CTR), which affects overall search performance.

Purpose / Why It Matters

Meta descriptions serve as the supporting copy in the search result listing.

They:

Clarify what the user will find on the page
Reinforce keyword relevance
Differentiate the listing from competitors
Encourage action
Support conversion before page load

In many cases, the meta description determines whether a user clicks or scrolls past.

Current Display Standards

Search engines do not impose a strict technical character limit. However, they do have what is considered an optimum range. This is what informs our character-length standards at Hibu: Therefore, the following practical display limits apply.

Desktop display typically truncates around 155–160 characters.
Mobile truncates earlier.
Ideal writing range: 150–160 characters.
Critical information must appear in the first 110–120 characters.

Because truncation is common, front-loading with valuable keywords is required.

Google Rewrites & Truncation Considerations

Google may rewrite meta descriptions if:

They do not match the search query
They are too vague
They appear keyword-stuffed
On-page copy better answers the query

Clear, relevant, intent-matched copy reduces rewrite likelihood.

Structure Guidelines

Page-Type Variations

Meta descriptions are structured differently depending on page type.

While all meta descriptions must:

Stay within 150–160 characters
Front-load key messaging
Encourage click

Structure and tone may vary for:

Always refer to the page-specific formatting guideline before writing or editing. Page-specific rules override general structure when applicable.

Front-Load Keywords
Place the most important terms at the beginning.
Align with Page Intent
The title must match the specific page content.
Include Name of Business (When Required)
Include NOB on:
Homepage
Contact
About
Utility pages
Strategic Use of Business Name & Geographic Modifiers (When Not Required)
For pages not listed above , the Name of Business (NOB) is not required. However, when space and context allow, it may be included strategically.
Meta descriptions on service, category, or geo-focused pages may also incorporate:
Secondary Geo (when relevant to page intent)
-OR-
Primary Geo
This is encouraged when it:
Strengthens local search relevance
Improves clarity in search results
Reinforces brand recognition
Aligns naturally with the page topic
Do not force business names or geographic modifiers into the description if they reduce clarity, feel repetitive, or read unnaturally.
Primary and secondary geo definitions are governed by the Hibu Geo Rules .
Maintain Sentence Case
Meta descriptions must be written in sentence case.
Avoid:
All caps (unless acronym: AAA, ASE)
Excessive punctuation
Overuse of exclamation marks
Avoid These Common Mistakes
Keyword stuffing
Repeating the title tag verbatim
Generic summaries (“Welcome to our website…”)
Writing only for search engines
Misalignment with page content
Duplicate meta descriptions across pages
Each meta description must be meaningfully distinct.

Title Tags

Mon, 02 Mar 2026 20:16:44 GMT

Title Tags

Effective Date: March 2, 2026 Last Updated: March 6, 2026

Hibu Policy

Each visible page must include one unique title tag written to:

Do not exceed 60 characters (maximum display boundary)
While phrases can be used, be aware that adding "and" requires 5 characters with the spaces, while a pipe separator only requires 3 characters. (added 4/9/2026)
Accurately reflect page intent
Do not randomly choose and place keywords. Make sure they relate and appear on the page. (added 4/9/2026)
Support click-through from search results
Title Tags slightly above 55 (56–60) are compliant when clarity requires it.

Definition

A title tag is the HTML <title> element that defines the official headline of a web page.

It appears:

As the primary clickable headline in search engine results
In the browser tab when the page is open
As the default headline for many link previews when the page is shared

Example HTML structure:

<title>Roof Repair in Austin, TX | ABC Roofing</title>

The title tag represents the page’s core topic and intent. It must accurately summarize the content while encouraging users to click.

Purpose / Why It Matters

The title tag:

Signals topic relevance
Impacts click-through rate
Controls search listing clarity
Sets expectation before page load

It is the most influential on-page SEO element for search visibility and click behavior.

Current Display Standards

Search engines do not impose a strict technical character limit. However, they do have what is considered an optimum range. This is what informs our character-length standards at Hibu:

Google typically truncates after ~60 characters.
Best performance range: 50–55 characters.
Writing goal: 55 characters.
Absolute boundary: 60 characters.

Keeping titles closer to 55 characters reduces rewrite risk and truncation.

If Over 60 Characters

If a title exceeds 60 characters:

Remove unnecessary separators (pipes).
Remove “Area” or redundant modifiers.
Remove city/state comma when possible.
Preserve clarity over rigid trimming.

If after clean-up it remains slightly above 60 but is accurate and readable, it may remain.

Structure Guidelines

1. Front-Load Keywords

Place the most important terms at the beginning.

2. Align with Page Intent

The title must match the specific page content.

3. Include Name of Business (When Required)

Include NOB on:

Homepage
Contact
About
Utility pages

Service pages may omit NOB when targeting generic queries.

4. Avoid:

Keyword stuffing
Colon-heavy formatting
Overuse of pipes
Artificial abbreviations
Swapping “and” with “&” in the NOB

Page-Type Variations

Not all title tags follow the same structure. Title formatting varies based on page type, intent, and whether the page targets branded, service-based, or geographic searches.

The general 55–60 character standards apply to all pages; however, structure and ordering may change depending on context.

Examples of page-type variations include:

Each page type follows its own approved formatting pattern for:

Keyword placement
City/state inclusion
Name of Business (NOB) usage
Separator usage (pipes, commas)
CTA inclusion (when applicable)

Refer to the dedicated guideline for each page type before writing or editing a title tag. The formatting rules on those pages override the general structure guidance when applicable.

Header Background Imagery

Wed, 25 Feb 2026 18:56:15 GMT

Header Background Imagery

Effective Date: February 25, 2026 Last Updated: February 25, 202 6

Hibu Policy

The header background must preserve readability, brand clarity, and structural integrity across all devices.

Approved header backgrounds include:

Solid brand colors
Subtle textures
Low-detail imagery that does not interfere with header content

Detailed photographs, images containing people, text, high contrast areas, or busy compositions that compete with the logo, navigation, or calls to action are not supported.

The header is a functional space first. Visual treatment must never compromise usability.

It is expected that the Hibu design team will rename files appropriately, and apply descriptive alt text when applicable.

Header Background Imagery At-Glance

Purpose / Why It Matters

The header is one of the most constrained and high-impact areas of the website. It must:

Load quickly
Remain readable across desktop, tablet, and mobile
Maintain consistent alignment and spacing
Clearly present branding and primary navigation

When a header background becomes visually complex, it introduces risk:

Reduced logo legibility
Navigation becoming harder to scan
Accessibility issues due to poor contrast
Visual clutter on smaller screens
Inconsistent behavior across breakpoints

A clean header ensures faster cognitive processing and stronger brand recognition.

Rules & Guidelines

Aceptable

Solid brand colors
Light textures
Extremely low-detail imagery (e.g., soft water texture for a pool company, faint wood grain for woodworking)
Backgrounds that maintain strong contrast with header content
If an image is used:
An overlay may be applied to soften contrast and improve text clarity.
The overlay must be subtle and support brand consistency.
The image must remain secondary to the header content at all times

Examples

Acceptable

A solid brand color (rather than white) behind a logo
A lightly blurred water texture (or generic other abstract) with minimal detail
A muted wood texture with low contrast

Not Acceptable

Detailed photographs with people or faces
Images containing text
High-contrast or busy compositions
Backgrounds that reduce readability of the logo or navigation
Imagery that competes with the header CTA
Patterns that create visual vibration or distraction

Design Standards

Contrast between background and header content must meet accessibility standards.
Background imagery must not visually overpower the logo.
If transparency is used, the image behind it must still preserve readability.
Performance considerations apply — large or unoptimized files are not supported.

Key Rule

Header background imagery is decorative support, not primary content. It must protect readability, brand clarity, and structural consistency across all devices.

Definition

Header background refers to the visual treatment behind the header content (reviews, logo, header CTA, phone number, geo, etc.). This may include color, texture, or imagery.

Not Acceptable

A team photo behind the navigation
A city skyline with strong contrast
A background containing readable words
A detailed action shot behind a transparent header

Tagline Placement Standards

Wed, 25 Feb 2026 18:35:05 GMT

Tagline Placement Standards

Effective Date: February 25, 2026 Last Updated: February 25, 202 6

Hibu Policy

Hibu does not place taglines directly beneath the logo in the website header.

While this placement was supported in the past, it is no longer permitted. Tagline length is difficult to control, and over time this led to crowded headers, inconsistent layouts, wrapping issues, and reduced readability — particularly on mobile devices.

To maintain clarity, performance, and visual consistency, the header is reserved for essential elements only: the logo, primary navigation, and approved calls to action.

Definition

A tagline is a short brand statement or marketing phrase that reinforces a company’s positioning, value, or personality (e.g., “Comfort now. Pay later. Stay chill.”).

Header tagline placement refers specifically to positioning that statement directly beneath or adjacent to the logo within the top navigation bar.

Purpose / Why It Matters

The header is one of the most constrained and performance-sensitive areas of the site. It must remain:

Clean and scannable
Structurally consistent across devices
Optimized for responsive behavior
Focused on navigation and conversion

Even short taglines can create layout instability due to:

Text wrapping across screen sizes
Translation length expansion
Font scaling on accessibility settings
Alignment shifts between desktop and mobile

When the header becomes crowded, usability declines. Visitors take longer to scan, primary actions become less prominent, and overall visual balance suffers.

This policy protects header clarity while ensuring the client’s messaging remains highly visible elsewhere.

Rules & Guidelines

Taglines may not be placed under or beside the logo in the header.
The header must remain limited to logo, navigation, and approved CTAs.
Exceptions are not permitted based on tagline length.
Header spacing may not be expanded to accommodate a tagline.
Taglines must not be embedded into the logo artwork to bypass this rule.

Approved Tagline Placements

Taglines are fully supported — just not in the header. Approved placements include:

Above the H1 headline in the hero
Below the H1 or below the primary CTA in the hero
As the headline for the introductory content section
As a caption tied to a client-supplied image (e.g., in Introduction or Why Choose Us sections)
Integrated naturally within approved body copy, including:

Homepage introduction copy
About Us page content
Service page introductions
Service Area page introductions

When included within body copy, the tagline should read naturally within the content and not feel duplicated or artificially inserted for repetition.

These placements keep the tagline above the fold, highly visible, and readable without compromising header structure.

Additional Header Phone Numbers

Wed, 25 Feb 2026 01:49:40 GMT

Additional Header Phone Number

Effective Date: February 25, 2026 Last Updated: April 1, 202 6

Hibu Policy

Hibu One supports one phone number in the header.

If a client requires multiple phone numbers, the header phone number and CTA lead-in must be replaced with a single button (e.g., “Contact Us” or “Call Us”) that opens the approved Multi-Phone Pop .

The Multi-Phone Pop , located under Pages → Pop-Ups in the site template, is the designated and only location where multiple phone numbers are managed and maintained.

This pop-up is pre-built within the site template and must be used as-is.
All additional phone numbers must be added and managed within this pop-up.
No custom pop-ups, duplicate builds, or structural modifications are permitted.
Multiple phone numbers may not appear inline in the header.

Definition

The Additional Header Phone Numbers feature replaces the static header phone number with a button that opens a pre-built modal containing multiple clickable phone numbers.

The Multi-Phone Pop supports up to 10 phone numbers.

On desktop and tablet , numbers display in two columns (up to five per column).
On mobile , numbers display as a single vertical column (up to 10).

Rules & Guidelines

Header Structure

Only one phone number may appear directly in the header.
If multiple numbers are required, the header phone number must be replaced with a button.
The button label may read “Contact Us,” “Call Us,” or another approved contact-based label.
Multiple phone numbers may not appear inline in the header.

Approved Pop-Up Types

Only the pre-built Multi-Phone Pop may be used.

Supports up to 10 phone numbers.
Located under Pages → Pop-Ups in the site template.
Must not be recreated, redesigned, or duplicated.
Structural edits are not permitted.

Pop-Up Availability & Required Setup

The Multi-Phone Pop is the required and approved component for displaying multiple phone numbers. However, availability may vary depending on when the site was created.

On newer sites, the Multi-Phone Pop will already exist under Pages → Pop-Ups .
On older sites, this pop-up may not be present.

If the Multi-Phone Pop is not available:

A new pop-up must be created using the Blank Pop-Up template .
The Multi-Phone section must be added from the Pop-Up Sections library .
Only the approved Multi-Phone section may be used to replicate this functionality.

Structural and layout requirements:

Horizontal scrolling is not permitted.
The pop-up must be adjusted to display correctly across desktop, tablet, and mobile .
Height and width must be configured to ensure all content is visible without layout breakage.
Visual balance and usability must be maintained across all breakpoints.

Linking Standards

The implementing team must follow current Additional Locations and Location Profile rules when linking phone numbers.
Phone numbers must connect to the Content Library Business Information when applicable.
All numbers must be clickable.
No independent or hard-coded phone numbers outside of approved data sources.

Labeling Restrictions

Each phone number must include a clear identifying label (e.g., town, office name, service area).

Label requirements:

Labels must represent a legitimate location, office, or geographic identifier.
Labels must be concise.
Labels should fit on a single line when possible.
Multi-line wrapping should be avoided.
Font size may be slightly reduced if necessary to preserve single-line presentation.
Readability may not be compromised.
Promotional language is not permitted.

Ordering standard:

Unless otherwise directed, locations or towns must be listed in alphabetical order.
If alphabetical order is not used, the client must specify the preferred order.

Design Standards

The header button must follow established Hibu One button standards.
Styling must align with the site’s approved brand palette.
Visual balance and clarity are the responsibility of the implementation team.
Structural redesign of the pop-up is not permitted.

Desktop & Tablet Column Distribution

On desktop and tablet, phone numbers display in two columns with a maximum of five per column.

To maintain visual balance, numbers must be placed by alternating between columns.

Placement rules:

Start in the left column
Place the next number in the right column
Continue alternating left → right → left → right until all numbers are placed

Resulting layout (desktop and tablet):

3 numbers → 2 left / 1 right
5 numbers → 3 left / 2 right
7 numbers → 4 left / 3 right
9 numbers → 5 left / 4 right

The left column may contain one additional number when the total is odd.

Columns must remain visually balanced. Stacking one column before using the other is not permitted.

Mobile Behavior

On mobile, all phone numbers display in a single vertical column .
No column distribution or alternation applies on mobile.

Multi-Phone Pop: At-a-Glance

Header / CTA Button Behavior

When implementing the Multi-Phone Pop, both desktop and mobile header experiences must be updated to ensure consistent behavior.

The header phone number must be replaced with a button on both desktop and mobile .
The button must trigger the Multi-Phone Pop.
The button must not be connected to dynamic or collection-based phone number fields.
The button label must be manually defined.
The Multi-Phone Pop headline must match the header button label exactly to maintain a consistent user experience. We won’t allow alternate phrasing unless explicitly requested by the client, as variation can create confusion and reduce interaction clarity. (04/01/26)

Approved labeling:

“Call Us” (default)
“Contact Us”
Other approved contact-based variations

Caller text is not supported with this implementation:

Any existing caller text must be removed from both desktop and mobile headers
Caller text must not be used in conjunction with the Multi-Phone Pop

Scope Restrictions (Placement Rules)

The Multi-Phone Pop is restricted to the header button only.

The Multi-Phone button must not be added to coupons, callouts, or any secondary content areas.
Coupons and callouts must not trigger the Multi-Phone Pop.
Phone numbers must not be displayed directly within coupons or callouts.

When a phone-based action is required in these sections:

Replace phone number references with an approved CTA label (e.g., “Contact Us”).
The CTA must link to the appropriate destination (e.g., Contact page or approved form).
Do not replicate or simulate multi-phone functionality outside of the approved header implementation.

Header CTA Button

Mon, 23 Feb 2026 19:19:58 GMT

Header CTA Button

Effective Date: February 23, 2026 Last Updated: February 23, 202 6

Hibu Policy

Hibu One supports a single Header CTA Button positioned in the top right corner of the desktop header. Only one button is permitted in this location.

If a client requests a different primary action (e.g., Make a Reservation, Shop Online, Pay Now, Translate), the existing Header CTA Button may be swapped for the requested action. Additional buttons will not be added to the desktop header.

The Header CTA Button does not appear on tablet and does not appear on mobile by default. If appropriate, the mobile header button may also be swapped at the client’s request. HTML embed code may replace the button in the desktop header; however, embedded code is not guaranteed to function in the mobile header.

If mobile placement is required and embed code cannot function in the header, the button or code will be placed in the Hero section beneath the primary CTA on the Homepage and Category Landing Pages only.

Geo Lead-in

City, ST

CTA Lead-in

 (888) 888-1111 

Serving the

Asheville, NC Area

Call or Text

 (888) 888-1111 

Purpose / Why It Matters

The header is a high-visibility, high-priority area of the site. Limiting this space to a single CTA:

Maintains design clarity and hierarchy
Prevents competing actions
Supports focused conversion behavior
Protects the integrity of the Hibu One design system

Allowing only one button ensures consistency across all Hibu One websites and preserves usability standards.

Definition

The Header CTA Button is the single action-oriented button located in the top right corner of the desktop site header. It represents the primary conversion action for the site.

Rules & Guidelines

Button Quantity & Placement

Only one button is permitted in the top right corner of the desktop header.
Additional buttons will not be added to the desktop header.
The Header CTA Button does not appear on tablet.
The Header CTA Button does not appear on mobile by default.

Swapping the Button

The default Header CTA may be replaced with a client-requested action.
Examples include, but are not limited to:
Make a Reservation
Shop Online
Pay Now
Translate Site
When receiving this request, teams must ask whether the client also wants the mobile CTA button swapped.

Mobile Considerations

The mobile header typically includes a CTA button to the left of the phone number.
This mobile header button may be swapped upon client confirmation.
HTML embed code may not function properly in the mobile header.
If embed code cannot function in the mobile header and the client requires mobile visibility, the solution is:
Place the button or embed beneath the Hero CTA
Placement allowed on Homepage and Category Landing Pages only

Design Standards

The Header CTA Button must follow the established primary or secondary button palette when using native Hibu button functionality.
If the Header CTA Button is replaced with client-provided HTML embed code, the styling may not match the Hibu One design system.
Hibu will not modify, rewrite, or restyle third-party embed code to force visual alignment with site button styles.
Any visual inconsistencies resulting from third-party code are not the responsibility of Hibu.

Blog Post #1

Sun, 22 Feb 2026 20:15:20 GMT

This is a subtitle for your new post

The body content of your post goes here. To edit this text, click on it and delete this default text and start typing your own or paste your own from a different source.

Blog Post #2

Sun, 22 Feb 2026 20:14:56 GMT

This is a subtitle for your new post

The body content of your post goes here. To edit this text, click on it and delete this default text and start typing your own or paste your own from a different source.

Blog Post #3

Sun, 22 Feb 2026 20:12:50 GMT

This is a subtitle for your new post

The body content of your post goes here. To edit this text, click on it and delete this default text and start typing your own or paste your own from a different source.

7 Signs It’s Time to Replace Your Roof in Asheville, NC

Sun, 22 Feb 2026 14:27:57 GMT

This is a subtitle for your new post

The body content of your post goes here. To edit this text, click on it and delete this default text and start typing your own or paste your own from a different source.

Why Your Gutters Matter More Than You Think

Sun, 22 Feb 2026 14:26:59 GMT

This is a subtitle for your new post

The body content of your post goes here. To edit this text, click on it and delete this default text and start typing your own or paste your own from a different source.

What Makes Stella Different from Other Asheville Contractors?

Sun, 22 Feb 2026 14:25:19 GMT

This is a subtitle for your new post

The body content of your post goes here. To edit this text, click on it and delete this default text and start typing your own or paste your own from a different source.

Hibu One Homepage and CAT Layout Standards

Sat, 21 Feb 2026 20:31:21 GMT

Hibu One Homepage and CAT Layout Standards

Hibu Policy (Non-Negotiable)

Hibu One Homepage and Category Landing Pages follow the same standardized layout model and defined section order governed by the Hibu One Website Layout Standards .

Both page types use the same structural framework. This layout may not be redesigned, rebuilt, or reordered outside of the rules defined in this guide.

This document governs page structure and module behavior. For rules about what content belongs in each section, see the Homepage & CAT Content Guidelines .

This guide establishes:

Which elements are non-negotiable
Which elements may be adjusted
What client-provided elements may be added to the layout
When layout requests may be considered

If any other document conflicts with this guide, this guide controls.

Effective Date: February 14, 2026 Last Updated: February 14, 202 6

Defined Section Order

Homepage and Category Landing Pages follow the same top-to-bottom section order.

The page begins with the Header and ends with the Footer and required policy elements.

By default, sections remain in this order.Limited repositioning of specific sections (such as Gallery, Coupons, or Brand Logos) may be permitted only where explicitly outlined in this guide.

Content, styling, and approved in-between elements may vary within sections where this guide allows.

Navigation

Mega Menu

Hero (Standard Layout / Non-Transparent Header)

Introduction

Why Choose Us

Assistant Banner

Gallery

Copy Blocks

Reviews

Additional Content (Above Footer)

Footer: Badge / Accreditation logos

Footer: Business Contact Information

Footer: Prohibited in Footer

Footer: Privacy, Cookies, Accessibility

Timing of Layout Requests

Layout and structural changes are not implemented during the initial build unless they are part of established platform standards.

After First Proof:

Requests may be reviewed
Adjustments must follow the allowances in this guide
Structural redesign is not permitted
This ensures consistency across all Hibu One sites while allowing controlled flexibility where approved.

Standard Layout Sequence

Not all sections are required on every page. When included, they must appear in this order.

Top to Bottom Structure

Header
Logo
Navigation
Utility elements (if included)
Hero
Hero Form (if included)
Introduction
Assistant Banner (if included)
Why Choose Us
Copy Blocks
Gallery (if included)
Coupons * (if included)
Recent Reviews
Recent Blog Posts (if included)
Footer
Badge / Accreditation Logos
Video Section
Business Contact Information - address, service area, hours, phone, social icons, etc.

Important

Sections may have approved style variations.
Only sections explicitly identified in this guide may be repositioned.
All other sections must remain in the defined sequence.
Additional elements must not disrupt the approved layout flow.

*The placement of the Gallery varies depending on the PBN. On most sites, the Gallery appears after the Coupons section (if included).

Why These Layout Standards Exist

Hibu One layouts are deliberate and performance-driven.

They are designed to maximize:

Conversion
Usability and visual clarity
Search visibility and mobile performance

Section order, spacing, and element placement are intentional. White space, hierarchy, and call-to-action positioning directly support lead generation and user behavior.

Layout discipline works together with the Hibu One Fair Use Policy – Media & Assets , which defines limits for images, videos, files, and third-party elements. These combined standards protect page speed, Core Web Vitals, SEO visibility, and overall performance — especially on mobile devices.

These standards ensure:

Consistent expectations for clients
Alignment between Sales and delivery teams
A single reference point when layout or asset questions arise

For full redesign expectations, see the Hibu One Website Design & Rebuild Policy .
For asset and quantity limits, see the Fair Use Policy – Media & Assets .

What Can and Cannot Be Changed

At-a-GlaNce Tables

Header

Footer: Photo Motion Video Row

Hibu One Website Design & Rebuild Policy

Sat, 21 Feb 2026 18:21:19 GMT

Hibu One Website Design & Rebuild Policy

Effective Date: February 21, 2026 Last Updated: February 21, 202 6

Hibu Policy

Hibu One Smart Sites are built to perform — not just to look good. Every site follows proven layouts that are clean, conversion-focused, mobile-friendly, and optimized for speed and search.

We do not replicate outdated designs, honor ad hoc layout requests, or revert to previous specifications. Instead, we use a standardized, data-backed approach that ensures better results for clients.

That said, we will attempt to make a client’s new Hibu One Smart Site look as much like their old site as is feasible. A typical consumer revisiting the site should “feel like” they’re engaging with the same business.

Whenever possible, we should try to convince clients to go get to the Proof stage. Debating hypotheticals isn’t productive, and 95% of the time when a client sees what we build they are happy with it and just want a few tweaks.

Why We Use Proven Layouts

Our design standards aren’t arbitrary. They are based on:

User Behavior Data: Real-world analytics showing what works.
SEO Best Practices: Structured layouts and headings that improve search visibility.
Conversion Strategy: Each element is placed to drive calls, form fills, and quote requests.
Performance Benchmarks: Clean code that meets Core Web Vitals for fast, mobile-friendly pages.

Following these standards ensures:

A consistent, high-quality product across all Hibu One Smart Sites
Faster build times and easier maintenance
Clear expectations across sales, design, and support teams
Better long-term results: more leads, better engagement, stronger brand perception

Why We Don’t Honor Old Designs or One-Off Layout Requests

We avoid outdated design specs and custom one-offs for several reasons:

Mobile-First Comes First: Most visitors view websites on their phones. Our layouts are designed mobile-first to ensure pages load quickly, display cleanly, and convert on small screens. Mobile-first design isn’t just about convenience — it directly affects conversions and SEO rankings. A slow or cluttered mobile site can cost leads and hurt visibility in search.
Proven Patterns Work: Our layouts are based on data — not personal preference.
SEO-First Decisions: Changing heading structure or element order can hurt search rankings.
Conversion Impact: Moving forms or calls-to-action risks lowering response rates.
Consistent User Experience: Visitors expect certain elements in familiar places.
Speed & Performance: Old designs often include slow sliders, heavy images, or extra widgets that hurt mobile speed scores.
Scalability: Standardized layouts make future updates faster and testing more reliable.
Brand Integrity: Random, untested changes risk making a site look inconsistent or unprofessional.

Core Design Principles

1. Professionalism That Converts

Each design presents a polished, trustworthy online presence.

Hero sections feature a clear headline (H1), subhead (H2), motivating copy, and strong call-to-action — with no visual clutter.
Client images (trucks, storefronts, team photos) are used strategically, usually below the hero or on the About Us page, to avoid reducing readability.

2. User Experience That Drives Action

Navigation and layout are designed for intuitive, frictionless flow across desktop, tablet, and mobile.

All paths lead to key actions — call, form submit, or quote request.
Buttons, forms, and CTAs are placed exactly where users expect to find them.

3. Performance & Page Speed as Non-Negotiables

Speed and usability are prioritized from the start.

No auto-playing video or sliders above the fold.
No extra header widgets or scripts that slow performance.
Sites are mobile-first and optimized to meet Core Web Vitals.

4. Purposeful Element Placement

Key information is always where it belongs:

Header phone number and hero CTAs are fixed and prominent.
Hero forms are short (about four essential fields) to encourage completion.
If location is needed, one short field (City/State or ZIP) is accept

Content, SEO, and Site Rebuild Process

When upgrading to a Hibu One site:

Content Carryover: Text, images, and assets from the old site may be carried forward if they are current, accurate, and align with Hibu One Smart Site design and SEO standards . Content that is outdated, redundant, overly long, or not optimized for performance will be refreshed or rewritten to fit best practices.
Geo Pages: Can be included by purchasing Geo Pages as part of your Hibu One Solution
301 Redirects: We set up redirects from old pages to preserve SEO value and prevent traffic loss.
Local Ranking Optimization: Our team may retain existing title tags and meta descriptions or re-optimize new pages for better performance, depending on which approach is most effective.

Ranking Expectations After Launch

Important: It’s normal to see search rankings dip immediately after launch. This is because Google needs to re-index the new site. Rankings usually stabilize and start improving within 7 to 10 days, especially with Local Ranking optimizations in place.

Page Removal & Deactivation (Post-Launch)

Thu, 19 Feb 2026 19:14:06 GMT

Page Removal & Deactivation (Post-Launch)

Effective Date: February 19, 2026 Last Updated: February 19, 202 6

Hibu Policy

When a client requests the removal or deletion of an existing page after the site has gone live , the page must not be permanently deleted. Instead, the page must be formally deactivated using the standardized removal process outlined below. This protects SEO equity, prevents 404 errors, and preserves the page for potential future reinstatement.

This policy applies only to live sites. It does not apply during pre-launch build.

Purpose / Why It Matters

Deleting a live page can create:

404 errors
Loss of indexed authority
Broken backlinks
Negative SEO impact

This process ensures:

No broken URLs
No unnecessary loss of ranking value
No permanent loss of content
The ability to quickly restore the page if needed

The page is retired — not erased.

Core Rule

We do not delete live pages. We rename the page, remove it from navigation, move it to the bottom of the root structure, and apply a 301 redirect from the original URL to the homepage. That is the standard.

Required Post-Launch Removal Process

Follow these steps exactly when removing a live page:

Step 1: Rename the Page

Update the internal page name to clearly indicate removal.
Add “removed-mmddyr” in front of the page name.
Example:
before - AC Repair
after - removed-021926-AC Repair

This ensures the team can immediately identify inactive pages within the CMS.

Step 2: Update the Page Slug

Copy existing slug (ac-repair)
Don't forget to copy!
Add to existing slug "removed-", as in "removed-ac-repair"
This allows us to keep the page and add a 301 redirect

Step 3: Move the Page to the Bottom of the Root Directory

Drag the page to the last position in the left-hand page tree.
It must sit below all active pages.

Removed pages must not remain intermingled with active content.

Step 4: Set Page to Draft (IMPORTANT)

Setting the page to Draft removes it from dynamic navigation and applies no-index, preventing search engine visibility.
When a mega menu is present, DPS/Amends needs to manually remove from either the top level nav or from mega menu.
If mega menu is added via the widget, DPS/Amends will need to add page name to Exclude Parent Page

Step 5: Apply a 301 Redirect

Go to URL Redirects.
Create a redirect from the page’s original URL (before renaming) -- what you copied in Step 2
Redirect it to the homepage.

This step prevents 404 errors and preserves existing traffic or backlinks.

The redirect must reference the original pre-modification URL. Redirecting the modified “removed-” slug is incorrect and will create unnecessary redirect chains.

Hiding or Removing Pages During Site Build

Thu, 19 Feb 2026 15:02:52 GMT

Pages That Must Be Hidden or Removed During Site Build

Hibu Policy

During every Hibu One site build, unused template pages are expected to be either:

Moved to the XTRA Pages folder and unpublished, or
Deleted entirely if they are not supported within the Hibu One framework.

This is a structural quality standard. It does not impact site performance, but it ensures clean architecture, prevents accidental indexing, and maintains build integrity.

Effective Date: February 19, 2026 Last Updated: February 19, 202 6

Purpose / Why It Matters

This expectation ensures:

Clean, intentional site hierarchy
Clear separation of live vs. inactive pages
Reduced QA errors
No accidental publishing or indexing
Consistency across all Hibu One builds

Unused pages left in navigation or in the root structure create confusion and weaken structural discipline.

Pages to Move to XTRA Pages (If Not Used)

If the following template pages are not actively being used, they must be moved to the XTRA Pages folder:

FAQs
Gallery
Request Form Page
Serving Area
Areas Served (anchor)
Locations (folder - Loc Cat + Loc Profile)
Core Page
Cat-Landing
DNT – Andrew

These pages:

Must not remain in primary navigation.
Must be clearly organized under XTRA Pages.

Set Page to Draft Status (IMPORTANT)

The following pages must be set to Draft Status when moved:

Request Form Page
FAQs Page
Core Page
Cat-Landing
DNT – Andrew

This ensures they are not indexed.

Serving Area Structure Requirement

If Serving Area is used:

SAP pages (SAP #1–#4, etc.) must be nested under the Serving Area parent.
SAP pages must be properly indented.
SAPs must not exist independently at the root level.

If Serving Area is not being used, it and its SAP pages must be moved to XTRA Pages.

FAQ: What should I say if a client runs a Ninja Cat, SEMRush or similar report?

Thu, 12 Feb 2026 19:38:20 GMT

FAQ: What should I say if a client runs a Ninja Cat or similar report?

When customers or sales reps send third-party website audit reports (SEMrush, Lighthouse, W3C, etc.), these often include alarming warnings, red flags, and urgent language that can create unnecessary concern.

To help ensure consistent, accurate responses, please use the appropriate message below based on who submitted the report.

Sales-Facing Response
Use this when the audit report is sent by a Sales Representative (SR).

Third-party audit tools (SEMrush, Lighthouse, W3C, etc.) are frequently used during competitive evaluations and often surface long lists of “warnings” designed to look urgent. In many cases, the goal is volume and intimidation rather than real impact.

These reports flag every possible best-practice recommendation—including items that have little or no effect on real-world performance—which is why they’re commonly used as scare tactics by competitors.

What Hibu can address
Clear on-page issues such as broken links, missing alt text, or missing/incorrect title and meta tags should be shared with our team for review and resolution where applicable.

What Hibu cannot control
Items related to off-page SEO signals, social presence, external scripts, platform-level code structure (including some heading hierarchy warnings), and third-party performance scoring factors are typically outside our direct control and are often low-impact.

Key takeaway
Not every flagged item requires action. Modern search engines and browsers tolerate minor warnings, especially on SMB websites. Our focus is on fixes that materially improve usability, accessibility, and search visibility—not chasing automated scores.

Client-Facing Response
Use this when the audit report is sent directly by a client.

We understand how concerning third-party website audit reports can look. When you see red warnings, exclamation points, and language like “must be fixed immediately,” it can feel like something is seriously wrong—even when your site is actually performing well.

These tools are designed to flag every possible recommendation, not just issues that meaningfully impact your website. As a result, many findings sound urgent but have little real-world effect, especially for small to mid-size business websites.

What we can help with
If a report identifies clear on-page issues like broken links, missing image alt text, or missing title or meta tags, we’re happy to review those and address them when appropriate.

What’s often outside our control
Some flagged items relate to things like off-site SEO signals, social media activity, third-party scripts, or platform-level code. These don’t necessarily indicate a problem and often can’t—or don’t need to—be changed.

The important thing to know is that not every warning requires action. We focus on updates that truly improve user experience, accessibility, and search visibility. If there’s something specific in a report that concerns you, we’re always happy to review it and talk through what actually matters.

FAQ: What should I say if a client runs a ChatGPT (or similar) SEO report?

Thu, 12 Feb 2026 19:27:39 GMT

FAQ: What should I say if a client runs a ChatGPT (or similar) SEO report?

ChatGPT doesn’t actually scan your site — it generates lists of common best practices and sometimes guesses wrong. That’s why its reports can sound alarming but don’t reflect real issues. Your Hibu Smart Site already has the core SEO built in: mobile responsiveness, fast hosting, and SEO tagging. If something like fresh content or reviews is flagged, that’s where we can focus together.

Key Takeaway
AI-generated reports like ChatGPT are not diagnostic tools. They provide broad lists of suggestions, many of which don’t apply to your site. Hibu Smart Sites already meet core SEO standards, and we focus on updates that actually drive results — faster performance, stronger visibility, and more leads.

Plan of Attack for Reps

Acknowledge and De-escalate – “I’m glad you’re looking at SEO — that’s why we manage these sites for you.”
Clarify Tool Limitations – “ChatGPT doesn’t scan your actual site. It creates generalized lists of possible issues.”
Reframe Platform Realities – “Every platform has trade-offs. Hibu’s advantage is that we handle hosting, updates, and security for you.”
Highlight What’s Built-In – “Your site already follows Google’s core guidelines: mobile responsiveness, meta tags, alt text, and page speed are handled for you.”
Acknowledge Valid Points – “Good callout — fresh content or reviews will help SEO. We can get that scheduled.”
Bring It Back to Outcomes – “Are you actually seeing fewer leads, or just concerned because this report flagged something?”
Offer Next Steps – “Let’s do a quick SEO tune-up: refresh content like more FAQs, testimonials (text-based or, even better, client video testimonials), before /after photos (if applicable), check SEO tags, and make sure everything’s in top shape.”

FAQ: What should I say if a client runs a Google Lighthouse or similar report?

Thu, 12 Feb 2026 18:53:26 GMT

What should I say if a client runs a Google Lighthouse or similar report?

Reports like Lighthouse or BBB flag technical items that sound serious but usually don’t affect how your site works, ranks, or generates leads. Even Google’s own sites don’t pass every test. Your Hibu Smart Site already meets the fundamentals: mobile-friendly design, fast hosting, and SEO tags. If the report flagged content freshness, images, or reviews, those are the updates we can act on.

Key Takeaway
Automated reports like Lighthouse or BBB highlight technical details, but they rarely reflect what truly matters to Google or your customers. Hibu Smart Sites already meet core SEO and performance standards. Instead of chasing perfect scores, we focus on updates that actually drive results — faster speed, fresh content, stronger credibility, and more leads.

More Information

Acknowledge and De-escalate – “I’m glad you’re keeping a close eye on performance — that’s why we manage these sites for you.”
Clarify Tool Limitations – “Reports like this scan everything, including minor technical items that don’t affect real-world results.”
Reframe Platform Realities – “No site — not even Google’s — scores perfectly. What matters is performance, clarity, and conversions.”
Highlight What’s Built-In – “Your site already includes the essentials: fast hosting, SEO tagging, mobile responsiveness, and alt text.”
Acknowledge Valid Points – “Good callout — adding new content or reviews will absolutely help SEO and trust.”
Bring It Back to Outcomes – “Are you seeing fewer leads, or are you just concerned because this report flagged something?”
Offer Next Steps – “Let’s do a quick SEO tune-up: refresh content like more FAQs, testimonials (text-based or, even better, client video testimonials), before /after photos (if applicable), check SEO tags, and make sure everything’s in top shape.”

Social Image (Open Graph / OG) Rules

Thu, 12 Feb 2026 14:05:29 GMT

Social Image (Open Graph / OG) Rules

Hibu Policy

Every Hibu One Smart Site includes a default Social Image.

The Social Image (technically referred to as the Open Graph or OG image) controls how a website appears when its link is shared on social media platforms, messaging apps, and mobile browsers.

The Social Image must meet defined size, aspect ratio, and content standards to ensure consistent rendering and professional representation across platforms.

After this section, the Social Image may be referred to as the OG image .

Social Image (Open Graph / OG): At-a-Glance

Effective Date: February 12, 2026 Last Updated: February 12, 202 6

Definition

A Social Image (Open Graph or OG image) is the primary preview image displayed when a website link is shared on platforms such as Facebook, LinkedIn, or in messaging applications like iMessage.

When a link is shared, these platforms automatically generate a preview using metadata from the page, including the page title, description, and Open Graph image.

Purpose / Why It Matters

The Social Image is often the first impression of a business when a link is shared. A properly sized and relevant image improves visual clarity, reinforces credibility, and increases engagement. Improper sizing or poor image selection may result in cropping, low-quality previews, or inconsistent display across devices.

Rules & Guidelines

Default Requirement

Every Hibu One Smart Site includes a default OG image.
In most cases, the OG image should be derived from the homepage hero image to maintain visual continuity between the preview and the landing page.
A cleaner or cropped version of the homepage hero image may be used when necessary to fit the required dimensions.

Image Size & Aspect Ratio

Minimum size: 1200 × 630 px
Maximum practical size: 2400 × 1260 px
Required aspect ratio: 1.91:1
Images smaller than the recommended size may appear soft or reduced in prominence on high-resolution mobile screens.

Where the Social Image Appears

The OG image may display:

When a link is shared on Facebook or LinkedIn
In iMessage previews on iPhones
In mobile browser link previews

Platform behavior varies:

On iPhone (iMessage and Safari) , OG images commonly appear in link previews.
On Android devices , preview behavior depends on the messaging app and is less consistent.
Some messaging platforms (e.g., WhatsApp, Messenger) may display the OG image; others may not.
Preview behavior is controlled by the external platform, not by Hibu.

Image Selection Standards

The OG image should clearly represent what the business does or the result the customer wants—not just the logo.

Preferred:

A strong homepage hero image
Outcome-focused imagery
Clear service representation

Avoid:

Equipment-only images
Trucks or tools as the primary focus
Text-heavy graphics
Logos alone (unless justified by strong brand recognition)

Logo Usage

If a client requests logo inclusion:

The logo may be layered onto a representative image.
It should not exceed approximately 20–30% of the image width.
Placement should be centered or in the lower third.
Subtle overlays may be used for legibility.
The underlying image must remain meaningful without the logo.

Logo Usage

If a client requests logo inclusion:

The logo may be layered onto a representative image.
It should not exceed approximately 20–30% of the image width.
Placement should be centered or in the lower third.
Subtle overlays may be used for legibility.
The underlying image must remain meaningful without the logo.

Page-Specific Overrides

A page-specific OG image may replace the default. This image appears when that specific page link is shared.

Using unique images per page is encouraged when it improves relevance and clarity. For example:

A roofing page may use a roofing project photo
A siding page may use a siding image
A windows page may use a windows installation image

This ensures the shared preview accurately reflects the content of the page.

Requirements:

Image must meet the 1200 × 630 px (1.91:1) standard
Image should be clear, well-composed, and relevant to the page

If no page-specific image is set, the page will use the default OG image.

Client Submissions

Clients may supply their own Social Image if it meets size, ratio, and file requirements. Hibu will not redesign client-submitted images that do not meet quality standards.

Text-Heavy Images and Mobile Display Rules

Wed, 11 Feb 2026 14:56:55 GMT

Hibu Policy

Text-heavy images must remain readable at mobile breakpoints.

This applies to designed promotional graphics such as:

Flyers
Coupons
Financing advertisements
Sales banners
Multi-offer composites
PDF-based layouts
Any image created primarily for desktop or print viewing

Landscape text-heavy graphics typically fail at mobile breakpoints because embedded text becomes unreadable when proportionally scaled down.

For reference:

Desktop hero images commonly exceed 1200px in width.
Mobile screens typically display between approximately 360px–430px in width.
When a 1200px+ promotional graphic is reduced to mobile width, embedded text becomes too small to read.

If a mobile-friendly version is not supplied, the landscape promotional image must be hidden on mobile.

Text-Heavy Images and Mobile Display Rules

Portrait Text-Heavy Images (Vertical Format)

Portrait orientation does not automatically make a text-heavy image mobile-friendly.

While portrait images do not compress horizontally like landscape graphics, they still introduce mobile usability concerns:

Excessive vertical height in high-visibility placements
Extended scrolling before key content appears
Embedded text that remains difficult to read at mobile width
Dense layouts that reduce visual clarity

If embedded text cannot be clearly read on a phone, the image does not meet mobile display standards.

When text-heavy images fail readability standards:

Users cannot clearly understand the offer or message.
Engagement decreases because visitors will not zoom or decode dense graphics.
Accessibility is compromised, as embedded image text is not readable by screen readers.
Search engines cannot interpret promotional messaging embedded within images.

Mobile readability is the approval standard.

SUB-RULE: USE AS A HERO IMAGE

Text-heavy promotional graphics may not replace the structured Hibu hero.

We will not:

Substitute a promotional flyer for the Hibu hero framework.
Place a text-heavy promotional graphic above the hero.
Remove the structured H1, H2 GEO, Motivating Factors, and CTA in favor of embedded graphic text.

If a client provides a landscape promotional graphic:

It may appear on desktop only.
A mobile-optimized version is required for mobile hero display.
If no mobile version is provided, it will be hidden on mobile.

Portrait promotional graphics may be included below the hero in a supporting section, provided readability standards are met.

For full hero structure requirements, see: Hero Definition

Effective Date: February 11, 2026 Last Updated: February 11, 202 6

Text-Heavy Images: At-a-Glance

What Qualifies as a Mobile-Friendly Version

A mobile-friendly version must be intentionally designed for small-screen viewing and must:

Use a simplified layout
Reduce overall text volume
Maintain clearly readable text at mobile widths (approximately 360px–430px)
Avoid dense multi-offer or multi-callout compositions
Prioritize a single primary message

If the text cannot be comfortably read on a phone without zooming, the image does not qualify as mobile-friendly.

Landscape Text-Heavy Images (Wide Format)

Landscape promotional images are the most common issue.

On desktop, they may appear readable, whereas on mobile, they typically:

Scale down embedded text to unreadable sizes
Compress fine design detail
Lose clarity when proportionally resized

Because the image must scale to fit the screen width, text becomes too small to function.For this reason, landscape text-heavy images are not approved for mobile hero display unless a mobile-optimized version is provided. If a mobile-friendly version is not supplied, the image must be hidden on mobile.

How Third-Party Apps Are Integrated in Duda

Mon, 09 Feb 2026 02:51:40 GMT

Preferred Third-Party Widgets

Hibu Policy

Hibu One Smart Sites are built on the Duda platform and support third-party applications only when they can be implemented using client-side code. Third-party apps must be embedded using HTML, CSS, and/or JavaScript and run entirely within the browser. Server-side integrations, plugins, or backend code execution are not supported.

This definition explains the technical capabilities available for integrating third-party applications within Duda. For recommended tools, refer to Preferred Third-Party Widgets . For rules, limitations, and unsupported use cases, refer to Third-Party HTML Widgets .

Effective Date: February 9, 2026 Last Updated: February 9, 202 6

Definition

Third-party app integration in Duda refers to the ability to embed externally hosted tools into a Hibu One Smart Site using client-side code, such as HTML, CSS, JavaScript, or iframe snippets, without modifying the platform’s backend.

Supported Integration Methods

Embed Code via HTML Widgets
Most third-party apps are added by pasting an embed snippet into an HTML widget or page section. These snippets are typically provided by the third-party service and may include:
HTML markup
JavaScript (inline or externally hosted)
iframe-based embeds
Inline or linked CSS included as part of the snippet
These embeds render client-side and do not require backend access.
Custom Code Areas (Header / Body)
Duda allows custom code to be added site-wide or on individual pages through designated Header HTML or Body End HTML areas. These locations are commonly used for:
Global JavaScript libraries or tracking scripts
Site-wide widgets or embeds
Inline or external CSS rules
Code added in these areas executes in the browser across applicable pages.

Supported Code Types

Key Principle: Any code that runs in the browser can be embedded. Code that requires server-side execution is not supported.

Preferred Third-Party Widgets

Mon, 09 Feb 2026 02:36:04 GMT

Preferred Third-Party Widgets

Hibu Policy

Hibu One Smart Sites support the use of client-supplied third-party widgets that can be embedded using HTML, CSS, or JavaScript. The tools listed in this definition represent commonly used third-party widgets that are known to embed cleanly within Hibu One websites. Inclusion in this list does not imply endorsement, certification, or support by Hibu.

Clients are responsible for selecting, subscribing to, configuring, and maintaining any third-party service. Hibu implements the embed code provided by the client but does not manage or support the third-party platform itself.

For technical rules, limitations, and unsupported integrations, refer to Third-Party HTML Widgets .

Chat & Messaging Widgets

Effective Date: February 9, 2026 Last Updated: February 9, 202 6

Definition

Preferred Third-Party Widgets are externally hosted tools that provide common website functionality—such as scheduling, chat, calculators, maps, reviews, or forms—and can be embedded into a Hibu One Smart Site using client-supplied HTML or JavaScript code.

Purpose / Why It Matters

This definition provides Sales, Account Teams, and Process partners with a clear, centralized reference of third-party widgets that are commonly recommended and compatible with Hibu One Smart Sites. It helps set accurate expectations with clients while avoiding unsupported plugin-based or backend integrations.

General Guidelines

All third-party widgets are client-owned and require a separate subscription with the provider.
Clients must complete setup and configuration directly with the third-party provider.
Hibu implements widgets using embed code supplied by the client.
Hibu does not troubleshoot, customize, or guarantee the performance of third-party tools.
Widget functionality, availability, pricing, and features are controlled by the third-party provider and may change over time.

Scheduling & Appointment Widgets

Calculators

Maps & Location Widgets

Forms & Lead Capture Widgets

Real Estate Widgets (Limited Support)

Important: Full MLS/IDX integrations are not supported. Embeddable real estate widgets may be added, but functionality is limited and SEO benefit is minimal. Clients must be informed of these limitations before proceeding.

Page Introduction Content Standards

Fri, 06 Feb 2026 20:08:26 GMT

Page Introduction Content Standards

Hibu Policy

All Hibu One websites must include a clearly defined introduction on the homepage, category landing pages, about us page, service area page, and all location profile pages.

Page introductions are required and must appear directly after the hero section. Their purpose is to establish context, reinforce credibility, and align page content with user and search intent. Pages without an introduction often lack context, produce weaker SEO signals, and reduce user confidence.

Category Landing Page Introduction

The Category Landing Page Introduction provides a focused overview of a specific service category offered by the business. Unlike the homepage, which presents a broad view of the business, this introduction narrows the scope to validate visitor intent and reinforce relevance through category-specific context.

This section explains the purpose and value of the category while reinforcing expertise, experience, authority, and trust (EEAT). The tone remains professional and informative, avoiding lists, instructional language, or detailed process explanations that belong later on the page.

For brick-and-mortar businesses, applicable locations should be referenced. For service-area businesses, the service areas should be clearly called out. The goal is to confirm relevance, build confidence, and prepare visitors for more detailed service content within the category.

Key Characteristics

Focuses on a single service or product category
Validates visitor intent through category-specific context
Reinforces expertise without instructional or process language
References applicable locations or service areas

See examples

About Us Page Introduction

The About Us Page Introduction establishes the business’s identity and credibility rather than promoting specific services. This section explains who the business is, what it stands for, and why it can be trusted, reinforcing expertise, experience, authority, and trust (EEAT) through reputation, values, and positioning.

When a client provides their own About Us content—such as a written overview, business history, or leadership narrative—that content should be used in place of a Hibu-written About Us introduction. Client-provided content takes precedence and should be respected as the authoritative expression of the business’s identity.

However, all client-provided content must still be reviewed and proofed by Hibu to correct grammar, spelling, clarity, and structural issues, without altering the client’s intent or voice.

Unlike the homepage or category pages, this introduction shifts away from selling and focuses on credibility, motivating factors, and long-term commitment to customers. When available, it may reference background, ownership, leadership, or guiding principles, but it does not require a full origin story to be effective.

The tone remains professional and grounded, avoiding promotional language or service detail. For brick-and-mortar businesses, this section should reference the physical location or locations. For service-area businesses, it should clearly call out the areas served.

Key Characteristics

Centers on identity, credibility, and trust rather than services
Highlights values, reputation, or long-term commitment
Defers to client-provided About Us content when supplied
Requires Hibu review for clarity, grammar, and structure
Avoids promotional claims or detailed service descriptions
References locations or service areas where applicable

See examples

Location Profile Page Introduction

The Location Profile Page Introduction serves as a localized entry point that establishes credibility for a specific city or community. It aligns content with local search intent and confirms relevance for that location.

This introduction is limited to local validation. It must not restate full business overviews or service explanations that exist elsewhere on the site.

Key Characteristics

Explicitly references the location by name
Establishes local credibility and presence
Avoids broad business or service detail
Transitions quickly into location-specific content

See examples

Global Introduction Structure (Applies to All Page Types)

All page introductions must follow a consistent structural pattern to support clarity, scannability, and layout balance across devices. These standards apply to homepage, category landing pages, About Us pages, location profile pages, and service area pages.

Structural Requirements

Each introduction must include a headline .
Each introduction must consist of two short paragraphs .
When layout space permits, a single primary CTA (request action or phone number) may be included beneath the introduction.

Introductions must remain editorial in nature. Headlines, paragraphs, and CTAs should support orientation, credibility, and trust without duplicating content presented elsewhere on the page.

Headline Guidance

For homepage, category landing pages, About Us pages, and location profile pages, headlines must follow the existing headline rules defined within their respective page definitions. No additional headline rules are introduced here for those page types.

Service Area pages are the only exception.

Service Area pages require specialized headline guidance due to their regional scope and first-touch role. Those headline requirements are defined explicitly within the Service Area Page Introduction section and should not be inferred from other page types.

CTA Guidance (updated 4/5/2026)

A CTA must be included within every page introduction, either as a text link embedded in the content or as a button when layout space permits.

Accepted CTA formats:

Text link (primary or secondary CTA)
Button (preferred when space allows)

Text Link Placement Rules:

Text links CTAs may appear at any natural point within the introduction (beginning, middle, or end)
Placement must feel contextually relevant and not disrupt readability
CTA language must be clear, action-oriented, and directly tied to user intent

Layout Constraints:

Buttons should be used when space permits within the design
If space is limited, a text link CTA is required instead of omitting the CTA

Restrictions:

CTAs must not interrupt the editorial flow of the introduction
CTAs must not replace or compete with primary conversion elements elsewhere on the page

Page Introduction: At-a-Glance

Page introductions are short editorial sections placed directly below the hero to establish context, relevance, and trust before deeper page content.

Effective Date: February 6, 2026 Last Updated: April 5, 202 6

Service Area Page Directory Introduction

(updated 02/17/26)

The Service Area Page Directory Introduction (SAP Directory Intro) establishes regional authority for businesses serving multiple cities or communities. It reinforces geographic relevance at a broad level and supports internal linking architecture without duplicating individual service area pages.

This introduction is intentionally limited in scope and must focus on regional positioning, credibility, and long-term consistency. It may reference core services at a high level but must avoid listing individual cities, sub-services, or geographic groupings already displayed elsewhere on the page.

Structural Requirements

A headline is required.
The introduction must include two paragraphs.
A single CTA or phone number may be included when space permits.
Content should remain concise, durable, and structurally consistent across similar service categories.
A primary keyword theme must be clearly defined for each Service Area Page.

Headline Guidance (Service Area Pages)

Service Area headlines must clearly communicate:
The core service or primary competency of the business.
The general region served, expressed broadly rather than through city lists.
Headlines should signal broad regional coverage and remain stable even if the list of cities or service areas changes.

Recommended headline formula:

[Primary Core Service] Across General Geo area (see header geo)
or
Professional [Primary Core Service] Services Throughout General Geo area (see header geo)

Headline must:

Use one designated primary keyword theme.
Remain consistent across all geo pages within the same service category.
Reflect broad regional coverage rather than specific cities.

Headline must not:

List individual cities or towns.
Rotate between keyword variations (e.g., landscaping company vs landscaper vs landscape contractor).
Repeat navigation labels verbatim.
Function as calls to action.
Include stacked keyword variations.

Keyword Variant Guidance

The SAP Directory Intro may target multiple keyword variations that represent the same search intent (e.g., landscaping company, landscaper, local landscaper).

To maintain clarity and avoid cannibalization:

1. Primary Keyword Rule

Each Service Area Page must designate one primary keyword theme.

The primary keyword:

Must appear in the headline.
Must appear naturally in the first sentence.
Anchors the page’s thematic focus.

2. Secondary Keyword Usage

Secondary variations may appear naturally in body copy but:

Must not be stacked.
Must not appear in headings.
Must not compete with the primary keyword.

Variations should read conversationally and organically.

3. Intent Integrity Rule

If multiple keyword variations represent the same user intent, they must not generate separate Service Area Pages.

Intent defines structure — not keyword tool output.

Body Copy Guidance

Paragraph 1 should:

Establish regional coverage.
Reference the primary service category.
Naturally include the primary keyword.
Reinforce geographic relevance without listing towns.

Paragraph 2 should:

Reinforce credibility and experience.
Highlight consistency, craftsmanship, or longevity.
Support trust across the entire region served.

The introduction must not:

Duplicate town lists.
Enumerate detailed service offerings.
Repeat content from individual service area pages.
Over-optimize by repeating keyword variants.

See examples

Homepage Introduction

The Homepage Introduction is a critical opening section that establishes the business’s overall identity, credibility, and scope of services. It serves as the primary first impression for visitors and a foundational SEO element, aligning the business with high-level search intent while reinforcing expertise, experience, authority, and trust (EEAT).

This content introduces who the business is, what it offers, and the value it provides without becoming overly detailed or promotional. The tone is professional and confident, avoiding lists, technical explanations, or deep service breakdowns. Instead, it focuses on clarity, reassurance, and relevance to a broad audience.

For brick-and-mortar businesses, the homepage introduction should reference the physical location or locations. For service-area businesses, it should clearly define the areas served. The section establishes context and trust while guiding visitors naturally into deeper site content.

Key Characteristics

Establishes overall business identity and credibility
Aligns with broad search intent and EEAT principles
Avoids detailed service explanations or technical breakdowns
References physical locations or defined service areas

See Examples

Better Business Bureau (BBB) Logo Usage

Fri, 06 Feb 2026 19:24:54 GMT

Better Business Bureau (BBB) Logo Usage

Effective Date: February 6, 2026 Last Updated: April 3, 2026

Hibu Policy

Hibu may reference the Better Business Bureau (BBB) on client websites only in ways that are accurate, non-misleading, and compliant with BBB trademark and hyperlinking requirements. BBB logos, text references, and links must not imply accreditation, endorsement, or a rating unless the business is officially accredited and the usage is permitted by BBB.

Read This First: Required Rules for BBB Usage

Accreditation status must be verified before approving any BBB seal, rating, or dynamic code.
Verification must be based on the business’s official BBB profile page.
A general browser search (e.g., Google results) is not sufficient for confirmation.
The client is responsible for providing the direct BBB profile URL or proof of accreditation.
Hibu will not independently verify or source accreditation status on behalf of the client.
A valid BBB profile must be provided by the client before any BBB logo, link, or reference can be used on the site. (updated 04/03/26)
If a valid BBB profile cannot be provided, do not include any BBB logo, link, or reference.
Once a valid BBB profile is provided, accreditation status must be verified before approving any BBB seal, rating, or dynamic code. (updated 04/03/26)
If accreditation cannot be confirmed, only a plain BBB logo (no rating) or a text-only link to the BBB profile may be used, provided a valid BBB profile URL has been supplied by the client.
Never imply endorsement, approval, or a letter grade without verified BBB authorization.
Dynamic BBB seals and rating badges must be provided directly by the client via official BBB-generated code.
Only use the provided code exactly as BBB generates it. Do not modify the image file, hyperlink, or rating text unless authorized.
The Hibu design team is expected to rename all uploaded BBB logo files and apply alt text that does not imply accreditation or endorsement.

Definition

The Better Business Bureau (BBB) is a consumer-facing organization that issues public business profiles. Accredited businesses may also receive accreditation seals and letter-grade ratings (A+ through F). Only accredited businesses may use BBB dynamic seal code that displays rating information.

Purpose / Why It Matters

BBB closely controls the use of its name, logo, and accreditation assets to prevent consumer confusion and protect trademark rights. Improper use—such as showing an “A+” badge for a business that is not accredited or not using authorized code—can mislead users and violate BBB rules. This policy protects both Hibu and its clients from compliance risk.

Rules & Guidelines

Allowed Usage

Hibu may include either a plain BBB logo or a text-only link under the following conditions.

Rules & Guidelines

Plain BBB Logo (No Rating) (updated 03/26/2026)

The logo must be a current, official Better Business Bureau (BBB) brand mark , including approved or updated logo variations, and must be either:
Provided by the client, or
Selected from Hibu’s approved asset library
The logo must not include:
Letter grades (e.g., “A+”)
“Accredited Business” language
Accreditation seals or rating badges
The logo must be:
Neutral in appearance
Non-misleading
Hyperlinked directly to the business’s official BBB profile page when a valid profile URL is provided by the client (updated 04/02/2026)
The business must have a valid BBB listing:
This must be confirmed by the DSC
All BBB logos must:
Be used without modification
Be provided by the client or obtained from official BBB-owned properties
Not imply accreditation, rating, or endorsement unless verified

Text-Only Links

A standard text hyperlink may be used instead of a logo, such as:
“View our Better Business Bureau profile”
“See our BBB listing”
“Learn more on BBB.org”
Text links must:
Point directly to the business’s official BBB profile URL
Only be used when a valid BBB profile URL is provided by the client (added 04/02/26)
Avoid mentioning ratings or accreditation unless verified and permitted
Be factual and descriptive

Placement

Non-Accredited BBB Logo (Plain Logo, No Rating)

A non-accredited BBB logo may be placed in the following locations, provided it is hyperlinked directly to the business’s official BBB profile:

The footer, within the badges, partner icons, or accreditation logos area.
Directly beneath the primary CTA in the hero.
The About Us page, visually associated with the About Us introduction copy.

When used, the specific BBB logo must always link to the client’s BBB profile page.

Text-Based BBB References (No Logo, No Rating)

Text-based BBB references may be included throughout site copy, provided they remain factual and do not imply accreditation, endorsement, or a letter grade. Depending on placement text-based BBB references will be hyperlinked to the business’s official BBB profile..

Permitted Locations (Hyperlinked)

Introduction copy on any page
About Us copy
Reasons to Contact Us sections on internal pages
General body copy throughout the site

Permitted Locations (Not Hyperlinked)

Text-based BBB references may appear without hyperlinks in the following sections:

Why Choose Us
Motivating Factors

In these areas, BBB references must remain purely informational and may not function as clickable links.

Accredited BBB Seal (Dynamic Code Only)

When a business is officially accredited and provides authorized BBB-generated HTML code, the dynamic accreditation seal may be placed in limited locations due to technical and layout constraints.

Approved placements include:

The footer
The right gutter, positioned as the last item beneath related links
Near the About Us introduction or Location Profile introduction, when layout supports embedded HTML

Accredited BBB seals must always use the client-provided code exactly as generated and may not be recreated, modified, or converted into static images.

Prohibited Usage

Hibu will not:

Display any BBB logo or text that:
Implies accreditation when the business is not accredited
Displays a letter grade (e.g., “A+”) without verified authorization
Suggests BBB endorsement, sponsorship, or approval
Use:
BBB accreditation seals
Dynamic BBB widgets or embedded rating code without client-provided authorized code
Use language such as:
“BBB Approved”
“BBB Certified”
“Top Rated by BBB”
Link to BBB in a way that is misleading, visually confusing, or inconsistent with BBB trademark guidelines.

How to Get Your BBB Dynamic Seal Code

If the business is BBB Accredited and has access to the BBB Business Portal, they can obtain the official dynamic seal code (which may include rating information). Here’s how:

Log in to the BBB Business Portal at: https://www.bbb.org/all/business-resources/business-login using your BBB business credentials.
Navigate to the section labeled Accredited Business Seals (or similar, depending on your BBB region).
Choose the seal design you want to display (formats/options may vary).
Copy the generated HTML code snippet that appears for your selection.
Provide that HTML snippet to Hibu for exact placement on your website.

Example Placeholder Code

</a>

Important: Only use the provided code exactly as BBB generates it. Do NOT modify the image file, the hyperlink, or rating text in the code unless authorized.

BBB Logo Usage: At-a-Glance

Google Tools & Tracking

Sun, 01 Feb 2026 23:40:50 GMT

Google Tools & Tracking

Hibu Policy

Hibu allows clients to connect their Hibu One Smart Site to Google tools such as Google Analytics, Google Ads, Google Tag Manager, and Google Search Console. All Google tracking must be supplied by the client and added through the Google Tools area in Duda.

Hibu does not create, own, or manage client Google accounts.

Supported Tracking Codes

Hibu supports client-supplied IDs for the following Google services:

Google Analytics – Global Measurement ID (G-) or UA Property ID (UA-)
Google Ads – Conversion ID (AW-*)
Floodlight / DoubleClick – Tracking ID (DC-*)
Google Tag Manager (GTM-*) – ID for managing tags
Google Search Console – Verification meta tag (client supplies code)

Rules and Limitations

Hibu will not create or manage Google accounts (Analytics, Ads, Tag Manager, or Search Console). Clients must provide their own IDs.
Google supports multiple tracking codes per site, so client IDs and Hibu’s internal tag can run together without conflict.
Tracking codes only function on published/live sites — they will not work on proofs.
If tracking appears broken, common causes include:
Site not yet published
Ad blockers preventing data collection
Setup within the past 24 hours (may not be active yet)

Internal Note (Transparency)

For internal testing and performance monitoring, Hibu includes its own Google Analytics tracking ID on every site .

This ID is aggregated across all Hibu websites.
Data from Hibu’s internal tag is not shared with clients .
This setup does not interfere with client-supplied IDs.

Definition

Purpose / Why It Matters

Many clients rely on Google tools to review performance data or compare results with other marketing programs. Supporting client-supplied Google tracking ensures continuity, transparency, and client ownership of analytics data while allowing Hibu to maintain a consistent and secure site framework.

Placement in Duda

All Google tracking IDs and verification codes must be added in the Google Tools tab under SEO & Settings .

Rules for placement:

All tracking IDs must be entered into the Google Tools fields.
Verification codes (for example, Search Console) must be entered as verification values only.
Never paste full script tags or meta tags into the site code or HTML areas.
Google Tools fields must always be used instead of custom code injection.

Transfer From Previous Hibu Sites

If a client’s previous Hibu website included Google tracking, those same tracking IDs must be transferred to the new Hibu One website to maintain reporting continuity.

Rules:

Existing Google Analytics IDs or Google Tag Manager container IDs must be reused.
All transferred IDs must be entered into the Google Tools fields in Duda.
Tracking continuity depends on using the same client-owned Google accounts.

Supported Tracking Codes

Hibu supports client-supplied IDs for the following Google services:

Google Analytics
Global Measurement ID (G-) or UA Property ID (UA-)
Google Ads\
Conversion ID (AW-)
Floodlight / DoubleClick
Tracking ID (DC-)
Google Tag Manager
Container ID (GTM-)
Google Search Console
Verification code (client-supplied)

Only supported ID formats may be added.

Rules & Limitations

Clients must provide their own Google tracking IDs.
Hibu does not create or manage Google Analytics, Google Tag Manager, Google Ads, or Search Console accounts.
Clients retain full ownership, access, and control of all Google data.
Google supports multiple tracking IDs on a single site; client tracking and Hibu internal tracking can run together without conflict.
Tracking functions only on published, live sites and will not work on previews.
If tracking appears inactive, common reasons include:
The site is not yet published
Ad blockers preventing data collection
New setups that have not fully activated (up to 24 hours)

Internal Note (Transparency)

For internal performance monitoring, Hibu includes its own Google Analytics tracking on every site.

This data is aggregated across Hibu websites.
Client data is not shared or exposed through this tracking.
Hibu’s internal tracking does not interfere with client-supplied Google tracking.

Google Tools & Tracking: At-a-Glance

Client-Supplied Google Analytics Access

Hibu can add client-supplied Google Analytics or Google Tag Manager tracking to a Hibu One Smart Site to support deeper performance analysis within the client’s own Google account.

Clients must provide their Google Analytics Measurement ID or Google Tag Manager Container ID. These Google accounts are owned, accessed, and managed entirely by the client. Hibu does not create, manage, or grant access to Google accounts.

Once added, clients can view performance data directly in Google Analytics and compare it alongside reporting available in the Hibu Dashboard.

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Third-Party HTML Widgets

Sun, 01 Feb 2026 23:38:26 GMT

Third-Party HTML Widgets

Hibu Policy

Hibu One Smart Sites support third-party functionality only through HTML-based widgets and client-side embed code. Plugin-based solutions, server-side integrations, and backend code execution are not supported. Third-party HTML widgets may be implemented only when they align with platform capabilities, performance standards, and compliance requirements.

This definition establishes the rules, limitations, and risk considerations associated with third-party HTML widgets. For a curated list of commonly recommended tools, refer to Preferred Third-Party Widgets . For technical integration capabilities, refer to How Third-Party Apps Are Integrated in Duda .

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Definition

Third-Party HTML Widgets are externally hosted tools embedded into a Hibu One Smart Site using client-supplied HTML, CSS, JavaScript, or iframe code. These widgets execute entirely in the browser and do not interact with the site’s backend infrastructure.

Core Rules & Guidelines

Only client-side code (HTML, CSS, JavaScript, iframe) is supported.
Server-side languages (PHP, ASP, Node, Ruby, etc.) are not supported.
Plugins designed for CMS platforms (e.g., WordPress plugins) cannot be installed or executed.
Widgets must be provided as embed code by the client.
Hibu does not customize, debug, or maintain third-party code.
Third-party widgets must not compromise site performance, security, or usability.

Plugins vs. Widgets (Critical Distinction)

Plugins are software extensions that modify or extend a website’s backend functionality. They typically require direct access to the site’s content management system and server environment. Plugins are not compatible with Hibu One Smart Sites.
Widgets are self-contained code snippets that render functionality within a webpage using client-side technologies. Widgets do not require backend access and are the only supported method for third-party integrations on Hibu One.

CRM-Based Forms (Replacement Considerations)

Clients may choose to replace a native Hibu form with a form generated by a third-party CRM such as HubSpot, Salesforce, Zoho, or Pipedrive, provided the form is delivered as an embeddable widget.

Important considerations:

Form submissions will route directly to the client’s CRM.
Hibu conversion tracking for form submissions will no longer apply.
Reporting and attribution within Hibu marketing tools may be impacted.
Clients should consult directly with their CRM provider to confirm form capabilities and integration options.

MLS / IDX Widgets (Limited Support)

Full MLS or IDX integrations are not supported on Hibu One Smart Sites due to platform constraints.

Key Limitations

No backend access for MLS/IDX feeds
Limited or no API compatibility
Reduced SEO value when content is delivered via iframe
Potential delays or lack of real-time data updates
Strict MLS compliance rules that may exceed platform capabilities

Allowed Approach

Embeddable MLS/IDX widgets may be implemented when provided as client-side embed code. Supported examples include:

iHomefinder
IDX Broker Lite
RealBird

Clients must be informed of limitations and manage all subscriptions, setup, and compliance requirements.

Caution: Many MLS/IDX providers offer competing digital marketing services, including websites, SEO, paid search, and social media. Exercise care when recommending these tools, as they may encourage client migration away from Hibu services.

Ecommerce & Payment Platforms

Shopify

Embedding a full Shopify store directly into a Hibu One Smart Site is not recommended. Shopify is resource-intensive and can negatively impact site performance and Google Core Web Vitals when embedded.

Best Practice: Link to the Shopify store from the Hibu site rather than embedding it directly.

Square Plugins

WordPress-based plugins, such as the Square WooCommerce plugin, are not supported. Clients may use Square-provided embeddable widgets or payment buttons when available and supplied as HTML or JavaScript embed code.

Performance, SEO, and Compliance Considerations

Embedded widgets may affect page load speed and Core Web Vitals.
iframe-based widgets generally provide limited SEO value.
Third-party scripts may introduce accessibility or compliance risks.
Hibu reserves the right to restrict or remove widgets that negatively impact site stability or performance.

Client Responsibilities

Select and subscribe to the third-party service
Configure and maintain the widget
Provide valid embed code to Hibu
Manage updates, compliance, and billing with the provider

Password-Protected Pages

Sun, 01 Feb 2026 23:28:24 GMT

Password-Protected Pages

Definition

A password-protected page is a page that requires a user to enter a password before viewing its content. This option is available by request and is best suited for restricting access to specific resources (e.g., downloads or private content).

Rules and Guidelines

Password-protected pages are available upon request.
Each page is protected with a single password entered by the client. Unique logins are not supported.
Password-protected pages are included in the site’s total page count.
Password-protected pages must be set to no index so they do not appear in search engine results.
Dynamic and anchored pages cannot be password-protected.

Example

See the sample password-protected page (password: swordfish).

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Page Types, Navigation Tiers, and Shared Terminology

Sun, 01 Feb 2026 23:04:58 GMT

Page Types and Navigation Tiers

Definition

Across teams, the same page is often referred to by different names depending on perspective — navigation depth, content function, SEO intent, or internal shorthand. For example, what one team calls a Core Page may also be referred to as a Tier 2, Interior Page, Service Page, Product Page, or even a “kitten.”

This guide aligns those terms into a single, consistent framework by defining:

What each page type is
How it typically appears in navigation
How different terms map to the same structural role

The goal is not to eliminate nuance, but to ensure we are always talking about the same thing — even when we use different words.

Key Principles

Navigation Tiers Are Structural, Not Semantic

“Tiers” describe where a page lives in navigation, not what the page is called. A single page type may appear in different tiers depending on strategy.

Page Types Describe Function

Page types (Home, Category, Core, Utility, Location) describe what a page does, regardless of what it is called in conversation.

Terminology May Vary — Structure Should Not

Multiple names may exist for the same page, but the underlying structure and intent should always align to this framework.

How to Use This Page

Use this page as the source of truth when:

Planning site architecture
Discussing navigation tiers
Writing documentation or training materials
Aligning across Product, Design, SEO, Content, and Build teams

If a term is used elsewhere (for example, Core Page, Tier 2, or Service Page), it should be traceable back to a definition here.

Page Types, Navigation Tiers, and Terminology Mapping

The table below maps normalized page types to:

Typical navigation tier placement
Common alternate terms used internally
Notes on how and when those terms apply

This allows different teams to work from a shared understanding, even when approaching pages from different angles.

Page Types, Navigation Tiers, and Terminology Mapping

The table below maps normalized page types to:

Typical navigation tier placement
Common alternate terms used internally
Notes on how and when those terms apply

This allows different teams to work from a shared understanding, even when approaching pages from different angles.

Category, Core, Utility, and Location Relationships

Every Core Page either:
Lives under a Category (Tier 2), or
Stands alone as a Tier 1 Core Page when strategically important
Category Pages function as parents and may:
Contain Core Pages, or
Act as a child Category under a broader Category
Utility Pages sit outside the category/core hierarchy but may host their own Tier 2 subpages
Location Pages mirror category behavior but are geography-driven

Why This Matters

Without shared terminology:

Planning becomes inconsistent
Documentation drifts
Teams talk past one another
This page exists to prevent that — and to ensure that regardless of the term used, the meaning is clear, consistent, and shared.

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Mega Menu Navigation

Sun, 01 Feb 2026 22:40:40 GMT

Mega Menu Navigation

Hibu Policy

The Mega Menu is a desktop-only navigation pattern used on Hibu One Smart Sites with larger service structures. It is required when a site includes three or more Tier 1 Category Landing Pages (CATs) and is designed to present services and related pages in a clear, multi-column layout.

The Mega Menu is automatically generated from the site structure defined in the Pages panel and must not be manually recreated or overridden.

Navigation styling—including background and link colors—is controlled by Theme Colors. Hover states are fixed and cannot be modified.

Effective Date: February 1, 2026 Last Updated: March 26, 2026

Definition

A Mega Menu is an expanded navigation system that displays Tier 1 CATs, their child pages, and approved standalone Tier 1 pages in a structured, multi-column layout. By default, all navigation groups are fully expanded, allowing users to view all available links at once.

Rules & Guidelines

When to Use a Mega Menu

Use when the site includes three or more Tier 1 CATs
Each CAT should have two or more child service pages
Standalone Tier 1 pages may be included when appropriate

When Not to Use a Mega Menu

Do not use when the site has two or fewer CATs
Do not use when standard navigation is sufficient

Navigation Structure Requirements

The Mega Menu is intended for:
Tier 1 CATs and their child pages
Approved standalone Tier 1 pages
Utility pages (e.g., About, Contact, general informational pages) are excluded by default
These may only be included if explicitly requested by the client
Important: Tier 1 CAT groups (a CAT and all associated child pages) or standalone Tier 1 pages may be removed from the Mega Menu and promoted to the top-level navigation when requested
When a CAT is removed, only the parent page needs to be excluded
All associated child pages will be removed automatically
All changes must be reflected in both:
The Pages panel / navigation structure (for placement in top-level navigation)
The Mega Menu settings (to exclude pages from the Mega Menu)
See How to Move Pages Out of the Mega Menu →

Layout & Behavior

The layout typically starts with three columns
It can expand up to five columns as needed
Column count should be adjusted to maintain balance and readability
The Mega Menu displays fully expanded by default , showing all CATs and their child pages at once
The Mega Menu must not introduce vertical scrolling at 1366px browser width
If any scrolling appears at this breakpoint, the layout must be adjusted
See vertical scroll example →
To resolve overflow:
Increase the number of columns (up to five)
Redistribute content evenly across columns
Collapse pages only when column expansion and redistribution do not resolve overflow
The layout updates automatically as pages are added, removed, or reorganized
On mobile, the Mega Menu collapses into a single-column navigation experience

Content Inclusion & Exclusion

The Mega Menu reflects the structure defined in the Pages panel
Pages or entire CAT groups can be excluded when they should not appear
Any exclusions should align with the intended navigation experience
Tier 1 interior pages are not included by default and must be intentionally accounted for

Ordering & Page Arrangement

Default ordering is alphabetical
Ordering can be adjusted to match a client’s preferred sequence
The Mega Menu displays pages in the exact order defined in the Pages panel
To change the Mega Menu order, pages must be rearranged in the Pages panel
See how Mega Menu ordering works →

Styling Rules

Background and link colors are controlled by:
Theme Color 10 – Navigation Background
Theme Color 11 – Navigation Text
Link colors must follow standard navigation rules
Hover behavior is predefined and cannot be changed

Typography & Visual Consistency

Fonts must match global navigation styles
Child links must appear smaller than parent links
Chevron icon:
Must match the navigation font color
Must not be changed unless specifically required
Must remain at the default size

Additional Constraints

The Mega Menu is desktop-only; tablet and mobile uses standard hamburger navigation behavior
All pages should be represented in the navigation structure, regardless of total page count
The Mega Menu reflects the structure defined within the navigation system and updates accordingly

Hidden Pages

Sun, 01 Feb 2026 22:37:21 GMT

Definition

A hidden page is a page that is available by request but not attached to the site’s global navigation. It can be accessed directly via URL and is included in the site’s total page count.

Rules and Guidelines

Hidden pages must contain complete content and design (no placeholders).
Hidden pages are available only by request and do not appear in global navigation menus.
To fully hide a page, the Hibu Team must:
Hide the page on all devices.
Set the page to no index to prevent it from appearing in search engine results.
Hidden pages are included in the site’s total page count.
A unique title tag must be included.
A meta description is optional and not required.

Required Build Process

To properly hide a page:

In the page list, click the three vertical dots to the right of the page name.
Select Show or Hide from Navigation , then choose Hide from All .
Once hidden, a grey “hidden page” icon will appear next to the page name.
Again, click the three vertical dots and select Edit Page SEO .
Under SEO settings, toggle Set page to no index .
This ensures the page will not appear in search engine results, even though it still exists in the sitemap.xml file.

Hidden Pages

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Title / Meta - Out of Norm Pages

Sun, 01 Feb 2026 20:58:00 GMT

Title / Meta - Out of Norm Pages

Hibu Policy

Every out-of-norm page on a Hibu One Smart Site must include:

One unique title tag built to the approved formula for that page type

One unique meta description aligned with the page's purpose and content, written within 150–160 characters

Title tags and meta descriptions must be accurate, aligned with page intent, and written to support click-through from search results. No component may be fabricated or assumed. All content must reflect the actual business.

Definition

Title tags and meta descriptions are HTML elements that control how a page appears in search engine results pages (SERPs) and when shared on social platforms.

The title tag acts as the headline.

The meta description acts as supporting copy.

Together, they function as a mini advertisement for the page — the pre-click version of the on-page experience. If the user does not click, the rest of the page experience does not occur.

Out-of-norm pages are pages that fall outside the standard home, category landing, and core / product / service page types. Each has its own approved title tag formula and meta description guidance. This guideline covers all currently defined out-of-norm page types.

Rules and Guidelines

Out-of-Norm Title Tag Structure

Page Name | NOB

Out-of-Norm Meta Description Structure

Identify the page type
Describe what content is on the page
Include the business name and location when relevant
When appropriate and space permitting, explain how the page helps the visitor (usefulness)

Purpose / Why It Matters

Title tags and meta descriptions:

Drive the first conversion: the click.
Signal relevance to search engines.
Influence click-through rate (CTR).
Establish consistency between the search listing and on-page content.
Support conversion-first messaging before a user ever reaches the site.

In many cases, the search result is the first and only impression a user receives. These elements must be written intentionally.

Current Display Standards

Search engines do not impose a strict technical character limit. However, they do have what is considered an optimum range. This is what informs Hibu's character-length standards.

Title Tags

Google typically displays up to ~60 characters on desktop before truncating.
Ideal performance range: ~50–55 characters.
Maximum upper boundary: 60 characters.
Writing target: 55 characters.

Going to 57–60 characters is acceptable when necessary. The goal is clarity and control, not arbitrary enforcement.

Meta Descriptions

Desktop display typically truncates around ~155–160 characters.
Mobile truncates earlier.
Ideal range: 150–160 characters.
Critical messaging should appear in the first ~110–120 characters.

Front-loading key information reduces the impact of truncation.

Examples:

Note: if you encounter a page that doesn't fall under one of the below headings, follow the formula for the closest match to the page type you have.

About Us - Specific to a company (default Smart Site About Us page)

Title Tag: About | NOB
Meta Desc: NOB [verb] offers / provides / serves / specializes in, etc. [Core business keyword (or phrase)] [City, ST or serving area]. Motivating factor. Motivating factor (space permitting). Motivating factor (space permitting).

About | Scott Family Dentistry

Scott Family Dentistry offers affordable dental care to the Cherry Hill, NJ community. Walk-ins are always welcome, and most insurance is accepted.

About | Mama's Pizza

Mama's Pizza has been serving the Lansdowne, PA area since 1975. Daily specials. Free deliveries for orders over $30. Open 7 days a week.

About | Beechwood Landscape

Beechwood Landscape, serving the Tri-State Area, offers lawn care services including, mowing, fertilization, and weed control. Senior discounts. Free estimates.

Blog

Title Tag: Blog | NOB
Meta Desc: Learn more about what's new and important/exciting/fun at NOB (with location/geo if applicable and space permitting).

Blog | Flanagan's Towne Auto Body

Learn more about what's new and important at Flanagan's Towne Auto Body of Unity, WI.

Blog | Wilson's Home Exteriors

Learn more about what's new and important at Wilson's Home Exteriors. Serving all of South Jersey.

Calendar

Title Tag: Name of Calendar | NOB
Meta Desc: View [NOB's] {name of calendar].

Yoga Class Schedule | Strike a Pose Yoga Studio

View Strike a Pose Yoga Studio's yoga class schedule.

Event's Calendar | Pennsauken Swim Club

View Pennsauken Swim Club's events calendar.

Coupons / Specials, Discounts / Offers, Rebates etc.

Title Tag: Coupons (or Specials, Discounts, etc.) | NOB
Meta Desc: [Clients / Customers / Patients -- as defined] can save save money in location/geo with [NOB]'s coupons / specials / discounts / offers / rebates, etc. Click to learn more.

Coupons | Tarry's Tax Service

Clients in the Columbus, OH area can save money with Tarry's Tax Service coupons. Click to learn more.

Specials | EZSmiles Dental

Patients in Boca Raton can save money with EZSmiles Dental specials. Click to learn more.

Specials and Rebates | Buzzy's HVAC

Tri-State area customers can save money with Buzzy's HVAC specials and rebates. Click to learn more.

Careers / Job Postings

Title Tag: Careers / Job Postings / We're Hiring, etc | NOB
Meta Desc: Join the winning team at [NOB] today. Click to learn more.

Job Postings | Mr. Robot

Join the winning team at Mr. Robot today. Click to learn more.

Careers | Man of Steel Security

Join the winning team at Man of Steel Security today. Click to learn more.

We're Hiring | Buzzy's HVAC

Join the winning team at Buzzy's HVAC today. Click to learn more.

eCommerce / Online Store

Title Tag: Online Store | NOB
Meta Desc:
Shop for items at [NOB]. Add "...and more." if applicable.
-OR-
Shop for [NOB] items (max 3). Add "...and more." if applicable.

Online Store | Wilson's Garden Center

Shop for mulch, stone, and soil by the yard at Wilson's Garden Center.

-OR-
Shop for mulch, stone, soil and more by the yard at Wilson's Garden Center.

Online Store | Buzzy's Pizza

Shop for Buzzy's Pizza gift certificates, t-shirts, and hats.

-OR-
Shop for Buzzy's Pizza gift certificates, t-shirts, hats, and more.

Finance

Title Tag: Finance | NOB
Meta Desc: Click to learn more about NOB financing options.

Finance | Buzzy's HVAC

Click to learn more about Buzzy's HVAC financing options.

Finance | EZSmiles Dental

Click to learn more about EZSmiles Dental financing options.

FAQs / Frequently Asked Questions

Title Tag: FAQs | NOB
Meta Desc: Visit our FAQs page to learn more about NOB our products/services.

FAQs | Flanagan's Towne Auto Body

Visit our FAQs page to learn more about Flanagan's Towne Auto Body and our services.

FAQs | Fred G. Johnson, Esq.

Visit our FAQs page to learn more about Fred G. Johnson, Esq. and our services.

Gallery

Title Tag: Gallery type (Portrait Gallery, Project Gallery, Before / After Gallery, New Roof Gallery, etc.) | NOB
Meta Desc: Browse / View / Take a look at, etc. [NOB] Type of Gallery (e.g. Portrait Gallery, Project Gallery, Before / After Gallery, New Roof Gallery, etc.) [featuring/showcasing type of images] -- if applicable, available, or apparent.

Project Gallery | Andrew's Roofing

View Andrew's Roofing Project Gallery featuring our recent residential and commercial roofing, siding, and window projects.

Before / After Gallery | Bob's Auto Restoration

Take a look at Bob's Auto Restoration Before/ After Gallery showcasing or classic and muscle car rebuilds.

Meet Our (or Your) Team, Technicians, Trainers, Attorneys, etc

Title Tag: Meet Our Team / Technicians / Trainers / Attorneys, etc. | NOB
Meta Desc: Our team/ technicians, trainers offer / provide / serve / specialize in, etc. [Core business keyword (or phrase)] [City, ST or serving area]. Motivating factor. Motivating factor (space permitting). Motivating factor (space permitting).

Meet Our Dentists | Pine Belt Dental PLLC

Out dentists specialize in general dentistry in Hattiesburg, MS. Advanced certified coursework. Cosmetic and restorative dentistry.

Menu (one menu)

Title Tag: Menu | NOB
Meta Desc: Browse/View NOB menu including / featuring / specializing in / serving [menu highlights e.g. appetizers, entrees, desserts, and kids menu, etc.]

Menu | 6 Guys Burgers

Browse 6 Guys Burgers menu featuring fried pickles, hand cut french fries, famous 1/2 pounder burger, breakfast burger, and impossible burger. At 6 Guys Burgers, we’re better than 5 Guys—because we’ve got one more guy.

Menu | Flo's Diner

View Flo's Diner complete menu including breakfast, appetizers, lunch, and dinner entrees.

Menu (multiple / specific)

Title Tag: Menu Name | NOB
Meta Desc: Browse/View NOB menu including / featuring / specializing in / serving [menu highlights e.g. appetizers, entrees, desserts, and kids menu, etc.]

Breakfast Menu | Bob's Burgers

View Bob's Burgers breakfast menu featuring steak and eggs, country fried chicken and waffles, pancakes, and 5 flavors of oatmeal.

Cocktail Menu | Lombardi's

Browse Lombardi's cocktail menu featuring frozen drinks, martinis, craft beers, scotches, whiskies, and dessert liqueurs.

Patient Forms / Resources

Title Tag: Patient Forms | NOB
Meta Desc - Option 1 for print / download forms meta description; Option 2 for online forms meta description
Print and fill out (or complete) NOB [type of form(s)] [instruction summary]
Online [type of form(s)] from NOB. [instruction summary]

Patient Forms | Aspen Chiropractic

Print and fill out these convenient Aspen Chiropractic new-patient forms before your first visit.

Patient Forms | PM Pediatric

Online patient and insurance forms from PM Pediatric. Simply complete the forms before your first visit.

Request __________________ Form

Title Tag: Request _____________ | NOB
Meta Desc - Request _________ [service, appointment, free estimate, call back, etc] from NOB. Motivating factor. Motivating factor (space permitting). Motivating factor (space permitting).

Request Home Inspection | A1 Waterproofing

Request a free estimate from A1 Waterproofing. Financing options are available. 24/7 emergency services. License, bonded and insured.

Request Appointment | Christine's Auto Shop

Request appointment with Christine's Auto Shop. Open 7 days a week. ASE Certified. Weekly specials.

Reviews

Title Tag: Reviews | NOB
Meta Desc - Read our [customer type e.g. patients, customers, clientele, patrons, etc -- as defined during consultation] reviews about NOB. Primary CTA.

Reviews | Dr. Steven Sirken

Read or post patient reviews about Dr. Steven Sirken. Call today to schedule your appointment.

Reviews | DH Painting

Read or post client reviews about DH Painting. Call today to schedule your in-home consultation.

Reviews | Nerenberg Law Associates, P.C.

Read or post client reviews about Nerenberg Law Associates, P.C.. Call today to schedule your free case review

Testimonials

Title Tag: Testimonials | NOB
Meta Desc - Read our [customer type e.g. patients, customers, clientele, patrons, etc -- as defined during consultation] testimonials about NOB. Primary CTA.

Testimonials | Dr. Stephen E. Paul

Read patient testimonials about Dr. Stephen E. Paul. Call today to schedule your appointment.

Testimonials | Solid Wood Cabinets

Read customer testimonials about Solid Wood Cabinets. Call today to schedule your in-home consultation.

Testimonials | Flywheel, Shyster, and Flywheel

Read client testimonials about Flywheel, Shyster, and Flywheel. Call today to schedule your free case review.

Service-Based Businesses (travels to customer)

Option 1:

Primary CTA [NOB] for your specific keyword phrase, specific keyword phrase, specific keyword phrase throughout the [broader service region].
Option 2:
Schedule your [form type] or call to speak with our team about your [keyword phrase] and related services throughout the [broader service region].

Brick-and-Mortar (single location)

Option 1:
Visit [NOB] for [keyword phrase], [keyword phrase], and [keyword phrase] at our [HQ City] location, proudly serving the [broader service region].
Option 2:
[NOB] provides trusted [keyword phrase] from our [HQ City] office, supporting customers throughout the [broader service region].

Brick-and-Mortar (multiple locations)

Option 1:
Visit [NOB] for your specific keyword phrase, specific keyword phrase, specific keyword phrase at any of our [#] locations, serving the wider [broader service region].
Option 2:
Call [NOB] for your specific keyword phrase, specific keyword phrase, specific keyword phrase at our [#] locations throughout the [broader service region].

Geo Pages (GEOs)

Title Tag: Product/Service Keyword | City, ST | NOB
Meta Desc: HVAC Repairs | Drexel Hill, PA | Joe’s Plumbing

Meta Description Requirements

Meta descriptions for GEOs are written manually and must:

Follow the homepage meta-description style
Include the Geo Town when relevant
Never imply the business is physically located in the GEO town

Single-Location Brick-and-Mortar

Option 1:
Primary CTA [NOB] for your [keyword phrase] and related services throughout the [Regional Area Name].
Option 2:
Visit [NOB] or call today for [keyword phrase] and more throughout the [Regional Area Name].
Option 3:
Schedule your [form type] or call our team for [keyword phrase] across the [Regional Area Name].

Multi-Location Brick-and-Mortar

Option 1:
Primary CTA [NOB] for your [keyword phrase] across all our [Location Count] locations throughout the [Regional Area Name].
Option 2:
Visit [NOB] or call today for [keyword phrase] supported by our locations throughout the [Regional Area Name].
Option 3:
Schedule your [form type] or call our team for [keyword phrase] at any of our locations throughout the [Regional Area Name].

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

About ______________ - Specific to an individual (i.e. bio page)

Title Tag: Prefix First Last, Title | NOB
Meta Desc: NOB [verb] offers / provides / serves / specializes in, etc. [Core business keyword (or phrase)] [City, ST or serving area]. Motivating factor. Motivating factor (space permitting). Motivating factor (space permitting).

Dr. Rufus T. Firefly, DDS | Scott Family Dentistry

Dr. Rufus T. Firefly, DDS has been specializing in family dentistry in the Boston area since 1994. Voted Top Doc by Boston Magazine 10 years in a row.

Joe Howe, Managing Partner | Dewey, Cheatem & Howe

Joe Howe, Managing Partner, has been specializing in bankruptcy filings in the Trenton area since 2005. Honored by Who’s Who In American Law for over 7 years.

Form Restrictions for Medical Related Service Websites

Sun, 01 Feb 2026 20:50:46 GMT

Form Restrictions for Medical, Legal, and Regulated-Service Websites

Policy
Hibu does not allow “Interested in Services” drop-down fields or open “Message/Comments” text fields on any form for websites associated with medical, healthcare, or insurance services.

This rule exists to prevent collection of protected health information (PHI) on our websites.

Related: Sensitive Restrictions Data and Prohibitive and Restricted Verticals

What This Policy Requires

No Services Drop-Down
Forms must not include any field that allows a visitor to select or describe medical, health or insurance services.
No Message or Free-Text Field
Forms must not include open comment boxes where visitors could disclose protected or sensitive information (e.g., symptoms, diagnoses, medical history, insurance status, etc.).
Permitted Fields
Only non-sensitive, structured fields may be used, such as:
Name
Phone
Email
Preferred appointment date/time
Preferred contact method

Medical & Healthcare Providers

Bariatric medicine
Cardiologists
Dermatologists
Endocrinologists
Family medicine practices
Fertility clinics
Gastroenterologists
General medical practices
Hospitals and medical centers
Internal medicine practices
Nephrologists
Neurologists
Obstetrics & Gynecology (OB/GYN)
Oncologists
Orthopedists
Pediatricians
Primary care physicians
Pulmonologists
Rheumatologists
Sports medicine practices
Specialty physicians (all specialties)
Urgent care centers
Walk-in clinics
Other physicians

Industries and Business Types Covered by This Policy

This policy applies to any business, practice, organization, or professional service that involves medical care, healthcare, diagnostic services, therapy, insurance handling, or related services , including the following types of businesses:

Dental & Oral Health Providers

Dental clinics and dental surgery centers
Endodontists
General dentists
Oral surgeons
Orthodontists
Pediatric dentists
Periodontists
Prosthodontists

Chiropractic & Musculoskeletal Providers

Chiropractic wellness centers
Chiropractors
Physical rehabilitation clinics
Spinal specialists

Therapy, Behavioral Health & Wellness

Addiction treatment centers
Behavioral health centers
Counselors and therapists
Eating disorder clinics
Marriage and family therapists
Mental health clinics
Psychiatrists
Psychologists
Substance abuse clinics

Insurance-Related Businesses

Dental insurance brokers
Disability insurance specialists
Health insurance brokers
Life insurance agencies
Long-term care insurance agencies
Medical insurance brokers
Medicare/Medigap advisors

Other Regulated or Sensitive Service Categories

Assisted Living Facilities
Blood donation centers
Compounding pharmacies
Genetics testing services
Home health agencies
Hospice care providers
Medical equipment suppliers (when patient details may be shared)
Nursing homes, nursing services and nurse practitioners
Pharmacies (independent or chain)
Specialty caregiving services
Telemedicine or virtual care providers
Wellness clinics that perform medical assessments
Attorney that works with any of the above, the message field is not allowed (added 3/31/26)

Rehabilitation & Specialized Care

Allergy & immunology clinics
Audiologists and hearing clinics
Diagnostic labs
Medical imaging centers
Neurological rehabilitation centers
Occupational therapy providers
Ophthalmologists
Optometrists
Pain management clinics
Physical therapy clinics
Radiology centers
Sleep clinics
Speech therapy clinics

Cosmetic, Aesthetic & Elective Medical Services

Cosmetic dermatology practices
Laser treatment centers
Medical spas (med spas)
Plastic surgeons
Vein treatment clinics
Weight-loss clinics with medical oversight

Effective Date: February 1, 2026 Last Updated: March 31, 202 6

Auto-responder Emails

Sun, 01 Feb 2026 20:34:51 GMT

Hibu Policy

Hibu supports an optional form auto-responder that sends an automated email confirmation to the person who submits a form on a Hibu One website. Auto-responders can only be enabled when explicitly requested by the client and when all required client-provided information is supplied.

Auto-responders are configured at the individual form level. When a client requests an auto-responder, Hibu must manually apply the same approved configuration to each eligible form. Auto-responders are not global and do not automatically apply across all forms.

Auto-responder Emails

Definition

A form auto-responder is an automated email sent to a form submitter immediately after a successful form submission. The email confirms receipt of the inquiry and displays a custom client-approved message followed by a copy of the submitter’s completed form information.

Rules & Guidelines

Client Request Requirement

Auto-responders are not enabled by default.
Auto-responders can only be added if the client explicitly requests them.
Auto-responders are configured per form and must be manually added to each eligible form.

Eligible Forms

Hibu will only add auto-responders to the following form types:

Request forms embedded on request-based pages (for example, Request a Quote or Request an Estimate)
The Contact Us form found on the Contact page (also referred to as the Send a Message form)
Custom forms requested by the client (for example, Submit Your Resume forms)

Auto-responders are not added to hero forms.

Required Client Inputs

Before an auto-responder can be enabled, the client must provide:

The email subject line
The full email message content

If either item is missing, the auto-responder cannot be added.

Client-Facing Script (Reference)

Before enabling an auto-responder, teams should clearly communicate the following to the client. This script may be copied into site comments, sent via email, or read aloud during a call:

Yes, we can add an auto-responder to your website forms. Before we can do so, we’ll need you to provide the email subject line and the exact message you want the email to contain. This message will appear above a copy of the customer’s submitted form information. The email is sent from a no-reply address, and replies are not monitored.

Below is an example of the type of message you might choose to include. You’re welcome to use this as-is or provide your own wording.

‘Thank you for reaching out to [Business Name]. We’ve received your request and will be in touch shortly to discuss next steps. If you need immediate assistance, please feel free to call us at [Phone Number].’

Thank You Page Requirements

When an auto-responder is enabled, Hibu must update the site’s system Thank You page.

Every Hibu One site includes a system Thank You page that is hidden from navigation.
The Thank You page must remain no-indexed. Indexing is disabled by default and must not be enabled.
The placeholder content on the Thank You page must be replaced with the client-provided auto-responder message.

Required Thank You Page Note

The Thank You page template (located in the Xtra Page folder) includes a standard confirmation note placed below the client’s message. This note is part of the Thank You page structure and must remain in place.

The note communicates that:

The visitor will receive an automatic confirmation email for their form submission
The email subject line (entered by the team)
The business name shown as the sender (entered by the team)
Guidance to check junk or trash folders if the email is not visible

The template includes placeholders for the business name and email subject line, which must be populated during setup.

This confirmation note appears on the Thank You page only and must not be included in the auto-responder email itself.

Platform Behavior (Duda)

By default, Duda sends an auto-reply to the form submitter when a valid email address is provided.
Hibu controls whether the auto-reply is enabled or disabled using the Auto-reply to form submitter toggle.

Sender Email Address

Auto-responder emails are sent from no-reply@websites.hibu.com .
This sender email address cannot be changed.
Replies to these emails are not monitored.

From Name

The visible "From name" in the recipient’s inbox initially uses the client’s business name.
This value must be manually entered during setup; it is not applied automatically.
If the client later requests a change to the sender name, Hibu may update it upon request.
Hibu does not proactively suggest alternative sender names.

Email Subject Line

The subject line must be provided verbatim by the client.
Hibu does not create, edit, or optimize subject lines.

Submitter Form Response Copy

A copy of the submitter’s completed form fields must be included in the auto-responder.
The option to include the submitter’s form response is not enabled by default.
Teams are required to manually select the option to include the form response during setup.
The form response section cannot be edited, reordered, or removed.

Email Message Content

The email message body must be provided verbatim by the client.
The custom message always appears above the submitter’s form response.
Hibu does not edit, rewrite, or optimize client-provided message content.

Auto-responder Emails: At-a-Glance

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Common Things to Look For

Sun, 01 Feb 2026 20:33:18 GMT

Common Things to Look For When Editing AI Content

There are a number of things that Copywriters and QA should look for when editing sites created by AI.

Ensure Clarity and Readability: Ensure that the AI-generated content is clear, coherent, and free of grammatical errors. Content should be engaging and persuasive.
Optimize for SEO: Leveraging your SEO expertise, you should optimize the AI-generated content for search engines.
Maintain Brand Voice: It's important to ensure that the edited content maintains the brand voice and tone of the client. Consistency in messaging is crucial for building a strong brand identity.
QA: Conduct thorough quality checks to ensure that the edited content meets high standards of quality, accuracy, and relevance.

Whether your role is Copywriter or QA, it's crucial to use your expertise in copywriting and SEO to enhance the quality and effectiveness of content generated by AI for small and medium-sized business websites. Look for things such as:

Repeated phrases & repetitive copy
Hallucinations
Consistency of language & NOB
Applicable CTAs
Appropriate & consistent tone written for the correct audience

Repeated Phrases

We’ve identified several phrases that get heavily overused by the AI tool. These phrases are usually fluff or “purple prose,” and do little to add quality content to our sites. While we instruct AI to not use them, it will still often slip them in throughout the text. Please eliminate as many of these as possible and replace with more appropriate text where necessary.

Some phrases that AI might overuse include:

"Welcome to..."
"Unleash the power of..."
"Reap the benefits of..."
"In the heart of..."
"Top-notch"
"Top-quality"
"Top-tier"
"Picture this, ..."
"Your go-to..."
"We're not just..."

If you see any other “fluff” phrases that don’t make sense or add value, feel free to eliminate or replace them as well.

Repetitive Copy

AI may repeat the same motivating factors and offers on the same page. While it's important to include Motivating Factors on each page, repeating the same ones verbatim on the same page can create a poor experience for the reader. Look for repeated or similar text throughout a page and edit as needed.

E.g. “Free estimates” being used 3 or 4 times on the same page is repetitive content, but being used once per page is not.

Repetitive Copy

E.g. “Free estimates” being used 3 or 4 times on the same page is repetitive content, but being used once per page is not.

CTAs

Each section of copy should include a CTA
The CTA will usually come at the end of the copy section
There should only be one CTA per paragraph
This will help avoid mistaken clicks when viewing in mobile
Most CTAs in the copy will be some variation of “Contact us today.”
Reach out to us
Get in touch with us
We’d love to hear from you
This will allow for injection of textable RCFs where necessary
Copy CTAs can link to either the Contact page or the Form page
Callout CTAs should be either the primary or secondary CTA
This is up to the writer/editor’s discretion, and should be based on what makes sense for the page and the callout
Refer to the Callout Training for examples and more details

Hallucinations

A hallucination occurs when AI misinterprets instructions or generates facts, services, or claims that were not provided. All page copy must be reviewed for hallucinations and corrected or removed as needed.

Common examples include:

Stating “In business for over 30 years” when the questionnaire only indicates “over 30 years of experience.”
Assuming a business offers a related service (e.g., “transmission installation”) because it offers another (e.g., “transmission repair”).
Adding unsupported claims such as “We offer emergency services” when this is not indicated by the client.
Incorrectly including commercial services when the business only offers residential services, or vice versa.
Any claim, service, or qualifier that is not explicitly supported by the client questionnaire or approved inputs must be edited or removed.

Consistent use of the NOB

Use the full NOB with extensions (e.g. LLC, PLL, Inc, etc.) once per site. Once per page, the full NOB without extensions should be used. All other instances of the NOB should use the short, informal version as dictated by the questionnaire. We recommend removing any extensions such as "Inc" or "LLC" before running the copywriter tool, and then manually adding the extension once per site (the first mention of the NOB is the best place to do this). It may also be useful to edit the NOB in the Copywriting Tool to use the shortened version of the NOB (if applicable) so that less editing needs to be done on the final site.

Know the Audience

The AI will often write its copy with a general consumer in mind, but many of our client target other businesses. When editing, make sure that the copy is writing to the correct audience, updating words like "residents" or "homeowners" as needed.

Consistency of Language

Occasionally, AI with return copy with British English spellings instead of American English. With the exception of certain affectations (e.g. “theatre” vs. “theater”) that may be by design, use American spelling.
“colour” should be “color”
“favourite” s/b “favorite”
Etc.
AI may confuses “warrantees” with “warranties.”
Warrantees: people to whom a warranty is given
Warranties: the plural of warranty, i.e., the actual written guarantees

Meta (Created by QA Using the SEO Tool in HWP)

With the exception of the Home Page Title Tag, use what the tool returns. Some editing may be required (removing pipes from descriptions, removing the phone number, other edits at the writer's discretion). As the tools in HWP are refined, this section will be updated to reflect any new processes and guidelines.

Home Page Title Tag: Edit to BAU per QAF 624
Other Title Tags: Use what HWP returns, but edit out phone number and NOB extensions if they are included
Ensure that the GEO location has been correctly returned by the SEO tool, and edit if necessary for applicable pages
Meta Descriptions: Use what HWP returns, but edit out the phone number and NOB extensions if they are included

Running Into Issues?

Collaborate with AI Hibu Process Team! Reach out to the Hibu Process Team to provide feedback on the quality of the content generated or for concerns when the AI system is not working as expected.

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Copywriter and QAE Responsibilities

Sun, 01 Feb 2026 20:17:32 GMT

Copywriter and QAE Responsibilities

Below are a list of steps the Copywriter and QAE should take when editing AI-created content.

Once in site Copywriter will complete the following.

Create backup in HWP “Pre_Copywriting_Kim_Collmann_CW”
Verify content is related to page and AI did not hallucinate
e.g. stump removal page indicates they do stump grinding and it was not on the questionnaire. This is an example of how AI might make things up.
Arrange pages in correct order using the questionnaire.
Reviews section if present on account.
Fill out motivating factors
H1 titles for home and internal pages (core pages)
Verify primary and secondary CTAs
Request form if it is part of the CTAs
Copywriter
Completes form on hero
QAE
Updates the button in the header and video
Updates the form on the request page
If virtual QAE replaces form on request page
Create links throughout the site
Create Callouts
Create Video script
Fill in footer with appropriate fields
e.g.: address vs. service area, hours, etc.
Create backup in HWP “Post_Content_Editing_Your_Name_CW before sending to build.
Internal product/service pages side bar. See detailed training
Testimonials if requested, Copywriter searches online if no link is present. Verify NOB, address and contact name if used in any of the testimonials.
Vertical navigation See detailed training
Links to CTA on home page intro paragraph and intro as well as closing paragraphs on internal pages.
Primary CTA can be used but using a general CTA is acceptable.
e.g. "contact us" rather than "call us."
Check for appropriate and judicious bolding in body copy (added 4/7/2026)
e.g. phrases like "FREE estimates" or "24/7 Service"
For definition-style bullet points, only the first part should be bolded
e.g. 24/7 Emergency Services: our team is here for you any time, day or night

Once in site QAE will complete the following:

Reference the following pages when editing:
Common things to look for https://my.websites.hibu.com/preview/6aa68f5a04544595a03ec5f09ad024ac
Editing internal page sections https://my.websites.hibu.com/preview/6aa68f5a04544595a03ec5f09ad024ac
Editing single copy blocks https://my.websites.hibu.com/preview/6aa68f5a04544595a03ec5f09ad024ac
Editing for skim reading https://my.websites.hibu.com/preview/6aa68f5a04544595a03ec5f09ad024ac
Check for ampersands in headlines and copy — In the headlines, be consistent. In the copy, try to avoid "&" if possible. In the meta, it doesn't matter if it mixes and matches (again, NOB being the exception).”
Request form if it is part of the CTAs
Copywriter
Completes form on hero
QAE
Updates the button in the header and video
Updates the form on the request page
If virtual QAE replaces form on request page
Add missing information in Yext:
Holiday hours
Additional payments not in Yext are added to the about page as a bulleted text box.
If the Product/Services field in the questionnaire and Yext are blank use website internal pages in Yext.
Facebook URL if missing in Yext.
QA - Create meta using meta tool
The home page follows current rules:
NOB without Inc, LLC, etc.
What does your business do? – general business products/services.
Provide additional business details – should be the 3 motivating factors from the content menu in HWP and the area they service or located in.
Leave tone of voice as is
Vertical pipes can be removed from the meta descriptions
Verify the content written is relevant to the page content
https://my.websites.hibu.com/preview/6aa68f5a04544595a03ec5f09ad024ac
Ensure Home Page Title follows current Hibu best practices for formatting.
Location/Hybrid Title Tag: Core Business Keyword (or phrase) | City, ST | NOB
Service-Based Title Tag: Core Business Keyword (or phrase) | Geo Area | NOB
Ensure the GEO is added and/or correct for each title tag (city, state/service area per QAF 624).
Replace redundant or irrelevant keywords in title tags with appropriate ones.
Remove the phone number from all Title and Description fields.
Remove pipes from the Description fields.
Ensure any extensions (Inc, LLC, etc.) are removed from the NOB in all fields.
Ensure spelling and grammar are correct for titles and descriptions.
If you are editing a title tag, make sure it’s within the 55-character limit.
A Meta Description of over 155 characters is no longer an error.

Effective Date: February 1, 2026 Last Updated: February 7, 202 6

Breadcrumbs

Sun, 01 Feb 2026 20:09:46 GMT

Breadcrumbs

Overview

Breadcrumbs provide a simple navigational trail that shows where a page sits within the site’s hierarchy. While originally designed for very large websites (100–1,000+ pages), Hibu One Smart Sites use breadcrumbs primarily for internal linking strength , on-page SEO , and structured data (schema) benefits.

All Hibu One templates include a Breadcrumbs widget by default.

Design, Build, and Copy teams do not need to add or configure breadcrumbs under normal circumstances — only confirm that the widget displays properly when creating or editing pages.

Rules & Guidelines

Where Breadcrumbs Are Required

Breadcrumbs must appear on all standard site pages , including:

Core service pages
About / Contact pages
Sub-pages and nested pages
Inventory pages
Blog posts (when applicable)

Breadcrumbs are placed automatically at the top of the page layout in the Hibu One template.

Note: Breadcrumbs appear on Mobile at the bottom of the page. This is true for all pages, the breadcrumb widget does not need to be deleted on mobile.

Purpose / Why It Matters

Even though Hibu One sites typically contain fewer pages than enterprise websites, breadcrumbs still offer measurable SEO value:

Strengthens internal linking between key pages
Improves crawlability and page context for search engines
Enables breadcrumb schema , which benefits modern AI search experiences
Provides a consistent, predictable UI pattern across all standard pages

Breadcrumbs are included for SEO first — not because our sites require complex navigation.

Definition

The Breadcrumbs widget automatically displays the page’s hierarchical position within the site. Breadcrumb Schema is applied by the Duda widget, providing clear page-relationship signals to search engines and AI systems.

Breadcrumbs support:

Stronger internal linking
Clearer content relationships
Improved navigation (when applicable)
Additional structured data benefits

Where Breadcrumbs Must Not Appear

Breadcrumbs must not appear on the following:

Homepage
Service Area Pages (SAPs)
Geo Pages (GEOs)

These exclusions are by design.

Breadcrumbs on SAPs/GEOs create false hierarchy signals, duplicate navigation paths, and incorrect schema relationships. The absence of breadcrumbs on these pages is expected, correct, and required .

Editor Behavior & Template Notes

In Duda’s content editor:

Breadcrumbs automatically show the current page
Content teams should not adjust advanced settings unless directed by Product or QA

The widget provides three options, but Hibu teams should leave defaults in place :

Show Home Page
Show Current Page
Hide on pages without a parent

Defaults already meet Hibu One requirements.

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Form Email, Subject, and Title Requirements

Sun, 01 Feb 2026 19:52:29 GMT

Form Email, Subject, and Title Requirements

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Overview

By default, Hibu One Smart Site forms are connected to the Content Library to ensure centralized management, accurate routing for multi-location businesses, and long-term consistency.
Email delivery is governed primarily by the Client Dashboard, with limited, policy-controlled exceptions.

Default Form Connection & Email Behavior

Connected Forms (Standard State)

All standard forms are connected by default.

When a connected form’s Email Address field is left blank:

Submissions are sent to the notification recipients configured in the Client Dashboard.

This is the expected and preferred configuration for most sites and forms.

Why forms remain connected:

Supports correct routing for multi-location or multi-entity businesses
Prevents cross-location or misdirected submissions
Enables centralized updates via location or business IDs
Reduces manual, form-by-form configuration

Disconnected Forms and Default Routing

A form may be disconnected only when a business requirement cannot be met while the form remains connected.

When a form is disconnected and no Email Address is entered :

Submissions still route to the Client Dashboard notification recipients.

Disconnecting a form does not change routing behavior unless a form-level email address is explicitly added.

Form-Level Email Address Policy

When to Use the Email Address Field

The Email Address field should be used only for rare, one-off scenarios, such as:

An HR or Careers form routed to a single individual
A specialized internal request form

This field must not be used for standard contact, lead, or request forms.

Critical Rule: Content Library Connection

If a form is connected to the Content Library, a unique email address cannot be added directly to that form.

Policy statement:
To route a form to a one-off recipient, the form must first be disconnected from content library.

When a form-level email address is added:

That address receives the submission
Client Dashboard notification recipients continue to receive the submission as well

Dashboard vs. Form-Level Routing

Client Dashboard (Preferred)

Use when recipients should receive submissions from:

Multiple forms
Standard contact and lead flows

This approach is centralized, scalable, and requires no form-level overrides.

Form-Level Override (Exception Only)

Use only when one specific form must route to one specific recipient.

Requires disconnecting the form from the collection
Should be treated as an exception, not a standard approach

Email Subject Line Requirements

If a Subject Line is entered on the form, it will be used in the notification email
If left blank, the system Dashboard default subject is applied
Subject customization is optional and should be used only when it improves clarity for the client.

Form Title Requirements

The Form Title appears in:

Email notifications
Dashboard submission records
Teams are encouraged to add contextual identifiers when helpful (for example: “ SAP Hero Request Form ” or “ GEO Hero Request Form ”) to clearly indicate submission origin.

Implementation Standards

Legacy or placeholder email addresses must not appear on live forms or location pages
Any exceptions must be intentional and documented
The Hibu design team is expected to rename uploaded files and apply appropriate alt text to all associated assets

Homepage & CAT Content Guidelines

Sun, 01 Feb 2026 19:44:05 GMT

Homepage & CAT Content Guidelines

Purpose (Non-Negotiable)

The Homepage and Category Landing Pages (CATs) are designed to:

Orient users
Build trust
Drive conversion

They are not meant to explain services in detail. Service- or product-specific depth belongs on individual service or product pages.

Fixed Structure (Off-Limits)

The following elements should not be removed, restructured, or reimagined :

Header and navigation
Hero section
Introduction section (below the hero)
“Why Choose Us” section
Core copy blocks
Reviews section
Footer

These elements exist for SEO, AI discovery, UX consistency, and conversion performance.

Allowed Content (With Guidelines)

Content added to the Homepage or CAT pages must be:

Company-focused
Broadly applicable
Conversion-oriented

Not Allowed (Non-Negotiable)

Service-Specific Content

Do not place service-level philosophy, process, or education on the Homepage or CAT pages.

Not Allowed Examples

“Our philosophy on AC repair”
“How we approach furnace diagnostics”
“Why our roofing process is different”
“Our step-by-step drain cleaning method”
Technical explanations, workflows, or service FAQs
These belong on individual service pages only .

In Summary

The homepage and Category Landing Pages are not meant to explain everything.

They are designed to orient, motivate, and direct — clearly, quickly, and intentionally.

When client-provided content is valuable, it should be integrated strategically , without compromising structure, clarity, or conversion performance.

Rule of Thumb

If the content answers “Who are you and why should I trust you?” , it belongs on the homepage or Category Landing Page. If it answers “How do you do this specific service?” , it belongs on the service page.

Placement Guidance

Company positioning content

May replace the Introduction section only if it closely matches the original length, tone, and intent
If longer or more detailed, place below the Copy Blocks , styled to match the Introduction layout

Business updates, announcements, visual proof, promotional callouts

Place below the Copy Blocks
Never above the Introduction or “Why Choose Us”

Design must match

Existing fonts, colors, spacing, and layout patterns
Content must feel intentional—not appended or dropped in

Appropriate Content Examples

Company Positioning

“Our commitment to reliable, honest service”
“A locally owned company focused on long-term customer relationships”
“Serving customers with dependable solutions backed by experience”
“Trusted across the region for responsive, professional service”

Business Updates & Announcements

Awards or recognitions
Certifications or accreditations
Milestones (years in business, expansion, new locations)
Press mentions or local news (summarized only)

Visual & Social Proof

Photo galleries (if representative and accurate)
Instagram galleries highlighting work, culture, or community
Award badges, certification logos, professional associations

Conversion-Supporting Callouts

Short promotional messages (e.g., online scheduling now available)
Brief trust statements paired with CTAs
Credibility highlights without process detail

Homepage & CAT Content Guidelines: At-a-Glance

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Duda Design Panel

Sun, 01 Feb 2026 19:39:22 GMT

Definition

The Design Panel contains the element-level controls that determine how content looks and behaves within the Editor 2.0 structure. It is divided into multiple sections—commonly including Layout, Spacing, Alignment, Background, Border, and Size—each responsible for a different aspect of styling. These controls allow teams to adjust the appearance of an element while preserving the site’s overall structure and theme integrity.

Duda Design Panel

Overview

The Duda Design Panel is the central styling and layout interface within Editor 2.0. It provides appearance, spacing, alignment, and responsive controls for whichever element—Section, Column, Inner Column, or Widget—is currently selected. The Design Panel ensures that visual adjustments follow a consistent system and remain aligned with theme settings, responsive behavior, and the broader Smart Site framework.

Consistency Across Breakpoints

Styling decisions should remain consistent unless a breakpoint-specific adjustment is required for readability or layout integrity.
Spacing, alignment, and size changes on smaller breakpoints should support the intended responsive design, not override it.
Avoid styling differences between breakpoints unless they serve a clear functional purpose.

What Should Not Be Overridden

The Design Panel supports extensive customization, but certain elements must remain aligned with system defaults:

Theme-Driven Styling

Do not override Theme Colors with one-off custom colors unless the design explicitly requires it.
Do not replace Theme Text settings with manual font choices for standard headings or paragraphs.

Additional Notes

The Design Panel controls appearance and layout, not structure— Sections, Columns, and Inner Columns must remain in their defined hierarchy.
Because responsive inheritance begins at the Desktop breakpoint, styling updates at the top level cascade downward unless intentionally modified on Tablet or Mobile.

Manual or Unsupported Workarounds

Avoid the following:

Using empty widgets for spacing
Forcing fixed heights or widths to control layout
Overlapping elements through negative margins
Applying extensive styling overrides that prevent templates from remaining flexible

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Springtime Cookies Widget

Sun, 01 Feb 2026 19:34:18 GMT

Definition

Every Hibu One Smart Site includes Consent Management by Springtime. This platform provides cookie banners and related tools that help align websites with evolving data privacy regulations. By enabling visitors to accept or decline categories of cookies, Springtime helps businesses demonstrate transparency, build trust, and reduce the risk of non-compliance.

Why It Matters

Consumer trust in data privacy is low — in many industries, 90%+ of people say they don’t trust businesses with personal data. At the same time, U.S. states are enacting their own privacy laws to protect consumers:

California (CCPA/CPRA)
Virginia (VCDPA)
Colorado (CPA)
Connecticut (CTDPA)
Utah (UCPA)
Delaware (DPDPA)
New Jersey (NJDPA)
Montana (MTCDPA)
Iowa (ICDPA)
Maryland (MCDPA)
Minnesota (MCDPA)
Tennessee (TIPA)
Nebraska (NCDPA)
Penalties: Up to $7,500 per violation in some jurisdictions

These state laws differ in details, but most share common requirements around transparency, consent, data rights, and protection of personally identifiable information (PII).

Hibu One Smart Site Rules

The Springtime consent management widget is automatically included with every new Hibu One Smart Site.
The Springtime icon appears in the bottom-right corner of both desktop and mobile sites.
By default, Springtime provides a cookie consent banner that allows visitors to:
Accept only essential cookies
Enable all cookies
Customize which categories of cookies are active
The widget’s position, size, and color cannot be altered.
Springtime may be removed at the client’s request. However, it is strongly recommended that the purpose and benefits be explained before removal.
Removal requires a Remedyforce ticket.

Script for Explaining Springtime Before Removal

"Springtime is included on your website to help protect your business and your customers. It manages consent for cookies and data collection, which is increasingly required by state privacy laws. Without it, your site may not clearly notify visitors about data use — which could impact trust and, in some states, carry compliance risks. We strongly recommend keeping it in place. If you’d still like us to remove it, we’ll need to create a Remedyforce ticket to process that request."

Default Options Explained

Visitors typically see two main options on the cookie banner:

Necessary Only
Loads only the cookies required for the site to function (e.g., session, security, or consent cookies).
Does not include analytics, marketing, or personalization cookies.
Ensures basic site usability but limits tracking and reporting features.
Enable All
Loads all cookie categories: necessary, analytics, functional, and marketing.
Allows full use of tracking, ad personalization, and analytics reporting.
Provides the most complete data for the business but requires explicit consent.

In addition, visitors may customize cookie categories individually:

Analytics cookies – Help measure visitor interactions and site performance (anonymous data).
Functional cookies – Remember visitor preferences (e.g., language or region).
Marketing cookies – Track users across sites to deliver tailored ads.

Springtime Cookies Widget

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Fair Use Policy — Media & Assets

Sun, 01 Feb 2026 19:29:39 GMT

Fair Use Policy — Media & Assets

Purpose
The Fair Use Policy defines the maximum volume of media and content assets that Hibu will upload, optimize, or configure on behalf of a client during a standard Hibu One SmartSite build. These limits ensure consistent quality, performance, and turnaround across all sites, regardless of size or page count.

Images (updated 04/02/26)
Hibu will upload and optimize up to 1,000 total images per site .

This includes all image assets used across the site, including logos, icons, badges, and recurring image assets
This may include up to 20 separate galleries , with each gallery containing a maximum of 50 images (up to 60 images allowed when needed)
All image assets count toward the 1,000-image total , regardless of type or placement
A reused image counts only once toward the total image limit, regardless of how many times it appears on the site
Hibu will rename all uploaded images and apply descriptive alt text to meet accessibility and SEO standards
Client-supplied images must meet platform quality and display requirements (50MB max file size, appropriate resolution for intended placement)
Images must be optimized for performance and clarity; refer to Image Size Guidelines for recommended sizing, file size, and quality standards
Gallery images should maintain consistent aspect ratios and be optimized for web display; refer to Image Size Guidelines for composition and sizing guidance
Legacy or low-resolution images may be excluded from prominent placements but can appear in supporting sections or galleries where quality impact is minimal.
Hero and background image selection, layout, and sizing rules are defined in the Hero Images and Image Size Guidelines definitions

Video

Hibu will upload or embed up to 20 total videos per site.
This total includes all video types used on a Hibu One Smart Site:
Client-supplied uploaded video files
Embedded videos from YouTube, Vimeo, or Dailymotion
Background videos (each counts toward the total)
Hero videos (each counts toward the total)

Logos, Partner Icons / Badges & Branding Assets

Hibu will feature one business logo in the site header — no exceptions
If a business has multiple versions of its logo, the client must select one for use in the header
The chosen logo will be optimized for both desktop and mobile display
Preferred file type: PNG
Accepted file types: SVG, JPEG, WebP
Not accepted: GIF or animated logo files
Logos must be clear, high-quality, and suitable for web display Low-resolution or pixelated logos are not permitted
High-resolution logo files are acceptable and will be scaled appropriately for display
In the site footer, Hibu will include up to 24 brand, partner, or accreditation icons
Icons must be visually consistent in size, quality, and orientation
SVG is preferred for scalability, though PNG and JPEG are acceptable
Animated or low-resolution graphics are not permitted
It is expected that the Hibu design team will rename all uploaded logo and icon files and apply appropriate, descriptive alt text to meet accessibility and SEO standards
All logos and icons are subject to layout and visual balance. Excess or redundant icons may be excluded at the designer’s discretion to preserve a clean, professional design
For sizing, file handling, and performance considerations, refer to Image Size Guidelines

Audio

Hibu will upload or embed up to 20 audio clips (e.g., SoundCloud, Mixcloud, or hosted MP3s).
Audio files must meet standard performance guidelines (≤50MB each).
It is expected that the Hibu design team will rename all uploaded audio files to ensure proper organization and consistency.
Continuous background audio or autoplay is not permitted for accessibility reasons.

PDFs, Files, & Downloads

Hibu will upload and link up to 50 PDFs or other downloadable files per site.
Larger document repositories or file libraries are not included in the standard build.
Files must comply with security and file-type rules (no executables, scripts, or unsupported formats).
It is expected that the Hibu design team will rename all uploaded files for clarity and consistency.
When applicable (e.g., image-based PDFs), appropriate alt text or file descriptions will be added to support accessibility and SEO.
Extensive collections (e.g., manuals, forms, or archives) may be consolidated into a single Download Center page with limited featured items and a client-provided ZIP or catalog PDF.

Blogs

Third-Party Widgets, Scripts, or Embeds

Hibu will install and configure up to 5 client-supplied third-party widgets or embeds (e.g., chat tools, calendars, booking systems).
Code must be provided in valid HTML, CSS, or JavaScript and comply with HTTPS standards.
Hibu will not create, debug, or maintain external widget functionality.

Custom Forms

Hibu will build up to 10 unique custom forms per site.
Each form must have a unique purpose and field setup.
Forms may be duplicated across multiple pages as needed but no more than 10 distinct forms will be created.
Custom forms with 10 or fewer fields can appear on any page.
Forms with more than 10 fields must appear on a dedicated page, which counts toward the site’s total page count.
Forms cannot exceed 25 total fields.
For consistency and SEO, the Hibu design team will rename any uploaded form-related assets (e.g., icons, background images) and apply descriptive alt text as needed.

Fair Use Policy: At-a-Glance

Legacy Hibu Blog Content (updated 4/23/26)

When upgrading from an existing Hibu website:

Hibu will migrate all existing blog posts.
Imported legacy blog posts will conform to current Hibu One Smart Site design standards and may differ visually from the legacy site.

Third-Party Blog Content (updated 4/23/26)

When a blog import is available via a valid RSS feed, Hibu will import eligible blog posts in accordance with platform limits, up to 300 posts per RSS feed per Duda system rules.
Blog posts beyond the 300-post system limit are not migrated due to platform capacity constraints.
It is in the best interest of Hibu to proactively inform the client that imported blog posts will not appear identical to the original site and may reflect updated spacing, fonts, and layout structures aligned with the Hibu One Smart Site framework.

Effective Date: February 1, 2026 Last Updated: April 2, 202 6

Header Navigation

Sun, 01 Feb 2026 19:27:31 GMT

Hover-State (Rollover)

Text color remains white
Underline appears or brightens smoothly (no shift or animation)
No background color change
Sub-navigation only: Inverts colors for hover — background becomes white (#FFFFFF), and text adopts Theme Color 10

Navigation States

Off-State (Default / Idle)

Text color: Theme Color 11 – Navigation Text
Background: Theme Color 10 – Navigation BG
No color transitions or animations
Underline appears only beneath the active link
Provides a clean, stable appearance

Legibility Exception:

Designers may adjust font color or weight if background contrast reduces readability.

Sub-Navigation (Dropdown Behavior)

Background matches Theme Color 10 – Navigation BG
Hover and active states follow the inverse color rule for clear visual feedback
Sub-navigation text should be slightly smaller (1–2 points) than global navigation text
Maintain consistent spacing and legibility at smaller sizes

General Behavior Rules

Dropdown width, spacing, and padding are standardized at the template level and should not be altered.
The dropdown position aligns directly below its parent global link, maintaining even spacing across all sub-menus.
Sub-navigation should open cleanly and close automatically when focus shifts elsewhere, ensuring a seamless user experience.

Design & Accessibility

The Header Navigation consists of:

Global Navigation (Tier 1)
Sub-Navigation (Tier 2)
See Site Architecture for additional about page structure / IA

All design and accessibility standards apply equally to both tiers unless noted.

Font type, size, color, and contrast must meet AA-level readability standards.
The Contrast Checker in the editor must be used to verify legibility in all states.
Navigation styles (on/off/hover) and behaviors are standardized at the template level and must not be modified unless explicitly approved after the first proof.

Definition

The Header Navigation is the main menu bar displayed above the hero section on desktop. It provides access to the site’s primary pages and is built using the Navigation Links widget, which is automatically added to the site header when a new site is created.

By default, it displays all pages marked “Show in Navigation” in the Pages panel.
Design, structure, and accessibility are governed by Hibu global standards to ensure clarity, consistency, and a cohesive user experience across all Hibu One Smart Sites.

Header Navigation

On-State (Active / Current Page)

Persistent white underline indicates the current page
Text color remains consistent with Off-State
Underline thickness and offset are defined at the template level and must not be modified

Typography & Legibility (Global Rules)

Font Type

Designers may select a font that enhances legibility or aligns with brand style. Use clean, professional, web-safe typefaces that complement the site design.

Font Weight

Bolding may be used to improve readability or hierarchy but must be applied consistently across all states (On, Off, Hover) and navigation levels.
Mixing bold and non-bold states creates visual instability and is not permitted.

Font Color

Default text color: white (#FFFFFF)
If contrast is insufficient against Theme Color 10 – Navigation BG , use black (#000000) or another dark tone for visibility.
Adjustments must be made at the theme level to ensure global consistency.

Text Transform

Text case (Title Case or Uppercase) may be adjusted to match the brand style or enhance legibility.
Uppercase may be used for clean, modern aesthetics but must remain consistent across all navigation levels.
Mixing Title Case and Uppercase within the same site is not permitted.

Legibility Priority

Accessibility and legibility always take precedence over style. All navigation text must pass AA-level contrast compliance and remain readable across devices and backgrounds.

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Hero (Standard, Form & Thin Heroes)

Sun, 01 Feb 2026 19:26:32 GMT

Purpose / Why It Matters

Each layout serves a distinct purpose. Choosing the right layout ensures content is clear, actions are prioritized, and users understand what to do next. These layouts support the 3-30-3 Rule by helping users quickly understand where they are, what is offered, and what action to take.

Typography & Spacing

Hero typography must remain clear and readable across all devices.

Designers may adjust headline styles slightly when necessary to maintain visual balance with the background image.

Designers are responsible for:

maintaining logical line breaks
keeping names and geographic references intact
ensuring headline readability across breakpoints

Centered headlines should pair with centered body text. Mixed alignment should be avoided unless required by layout balance.

CTA buttons must maintain sufficient contrast against the background image.

If hero text becomes visually crowded, vertical spacing should be adjusted to preserve readability.

Hero (Standard, Form & Thin Heroes)

Additional Locations: At-a-Glance

The hero is the primary visual and messaging area at the top of a webpage and is the first element visitors see before scrolling. In a Hibu One Smart Site, hero sections follow a controlled structure designed to maintain readability, performance, and consistent conversion behavior across all sites. Each page supports one hero section only, using one of the approved hero layouts defined in this guideline.

Heroes may appear on the following page types:

Homepage
Category Landing Pages (CATs)
Core Service Pages
Service Area Pages
Geo Pages
Utility Pages (Thin Hero only)

Each hero combines structured elements including:

Headline (H1)
Geographic reference
Motivating factors
One or more calls to action (CTAs)
Optional open/closed hours widget
Full-width background image

Interactive or experimental hero layouts are not supported. Hibu One Smart Sites do not permit sliders, animated hero banners, or non-standard hero structures.

Layout decisions must align with the image selection, composition, and quality standards defined in Hero Images , and all sizing, ratio, and file requirements defined in Image Size Guidelines .

Effective Date: February 1, 2026 Last Updated: March 26, 202 6

Hero Rules

The following rules apply across all hero types unless otherwise specified.

One Hero Per Page
Each page supports a single hero section only.
Stacked heroes, multiple banners, or additional hero-style sections above the fold are not supported.

CTA Limits

Standard hero layouts support up to two CTA buttons.

Examples include:

Call
Visit Us
Request Estimate

Additional CTAs are not permitted because they dilute conversion focus.

For button behavior and styling rules, see Buttons .

Trust Indicators (updated 03/26/2026)

Trust indicators (e.g., affiliations, certifications, or brand logos) may be included within the hero to reinforce credibility and build user confidence.

Rules & Guidelines

Trust indicators may be added to homepage and category landing page heroes only
A maximum of 3 trust indicators is permitted per hero
Placement must support the overall hierarchy and must not compete with the headline or primary CTA
Trust indicators must be visually consistent and not create clutter

Request & Approval Process

Trust indicators are not collected during the initial questionnaire
They may be introduced after the first proof , based on client feedback or request
Clients must clearly specify which brands, affiliations, or credentials should be included
Designers must ensure all submitted assets meet quality and formatting standards

Hero Layout Variations

In addition to the default centered hero layout, Hibu One Smart Sites support several controlled layout variations when needed to improve readability or accommodate client imagery.

These variations maintain the same hero messaging structure while adjusting alignment or composition.

Available layout variations include:

Left-aligned hero text
Offset hero layout
Hero with form

These layouts are available through pre-built sections located in the Hero / Section Hero library and should not be recreated manually.

Background Hero Video

Hero sections may support a background video within the VideoHero layout . Background video appears behind hero content and must remain subtle to avoid interfering with readability or calls to action.

Background hero video displays only on desktop and tablet devices . Mobile devices display a static hero image instead.

For full requirements, see Background Hero Video .

GEO Display Rules

Geographic references appearing in the hero must follow standardized formatting rules to ensure consistency between the header, hero headline, title tag, and page content.

For full requirements, see GEO Display Rules – Header, Hero, Title, and Page Content .

Tagline Placement

Hibu does not place taglines directly beneath the logo in the website header.

When used, taglines may appear within the hero area or within supporting page content.

For full placement rules, see Tagline Placement Standards .

Text-Heavy Promotional Images

Promotional graphics containing large amounts of embedded text are generally not suitable for hero backgrounds because the text becomes unreadable on mobile devices.

For full rules, see Text-Heavy Images and Mobile Display Rules .

Thin Hero (Utility Pages)

The Thin Hero is used only on utility pages where quick identification is needed without encouraging immediate conversion.

Examples include:

• About Us
• Contact Us
• FAQ
• Reviews
• Blog
• Careers
• Finance
• Gallery

Thin heroes contain only minimal identifying information and do not include CTAs or motivating factors.

Structure

Thin heroes contain:

Page name (H1)
Optional business name

Thin heroes may use either:

a solid color background
a simple two-color gradient

Hero CTAs, motivating factors, and forms are not used within Thin Hero layouts.

Related Hero Component Rules

Several hero elements are governed by dedicated Hibu One guidelines. These rules apply to hero content but are maintained separately to avoid duplicating documentation.

Left-Aligned Hero Text

Hero text is centered by default.

However, when the composition of the background image improves readability or visual balance, hero text may be left-aligned .

Left alignment is typically used when the primary subject of the image occupies one side of the frame and the hero content can be placed on the opposite side without obstructing the visual.

When left alignment is used, all hero elements must remain consistently aligned, including:

headline (H1)
geographic reference
motivating factors
CTA buttons

Mixed alignment within the hero should be avoided.

This layout is available through pre-built hero sections within the Hero / Section Hero library .

Offset Hero Layout (updated 03/26/2026)

The offset hero layout introduces asymmetry by positioning content (text or CTA) to one side, creating a more dynamic visual presentation. This layout can be effective when there is strong supporting imagery and sufficient space to maintain balance.

Rules & Guidelines

Offset layouts may be used when they support visual hierarchy and readability
Content must remain clear, balanced, and aligned with the focal point of the image
The layout must maintain consistency across desktop, tablet, and mobile

Form Restrictions

Offset hero layouts are not permitted when a hero form is present
Forms require a stable, balanced layout to maintain usability and readability, which offset layouts cannot reliably support

Exception Handling

If a customer explicitly requests an offset layout after being presented with a hero form option:
The hero form must be removed
A CTA button (e.g., “Get a Quote,” “Contact Us”) must be used in place of the form
The CTA should link to a dedicated form elsewhere on the site

Offset heroes should be implemented using the pre-built sections located in the Hero / Section Hero library .

Hero with Form

Some hero layouts include a lead-capture form positioned within the hero area to allow visitors to submit quick inquiries directly from the page.

Hero forms follow strict limits on the number and type of fields to maintain strong conversion performance and ensure usability on mobile devices.

Learn more about Hero Form requirements and specifications .

Implementation Note

If a form needs to be added to an existing hero, designers should use a pre-built hero section that includes a form rather than attempting to construct the layout manually.

Similarly, if a form is removed from an existing hero, it is recommended that the hero be replaced with a pre-built standard hero section rather than simply deleting the form column.

All hero-with-form layouts are available in the Hero / Section Hero library .

For full form requirements, see Hero Form .

Definition

A hero is the large visual banner positioned at the top of a page. It introduces the business or service, confirms relevance for the visitor, and presents the primary action the visitor should take.

The hero supports three core goals:

Immediately clarify the business and service offered
Establish credibility through strong visuals and messaging
Encourage visitors to take action through calls to action or lead capture

The hero system includes the following layouts:

Standard Hero
Hero with Form
Thin Hero

Each layout supports different page purposes while maintaining consistent messaging structure and readability.

Hero with Form

Some hero layouts include a lead capture form positioned within the hero area to capture quick inquiries directly from the page.

Hero forms follow strict limits on the number and type of fields in order to maintain strong conversion performance and mobile usability.

In certain cases, the form module may be replaced with alternate content elements, including:

an inline video
a Hibu coupon or promotional offer
a client-supplied promotional image

Replacement content must fit within the existing form module area and may not alter the overall hero layout structure.

Images used in place of the form should be appropriately sized to fit the module area and ideally appear in a square or near-square format .

Replacement content must preserve the readability of the hero headline, motivating factors, and primary calls to action.

Static Background Required

Heroes use a full-width background image or gradient.
Background images must meet Hibu image sizing standards to maintain clarity across desktop, tablet, and mobile breakpoints.
For detailed specifications, see Image Size Guidelines .

Sliders and Animated Heroes Are Not Permitted

Hero sections may not contain:

image sliders
rotating banners
animated hero graphics
carousels

These elements reduce readability and negatively affect performance and conversion behavior.

Dynamic Rows

Sun, 01 Feb 2026 19:25:41 GMT

Dynamic Rows

Definition

Dynamic Rows (also called InSites or Personalization) were previously used to display announcements or promotions that changed dynamically. On Hibu One Smart Sites, they are no longer supported because they slowed sites down, caused layout shifts, and hurt SEO performance.

Hibu One Smart Site Rules

Hibu One Smart Sites do not use Dynamic Rows or InSites .
All announcements, promotions, or business updates are handled through a static Alert Banner
Alert Banners are placed at the top of the homepage .
They are styled to match the site’s branding.
They load quickly and do not harm site speed, SEO, or user experience.
Banner guidelines:
Text should be short (1–2 lines).
Banners cannot include scripts, auto-updating content, or custom HTML.
All updates must be handled through Hibu.

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Countdown Widget

Sun, 01 Feb 2026 19:25:07 GMT

Definition

The Countdown widget displays a real-time timer that counts down to a specific date and time. It is used to build interest, create urgency, and encourage action for upcoming events, promotions, or launches.

Hibu One Smart Site Rules

The widget is best suited for seasonal or one-time future events (e.g., sales, product launches, grand openings).
It is not suitable for recurring events (e.g., weekly specials or happy hours) because it does not automatically restart.
The widget only counts down ; it does not count up.
The widget will only be added after the first proof or once the site is live .
Placement is limited to the content body of the site (between the header and footer).
A designed section is available for Hibu builds to add the countdown widget.
A custom “time’s up” message may be displayed when the countdown ends.
Once the timer runs down, the countdown placeholder remains in place and does not disappear automatically. The client (or their Hibu representative) must request removal. Hibu will not proactively remove expired countdowns.

Countdown Widget

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Buttons

Sun, 01 Feb 2026 19:23:51 GMT

Definition

Buttons are a primary way users interact with a Hibu One Smart Site. They guide visitors toward key actions (e.g., contacting a business, requesting a quote, or, simply, learning more). Button style, size, and text are defined by design standards but must always remain clear, accessible, and consistent.

Buttons

Effective Date: February 1, 2026 Last Updated: April 2, 202 6

Buttons: At-a-Glance

Design & Accessibility

Use the Contrast Checker in the editor to ensure text meets accessibility standards.
Aim for green check (AA or AAA) compliance.
Strong contrast improves readability, accessibility, and conversions.

Color & Theme Rules

Primary and secondary button colors — including both default and hover states — are controlled by theme color placeholders:
18 – Button Primary
19 – Button Secondary
By design, the secondary button’s hover state is the inverse of the primary button to maintain visual balance and consistency.
Font color for all buttons is linked to 2 – White by default.
Buttons must not use a default color that matches or closely blends with the background they are placed on. Buttons must remain visually distinct and immediately identifiable as interactive elements. (added 3/31/26)
All button states (default and hover) must remain visually distinct from the background they are placed on. If a button’s fill color does not provide sufficient contrast, adjustments must be made to preserve visibility. This may include modifying colors or introducing a border to maintain clear separation, provided the button remains clearly recognizable as interactive in all states. (updated 4/02/26)

Not Allowed — Fails visibility requirement

Allowed — Maintains visual separation

Adjusting Button Colors

Designers may update button primary , secondary , or font color values only at the theme level — never inline on the page.
Inline color edits prevent future theme-level updates from applying correctly and create maintenance issues.
Any changes should maintain strong color contrast for readability.
When customizing, the secondary button should typically remain the opposite of the primary to preserve hierarchy and consistency.

Borders & Effects

Button borders are off by default .
If a border is needed for design clarity, set the border width to 1px on both primary and secondary buttons.
By default, this adds a 1px white border in both the on and hover states.
Gradients on buttons are strictly prohibited. Flat color designs support clarity, contrast, and consistency across all devices.

Corner Radius (Button Roundness)

Research consistently shows that rounded buttons outperform sharp-cornered ones in click-through rates. Rounded shapes are perceived as more friendly and approachable, encouraging user interaction — whereas sharp edges can feel formal or even intimidating.

Default: Corner radius is set to 10 px.
Increase roundness (e.g., 20–30 px): Only if the brand style calls for softer, friendlier shapes — for example, wellness, childcare, or community-focused businesses.
Remove roundness (0 px): Only if the brand identity or design aesthetic demands a sharper, more structured look — for example, law firms, financial institutions, or industrial services.
Button shadow: Off by default. Use extreme caution if enabling shadows, as they may render poorly on colored or textured backgrounds and can reduce accessibility.

Button Text Best Practices

In most cases , “Learn More” is the right choice. It’s simple, expected, and works well across most copy blocks and callouts.
In some cases, however, a more specific, action-oriented call to action fits better. Examples include:
Menu: “View Menu”
Event: “Register Now”
Estimate: “Request Estimate”
Careers: “View Openings”
Blog: “Read Article”
Download: “Download Guide”
Use the “I want to…” test when deciding: complete the phrase from the visitor’s perspective.
Example: If the button text is “Request Estimate,” the user is essentially saying, “I want to request an estimate.”
This keeps labels user-focused and action-oriented.

Before / After Widget

Sun, 01 Feb 2026 19:22:43 GMT

Before / After Widget

Definition
The Before/After widget displays two images in a slider for side-by-side visual comparison. It’s most effective for showcasing clear transformations (e.g., lawn care, roofing, remodeling).

Best Use Cases

Home services or contractors showing project results.
Side-by-side transformations that highlight quality of work.
Any scenario where a simple visual comparison strengthens credibility.

Limitations

Avoid if images are taken from different angles, distances, or lighting conditions — mismatches will distract rather than impress.
Avoid if images already contain “Before” / “After” text or other embedded labels (creates visual clutter).
Not recommended if one or both images are low resolution or heavily pixelated.

Setup & Naming Conventions

Add the widget from Widgets → Before & After , then drag onto the page.
In the Content Editor :
Click + Image to upload/select your before and after images.
Always place “Before” on the left and “After” on the right .
For multiple sets, use a simple naming convention (e.g., before-01/after-01, before-02/after-02, etc.) for organizational clarity.
Add alt text for each image (e.g., “residential roof replacement – before” / “residential roof replacement – after”). AI alt text may be used but should be refined if needed.

In the Design Editor:
Customize images under Images & Slider.
Ensure displayed size never exceeds the actual image resolution.
Keep before and after images the same size (avoid distortion).
Labels: Use default “Before” and “After” labels unless otherwise instructed. You may hide labels if not needed.

Key Notes

If images are well-matched and free of embedded text, designers are free to use this widget to create engaging, interactive comparisons.
When used correctly, this widget provides strong proof of work and supports lead conversion.

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Click to Call

Sun, 01 Feb 2026 19:12:35 GMT

Definition

A Click-to-Call button allows visitors to initiate a phone call directly from the website by tapping or clicking the displayed phone number. It provides a fast, frictionless way for users to contact the business — supporting conversions, accessibility, and user convenience across devices.

Click to call Button

Hibu One Smart Site Rules

Click-to-Call functionality is supported on both mobile and desktop versions of Hibu One Smart Sites.
On desktop layouts, Click-to-Call buttons may appear in Hero sections , Callouts , Coupons , and Footers .
On mobile, connected text-based phone numbers automatically display as tappable links .
Phone numbers used in Click-to-Call buttons must be:
Active and valid business contact numbers
Connected through Yext and the Business Information content library
When a client has multiple business locations or phone numbers, the number used for Click-to-Call must match the primary number listed in Business Information.
If a client requests alternative button text (e.g., “Call Now,” “Contact Us”), the change may be made only after first proof.

Design & Accessibility

The default Click-to-Call button design must display the full phone number (e.g., Call (555) 123-4567).
Research consistently shows that users are more likely to click when they see a recognizable phone number rather than generic wording such as Call Us or Contact Us. Displaying the number reinforces trust and immediacy, improving conversion rates.
The standard display format for phone numbers across all pages and buttons is (XXX) XXX-XXXX .
Buttons must maintain AA-level color contrast and legibility against background images or colors.
Text within the button must be concise, clear, and easily readable at all device sizes.

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Favicon

Sun, 01 Feb 2026 19:10:38 GMT

Favicon (site Icon)

Hibu Policy

The favicon must be a simplified, square image that clearly represents the client’s brand at very small sizes.

When a logo mark (symbol or icon from the logo) is available, it must be used. Generic or industry-based icons should only be used when no identifiable brand mark exists.

Duda automatically generates the favicon from the uploaded image. Designers are responsible for selecting an appropriate source image; the platform handles all scaling and formatting.

Effective Date: February 1, 2026 Last Updated: March 27, 202 6

Favicon At-a-Glance

Image Selection Guidelines

The favicon must represent the business in a way that is immediately recognizable and consistent with the brand, even at very small sizes.

Priority Order (Required)

Primary: A simplified version of the client’s logo mark (symbol or icon)
Secondary: A recognizable brand-specific icon or mark derived from the logo
Last Resort: A generic or industry-related icon (only if no brand mark exists)

What is a Logo Mark?

A logo mark is the symbol or icon portion of a logo, separate from the business name (e.g., an abstract shape, emblem, or graphic used consistently in branding).

Favicon Requirements

Duda will automatically generate the favicon from the uploaded image
The image must be square (1:1 ratio)
Any square image size is acceptable (e.g., 100×100, 500×500, 2000×2000)
Designers do not need to manually resize images to favicon dimensions (e.g., 16×16 or 32×32)
The image should be simple and recognizable at small sizes

Definition

A favicon (short for “favorite icon”) is the small image associated with a website that appears in browser tabs, bookmarks, and search results. It helps users quickly identify and recognize a site.

Avoid

Generic or industry-based icons when a brand mark is available (e.g., roofs, tools, symbols not tied to the logo)
Full logos with small or unreadable text
Complex or detailed graphics that lose clarity when scaled down
Photographs or multi-subject images

Key Principle: If the business has a defined logo mark, that mark must be used. Generic icons are only acceptable when no brand mark exists.

Design Considerations

Keep the design minimal and high-contrast
Ensure the icon remains legible at very small sizes
Center the subject with sufficient spacing around it
Prioritize brand recognition over creativity ; the favicon should reinforce the logo, not reinterpret it

Preferred

A simplified version of the client’s logo mark (icon or symbol), when available
A recognizable brand mark that directly matches the company’s identity
Consistent use of brand colors and shapes

Examples of Proper Favicon Selection:
Simplified logo marks (shown on the right) are used as the favicon to maintain brand consistency and recognition at small sizes.

Preferred
Uses the company’s logo mark, reinforcing brand identit y and improving recognition across the site experience.

Acceptable (When No Mark Exists):
Uses a generic industry-related icon. This is only appropriate when the business does not have a defined logo mark.

Geo Display Rules

Sun, 01 Feb 2026 19:09:16 GMT

GEO Display Rules – Header, Hero, Title, and Page Content

Two Locations or Two Service Areas (When the Additional Locations Product Has Not Been Purchased)

Two is the maximum number of locations or service areas that may be named in primary Geo surfaces.

Allowed for businesses with:
Two physical locations, or
Two defined service areas
No additional locations or service areas may be referenced.
Header and Hero Geo must remain aligned in meaning.
Header and Hero Geo text should align in meaning, not require exact text matching. Minor variations such as ampersands vs. “and,” abbreviations, or spacing adjustments are acceptable to accommodate layout and space constraints.

Title Tag Guidance (Two Locations / Service Areas)

Title tags should use the primary address listed in the questionnaire .
This is typically the first (primary) address provided and represents the business’s main location.
Do not select a city from additional locations or secondary service areas when determining title tag Geo.
If questions arise, default to the primary address shown in the questionnaire and resolve exceptions on the back end.
Do not attempt to abbreviate or compress multiple locations.

Meta Description Guidance (Two Locations / Service Areas)

Meta descriptions may reference both locations or service areas if space allows.
Broader or supporting geographic language is acceptable.

Example text – Physical Locations (2)

Header Geo: Located in River Hills, WI and West Bend, WI
Hero Geo: Veterinary Care in River Hills, WI and West Bend, WI
Title tag: Veterinary Services | River Hills, WI | Good Mojo Pet Care
Meta description: Good Mojo Pet Care provides veterinary and pet care services in River Hills and West Bend, WI, welcoming new patients and offering same-day visits.

Example text – Service Areas (2)

Header Geo: Serving Denver and Colorado Springs Areas
Hero Geo: Landscaping and Hardscaping in Denver and Colorado Springs Areas
Title tag: Landscapes & Hardscapes | Denver, CO | Garcia Landscaping
Meta description: Garcia Landscaping provides professional landscaping and hardscaping services throughout the Denver and Colorado Springs areas, including lawn care, design, and outdoor improvements.

Primary vs. Secondary Geo

Primary Geo (Strict)

Header
Hero Geo
Title tag
Rules:
Header and Hero Geo must remain aligned in meaning.
Header and Hero Geo text should align in meaning, not require exact text matching. Minor variations such as ampersands vs. “and,” abbreviations, or spacing adjustments are acceptable to accommodate layout and space constraints.
The wording, scope, and geography must be the same, the word "area" could be included.
Title tags should use the primary address listed in the questionnaire
Title tag Geo must align with the same geographic reference.

Secondary Geo (Flexible)

Meta descriptions
Body copy
Rules:
May reference broader or additional service areas.
May include regional language (for example, “ The Corridor ” or “ Central Ohio ”).
Must not imply physical locations that do not exist.

Related Definitions

For additional context, see:

Three or More Locations or Service Areas

When a business has three or more locations or service areas, listing individual geographies in the header or hero creates readability and layout issues. At this scale, Geo must shift to numeric or generalized language.

Rules:

Do not list multiple cities, counties, or regions in the header or hero.
Header and Hero Geo must use the same generalized Geo approach.

Approved Geo approaches (3+)

For businesses with three or more locations or service areas, Geo must use regional or generalized language rather than listing individual cities.

Approved approaches include:

Regional Geo language anchored to a single, recognizable area
(for example, “Serving the San Diego Area” or “Serving Multiple Locations Across Metro Denver”)
Primary, Yext-supported Geo paired with “and surrounding areas”
(service-area use cases only)

Numeric-only phrasing without a geographic anchor (for example, “Serving 3 Convenient Locations”) is not permitted.

Title Tag Guidance (Three or More Locations / Service Areas)

Title tags should use one primary address listed in the questionnaire .
This is typically the first (primary) address provided and represents the business’s main location.
Do not select a city from additional locations or secondary service areas when determining title tag Geo.
If questions arise, default to the primary address shown in the questionnaire and resolve exceptions on the back end.
Do not list or summarize multiple locations or service areas.

Meta Description Guidance (Three or More Locations / Service Areas)

Meta descriptions may include multiple locations or service areas, space permitting.
Broader regional language is permitted if accurate and Yext-supported.

Allowed examples:

The following examples illustrate acceptable header Geo phrasing for businesses with three or more physical locations .

In all cases, the geographic area referenced must be supported by Yext (as a defined service area, regional designation, or aggregation of listed locations).

Physical Locations (3+) — Regional (Preferred)

Serving Multiple Locations in the Columbus Area
Serving Multiple Locations Throughout the Cedar Rapids Area
Serving Multiple Locations Across Metro Denver
Multiple Locations Serving the Greater Milwaukee Area

Requirement:

When using a regional Geo for physical locations, at least one physical location within the referenced region must exist in Yext . The region itself must be a reasonable aggregation of listed Yext locations.

Physical Locations (3+) — Regional + Numeric (When the Number Is Important)

Serving the Nasville Area with 5 Locations
Serving the Boston Area with Multiple Locations
Serving Metro Denver with 4 Local Locations
Serving the Greater Milwaukee Area with Multiple Locations

Numeric phrasing is optional and should be used only when it adds meaningful context.
The region must remain the primary anchor, and the number should function as supporting detail.

Service Areas (3+)

Serving Burlington County and Surrounding Areas
Serving Philadelphia and Surrounding Cities
Serving the Asheville, NC Area and Surrounding Communities

Secondary Geo guidance:

Body copy may list specific locations or service areas in full.
Meta descriptions may be more descriptive if space allows.
Secondary Geo content must not conflict with Yext-supported data.
Location details must be communicated elsewhere on the page or site.

Example text – Multiple Physical Locations (3+)

Header Geo: Serving the Chula Vista Area with Multiple Locations
Hero Geo : Serving the Chula Vista Area with Multiple Locations
Title tag: Insurance Agency | Chula Vista, CA Jim Hill Insurance Group
Meta description (preferred): Jim Hill Insurance Group provides personalized commercial and personal insurance coverage with offices in Chula Vista, National City, and San Diego, CA.
Meta description (fallback): Jim Hill Insurance Group provides personalized commercial and personal insurance coverage with offices throughout the Chula Vista area, including San Diego and National City.

Example text – Multiple Service Areas (3+)

Header Geo: Serving Buncombe County and Surrounding Areas
Hero Geo: Home Exterior Services in Buncombe County and Surrounding Areas
Title tag: Home Exteriors | Buncombe County NC | Stella Home Builders
Meta description: Stella Home Builders provides roofing, siding, and exterior home services throughout Buncombe County, including Asheville, Black Mountain, Weaverville, and surrounding areas.

Listings (Yext) Alignment (Non-Negotiable)

All Header Geo and Hero Geo content must be fully aligned with the business’s Yext listings.

Any city, area, or region shown in the Header Geo or Hero Geo must already exist in Yext as:

A physical location, or
A defined service area
Important: If a location or area is not present in Yext, it cannot be displayed in the header or hero.
Important: Generalized, implied, or legacy regional phrases carried over from older Hibu websites (for example, “ Serving the Greater TriState Area ”) are not permitted in the Header Geo, Hero Geo, or Title Tag unless they are explicitly supported by Yext.
Geographic areas used for header or hero display must be selected in Yext using one of the supported Service Area fields (City, County, or State/Region). Areas entered manually or outside the preset Yext fields are not valid for header or hero Geo usage.

Line-Wrapping Guidance

Historically, Header Geo text was restricted to a single line. As Geo requirements have evolved—particularly with the approved use of phrases like “and surrounding areas”—a two-line Geo is now permitted when necessary .

This allowance applies to businesses with two or more locations or service areas and is an intentional exception, not a default behavior.

Rules

Geo text may wrap to a second line when required by character length.
Two-line Geo usage is most commonly expected when:
Displaying two locations or two service areas, or
Using approved phrases such as “and surrounding areas” for three or more service areas
Designers should not force wrapping for visual preference alone.

Visual Alignment Requirement (Critical)

When Geo text wraps to a second line:

The CTA lead-in (for example, “Call Now”) and
The primary phone number must be vertically aligned with the second line of the Geo , not the first.

This alignment:

Preserves visual balance within the header
Prevents the layout from feeling top-heavy
Maintains a clear visual relationship between Geo context and conversion elements

Misaligned CTAs or phone numbers are considered a design defect and must be corrected.

Hibu Policy

This definition establishes the authoritative rules for how geographic (Geo) information is displayed across Hibu One websites.

These rules exist to ensure:

Clear and consistent Geo messaging for users
Alignment across header, hero, title tags, and page content
Compliance with listings data, search platforms, and SEO best practices
Predictable behavior across different location and service-area scenarios

Hibu policy requires that:

Header Geo, Hero Geo, and Title Tag GEO remain aligned
Geo decisions are based on verified Yext listings data
The number of locations or service areas determines the allowed Geo approach
Product-based behavior (Additional Locations) overrides standard count-based rules
Geo display rules may change as Google and other platforms evolve

The Quick Reference Guide below provides a fast, decision-ready summary of these rules. Detailed explanations and examples follow.

Notes:

If the client is already ranking locally and local SEO has been added, the header, hero geo reference, and title tag may differ slightly to support those rankings.
For single locations or service areas, if an expanded Geo - such as the primary AND a secondary location - is used in one meta description, it should be used in all other meta descriptions. added 3/31/2026
If there are multiple locations in Yext, select the largest service area for the Geo (added 4/9/2026)
If the largest area can't be determined, default to using the first area listed

Definition

Geo Display Rules define how and where geographic references (city, county, region, or service area) may appear across a website, including:

Header
Hero Geo
Title tag
Meta description
Body copy

Important Note on Google & Search Platform Behavior

Search platforms, including Google, regularly change how they interpret and enforce location signals. These changes can impact search visibility, listings compliance, and account standing.

Hibu may update geo display rules at any time to remain aligned with search platform requirements and best practices. Teams should treat these rules as authoritative but subject to change.

Single Location or Single Service Area

Display one Geo only (city, county, or region).
Geo must be supported by Yext.
The same Geo must appear in:
Header
Hero Geo
Title tag

Example text – Physical Location

Header Geo: Located In Chula Vista, CA
Hero Geo: Insurance Coverage Made Simple | Chula Vista, CA
Title tag: Insurance Coverage Chula Vista CA Jim Hill Insurance Group
Meta description: Jim Hill Insurance Group provides personalized commercial and personal insurance coverage in Chula Vista, CA. Same-day responses and licensed agents.

Example text – Service Area

Header Geo: Serving Asheville, NC Area
Hero Geo: Home Exterior Services in the Asheville, NC Area
Title tag: Home Exteriors | Asheville, NC | Stella Home Builder
Meta description: Stella Home Builders provides home exterior services throughout the Asheville, North Carolina area.

Additional Locations Product Behavior

The Additional Locations product changes how location information is displayed in the header and hero, regardless of whether a business has two locations or more.

When the Additional Locations product is active:

Individual location names are not displayed in the Header Geo
The Header Geo follows the Additional Locations header configuration , not standard one-, two-, or three-location Geo rules.
Locations are represented through:
Location Category Landing Pages
Approved location cards placed within page content
When the Additional Locations product is active, the Hero Geo may reference locations only in an aggregate or descriptive manner (e.g., number of locations, “local offices,” or general service area). Individual location names or city-level Geos must not be listed in the Hero Geo.
Four Convenient Offices to Serve You
Three Offices in New Hampshire
3 Convenient Local Locations

Key clarifications:

Additional Locations behavior is product-based.
A business may have the Additional Locations product with only two locations .
When Additional Locations is active, its header rules take precedence over standard two-location and three-location Geo rules.

Geo Display Rules: At-a-Glance

Effective Date: February 1, 2026 Last Updated: February 8, 202 6

Location & Service Area Geo Rules

These rules apply equally to businesses with physical locations and businesses that serve defined service areas.

Duda Widgets

Sun, 01 Feb 2026 19:07:54 GMT

Definition

A widget is a self-contained element with its own content settings, design controls, and responsive behavior. Widgets allow teams to structure content consistently and visually while working within the Editor 2.0 layout system.

Duda Widgets

Overview

Widgets are the individual content and functional elements used throughout Editor 2.0. They are placed inside Columns and Inner Columns and represent every visible or interactive piece of a Hibu One Smart Site. Widgets form the building blocks of each page and determine how text, images, buttons, forms, and other components appear across devices.

This post covers Duda Widgets only . For information about third-party integrations, see: → Third-Party HTML Widgets

Widget Categories

Content Widgets

Used for written and structured content.
Examples: Text, Heading, List, Icon + Text, Accordion.

Media Widgets

Used for images, video, downloads, and visual assets.
Examples: Image, Gallery, Video, Slideshow, File Download.

Layout Widgets

Support alignment, grouping, or spacing inside containers.
Examples: Row, Column, Line, Spacer (limited use).

System Widgets

Widgets that interact with platform-level functionality or Connected Data.
Examples: Form, Button (connected), Map, Business Hours, Reviews, Breadcrumbs.

Usage Standards

Placement

Widgets are always placed inside Columns or Inner Columns.
They are not placed directly in Sections.

Consistency

Each widget type serves a specific purpose; teams should use the correct widget for the content being presented.
Repeated design patterns should use the same widget types for clarity and consistency.

Behavior & Styling

Widgets inherit theme-level styling unless intentionally adjusted for a design requirement.
Responsive behavior should be managed using built-in widget settings, not spacing hacks or manual formatting.

Restrictions

Some widget actions are intentionally limited to protect site structure and maintain long-term stability.

HTML/CSS Editing

Custom HTML or CSS applied directly to widgets is restricted and only used when approved for specific needs. The Editor 2.0 experience is not a freeform code environment.

Unintended Transformations

Widgets should be used for their intended function—for example, icons should not replace bullet lists, and headings should not be used for paragraph text.

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Color & Contrast Requirements

Sun, 01 Feb 2026 19:06:54 GMT

Color & Contrast Requirements

Hibu Policy

All text on a Hibu One Smart Site must maintain clear, readable contrast across devices and screen types. Designers must follow WCAG contrast principles and the platform’s built-in contrast indicator. While WCAG AA standards remain the target, Hibu allows a controlled exception zone for cases where strict AA compliance results in a poorer visual outcome. Under no circumstance may text fall below the minimum contrast threshold defined in this rule.

Rules & Guidelines

1. Standard Requirement (Green Target)

Designers should choose color combinations that display a green contrast indicator whenever possible.

Green = fully acceptable and preferred.

3. Hard Stop — Not Allowed

Text with a contrast ratio below 3.4 may not be used under any circumstance.

Below 3.4 = unreadable / fails immediately (no exception)
No exceptions. No overrides.

2. Exception Zone (Red Allowed With Limits)

Designers may use a color combination that shows a red indicator only when the contrast ratio is: 3.5 or higher

Designers may proceed within this range if :

The “green” option produces a noticeably worse design result
The chosen color is still clearly readable
The color aligns with the site’s theme and visual hierarchy
Minor adjustments (lightening or darkening either color) should be attempted before relying on the exception.

Final Thought

At Hibu, readability is non-negotiable. If visitors can’t clearly read the text, they won’t engage, won’t trust the content, and won’t convert. The contrast checker exists to protect the user experience—but good judgment still matters. When a color choice falls within the safe exception range (3.5–4.49), designers may choose the option that genuinely improves clarity and layout.

Purpose / Why It Matters

Strong contrast ensures users can read text easily across screens, lighting environments, and accessibility needs. This rule maintains visual consistency while allowing designers controlled flexibility within safe limits.

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Image Optimization

Sun, 01 Feb 2026 19:04:25 GMT

Definition

Duda automatically optimizes images on Hibu One Smart Sites to improve load speed, performance, and visual quality across devices. This optimization includes resizing, compression, WebP conversion, and delivery through a global Content Delivery Network (CDN). These processes ensure images load quickly without requiring manual adjustments from the user or designer.

This post covers system-level optimization for standard images. For guidelines on image quality, and file limits, see the Images guidelines

Automatic Optimization

Duda applies several built-in optimization techniques the moment an image is uploaded:

Automatic Resizing
Images are resized to match the display dimensions of the element they’re placed in, ensuring they are never stretched beyond their original size.
Lossy Compression
Redundant data is removed to reduce file size while maintaining visual clarity. This significantly improves load speed without noticeably affecting quality.
WebP Conversion
JPG and PNG files are automatically converted to the WebP format, providing smaller file sizes with high image quality.

Duda Image Optimization

Device-Specific Delivery

To ensure images are displayed optimally on all devices:

Responsive Images
Duda serves each device (desktop, tablet, mobile) an image sized specifically for that device’s screen and container.
Adaptive Content
Images load at the ideal resolution for each viewing environment, keeping them sharp on large screens and efficient on small screens.

Best Practices

To support both quality and performance:

Upload images sized appropriately for their intended placement
Avoid tiny images that will appear blurry when enlarged
Avoid unnecessarily large source files (e.g., 4000px images used in a 300px container)
Use high-resolution images for full-width or large background sections

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Renaming PDFs & Downloadable Files

Sun, 01 Feb 2026 19:02:06 GMT

Renaming PDFs & Downloadable Files

Hibu Policy

All PDFs and downloadable files uploaded to Hibu One must be renamed using a standardized, descriptive naming convention that prioritizes file subject and context before the business name. This ensures files are easy to scan, sort, and locate within the Media Manager and by users.

For additional context, see: Renaming Image File Names

Renaming PDFs & Downloadable Files: At-a-Glance

Core Naming Principle

At the core, all client-supplied or Hibu-added downloadable files—including PDFs and other supported formats—must include the file’s subject or purpose, the business name, and a page reference and/or number when applicable.

Why File Naming Matters

Downloadable files are indexed by search engines and surfaced within the Media Manager. Each file is treated as a standalone, searchable document, meaning its name helps signal what the file contains before it is opened. Files with generic or unclear names reduce visibility, slow file selection, and create unnecessary friction during site updates.

Well-structured file names support:

Faster file discovery in the Media Manager
Clearer, more meaningful download buttons for site visitors
Better internal organization across pages and file types
Improved search visibility for indexed documents

Improved Scanability with Subject-First Naming

These examples show how downloadable files appear in the Media Manager when file names lead with the business name. When filenames are truncated, it becomes difficult to distinguish between similar documents.

Files with unclear or generic naming force users to open each file to understand its contents, slowing selection and increasing friction during site updates.

Why the Naming Order Changed

Previously, downloadable files were commonly named with the business name first. While consistent, this approach created a usability issue when browsing or searching files in the Media Manager.

When file names are truncated in tile or list views, the most important information—the file’s subject or purpose—is often hidden.

Poor vs. Descriptive File Names

These examples show the same types of files renamed using the updated, subject-first naming convention. Leading with file context makes it easy to identify documents at a glance, even when filenames are partially truncated.

Leading with file subject ensures:

Related documents group together naturally
File purpose is immediately visible
Files are easier to scan and differentiate

Pro tip: When viewing files in the Media Manager, long filenames may be truncated in tile view. Switching to list view displays more of the filename, making it easier to distinguish similar documents.

File Formats & Conversion

Preferred format: PDF
Other accepted formats (converted to PDF when possible): doc, docx, xls, xlsx, ppt, pptx, psd, zip, xml, mp3

Conversion rules:

Hibu will convert supported files into PDF prior to upload when possible.
Hibu will not edit client-supplied files before conversion.
Hibu will not create new PDFs on behalf of clients.

Files that cannot be converted must still follow the same naming standards.

File Naming Standards

All downloadable files must follow these standards:

Use lowercase letters and hyphens
Do not use spaces, underscores, or special characters
Keep filenames concise and descriptive
Do not include legal suffixes (Inc, LLC, Corp, etc.)
Lead with the file’s subject or purpose
Place the business name at the end of the filename

File Naming Standards

All downloadable files must follow these standards:

Use lowercase letters and hyphens
Do not use spaces, underscores, or special characters
Keep filenames concise and descriptive
Do not include legal suffixes (Inc, LLC, Corp, etc.)
Lead with the file’s subject or purpose
Place the business name at the end of the filename

Examples

automotive-services-form-mikes-automotive.pdf
dinner-menu-joes-italian-bistro.pdf
hardwood-floor-faq-juniors-flooring-and-tile.pdf
rental-agreement-madison-hardware.pdf
new-patient-intake-form-dr-lou-reed.pdf

Fair Use Rules

Per the Fair Use Content Policy :

A site may include up to 50 PDFs or other downloadable files total.
Files may be placed on individual service pages or grouped on a dedicated downloads page.
Multiple files may be added to a single page, but the site total may not exceed 50 .

Notes & Clarifications

Downloadable file names are what appear in download buttons (e.g., “Download [File Name]”).
File numbers do not need to reflect display order on the page.
The Hibu design team is responsible for renaming uploaded files to match naming standards.
Track total file count against the 50-file site maximum.

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

AI and llms.txt

Sun, 01 Feb 2026 19:00:59 GMT

AI and llms.txt

Definition

All major AI platforms — ChatGPT, Perplexity, Gemini, Google AI Overviews, Copilot, and others — build their results from the same public internet that powers traditional search. These systems crawl, index, and interpret site content, then decide whether to reference it when users ask a question or perform a search.

Hibu One Smart Sites are built to maximize the chances of being indexed, understood, and referenced in these AI search experiences.

How Hibu One Sites Are AI-Friendly

Content Depth – Detailed, robust copy gives AI models meaningful, context-rich information about the business.
Local Ranking Boost – Adds optimization (on-site and off-site), improving the likelihood of being referenced in local AI queries.
Geo & Service Area Pages – Expand coverage, making it easier for AI and search engines to match the business with location-based or service-specific searches.
Structured Clarity – Coding (similar to schema) helps AI systems interpret content accurately, including the llms.txt file.
llms.txt File – A machine-readable file giving large language models direct context about the business, its services, and how site content can be referenced.

How to View llms.txt

You can view the llms.txt file for any live site by adding /llms.txt to the end of the domain (e.g., www.example.com/llms.txt ).

When reviewing the file, look for:

Business context (signals like “local service provider” or “medical practice”).
Content definitions (services, pages, FAQs).
Usage guidance (instructions to AI systems on how content may be interpreted or referenced).

Why It Matters

AI Visibility - Schema + llms.txt help AI systems understand not just what’s on the site, but what it means.
Local Relevance - Expanded service and geo content increases opportunities for matches in AI search.
No Guarantees - Just as with Google organic results, no platform guarantees inclusion or ranking in AI answers. Proprietary algorithms ultimately decide what to show. Our role is to give every client the best possible opportunity to appear where it’s relevant and valuable.

Rules and Guidelines

llms.txt is included automatically with every Hibu One Smart Site.
The file is not customizable ; its content is generated and maintained automatically by the platform.
Local Ranking enhances AI optimization by expanding service area and geo coverage, which increases the likelihood of being referenced by AI platforms.
Clients may view the llms.txt file at any time by appending /llms.txt to their domain.
The llms.txt file updates automatically whenever a page is added, deleted, and the site is republished.
Hidden pages are included, but any page set to “no index” will not appear.

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Schema

Sun, 01 Feb 2026 19:00:21 GMT

Schema

Definition

A Hibu One Smart Site is designed to be clear and easy for search engines to understand. Structured data (schema) provides behind-the-scenes context that makes site content easier to interpret, more visible in search results, and more useful to potential customers.

Schema Types Included by Default

Each Smart Site includes multiple schema types to define what different parts of the site mean:

Website Schema – Identifies the site as the client’s main online presence.
Local Business Schema – Highlights business name, address, phone, hours, and service areas for accuracy in local and map results.
FAQ Schema – Surfaces common customer Q&As directly in search results, driving visibility and clicks.
Breadcrumb Schema – Shows page relationships, making navigation clearer for both search engines and users.
Blog Schema* – Enables articles to appear in “Discover” feeds or as featured posts when users search related topics.
Video Object Schema* – Helps videos surface with thumbnails and key details in search.
Reviews Schema* – Highlights customer reviews and ratings, helping businesses stand out with trust signals directly in search results.

* These schema types are applied only when the related content is displayed on the site.

Rules and Guidelines

Schema is automatically included with no option for direct client-side customization.
If a client requests additional schema (e.g., Service, Product, Person, or Organization), they must generate it externally and provide the code.
Hibu can insert client-supplied schema into the header HTML section of a specific page using the single-page SEO options.
All schema must be accurate, relevant, and tied to visible on-page content.

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Page URLs (Slugs)

Sun, 01 Feb 2026 18:59:56 GMT

Page URLs (Slugs)

Effective Date: February 1, 2026 Last Updated: February 12, 2026

Hibu Policy

All page URLs on a Hibu One Smart Site must follow standardized slug formatting.

Slug rules apply sitewide. Certain page types — including Service Area Pages (SAPs) and Geo Pages (GEOs) — require defined structural patterns.

Dynamic URL segments (SAPs city-st) are system-controlled and must not be manually modified.

URL integrity is part of overall site architecture and must remain consistent across all builds.

Page URLs (Slugs): At-a-Glance

Definition

A URL slug is the portion of a web address that appears after the domain and identifies a specific page.

Example: domain.com/residential-painting-services
In this example, /residential-painting-services is the slug.
The slug communicates page content to both users and search engines.

Purpose / Why It Matters

Hibu standardizes slugs to:

Maintain consistent site architecture
Support SEO clarity and keyword alignment
Prevent formatting errors and duplication
Enable scalable dynamic page generation
Protect long-term site integrity

Slug structure is not stylistic — it is structural.

Service Area Pages (SAPs) URL Structure

Service Area Pages follow a structured format that includes a defined keyword and a dynamically generated city-state value.

Parent Service Area Page (PSAP): /contact/keyword-service-area/
Dynamically Generated SAPs: /contact/keyword-service-area/ city-st
Example: com/contact/residential-painting-service-area/ king-of-prussia-pa
Important : The city-st portion is automatically generated based on the connected location collection. Users do not manually enter or modify this segment.

Universal Slug Formatting Rules (All Pages)

These rules apply to every page unless otherwise specified.

Use the navigation label as the basis for the slug.
Use hyphens to separate words ( /roofing-services ).
Do not use underscores.
Use lowercase characters only.
Do not use special characters ( # & % + * = @ ~ ^ $ ), punctuation, or symbols.
Keep slugs concise, literal, and readable.
Avoid unnecessary filler words.
Do not create duplicate or conflicting paths.
Do not manually alter system-controlled segments (SAPs /city-st)
Avoid unnecessary filler words

Geo Page URL (GEOs) Structure

Geo Pages follow a required keyword + city-state structure.

Structure: /contact/keyword-city-st
Example: /contact/residential-painting-king-of-prussia-pa
The structure is standardized.
The city-state follows the city-st format.
The city-state segment is not manually formatted outside system rules.

Title and Meta Description Tags - An Overview

Sun, 01 Feb 2026 18:58:56 GMT

Title and Meta Description Tags - An Overview

Effective Date: February 1, 2026 Last Updated: March 6, 2026

Hibu Policy

Every visible page on a Hibu One website must include:

One unique title tag (target: ~55 characters; maximum: 60 characters)
One unique meta description (target: 150–160 characters)

Title tags and meta descriptions must be descriptive, accurate, aligned with page intent, and written to support click-through from search results.

These elements function as the pre-click version of the 3-30-3 Rule . If the user does not click, the rest of the page experience does not occur.

Definition

Title tags and meta descriptions are HTML elements that control how a page appears in search engine results pages (SERPs) and when shared on social platforms.

The title tag acts as the headline.
The meta description acts as supporting copy.

Together, they function as a mini advertisement for the page.

Purpose / Why It Matters

Title and meta tags:

Drive the first conversion: the click.
Signal relevance to search engines.
Influence click-through rate (CTR).
Establish consistency between search listing and on-page content.
Support conversion-first messaging before a user ever reaches the site.

In many cases, the search result is the first and only impression a user receives. These tags must be written intentionally.

Current Display Standards

Search engines do not impose a strict technical character limit. However, they do have what is considered an optimum range. This is what informs our character-length standards at Hibu.

Meta Descriptions

Desktop display typically truncates around ~155–160 characters.
Mobile truncates earlier.
Ideal range: 150–160 characters.
Critical messaging should appear in the first ~110–120 characters.

Front-loading key information reduces the impact of truncation.

Title Tags

Google typically displays up to ~60 characters on desktop before truncating.
Ideal performance range: ~50–55 characters.
Acceptable upper boundary: 60 characters.
Writing target: 55 characters.

Going to 57–60 characters is acceptable when necessary. The goal is clarity and control, not arbitrary enforcement.

Core Rules and Guidelines

Every visible page must have a unique title and meta description.
Titles and metas must align with page intent.
Homepage, Contact, and Utility pages must include the Name of Business (NOB).
Service/Product pages may omit NOB when user intent is generic.
Meta descriptions must be written in sentence case.
Titles and metas must work together as headline + supporting copy.
Avoid keyword stuffing and awkward phrasing.
Write for humans first, search engines second.
Conversion-first phrasing is required where appropriate.

Copy, Tone, and Audience Fit

Sun, 01 Feb 2026 18:57:32 GMT

Copy, Tone, and Audience Fit

Definition

AI generates the initial copy for Hibu One Smart Sites. Copywriters and QA refine that content to ensure it is accurate, clear, brand-appropriate, and designed to convert. Copy plays a critical role in the 3-30-3 Rule: while motivating factors and the headline hold visitors past the first 3 seconds, it’s the copy and tone that keep them engaged for the next 30 seconds — long enough to prove value and encourage deeper exploration.

Overall Expectations

Copy must be professional, approachable, and conversion-focused.
Tone should match the business type (serious, professional, casual, etc.) and remain consistent across the site.
Copy should emphasize benefits over features and always guide visitors toward a CTA.
Clear, scannable formatting (headings, bullets, short paragraphs) ensures visitors can quickly find what matters.
Copy must reinforce motivating factors and extend them with supporting detail, proof points, or offers.

What to Look for When Editing AI Copy

Copywriters and QAEs should refine AI content as usual, with a focus on carrying users from attention (3 seconds) → value (30 seconds):

Fix formatting issues (spaces, breaks, headings).
Verify CTAs are present, varied, and linked correctly. Limit to one CTA per paragraph.
Remove clichés, fluff, hallucinations, or repetition.
Confirm tone consistency and proper use of the Name of Business (NOB).
Ensure copy connects back to Speed, Quality, Offer, and Trust factors where appropriate.
Check spelling, grammar, and American English consistency.

Adding Additional Content

Insert new content within the main text block before the Contact Us section on internal pages.
Maintain heading hierarchy (H2/H3).
Align new copy with the site’s chosen tone and ensure it includes a CTA.

Copywriter & QAE Responsibilities

Copywriters : Refine AI text, add CTAs, ensure accuracy, and expand motivators into persuasive supporting copy.
QAEs : Verify edits, confirm consistency, and ensure the site is conversion-ready by supporting the 3-30-3 flow (attention, value, conversion).

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Motivating Factors & 3-30-3 Rule

Sun, 01 Feb 2026 18:56:29 GMT

Motivating Factors & 3-30-3 Rule

Definition

Motivating Factors are the core reasons visitors choose to stay on a site and take action. They answer a user’s immediate questions and reassure them they are in the right place — within the first three seconds of arriving.

By design, Hibu includes motivating factors in the hero sections of the homepage, category landing pages (CATs), and core service pages. On homepages and CATs, we also include a “Why Choose Us” section featuring six motivating factors for added visibility.

Hibu refers to these as S.Q.O.T. Factors :

Speed – “How fast can you fix my problem?”
Examples
24/7 Emergency Services
Express Check-In and Check-Out
Walk-Ins Welcome
Quality – “Do you stand by your work? Why should I hire you?”
Examples
State-of-the-Art Facilities
More Than $50 Million Won for Our Clients
Offer – “How much will it cost? What savings or guarantees are available?”
Trust (Reviews/Testimonials) – “Why should I trust you?”

Why They Matter

Motivating factors, paired with a strong headline and hero design, are what get users past the first 3 seconds . If we can’t confirm to a visitor that they’ve landed on the right page, they’ll leave — and conversions are lost.
They directly support the 3-30-3 Rule :
3 seconds : Headline + motivating factors confirm relevance.
30 seconds : Benefits, trust signals, and Why Choose Us sections prove value.
3 minutes : Clear CTAs and persuasive copy drive conversion.
Effective motivating factors drive conversions, reduce cancellations due to “poor ROI,” and make it harder for competitors to steal away traffic.

Rules and Guidelines

Motivating factors must be relevant, specific, and honest — based on the client’s industry and customer needs.
Avoid weak or throwaway motivators (e.g., “Service with a smile”). Focus on what truly drives action: speed, quality, offers, and trust.
Writers and QA must review motivators carefully and edit if they don’t make sense for the business or audience.
Motivators should be prominent and mobile-friendly — easy to see at a glance.
3 motivating factors in the hero is the default
Minimum of two motivating factors must be used in the hero
6 motivating factors is the maximum allowed in the hero
more than 6 won't render properly on mobile devices and will lead to a poor UX (added 4/7/26)
Repetition is encouraged when appropriate: global offers or guarantees may appear across multiple pages, since any page can serve as a landing page.
Client requests for different motivating factors on different pages :
This is acceptable only after first proof.
Motivating factors must be connected to a business text field. No manual-only motivators are allowed.
A Hibu team member must create a new field in Business Text (e.g., Motivating Factors 2, Motivating Factors 3, Motivating Factors 4).
Motivating factors must be connected to a business text field. No manual-only motivators are allowed.

Motivating Factor Examples

Animal / Pets

Animal Hospitals – Walk-Ins Welcome | Care Credit Accepted | 24/7 Emergency Pet Care
Grooming / Spa – Same-Day Appointments | No Breed Restrictions | $15 Off Grooming Services

Community, Social

Childcare – Financial Assistance Available | USDA-Approved Meals | 5% Military Family Discount
Senior Care – Around-the-Clock Care | Personalized Care Plans | $100/day drop-in rate

Contractor

Cleaning – No Long-Term Contracts | Contractor Background Checks | Same-Day Estimates
Concrete – Financing Options | Weekend and Emergency Deliveries | 25% Off Your Next Project
Electrical – Same-Day Estimates | BBB A+ Rating | Up-Front Pricing | Emergency Service | 5-Year Service Warranty
Fencing – 15-Year Warranty | FREE On-Site Estimates | 0% Financing Available | 20% Off Installation
Flooring – Starting at $2.49/Sq. Ft. | FREE Room Measurement | Next-Day Installation
General – Same-Day Response | Home Advisor-Approved | All Work Guaranteed in Writing
HVAC – Flat-Rate Pricing | 24 / 7 Emergency Services | No Extra Fee for Weekends
Landscaping and Garden – A+ BBB Rating | 5% Prepay Discount | FREE Custom Lawn Analysis
Painting – Up-Front Pricing w/ No Hidden Fees | First-Time Customers Get 10% OFF | Satisfaction Guarantee - Free Touch-Ups
Pest Control and Maintenance – Satisfaction Guaranteed | Free Year-Round Inspections | Pet-Friendly Treatments
Plumbing – 24/7 Emergency Plumbing Services | “Smart-Pay” Options | No-Hassle Guarantee
Pools, Spas, and Saunas – No Subcontractors | FREE On-Site Assessment | 25% Off Year-Round Maintenance Programs
Roofing – 12 Months No Interest, No Payments | Lifetime Warranty | Free 3-Year Roof Washing with New Roof
Windows and Doors – Same-Day Service | $239 Window Installation

Dining

Bar – 100+ Beers on Tap | Late-Night Happy Hour | Free Delivery - Orders Over $10
Catering Services – Rent-a-Chef | Top 25 for Brides by theknot.com | Complete Event Planning Services
Pizza – Half-Off Game-Day Specials | FREE Delivery | Voted Best in Springfield County 2017
Restaurant – Kids Under 5 Eat FREE | Daily Specials | “Gluten-Free” Menu Available

General

Accounting and Tax Services – Maximum Tax Refund Guarantee | FREE Financial Analysis
Insurance – Low Rates from $24.94 a Month | Multi-Policy Discounts
Storage – 24/7 Access | First Month FREE | Climate-Controlled Units
Moving – Satellite Truck Tracking | FREE No-Obligation Quote | Fixed-Rate Pricing
Real Estate – 3,000+ Homes Sold | FREE Home Value Assessment | Personalized Marketing
Waste Removal – No Job Too Small | Same-Day Service | No Credit Card Required

Health

Dental Care – Emergency Walk-Ins Welcome | Sedation Options | 25% Off New-Patient Services Specials
Physicians and Doctors – Philly Magazine “Top Doc” | All Insurances Accepted | Weekend and Evening Hours
Therapy and Counseling – Accepting New Patients | Weekend and Evening Hours | 24/7 On-Call Support
Vision Care – Walk-Ins Welcome | 5-Star Ratings on Yelp and Google | Welcoming New Patients
Eyewear – 2 Pairs of Eyeglasses for $69.95 | 50% Off New Patient Eye Exam | Same Day Glasses

Legal

Bail Bonds – Hablamos Español | All Interactions Confidential | No Administration Fees |
Lawyers/Attorneys – You Win or You Don’t Pay | $100,000,000+ Awarded | FREE Case Evaluation

Retail

Antique, Pawn Shops, Thrift, and Vintage, etc. – Cash for Gold | We Make House Calls | Open Nights and Weekends
Appliances Sales and Repairs – Low Price Guarantee | 0% Interest Financing | FREE Delivery
Computer Repair – On-Location Repairs | Same Day Repairs | 90-Day Warranty
Home Furniture and Furnishings – FREE Delivery | Financing Available | 90-Day Warranty
Jewelry, Watch, and Clock – Open Nights and Weekends | Complimentary Cleaning and Inspection
Locksmith – 24/7 Availability | Same-Day Rekeying Service | Price Match Guarantee

Travel

Car, Taxi, Limo, and Shuttle – 24/7 Service | Event and Corporate Pricing | Angie’s Super Service Award 2017

Vehicles

Auto Glass and Tinting – 60-Day Warranty | Mobile Service | 24/7 Emergency Service | No Appointment Needed
Auto Parts and Accessories – Price Match Promise | 60-Day Warranty | FREE Installation with Purchase
Carwash and Detail – Open Nights and Weekends | Gift Certificates Available | Seasonal Detail Discounts
Collision Repair – 15,000+ Cars Serviced | On-Time Guarantee | Lifetime Warranty on All Repairs
Repair and Maintenance – After-hours Drop Off | FREE Diagnostics | 24/7 Round the Clock Towing
Truck and Trailer Rental – Unlimited One-Way Mileage | In-Town Move from $19.95

Wellness / Beauty

Hair Salon – $20 OFF for New Clients | Gift Cards Available | Voted Best Salon by SJ Magazine 2023
Spa – Open 7 Days a Week | Walk-Ins Welcome | Membership Program Available

Auto Repair Motivating Factors Cheat Sheet

Roofing Motivating Factors Cheat Sheet

HVAC Motivating Factors Cheat Sheet

Plumbing Motivating Factors Cheat Sheet

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Badge / Accreditation Logos

Sun, 01 Feb 2026 18:54:40 GMT

Hibu Policy

If a client supplies badge, accreditation, certification, award, or industry logos, we will place them according to the following rules:

If two (2) to twenty-five (25) logos are provided, they will be placed in the designated badge row within the Footer.
If more than twenty-five (25) logos are provided: (added 03/26/2026)
A maximum of twenty-five (25) logos will be displayed in the Footer badge row.
The Footer selection must represent the most relevant, recognizable, or highest-value credentials.
All provided logos must be placed on an interior page (e.g., About page) to present the full collection.
Logos displayed in the Footer may also appear on the interior page. This duplication is intentional and supports both summary and full-detail presentation.
If a client provides a quantity slightly above the limit (e.g., 26–30 logos), the same rule applies:
Do not reduce the Footer count below twenty-five (25).
Do not split the logos evenly across locations.
Display up to twenty-five (25) in the Footer and include the full set on the interior page.
If only one (1) logo is provided, it will be placed within the Footer column (aligned with business information). A single-logo badge row will not be created.
Up to three (3) logos may be placed in the Hero beneath the primary CTA if requested.

Hero Placement (Limited Exception) (updated 4/05/2026)

Up to three (3) logos may be placed beneath the primary CTA within the Hero only if requested.

Conditions:

Logos must remain visually secondary to the primary CTA.
Sizing must be balanced and proportional.
The Hero must not become visually cluttered.

The Footer remains the primary and required badge location in all cases.

Badge / Accreditation Logos

alt text tag = EcoTherm Insulation

alt text tag = The National Trial Lawyers Top 100 Trail Lawyers

alt text tag = Best of the Best Dentists

Naming Standard

All badge, icon, accreditation, award, and non-client logos must follow a standardized naming convention.

Format:

entity-name-badge-name-of-business

Examples:

angies-list-2025-badge-kenny-and-son-builders
angies-list-2026-badge-kenny-and-son-builders
homeadvisor-badge-kenny-and-son-builders
gaf-certified-badge-kenny-and-son-builders
owens-corning-badge-kenny-and-son-builders

No variation in naming format is permitted.

Effective Date: February 1, 2026 Last Updated: March 26, 202 6

Definition

For governance purposes, “Badge / Accreditation Logos” includes:

Certifications
Awards
Membership badges
Professional seals
Industry logos
Recognition marks
Non-client logos

Regardless of how the client refers to the asset (badge, icon, accreditation, logo), all are governed under this single standard.

If someone asks, “Is this really a badge?” — for naming and placement purposes, the answer is yes .

Placement Rules

Primary Location (Footer)

The Footer badge row is the required and primary location for all Badge / Accreditation Logos.

A maximum of twenty-five (25) logos must be displayed in the Footer badge row.
The Footer must always contain the most relevant, recognizable, or highest-value credentials.
Logos in the Footer must be visually normalized for consistent presentation.

Client-Requested Additional Placement

If a client requests specific badge placement outside of the Footer, the following rules apply:

The Footer requirement remains mandatory; up to twenty-five (25) logos must still be included in the Footer.
The same logos may be reused in additional locations across the site (e.g., within page content, sections, or supporting areas).
Repetition of the same badge in multiple locations is permitted and expected when supporting client requests.
Additional placements must not replace, reduce, or override the Footer badge row.

Single Badge Exception

If only one (1) badge is provided:

Place the badge within the Footer column (aligned with business information).
Do not create a dedicated badge row for a single logo.

Alt Text Requirements

Every badge must include descriptive alt text.

Alt text must:

Include all readable text shown on the badge.
Accurately describe the accreditation or award.

Example:
“The National Trial Lawyers Top 100 Trial Lawyers”

Do not use generic alt text such as:
“Badge logo” or “Award icon.”

Design Standards

Consistency

Logos of varying shapes and proportions must be normalized.

Place each badge on a square canvas.
Maintain 15–20px white space for uniformity.
Ensure consistent spacing between badges.

This may slightly adjust original proportions for visual alignment.

Quality Standards

If a badge appears pixelated or low-resolution:

Confirm placement size.
Search for higher-resolution sources (resource library or verified source).
Replace both desktop and mobile assets for consistency.

If a high-quality replacement is unavailable:

Use the best available file.
Document the limitation in assumptions if quality impacts presentation.

Missing Badge Policy

If a client references a badge but does not provide a usable file:

Do not recreate it.
Do not design a substitute.
Do not create a text-based replacement.

Add the following assumption: “Assumption: Badge/accreditation logo unavailable, not added.”

Instagram Feed

Sun, 01 Feb 2026 18:52:41 GMT

Definition
The Instagram Photo Gallery Feed allows a Hibu One Smart Site to automatically display images from a connected Professional Instagram account (Business or Creator). The feed pulls recent image posts directly into the site’s Photo Gallery widget, keeping the display current without manual updates.

Instagram Photo Gallery Feed

Eligibility & Account Requirements

Only Professional Instagram accounts (Business or Creator) are supported.
Personal or private accounts cannot be connected.
Only one Instagram account may be connected per site.
Clients do not provide login credentials to Hibu; access is handled securely through Instagram’s permissions workflow.

Display Rules & Content Behavior

The widget displays image posts only .
Videos, reels, stories, and collaborations are not supported .
Up to 100 of the most recent images may appear.
Captions may display on desktop only , when enabled in settings.
Feed updates automatically; new images may take up to two hours to appear.
Due to Meta’s 2024 update, connections made before December 2024 must be reconnected .

Client Expectation Note
The Instagram Photo Gallery Feed is intended for clients who maintain an active, professional-quality Instagram presence. Connection reliability and content display depend on Meta’s integration and account status.

Integration With Hibu One Site

The Instagram Photo Gallery can be used in two ways:

1. As a Replacement for the Standard Gallery

The Instagram feed may replace the Home, Cat, or Core Page’s static gallery when:

If questionnaire does not indicate specific Instagram placement on Gallery Page
The client actively maintains a strong photo-based Instagram presence.
Instagram contains more or better-quality images than the client provided.

2. Combined With Client-Supplied Images on a Gallery Page

The Instagram feed can be placed above or below the client’s images on the Gallery page. It can also act as a standalone gallery.

Placement rules:

If the client has 25+ images (as one large set or multiple gallery sections):
Place the Instagram gallery at the bottom of the page.
This prevents overwhelming the layout and keeps the client’s photos primary.
If the Instagram feed contains more images than the client provided:
Place the Instagram gallery above the client images.
This ensures visitors see the most up-to-date and active content first.

Anchor-Link Requirement

In all placement scenarios:

Add an anchor link labeled “Instagram Gallery” that points directly to the Instagram gallery section, in addition to any client-provided image sections.
Do not add an anchor if the Instagram Gallery is the only gallery on the page.
This allows gallery sub-navigation, internal navigation, CTA buttons, and homepage copy blocks to link users precisely to the correct gallery section.

Client Expectation Note

The Instagram Photo Gallery Feed is intended for clients who maintain an active, professional-quality Instagram presence. Connection reliability and content display depend on Meta’s integration and account status.

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Site Architecture

Sun, 01 Feb 2026 18:51:33 GMT

Site Architecture

Definition

A solid site architecture is the foundation of a Smart Site. Without clear structure, even the best copy and SEO will not convert.

Rules and Guidelines

Each page should have one clear purpose (service, topic, or intent).
Avoid duplicating content; use hierarchies and internal links instead.
Separate topics when search intent is different; combine them when phrases are synonymous.
Use predictable, consistent structures (Homepage → Category Landing Pages → Core Pages).
Label pages in clear, human language so visitors (and Google) instantly understand them.

Key Takeaway

Strong architecture ensures users find what they need, Google understands the site, and conversion pathways remain simple and effective.

Also see Page Types and Navigation Tiers

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Content & SEO Introduction

Sun, 01 Feb 2026 18:50:34 GMT

Introduction

When it comes to content and SEO, our goal is simple:

Build sites that rank by being technically sound and search-friendly.
Build sites that convert by speaking directly to the audience with clear, motivating content.
Build sites that are sustainable — consistent, trustworthy, and aligned with modern search and user experience standards.

But above all: if visitors don’t stay on the site, nothing else matters. That’s why every Hibu One Smart Site follows the 3-30-3 Rule :

3 seconds to confirm the visitor has arrived in the right place — through the combination of headline, motivating factors, and hero design. The immediate goal is to keep them on the page.
30 seconds to prove value — with benefits, trust signals, and supporting offers that reassure them this business can meet their needs.
3 minutes to drive conversion — guiding them with clear CTAs, scannable content, and persuasive supporting copy.

If a visitor isn’t convinced in the first 3 seconds, the money spent to drive them to the site is wasted. Our responsibility is to make sure they stay, engage, and convert.

Hibu One Smart Sites are AI-optimized for SEO and built to convert. Our approach is not simply to “add keywords,” but to create technically sound, trustworthy, human-centered websites that rank well because they are designed for both people and search engines — and ultimately drive visitors to act.

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Sections, Columns, and Inner Columns

Sun, 01 Feb 2026 18:48:02 GMT

Definition

The layout structure is the system of containers that defines how every part of a Hibu One website is arranged. These containers create the underlying framework for the site’s design, spacing, and responsive behavior.

Sections, Columns, and Inner Columns

Overview

Editor 2.0 uses a standardized layout hierarchy built around Sections , Columns , and Inner Columns . All Hibu One Smart Sites follow this structure as the foundation for how content is organized and displayed across every device.

Sections

Sections are the primary horizontal building blocks of every page. Each section represents a major content area — such as a hero, a service callout, or a testimonial block. Sections set the overall width, background, and visual boundaries for the content inside them.

Inner Columns

Inner Columns provide an additional layer of layout control inside a column. They are used when a design requires more detailed organization — for example, pairing an icon with a label, grouping items inside a card, or creating consistent spacing between repeated elements..

Purpose / Why It Matters

Sections, Columns, and Inner Columns form the core layout system of Editor 2.0. Understanding these containers helps teams interpret templates correctly, troubleshoot layout behavior, maintain consistent visual patterns, and ensure that content responds cleanly on every device.

Additional Notes

Widgets are placed inside Columns and Inner Columns, not directly inside Sections.
Responsive behavior is shaped by how these containers relate to each other.
The Layers Panel provides a clear view of this hierarchy and how content is grouped.
A clean structure supports accessibility, predictable spacing, and reliable design outcomes.

Columns

Columns divide a section into vertical regions, allowing content to be grouped side-by-side or stacked in structured ways. Columns determine how elements align within a section and how that arrangement adapts as the viewport changes from Desktop to Tablet to Mobile.

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

301 / URL Redirects

Sun, 01 Feb 2026 18:45:03 GMT

301 / URL Redirects

Definition

A 301 / URL Redirect is a permanent URL forward that sends visitors — and search engines — from an old URL to a new, correct page location. Redirects prevent 404 errors, preserve SEO value, and ensure that bookmarks and external links continue to function even when pages change or are removed.

301s are required whenever a previously public URL no longer exists or has been replaced.

Purpose / Why It Matters

A clean redirect strategy ensures:

No broken paths for visitors landing on outdated URLs.
Preservation of SEO equity , so rankings pass from old URLs to new ones.
Smooth migration from a client’s prior website (Hibu-built or 3rd-party) to a new Hibu One Smart Site.
Professional UX , avoiding “Page Not Found” errors that hurt trust and conversion.

Old URLs may continue to appear in Google results for weeks or months after launch, making proper redirects essential.

When Hibu Uses 301 Redirects

Hibu will apply redirects when:

A Previous Website Is Replaced by a Hibu One Smart Site
Hibu redirects the client’s old URLs to appropriate locations on the new site — typically the home page or closest equivalent page.
Old Next Gen / Smart Site URLs → new Hibu One site home page or closest page equivalents
Old BYOD URLs → new Hibu One site home page or closest page equivalents
A Previous Website Is Replaced by a Hibu One Smart Site
If a URL slug changes (e.g., /roof5730 → /roofing-services ), a redirect ensures both users and Google reach the correct updated page.
A Single Page Is Split Into Multiple New Pages
If a client’s old “Services” page covered many topics and is converted into separate, topic-specific pages, the old URL must be redirected appropriately.
/services → appropriate new locations (often homepage when no direct equivalent exists).
Multiple Old Pages Are Consolidated into One New Page
When redesign strategy merges many pages into one modernized page, old individual URLs must point to the consolidated destination.
Example (Page 6):
10 lawyer bio pages → 1 consolidated attorney page

Redirect Scope & Limitations

What Hibu Will Redirect
Old Hibu-built site URLs
Old third-party site URLs as long as the same domain is used
Any URL changed or removed as part of the new build
What Hibu Cannot Redirect
Domains the client is no longer using — only the domain used on the new Hibu One Smart Site can be redirected.
(Client must handle domain-level redirects through their registrar.)
Page 1 reference.
URLs for which no ownership or DNS access exists
Redirects within external platforms (e.g., Shopify, Wix, 3rd-party apps)

Redirect Destination Rules

To maintain consistency and avoid incorrect forwarding:
Acceptable redirect targets
The new page that best matches the old page’s intent
The new homepage (when no equivalent page exists)
A consolidated topic page (if the content was merged)
Unacceptable redirect targets
Redirects that create loops
Redirects to external domains not controlled by the client
Redirects that mislead users by pointing unrelated old pages to irrelevant new pages

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Photo Galleries

Sun, 01 Feb 2026 18:44:53 GMT

Hibu Policy

Photo Galleries are used to showcase real, client-supplied imagery that highlights a business’s work, products, or services. Galleries must support user experience, maintain page performance, and follow Hibu One Smart Site structure guidelines.

Photo gallery usage is governed by both this definition and the Fair Use Policy. All gallery images count toward the total site limit of 1,000 images.

Stock images are not permitted within photo galleries.

This post covers the photo galleries only. For Images , Image Renaming Rules, Header Logo , Favicon and Social Network Images , Badges/Icons , and Duda Image Optimization please refer to their dedicated guidelines.

Photo Galleries

Photo Galleries: At-a-Glance

Definition

A Photo Gallery displays a structured collection of client-supplied images, typically organized by service, product, or category. Galleries reinforce credibility by presenting real examples of a client’s work.

Gallery Limits & Placement Rules (updated 03/26/26)

A site may include up to 20 total galleries
Each gallery should target up to 50 client-supplied images
A maximum of 60 images per gallery is allowed when image counts slightly exceed the standard limit
All gallery images contribute to the 1,000 total image limit per site
Exceeding these limits is not permitted

Handling Overages:

If image count slightly exceeds 50 (e.g., 51–60), images may remain within a single gallery
If image count exceeds 60, images must be split into multiple galleries
When splitting galleries, images should be distributed as evenly as possible (e.g., 62 images = 31 / 31)

Effective Date: February 1, 2026 Last Updated: March 26, 202 6

Page-Level Placement

Service / Product pages:
Maximum of 1 gallery per page
Main Gallery page:
May include up to 20 galleries total
Galleries should be organized and grouped for clarity

Organization & Structure (updated 03/26/26)

Galleries must be grouped by:
Service
Product type
Category or theme
When a client has a high volume of images:
Images must be distributed across multiple galleries
Oversized, single-gallery groupings are not allowed beyond the 60-image maximum
Galleries should be balanced to maintain clarity, usability, and visual consistency

Image Requirements

All images must be:
Client-supplied
Relevant to the business
High-quality and clear
Stock imagery is not permitted in galleries under any circumstance

Design & Presentation

Designers may:
Adjust cropping for composition
Reposition focal points
Apply overlays or supporting elements when appropriate
Gallery layout and styling:
Must align with overall site design
Must prioritize clarity and usability over visual density

Consistency Standards

All galleries on a site must follow a consistent design approach when using:
Headings
Text overlays
Buttons
Spacing and alignment

File Naming & Accessibility Standards

The Hibu design team is expected to:

Rename all uploaded gallery images for organization and consistency
Apply descriptive alt text to all images to support accessibility and SEO

Performance Impact (added 03/26/2026)

Gallery image limits exist to protect overall site performance, usability, and load behavior.

Large image groupings can negatively impact page load speed, particularly on mobile devices
Excessive images in a single gallery can create poor user experience due to long scroll depth and delayed rendering
Balanced galleries improve scanability and help users navigate content more efficiently
Maintaining consistent gallery sizes supports predictable layout behavior across breakpoints

These limits ensure galleries remain performant, visually organized, and aligned with Hibu One Smart Site standards.

Hero Images

Sun, 01 Feb 2026 18:42:33 GMT

Hero Images

Hibu Policy

Hero images must be high-quality, relevant, and aligned to the service being represented. The selected hero must clearly reflect the business offering and support strong visual hierarchy across desktop, tablet, and mobile.

Hero types (Standard, Form, and Thin Heroes) follow consistent structural and content expectations, including image clarity, overlay readability, and appropriate use of text and conversion elements.

Image reuse is restricted across unrelated services or page types. Each hero should feel intentionally selected for the content it supports.

When multiple pages represent the same core service, reuse of the same hero image is permitted. This includes core service pages and their corresponding Geo Pages or Service Area Pages (SAPs), as well as closely aligned pages derived from the same service or category. In these cases, the same image may be used consistently across all variations of that service, provided it remains accurate and contextually appropriate. (added 4/05/2026)

The Hibu design team is responsible for renaming all image files and applying appropriate alt text to support accessibility and SEO standards.

Hero image selection, composition, and quality standards are defined within this guideline. Layout behavior, including standard, form, and thin hero structures, is defined in Hero (Standard, Form & Thin Heroes) . Image sizing, ratios, and file requirements are governed by Image Size Guidelines .

Effective Date: February 1, 2026 Last Updated: April 5, 202 6

Definition

A hero image is a full-width visual placed at the top of a page. It works alongside the headline (H1) and motivating factors to confirm page relevance and guide user action within the first few seconds.

Purpose / Why It Matters

Hero images establish immediate context and visual credibility. They support the 3-30-3 Rule by helping users quickly understand where they are, what is offered, and what action to take.

When used correctly, they support engagement and conversion. When used poorly, they create confusion, reduce readability, and weaken the overall experience.

Rules & Guidelines (updated 4/05/2026)

Image Content & Selection

Images must clearly relate to the service, product, or page topic
Each page must include a unique hero image to reinforce page relevance and support clear navigation
Hero image reuse is allowed when pages represent the same core service, including:
Core service pages and their Geo Page variations
Core service pages and corresponding Service Area Pages (SAPs)
Category-aligned pages where a direct service equivalent does not exist
Acceptable examples:
“AC Repair” core page reused across all “AC Repair [City]” pages
“Roofing Services” category hero reused for a related Geo/SAP page
Avoid visuals that compete with or repeat the on-page message
Close-up or texture-based images are often more effective because they reduce visual noise
Client images featuring signage, vehicles, or team members should be used in supporting sections—not in the hero

Readability & Visual Hierarchy

The image must support the headline and CTA—not compete with them
Avoid busy or high-contrast backgrounds behind text
Ensure there is enough open space for content placement
Keep the top portion of the image clean for navigation and header elements

Overlays

Use overlays when needed to improve text readability
Brand-aligned colors are preferred, but clarity always comes first
Overlays should:
Make text easy to read
Keep image details visible
Support the design without overpowering it

Composition & Cropping

Images must hold up across desktop, tablet, and mobile
Important subjects (faces, products, focal points) cannot be cropped at different breakpoints
Choose images with natural open space for text, forms, and CTAs
If needed, mirroring the image is acceptable to improve balance

Header & Layout Compatibility

For transparent headers, the top ¼–½ of the image must remain uncluttered to ensure navigation and text remain readable
The image must display consistently across desktop, tablet, and mobile

Image Quality Requirements

Images must be high resolution and free from distortion or compression artifacts
Stretched, pixelated, or outdated images are not permitted
Legacy assets that do not meet current standards must be replaced
Refer to Legacy Image Guidelines for additional detail

Image Size Reference (Hero-Specific) (updated 3/31/26)

Minimum acceptable size: 1200 × 534 px
This is the absolute minimum required to support the hero container. Images below this size are not permitted, as they will be scaled up and appear blurry on desktop
Recommended size: 1920 × 1280 px or larger
This range provides consistent clarity, supports flexible cropping, and ensures strong visual quality across devices
Maximum width: ~2400 px
Images up to approximately 2400px wide provide optimal clarity on high-resolution (retina) displays without introducing unnecessary file size or performance impact
Avoid excessively large images (above ~2400–2600 px wide)
Very large images increase file size and may be automatically compressed or resized by the platform, which can reduce image quality and negatively impact load performance
If a source image exceeds the recommended maximum size, it should be scaled down to an appropriate width (typically between 1920–2400 px) before upload
Images must be properly composed to support the hero layout without excessive cropping or loss of key visual content
For full image sizing, ratios, and file requirements, refer to Image Size Guidelines .

File Handling & Accessibility

The Hibu design team will rename all uploaded image files
All images must include descriptive, SEO-friendly alt text
Refer to Image Naming Guidelines for file naming standards and conventions
Refer to Alt Text Guidelines for accessibility and SEO requirements

Hero Images: At-a-Glance (added 4/02/26)

Images

Sun, 01 Feb 2026 18:41:29 GMT

Hibu Policy (updated 4/05/2026)

Hibu will upload and optimize up to 1,000 total images per site . This total includes all image assets used across the site, including logos, icons, badges, and reused image elements .

Images must meet platform quality standards and display requirements to ensure a consistent, professional website experience across desktop, tablet, and mobile devices.

This post covers the images only. For Image Renaming Rules, Header Logo , Favicon and Social Network Images , Badges/Icons , and Photo Galleries , Duda Image Optimization please refer to their dedicated guidelines.

Definition

Images include all photographic and graphical assets used throughout a Hibu One site, such as standard images, gallery images, logos, icons, badges, and other recurring visual elements.

Images

Hero Image Requirements

The main hero image at the top of a page requires a wide, high-quality landscape image .

Hero image specifications:

Ideal width: 1920 pixels
Minimum width: Approximately 1200 pixels
Orientation: Landscape (wide)

Portrait or vertical images are not supported for primary hero placement . Vertical images require heavy cropping to fit the space, which often removes key visual details and results in a less refined appearance. Supplying a wide, high-resolution image ensures consistent quality across all devices.

Image Limits & Counting Rules (updated 4/05/2026)

A site may include up to 1,000 total images .
This includes all image assets used across the site, including logos, icons, badges, and recurring image assets .
A site may include up to 20 separate galleries , with a maximum of 50 images per gallery .
All image assets count toward the 1,000-image limit , including:
Brand logos
Icons
Badges and accreditations
Gallery images
Standard and supporting images
Reused images
A reused image counts only once toward the total image limit, regardless of how many times it appears on the site.

Images: At-a-Glance (updated 4/05/2026)

Legacy or Low-Resolution Images

Older or low-quality images may be restricted as follows:

Excluded from high-visibility placements such as hero areas, sliders, or callouts
Allowed in supporting sections or galleries when visual impact is minimal

Refer to Legacy Images for additional details and clarification.

Hibu File Standards

It is expected that the Hibu design team will:

Rename all uploaded images for organization and consistency
Apply descriptive alt text to all images to meet accessibility and SEO standards

Effective Date: February 1, 2026 Last Updated: April 5, 202 6

Header Logo

Sun, 01 Feb 2026 18:21:19 GMT

Header Logo

Hibu Policy

The header logo is the primary visual identifier of a business and appears in the site header of every Hibu One Smart Site. Each site features one official business logo in the header — no exceptions .

The logo must be clear, high-quality, properly optimized, and consistent across desktop, tablet, and mobile to maintain brand integrity and a professional appearance.

This guideline applies to the header logo only. For favicon and social network images, badges/accreditation logos, and Client Logo Use Before Release Agreement requirements, refer to their respective definitions.

This guideline applies to the header logo only . For Image Size Guidelines , Favicon and Social Network Images , , Badges / Accreditation logos , and Client Logo Use Before Release Agreement please refer to their dedicated guidelines.

Effective Date: February 1, 2026 Last Updated: April 2, 202 6

Header Logo: At-a-Glance (added 04/02/26)

CTA Lead-in

 (888) 888-1111 

Call or Text

 (888) 888-1111 

Definition

The header logo is the official business mark displayed in the website’s global header area. It represents the business brand and anchors site identity across all pages and devices.

Purpose & Why It Matters

The header logo is the most visible branding element on the site. It establishes trust, reinforces recognition, and supports a consistent user experience across devices.

A low-quality, inconsistent, or improperly formatted logo negatively impacts perceived credibility and site professionalism.

Rules & Guidelines

Logo Usage

Only one business logo may be featured in the site header.
If multiple logo variations exist, the client must select one for website use.
The selected logo must be optimized for desktop, tablet, and mobile headers.
The logo must be appropriate for full-width header layouts and remain legible at smaller sizes.
Hibu does not redesign, rebuild, or recreate logos.

Accepted File Types (updated 04/02/26)

Preferred: PNG
Accepted: SVG, JPEG, WebP
Not permitted:
GIF (animated or static)
BMP
Any logo containing animation, flashing elements, or motion

Minimum Quality Requirements

Recommended minimum size: ~250–400 wide (depending on header layout)
Logos must appear sharp and free of pixelation on all devices.
Blurry or low-resolution logos are not acceptable.

If a submitted logo does not meet quality standards, the Hibu design team will:

Search for a higher-resolution version , which may include:
Reviewing the client’s existing or prior website
Checking verified business listings (e.g., Google Business Profile)
Conducting a Google image search using the business name or “Business Name logo,” filtered for large image sizes
Confirming any discovered version is an exact match in style, color, typography, and design before use
Or use the best available version and document limitations in assumptions
Only logos that are identical to the client’s established branding may be used. Logos containing added elements (e.g., phone numbers, taglines, promotional text) must match the official brand mark or be cleanly separable without altering the logo itself.

Connected Data & Device Behavior

The header logo is connected through:

Content → Connected Data → Business Images → header-logo
(formerly “dark-logo”)

Device Independence

Header logos on desktop, tablet, and mobile are not linked to one another .

This means:

Disconnecting or updating the logo on one device does not update it automatically on other devices.
Any logo updates must be repeated across all device views.
This separation ensures proper scaling and layout control for each header configuration.

Client Logo Use Before Release Agreement

A client’s logo may be used during the build phase prior to a signed Digital Content Release Agreement only when there is clear, visible evidence that the client publicly uses and owns that logo .
If ownership or usage cannot be reasonably validated, the logo must not be used until the release is signed.
Designers must document the evidence supporting usage when proceeding under this assumption.
For full requirements, validation standards, and examples, refer to the Client Logo Use Before Release Agreement guideline.

Transparency & Header Compatibility

Logos must work across header variations, including solid and transparent headers
When a transparent header is used:
A white or single-color light version and a full-color version of the logo may both be used strategically
A white/light version may be used where background imagery requires contrast
Full-color logos may be used on interior pages or solid backgrounds where contrast allows
All variations must be official brand-approved versions

File Handling & Accessibility

The Hibu design team will rename uploaded logo files appropriately
Descriptive alt text must be applied to each logo version for accessibility and SEO

Hibu Digital Content Release Agreement

Sun, 01 Feb 2026 18:18:41 GMT

Definition

The Hibu Digital Content Release Agreement authorizes Hibu to collect, use, and reproduce content from third-party websites or online sources not owned or controlled by the client for use in Hibu digital products, including websites, display ads, and social media campaigns.

This agreement is not required for original content provided directly by the client. (added 2/09/26)

Hibu Digital Content Release Agreement

When Required

This agreement is required only when a client requests the use of content, imagery, or materials sourced from a third-party website that is not owned or hosted by Hibu or the client .

Clients providing original content, imagery, or text they own do not need to complete a Digital Content Release Agreement.
Clients migrating from a legacy Hibu program or an existing Hibu Smart Site to a Hibu One Smart Site do not need to complete this form, as existing assets are already covered under Hibu’s original content permissions.
If third-party content is requested for use and ownership or usage rights are not already established, a completed Digital Content Release Agreement is required before that material can be published.

Client Logo Exception (added 2/09/26)
In limited cases, a client’s logo may be used before a signed Digital Content Release Agreement when there is reasonable, visible evidence that the client already owns and publicly uses the logo.

See Client Logo Use Before Release Agreement for full criteria and documentation requirements.

Form Details

The agreement requests the following information:

Business name and contact information
URL(s) from which Hibu will collect content
Identification of the content owner (client or third party)
Signature and date authorizing collection and use
The form is mobile-friendly and can be completed directly from a phone or tablet for convenience.
 This form must only be completed by the client or authorized business personnel — not by Hibu Sales or internal staff.

View the Hibu Digital Content Release Agreement

Effective Date: February 1, 2026 Last Updated: February 9, 202 6

Legacy Images

Sun, 01 Feb 2026 18:10:43 GMT

Older assets from narrow layouts (e.g., 960px designs) may appear blurry or stretched on modern 1200px+ layouts.
Such images may not be carried over. Instead:
We will use high-quality, current images that fit the design.
Clients may supply updated, higher-resolution versions.
Lower-quality images may still be used in secondary sections or galleries , but not as hero images.
Mandatory: If a client-supplied image is excluded from the hero due to quality, the designer must log a detailed assumption, share with the DSC, and ensure it is included in client communications. Transparency is required.
Options for legacy images:
Use in galleries (if grouped, see below).
Use in secondary placements where scaling or cropping issues are less visible.
Exclude from site with documented reasoning.

Legacy Images

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Blog Overview

Sun, 01 Feb 2026 17:09:29 GMT

Hibu Policy

The Blog feature in Hibu One allows businesses to publish article-based content that supports SEO, thought leadership, and ongoing site freshness. Blog content may be created natively within Hibu One or imported from an existing site, subject to defined platform limits and migration rules.

Blog Overview

Definition

The Blog is a structured content feature within Hibu One Smart Sites that enables publishing, managing, and displaying time-based articles. Blog posts are distinct from standard site pages and follow platform-specific limits and import rules.

Blog Availability & Ownership

Every Hibu One Smart Site includes a blog option.
The blog becomes visible on the live site only after at least one post is published.
Customers have full DIY access to create, publish, unpublish, and manage blog posts.
Blog posts are independent of standard website pages and do not count toward the 1,000-page site limit.
Hibu does not create or write blog posts unless included as part of a contracted service.

Blog Content Limits & Capacity

Platform Capacity

A Hibu One Smart Site supports up to 1,500 total blog posts .
This limit includes all created, imported, and retained posts.
Blog posts are managed within the Duda blog platform.

Importing Blog Content

RSS Import (Third-Party Sites)

Up to 300 posts per feed (system limit)
Imported blog posts from an external (non-Hibu) site
Blog posts are imported via a valid, supported RSS feed.

Legacy Hibu Site Migration

When upgrading from an existing Hibu website:

Blog content is imported via RSS when available.
If an RSS feed is unavailable or unsupported, Hibu will follow the import process defined in Blog Post Migration, including page source feed discovery and Operations Support ticket for scrape.

What Typically Imports

When importing blog content (via RSS or rebuild), the following elements are generally supported:

Text content (H1/H2/H3, paragraphs)
Post title, post URL/name, author, and publish date
Meta titles and meta descriptions, when available

Content Limitations

Images, videos, and embedded HTML may not transfer correctly and are dependent on the source platform.
Styling, layout, and visual presentation will not match the original site.

All imported or rebuilt content automatically conforms to Hibu One Smart Site design standards to ensure consistency, performance, accessibility, and mobile responsiveness.

SEO Considerations

Published blog posts automatically generate SEO-friendly schema markup.
Posts include editable meta titles, descriptions, tags, and URLs.
Preserving original URLs and metadata is attempted when technically feasible to maintain SEO continuity.

Key Notes & Client Communication

Imported posts may differ visually from the original site due to updated spacing, fonts, and layout structures.
It is expected that teams proactively inform clients that:
Older blog posts may not be retained
Visual presentation will align with Hibu One standards, not the legacy design

Blog Overview: At-a-Glance

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Image Labels vs. Image File Names

Sun, 01 Feb 2026 16:50:55 GMT

Image labels are not the same as image file names and should not follow the same rules.

An image label is a descriptive name applied to an image inside the Content Library or a Collection. Labels exist solely to help teams find, identify, and connect the correct image when placing it on a page in Duda.

Image labels are commonly used when assigning images to:

Headers or logos
Hero sections or hero backgrounds
Section or column background images
Collection-driven images

The primary purpose of an image label is internal clarity and searchability , not SEO.

Image Label Guidelines

Labels should describe what the image is used for , not the business name.
Labels should be written in plain, human-readable language.
Labels should make it easy for someone—including the original designer—to quickly search for and reuse the correct image.

Examples of acceptable image labels:

Home Page Hero Background
Header Logo
Interior Gallery Image
Service Area Hero Image

What Image Labels Are Not

Image labels are not visible to site visitors .
Image labels are not used by search engines .
Image labels do not replace alt text.
Image labels do not follow image file naming standards.

Image file naming, alt text, and image labels each serve a different purpose and must be treated separately. Labels exist to support efficient site builds and long-term maintainability within the editor.

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Image Labels vs. Image File Names (Important Distinction)

Additional Locations

Sun, 01 Feb 2026 16:50:03 GMT

Additional Locations (Multi-Locations)

Hibu Policy

Additional Locations, also referred to as Multi-Locations , is a paid add-on product within Hibu One Smart Sites.

When this add-on is present on a site, it indicates the product has been purchased and validated through Hibu’s ordering system. Additional Locations enable a single website to support multiple real, physical business locations through structured, location-specific pages.

Additional Locations represent legitimate, customer-facing business locations. They are not used for service areas, SEO-only city targeting, or virtual offices.

Related Definitions

For additional context, see:

Effective Date: February 1, 2026 Last Updated: February 8, 202 6

Additional Locations: At-a-Glance

Definition

Additional Locations (Multi-Locations) is a paid add-on product that creates Location Profile Pages for each physical business location beyond the primary location, while maintaining a single, unified website experience.

NOTE: The additional location or locations need to be an actual storefront or business property, not a residential address.

What Additional Locations Create

When the Additional Locations add-on is active, the site includes:

A Locations Category landing page
Location Profile Pages for each location
Location Cards displayed where applicable
Location entries in site navigation and footer

Each Location Profile page supports:

Location-specific address and contact details
Location-specific unique content and imagery when provided
Location-level CTAs and routing

Header Behavior

When the Additional Locations product is active, header content must remain intentionally generic and must not surface individual location detail. The header represents the business as a whole, not any single branch.

The product-specific header configuration is required when Additional Locations is active. A standard Smart Site header must not be edited or restructured to replicate Additional Locations behavior. Header structure, navigation logic, and dropdown functionality are controlled by the Additional Locations product framework and are not custom-built or adjusted per site. (updated for clarity 2/12/26)

To avoid misleading GEO emphasis, visual clutter, routing inconsistencies, and inconsistent experiences across devices, the following rules apply:

Individual location names must not appear in the header
City-level GEO references must not appear in the header
Headers must not include lists, rollups, or implied groupings of locations
Header content must remain concise and business-level in scope

These rules apply across all supported header patterns (desktop, tablet, and mobile). Location-specific detail is intentionally reserved for the Location Category Landing Page and Location Profile Pages.

Hero GEO H2 Behavior

The Hero GEO H2 is the only approved header-level area where limited location referencing is permitted when the Additional Locations add-on is active.This allowance is intentionally constrained to balance clarity, SEO intent, and visual hierarchy.

Location Reference Limits

The Hero GEO H2 may reference up to two locations or offices by name
When referencing more than two locations , the Hero GEO H2 must use aggregate or descriptive phrasing
Listing or rolling up multiple city names beyond two locations is not permitted

This rule applies regardless of business type, industry, or service area size.

Approved Usage Patterns

Direct reference (maximum of two):
Serving Portland and Vancouver
Offices in Boston and Cambridge

Aggregate or descriptive reference (required when more than two):

Four Convenient Offices to Serve You
Three Offices in New Hampshire
Three Convenient Local Locations
Multiple Locations Across Southern California

Aggregate phrasing may reference:

Total number of locations
A state, region, or general service area
Descriptive terms such as “local,” “convenient,” or “near you”

Not Allowed in the Hero GEO H2

Listing more than two city names
Long-form city strings or comma-separated locations
Repeating navigation-style location lists
Using the Hero GEO H2 as a substitute for the Location Category Landing Page

Location discovery and selection must occur on the Location Category Landing Page , not in the hero.

Naming Conventions

Location labeling is based on business type to align with customer expectations.

Use “Locations” (default) for:

Auto repair shops
Salons and spas
Retail stores
Restaurants
Other storefront-style businesses

Use “Offices” (by exception) for:

Law firms
Medical practices
Dentists
Chiropractors

Using industry-appropriate terminology reinforces professionalism, trust, and clarity.

Location Category Landing Page

The Location Category Landing Page provides a centralized overview of all business locations.

Key characteristics:

Page Title (H1): Displays “Locations” or “Offices,” based on business type
Location Cards list each location by city
Each card includes address, phone number, and primary CTA

CTAs:

Request-style CTA (e.g., Schedule Service, Request Appointment) linking to the corresponding Location Profile Page
Location Details CTA linking to the full Location Profile Page
This layout allows users to quickly identify and access the most relevant location.

Location Profile Page Overview

A Location Profile Page provides detailed, location-specific content focused on a single business location. Core sections include:

Introduction

Business name + city
Localized service messaging
Location-relevant imagery

Contact Information

Address, phone, hours, and map
Data populated via connected sources
Request CTA anchored to the form section

Reviews

Populated via the Hibu Reviews widget
Each Location Profile Page displays reviews tied to its specific merchant ID
Additional Locations sites are expected to support multiple merchant IDs when applicable (added 2/12/26)
Reviews are not aggregated across locations (added 2/12/26)

Optional Sections (when content is provided):

Gallery
Menu or price list
Team

About Section

Data-driven content modeled after the main About page

Request / Contact Form

Product-specific form unique to each location
Tied to that individual branch
CTAs throughout the page anchor to this form (added 2/12/26)
A hidden form page supports routing and configuration but is not visible in site navigation (added 2/12/26)

Header Phone Behavior (Overview)

When the Additional Locations add-on is active, header phone behavior adapts based on how phone numbers are configured across locations. This ensures a clear and predictable experience across desktop, tablet, and mobile devices.

Shared Phone Number Across All Locations

When all locations use the same phone number:

Desktop:
The phone number displays as a click-to-call button in the header, following standard desktop header behavior.
Mobile:
The phone number displays as a click-to-call button, following standard mobile header behavior.
Tablet:
A Contact-style button is displayed instead of a phone number.
This button links to the Location Category Landing Page .

The Contact-style button label is selected by the copywriter based on business type and audience expectations (for example, “Find a Location,” “Find an Office,” or “Contact Us”).

Footer Location Display

The footer provides persistent access to location-specific information and must present each location in a consistent, structured format.

Each location displayed in the footer includes:

Location Name (Headline):
Displays the full location name (for example, “Vancouver Location”).
This must match the H1 used on the corresponding Location Profile Page and is entered manually.
Contact Information:
Displays the street address and phone number for the location.
This information is dynamically populated from connected data sources.
All phone numbers are displayed, even when multiple locations share the same number.
Call-to-Action Button:
Labeled either “Location Details” or “Office Details.”
The label is entered manually.
The button links directly to the corresponding Location Profile Page.

Not Included in the Footer

Call or text buttons are not included in this layout
Footer CTAs must not link directly to forms or alternate destinations
The footer always points users to the appropriate Location Profile Page, preserving a clear and consistent navigation path.

Unique Phone Numbers Per Location

When locations use different phone numbers:

Desktop, Tablet, and Mobile:
No phone number is displayed in the header.
A Contact-style button is displayed in the header instead.
The button links to the Location Category Landing Page , allowing users to select the appropriate location.
The button label is selected by the copywriter and should reflect the business vertical and customer intent.

CTA Consistency Requirement

To maintain clarity and professionalism, CTA language must remain consistent across the site.

If the header uses a label such as “Find a Location” or “Find an Office,” that same phrasing should be used in prominent CTAs elsewhere (such as the hero section). Mixed or contradictory CTA language is not permitted, as it creates confusion about destination and intent.

Navigation Behavior

When the Additional Locations add-on is active, primary navigation behavior changes to prioritize location discovery over generic contact access.

Top-Level Navigation Label

The standard “Contact Us” navigation item is replaced with “Locations” or “Offices” , based on business type.
This label must align with the Naming Conventions defined for the site.
“Contact Us” is not used as a top-level navigation item when Additional Locations are present.

This ensures users are directed to location selection first, rather than a generic contact destination.

Navigation Dropdown Behavior

When a dropdown is supported:

Dropdown items list city names only
Each city links to the corresponding Location Profile Page
Location names must be concise and avoid additional descriptors beyond the city name

Example dropdown pattern:

Battle Ground
Camas
Vancouver

This structure allows users to quickly identify and access the most relevant location without overwhelming the navigation.

About Content Behavior

When the Additional Locations add-on is active, a dedicated, standalone About Us page is not used.

Instead, an About folder replaces the About Us page. The folder serves as the primary destination for trust and informational content and functions similarly to the traditional About Us experience.

The About folder may include:

FAQs
Blog
Reviews
Other informational or trust-related content

Location-specific About content sourced from Yext is displayed on each Location Profile Page , ensuring that About messaging reflects the context of the individual location rather than the business as a whole.

Areas Served (GEO Pages) Behavior

When a client has purchased Geo Pages (GEOs) alongside the Additional Locations add-on, the placement and navigation of GEO links changes to align with the multi-location site structure.

Navigation Placement

A dedicated “Areas Served” navigation item appears under the “Locations” or “Offices” menu
“Areas Served” is not placed under a Contact Us navigation item, as a standalone Contact Us page is not used when Additional Locations are active

This ensures GEO content remains discoverable while prioritizing location selection first.

Anchor Destination

The “Areas Served” navigation item anchors to an Areas Served section on the Location Category Landing Page
This section mirrors the standard GEO presentation used elsewhere, but its placement reflects the absence of a Contact Us page

Areas Served Section Behavior

The Areas Served section:

Displays up to 10 GEO Pages
Uses a thin hero-style layout consistent with GEO Page standards
Lists GEO links in a clear, scannable format
Links directly to individual GEO Pages

Renaming Image File Names

Sun, 01 Feb 2026 16:42:34 GMT

Why the Naming Order Changed

Previously, filenames led with the business name. While consistent, this approach caused a usability issue when browsing or searching files in the asset library.

When filenames are truncated in list views, the most important part of the filename—the asset’s purpose—is often hidden.

Renaming Image Files: At-a-Glance

Image File Naming Best Practices

All image and file names must follow these standards:

Use lowercase letters and hyphens
Do not use spaces, underscores, or special characters
Keep filenames concise and descriptive
Do not include legal suffixes (Inc, LLC, Corp, etc.)
Replace ampersands with “and”
Example: jimi-and-stevies-guitar-shop

When multiple images share the same purpose, add a number at the end of the filename. Use leading zeros for consistency (e.g., -01 , -02 ).

Note: If the same image is used in multiple locations (homepage, gallery, video splash, etc.), it does not need to be renamed for each use.

Notes & Clarifications

Filenames are not the same as image labels used within the Content Library or Collections.
Numbers do not need to reflect display order on the page.
The Hibu design team is responsible for renaming all uploaded files and applying appropriate alt text.

Why File Naming Matters

Search engines and internal tools rely on filenames to understand, organize, and retrieve assets. Files with generic or unclear names reduce visibility, slow down asset selection, and create unnecessary friction during builds and updates.

Well-structured filenames support:

Faster asset discovery
Cleaner asset libraries
Better internal organization across pages and file types
Improved accessibility and search relevance when paired with descriptive alt text

image20384.jpg

home-hero-bills-plumbing.jpg

Poor vs. Descriptive File Names

This comparison demonstrates how descriptive filenames immediately communicate what an image is and where it belongs, without requiring the file to be opened.

These images demonstrates how leading with the business name makes it difficult to distinguish between assets when viewing files in a list. By the time the asset’s purpose appears, it may no longer be visible.

Leading with asset context ensures:

Similar assets group together
Purpose is immediately visible
Image files are easier to differentiate at a glance

File List Truncation in Media Manager

 Pro Tip: When viewing files in the Media Manager, long filenames may be truncated in the tile view. Switching to list view displays more of the filename, making it easier to distinguish similar assets.

Renaming Image Files

Hibu Policy

All customer-supplied image and file assets uploaded to Hibu One must be renamed using a standardized, descriptive naming convention that prioritizes asset purpose and context before the business name. This ensures files are easy to scan, sort, and locate within the platform.

At the core, all client-supplied or Hibu-added image and file assets—including PNGs, JPGs, SVGs, GIFs, icons, and favicons—must include asset context, the business name, and a page reference and/or number when applicable.

For additional context, see: Renaming PDFs & Downloadable Files

AI Hero Image Collection

Upon site creation, the hero images are automatically inserted into the Hero Image Collection and placed on the site.

The image can also be replaced in the collection to keep the images organized and coming from the same place for all hero images.

Page-placement-1-nob-ref-002394.jpg = home-hero-joes-pizza-ref-002394.jpg (do not remove the ref #)
Page-placement-nob-cust = manually renamed by Build (all lowercase) i.e. home-hero-joes-pizza-cust.jpg
If Build selects a different image from the resource library the following naming convention is used page-placement-nob

o NOTE: Customer supplied images should always take precedence over resource library images.

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

SAPs vs GEOs Quick Comparison Table

Sun, 01 Feb 2026 16:28:57 GMT

SAPs vs GEOs Quick Comparison Table

This table provides a side-by-side comparison of Service Area Pages and Geo Pages to help teams quickly determine which page type aligns with a client’s business model. It highlights the core differences in eligibility, structure, metadata, navigation, and editorial requirements. For full details on how each page type works, see the complete SAP and GEO guidelines linked above.

Effective Date: February 1, 2026 Last Updated: February 7, 202 6

Writing Requirements & Editorial Exceptions

Service Area Pages (SAPs) and Geo Pages (GEOs) have distinct editorial intents based on how each page type functions within the site structure and search ecosystem. Writing must always reflect how the business actually operates, even when a page is sold or generated in a way that does not perfectly align with the business model.

Service Area Pages (SAPs)

By default, Service Area Pages are written for businesses that travel to serve customers .

SAP copy should:

Emphasize regional coverage across multiple towns or cities
Reinforce a “we come to you” service model
Avoid implying a physical office in individual service towns
Avoid language suggesting customers travel to a fixed location

Editorial Exception: SAPs Sold to Location-Based Businesses

There are cases where Service Area Pages are sold to location-based businesses . This scenario cannot currently be system-controlled .

When this occurs:

The Content Writer must modify the generated SAP copy
SAP content must follow Geo-style writing rules , including:
References to a physical location
Language indicating customers travel to the business
All SAP structural, technical, and layout constraints must still be followed

Geo Pages (GEOs)

Geo Pages are always written for location-based businesses .

GEO copy must:

Clearly establish the existence of a physical location
Communicate that customers travel to the business
Avoid any “we come to you” or regional service-area language

Editorial Priority

In all cases:

Editorial accuracy takes precedence
Content must reflect how the business actually operates
Writers are expected to adjust copy when page type and business model do not align

Background Hero Video

Sun, 01 Feb 2026 16:16:30 GMT

Background Hero Video

Hibu Policy

Background hero videos are allowed only on the homepage and Category Landing Pages (CATs) and are displayed on desktop and tablet devices only . Background videos are not supported on mobile devices.

When a background video is applied, it replaces the hero background image within the hero section on desktop and tablet. The video does not display on mobile.

A static background image must be applied for mobile display. This image is manually assigned and is not automatically maintained once the hero image is replaced by a video.

Background videos must:

Be silent (no audio)
Not interfere with readability or usability
Follow all performance and quality standards outlined below

Background hero videos are only implemented after first proof. If requested, the build team must evaluate compatibility with existing hero elements before applying the video.

Background videos are not supported in hero sections that contain a form (Hero Form) . If a video is applied:

The form must be removed or hidden on desktop and tablet for that section
The form may remain on mobile, where the video is not displayed
Removing or hiding the form at the hero level does not require removal from other areas of the site. Forms may remain on other pages or sections as appropriate.

Effective Date: February 1, 2026 Last Updated: April 3, 202 6

Definition

A background hero video is a client-provided video file or externally hosted video (YouTube, Vimeo, or Dailymotion) applied directly to the hero section in place of a static background image.

When implemented, the video becomes the background for desktop and tablet devices, while mobile relies on a manually assigned static image.

Background Hero Video: At-a-Glance

Call or Text

 (888) 888-1111 

Spring Special - Save $3,000 on a new roof and get your home ready for the season — Call for details .

Home Exterior Services

Asheville, NC Area

Request Free Estimate

Background Video Applied

Hibu One Smart Site Rules

Where Background Videos Are Allowed:

Homepage hero (desktop and tablet only)
Tier 1 and Tier 2 Category Landing Page (CAT) hero (desktop and tablet only)
Not allowed on sub pages, service pages, utility pages, or any other section of the site
Background videos are not allowed in hero sections that contain a form unless the form is removed or hidden on desktop and tablet

Device Behavior

Hero sections are initially connected to the hero image collection, which populates the background image across all devices.

When a background video is added:

The connection to the hero image collection must be manually removed for that section
The video becomes the background on desktop and tablet
The video does not display on mobile

Once the image connection is removed, the hero no longer inherits a background image from the collection. As a result, the section will not have a default image background unless one is explicitly applied.

Mobile devices do not support background video due to performance limitations, including load speed, bandwidth usage, and limited visual impact.

Because of this, a static image must be applied to the hero section for mobile display. This image is assigned at the hero section level and is not pulled from the hero image collection once a video is applied.

If no mobile background image is applied, the hero background will display as a solid black background on mobile.

The mobile background image must be one of the following:

The original hero image (from the hero image collection)
A client-provided image
A still frame captured from the video

A still frame captured from the video may be used when visual consistency between desktop and mobile is desired. The specific frame is not typically provided by the client; selection is based on design judgment.

The selected frame must:

Clearly represent the business or service
Be free of text, overlays, or motion artifacts
Maintain sufficient clarity and quality when displayed full width

The mobile background image must function as a clean, static background and must not compete with foreground content.

When in doubt about image or video suitability, escalate to a manager or contact the Product Lead.

If a hero form is present, background video cannot be applied unless the form is removed or hidden on desktop and tablet.

Important

iPhone users may not see video playback in low power mode
Some Android devices may restrict autoplay behavior
Video playback behavior may vary slightly depending on device and browser

Background Video Requirements

Background videos must meet the following requirements:

Landscape orientation only (portrait/vertical video is not allowed)
Video may be client-provided or sourced from YouTube, Vimeo, or Dailymotion
Subtle motion (no rapid movement, flashing, or heavy action)
Silent (no audio)
File size must be 200MB or less
Maintain clear readability of all hero content, including:
H1
H2
Motivating Factors
CTA buttons

Videos must be high enough resolution to prevent blurring or distortion at full width.

Landscaping and Hardscaping

Denver, Co Area

Request a Free E stimate

Recommended (Subtle, Non-Competing Video)

Not Recommended / Prohibited Background Videos

The following may not be used as background videos:

Videos containing readable text, logos, or promotional messaging
Testimonial, staff, or speaking-based videos
Fast-paced or high-motion sequences
Portrait (vertical) videos are not allowed
Footage that distracts from or competes with foreground content

These types of videos may be used elsewhere on the site under standard video usage guidelines.

Background Videos May Not:

Contain text overlays, logos, or promotional messaging
Include people speaking, staged introductions, or testimonials
Function as advertisements or commercials
Include distracting or high-action motion
Compete visually with foreground content
Such videos may still be used elsewhere. See → Video (Standard Video Usage)

Call Today

 (888) 888-1515 

Landscaping and Hardscaping

Denver, Co Area

Request a Free E stimate

Not Recommended (Portrait / Improper Format Video)

Call Today

 (888) 888-1515 

Landscaping and Hardscaping

Denver, Co Area

Request a Free E stimate

Not Recommended (Busy / High-Distraction Video)

AudioEye Widget

Sun, 01 Feb 2026 16:13:56 GMT

AudioEye Widget

Definition

AudioEye is an accessibility tool included with every Hibu One Smart Site. It helps websites move toward ADA and WCAG 2.2 compliance through automated technology and expert support.

Hibu One Smart Site Rules

The AudioEye widget is automatically included with every new website.
The AudioEye “Blue Man” icon is visible in the bottom-left corner of both desktop and mobile sites.
On mobile, the icon becomes visible only after the site is live.
The icon’s position, size, and color cannot be altered .
AudioEye may be removed at the client’s request. However, it is recommended that the purpose and benefits be explained before removal.
Removal requires a Remedyforce ticket.

Script for Explaining AudioEye Before Removal

" The Americans with Disabilities Act (ADA) requires certain businesses to make accommodations for people with disabilities. The app that we have included on your website helps you to provide an ADA-compliant website to your customers. This will not only help protect you against lawsuits and fines, it will also provide accommodations for your customers with disabilities who may visit your site. "

Why Accessibility Matters

Over 1.3 billion people worldwide (16% of the population) live with a disability. This number is expected to reach 2 billion by 2030 .
Website accessibility lawsuits are increasing, with over 4,000 lawsuits filed in 2022 and 4,280 in 2024 .
Sites that are not accessible risk lost business opportunities and potential legal action.

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

UTM-Tagged URLs

Sun, 01 Feb 2026 16:10:10 GMT

UTM-Tagged URLs

Use of UTM Parameters

The Hibu One Smart Site fully supports URLs that contain UTM parameters . Any UTM-tagged URL supplied by the client will be added exactly as provided. The site does not remove, rewrite, or alter tracking parameters.

Accepted example:

https://foo.com/services/?utm_source=display&utm_medium=cpc&utm_campaign=winter_sale

The client must supply the full, UTM-tagged URL they want used.
URLs will correctly pass through UTM parameters for analytics tools to capture.
UTM parameters may be added to buttons, links, and CTAs as long as the full string is provided.

Relationship to GTM (Optional)

If the client provides Google Tag Manager (GTM) or requests GTM installation (see GTM documentation), Hibu One will:

Install the GTM container code exactly as supplied
Ensure UTM parameters are retained in URLs for GTM to read

Hibu One does not configure, test, or troubleshoot GTM setups.

Client Responsibilities

Creating UTM-tagged URLs
Providing exact URLs and/or GTM container code
Testing and validating all tracking, triggers, conversions, and reporting
Troubleshooting any analytics or attribution issues

Once UTM URLs (and GTM, if applicable) are added, there is no additional configuration Hibu One performs. All tracking behavior is controlled by the client’s analytics setup.

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Sensitive Data Restrictions

Sun, 01 Feb 2026 15:56:55 GMT

Definition

While Hibu One Smart Site forms can be used to collect information from visitors, certain types of data are considered sensitive and must never be requested. This protects website users — our clients’ customers — from hackers and data breaches.

Related: Form Restrictions for Medical Related Businesses and Prohibitive and Restricted Verticals

Policy

Most Personally Identifiable Information (PII) is considered sensitive and must not be collected through Hibu forms.
If a client requires collection of sensitive data, recommend a third-party form platform (e.g., FormSite.com, 123formbuilder.com, Fast Fields, JotForms).
The client is responsible for creating and managing the third-party account.
The client must provide embed code to Hibu for implementation.

Sensitive Data List

The following types of information are considered sensitive and must never be requested through Hibu forms:

Any number or information that can be used to access a person’s financial resources
Biometric identifiers (e.g., fingerprints)
Birthdate
Certificate or license numbers
Checking account numbers
Citizen visa code
Citizenship
Credit card numbers
Credit rating/history
Debit card numbers
Device identification/serial numbers
Driver's license
Employer tax ID
Ethnicity
Federal Tax ID
Financial aid/grant information
Financial worth statements
Health plan number
Health records
Income levels
Medical record number
Non-banking related financial information
Passport numbers
Passwords
Payroll timesheets
Personal identification (PIN) codes
Savings account numbers
Social Security number
State identification card
Student ID number
Vehicle identification (e.g., VIN, serial numbers, license plate numbers)
Veteran and disability status
Wire transfer information
Worker’s compensation or disability claims

Sensitive Data Restrictions

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Form Design Rules of Thumb

Sun, 01 Feb 2026 15:53:59 GMT

Form Design Rules of Thumb

When building custom forms in Hibu One Smart Sites, the following UX (user experience) and design guidelines should be followed to ensure forms are easy to use, accessible, and function correctly.

General Options (Most Field Types)

Required Fields :
If left blank, a red box will appear around the field.
No automatic indicator (e.g., asterisk) is added — builders should manually add “*” or text like “(required)” in the Field Label or Placeholder.
Start New Line :
Use this option to force a field to display on its own line.
Field Size :
Adjust width to improve layout and responsiveness.

Specific Field Considerations

Radio Buttons & Checkboxes :
Images can be added to display as option choices.
Images will not appear in the email submission.
The selected label will still appear in the email (even if hidden on the site).
Time Field :
The “Use 24-hour clock” toggle only affects how submissions display.
The time picker shown to visitors depends on their browser settings.
File Attachment Field :
File name must not include spaces.
File size limit: 10MB.
Only one file per attachment field (add multiple File Attachment Fields if needed).
Supported formats:
Documents: .pdf, .doc, .docx, .xls, .xlsx, .ppt, .pptx, .txt, .xml, .odt, .ott
Images: .png, .jpg, .jpeg, .gif, .svg
Fonts: .ttf, .otf, .woff, .eot
Code: .js, .css
Other: .zip, .rar, .psd, .mp3, plus all video formats
Files are not added to the Media Manager.
Phone Number Field :
Validation checks for proper formatting.
Valid characters: numbers, spaces, +, -, and periods.
At least one number must be present.

reCAPTCHA

Added by default to all forms to protect against spam and speed up the submission process.
The reCAPTCHA icon appears in the bottom-left corner only when a visitor interacts with the form (clicks into a field).
The icon disappears after submission or page refresh.
reCAPTCHA cannot be disabled.

Best Practices for Form Design

To maximize usability and conversion rates, follow these guidelines when building forms:

Keep it short : Fewer fields = more submissions. Only ask for information that’s necessary at the first touch.
Group related fields together : Improves readability and makes forms feel less overwhelming.
Avoid unnecessary long-text fields : Use sparingly; these fields slow users down and reduce completion rates.
Label clearly : Use plain, descriptive field labels (e.g., “Phone Number” instead of “Best contact method”).
Use required fields strategically : Mark only essential fields as required to reduce friction.
Prioritize mobile experience : Review all forms on mobile devices to ensure spacing, field size, and button placement work well.

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Custom Forms

Sun, 01 Feb 2026 15:50:35 GMT

A custom form is any form added to a Hibu One Smart Site that is not a Contact, Request, or Hero form. Custom forms allow businesses to collect specialized information from visitors while following Hibu’s compliance and usability standards.

Rules

Hibu will build up to 10 unique custom forms per site .
Each custom form must serve a unique purpose and contain its own set of fields.
Forms may be duplicated across multiple pages as needed, but no more than 10 distinct forms will be created.
Custom forms may not exceed 25 fields .
Forms with 10 or fewer fields may be placed on any page.
Forms with more than 10 fields must be placed on their own dedicated page, which counts toward the site’s total page count.
Custom forms may include any of the available DUDA platform form fields , except where HIPAA restrictions apply (see below).
Field Validation : Custom forms follow the same validation rules as all Hibu One Smart Forms (see Common to All Forms ).
Tracking & Integrations : Third-party tracking and integrations (e.g., Google Ads, Sheets, Webhooks) may be connected to this form. ( view details )

Restrictions

Sensitive Data Restrictions : No form may request medical, financial, or other sensitive information. ( view list )
Healthcare Businesses : Message/long-text fields and service fields must be excluded. Applies to doctors, dentists, pharmacies, therapists, nursing homes, counselors, and insurance providers handling medical/life/health/dental. ( see list )

Custom Form

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Video

Sun, 01 Feb 2026 15:50:24 GMT

Video

Definition

Video can be incorporated into a Hibu One Smart Site through the Video widget or through embedded third-party links from platforms such as YouTube, Vimeo, or Dailymotion, and (when embeddable) Facebook or Instagram. Videos help demonstrate services, showcase results, and support engagement when used thoughtfully.

This post covers standard videos only. For rules on background videos , see: → Background Videos

Hibu One Smart Site Rules

Accepted Video Sources

Hibu supports the following types of videos:

Client-supplied files uploaded directly to the site
YouTube embeds
Vimeo embeds
Dailymotion embeds
Facebook / Instagram embeds , when a valid public embed link is available

All uploaded video files become accessible in the Media Manager.

Video Usage Rules

Videos may be used throughout the body of a Hibu One Smart Site, including:

Standalone video row below the hero
Introduction section
Why Choose Us section
About Us
Appropriate service/category pages
Hibu Video swap (case-by-case)

Important Notes

All mobile users (android / iphone) may see videos autoplay in low power mode is enabled
Optional thumbnail selection (uploaded videos only)

The video may be set to private or restricted on the hosting platform. Videos must be publicly shareable to display properly.

Background and full-width video elements crop content based on aspect ratio and screen size. This is expected behavior for responsive layouts.

No. The client must provide a final, compliant version.

Fair Use Limits (Standard Videos)

Hibu will upload or embed up to 20 total videos per site , including:

Uploaded client video files
Embedded videos (YouTube, Vimeo, Dailymotion, etc.)
Hero videos
Background videos (count toward the same 20-video total)

File & Format Requirements

Maximum file size: 200MB per uploaded video
Supported formats: all major types except .swf
Hibu will rename all uploaded video files for clarity and consistency
Hibu will not edit, compress, trim, or modify any video ; the client must supply final, web-ready files

Embedded video thumbnails are controlled by the hosting platform. Hibu cannot modify these.

Load times depend on the user’s internet speed. Background videos may load more slowly due to size or motion content.

If the hosting platform restricts the video’s visibility, the embed will fail. Test with a different link to confirm.

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Hero Form

Sun, 01 Feb 2026 15:43:24 GMT

Hibu Policy

Hero Forms are used when the primary or secondary CTA is a request-based form fill.

When used, the form is placed on the homepage, category landing pages, and core service or product pages. Clients may request removal of the form on specific pages where it is not applicable.

Hero Forms use four fields by default. A fifth field is permitted only upon request. Hero Forms must never exceed five total fields.

Hero Form

Effective Date: February 1, 2026 Last Updated: April 21 202 6

Definition

A Hero Form is a short, high-visibility lead form placed within the hero area to support quick conversion.

Purpose

Hero Forms are designed to capture quick leads with minimal friction. Keeping the form short improves completion rates, supports mobile usability, and increases overall lead volume.

Default Setup

Four fields are standard and expected for all Hero Forms:
Full Name
Phone
Email
Services/Products dropdown
The dropdown uses connected data populated through the form collection.
By default, the form title and button label display as “Request CTA.”
Clients may request alternate wording such as “Request Info,” “Schedule Now,” or “Free Estimate.”
The CW team is expected to update both the form title and the button label so they match.

Field Limitations

Hero Forms are limited to four fields by default.
A fifth field may be added only upon request.
The fifth field must be a short field, such as Zip Code, City/State, or “How did you hear about us?”
Hero Forms must never exceed five total fields.
Long-text boxes, message fields, and multiple additional fields are not allowed.
If more detailed information is required, the Hero Form must be replaced with a button CTA linking to a dedicated Request Form page.

Tracking & Integrations

Third-party tracking and integrations (e.g., Google Ads, Sheets, Webhooks) may be connected to this form. ( view details )

Client Requests for Page-Specific Hero Forms

Requests to modify field structure are permitted within the 4–5 field limit (e.g., swap one field for another, or add a fifth short field).
Requests to remove fields are also permitted (e.g., one page may have three fields, another may have two, another may have four).
Field type validation: If replacing specialized fields (e.g., Phone or Email) with a general text field, the Hibu Team must also change the field type to “text.” If not updated, validation errors will occur (e.g., a non-email entry being rejected).
Long-text fields are not permitted in Hero Forms. Only short text fields may be used to maintain conversion performance and mobile usability.

Request Forms

Sun, 01 Feb 2026 15:42:09 GMT

Request Form

A Request Form is a detailed, multi-field form placed on a dedicated page to support the site’s primary call to action (e.g., Request a Free Estimate, Request a Quote, Request an Inspection, Request a Callback).
Request Forms do not count toward the total page count.
The type of Request Form should align with the client’s call to action (CTA).
The DSC is responsible for determining the correct form to match the CTA and relaying that to the Build Team.
By default, the form title and button label display as “Request Information.”
Clients may request alternate wording such as “Request a Quote,” “Schedule Appointment,” or “Get a Free Estimate.”
It is expected that the Hibu Build Team updates both the form title and the button label so they match.
The URL slug must also be updated to match the CTA (e.g., /request-quote, /request-appointment).
By default, Request Forms include:
Full Name
Email
Phone
Preferred contact method
Product/Service selection
Message/long-text field (unless restricted by HIPAA).
May include additional fields upon request (such as dropdowns or checkboxes), as long as they adhere to the rules and guidelines outlined below.
Sensitive Data Restrictions : No form may request medical, financial, or other sensitive information. ( view details )
Healthcare Businesses : Message/long-text fields and service fields must be excluded. Applies to doctors, dentists, pharmacies, therapists, nursing homes, counselors, and insurance providers handling medical/life/health/dental. ( view details )
Tracking & Integrations : Third-party tracking and integrations (e.g., Google Ads, Sheets, Webhooks) may be connected to this form. ( view details )

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Image Size Guidelines

Sun, 01 Feb 2026 15:10:23 GMT

Hibu Policy (added 04/10/26)

Hibu provides image size recommendations as guidance only. These values represent ideal ranges for clarity, performance, and consistency, but they are not strict requirements.

Images do not need to be resized to match the recommended dimensions listed in this guideline. Client-provided images may be used outside of these ranges as long as they meet minimum quality, orientation, and file type requirements.

Images that fall below minimum thresholds (such as hero images under 1200 × 534 px) may not be usable due to quality limitations. Images that significantly exceed recommended maximum sizes may impact performance and should be evaluated before use.

Image Size Guidelines

File Types (updated 04/02/26)

Supported formats include JPG (JPEG), PNG, and WebP
JPG is preferred for photographic images
PNG should be used when transparency is required
The following formats are not permitted for primary or large image use (e.g., hero, background, or full-width sections) :
GIF (inefficient for large visuals and negatively impacts performance)
BMP (uncompressed and inefficient for web use)
Limited use of GIFs is permitted under the following conditions:
GIFs must be small, supporting elements only (e.g., badges, coupons, or small promotional graphics)
GIFs must not be used as hero images, background images, or any image that spans a large portion of the page

Recommended Image Sizes (intro added 04/10/26)

These recommendations define ideal image sizes for common use cases across the site. They are intended to guide selection and ensure consistent visual quality, but they do not restrict the use of images that fall outside these ranges.

Images should be evaluated based on clarity, composition, orientation, and performance rather than strict adherence to specific dimensions.

Hero / Background Images (updated 3/31/26)

Minimum size: 1200 × 534 px (absolute minimum)
Images below this size are not permitted, as they will be scaled up and appear blurry on desktop
Images below the minimum size may not be used due to visible quality degradation (updated 4/10/26)
Recommended size: 1920 × 1280 px or larger
This range provides consistent clarity, supports flexible cropping, and ensures strong visual quality across devices
Preferred maximum width: ~2400 px
Images up to approximately 2400px wide provide optimal clarity on high-resolution displays without unnecessary file size
Images above 2400px may be compressed or resized by the platform, which can reduce image quality and negatively impact load performance
I mages above the preferred maximum do not need to be resized, but should be reviewed for performance impact (added4/10/26)
Best for large, full-width banners at the top of a page
Use wide (horizontal) images only

Copy Blocks (Section Backgrounds & Supporting Images)

Images should generally fall within the 1200–1600 px width range
Use landscape (horizontal) images where possible
Images must support content readability and not compete with text
Avoid overly detailed or high-contrast backgrounds behind copy

Photo Galleries

Images should generally fall within the 1200–1600 px width range
Maintain a consistent aspect ratio within each gallery
Best practice: use 3:2 or 4:3 landscape orientation
Maintain consistent quality and composition across all images

Logo Images

Logos should be clear, high-quality, and properly scaled for their placement
Large, high-resolution logo files are acceptable and may be used
Logos will be resized as needed for display, so larger source files do not negatively impact the site when properly optimized
Recommended display range: ~250–600 px wide , depending on header layout
Logos must remain sharp and legible across desktop, tablet, and mobile
Use PNG or SVG when transparency is required
JPG may be used when transparency is not needed
Avoid low-resolution, pixelated, or distorted logo files
Do not stretch or scale logos beyond their original proportions

For full requirements, usage rules, and header-specific behavior, refer to Header Logo Guidelines

Image Quality

There is no DPI requirement for websites
What matters is pixel size , not DPI
Images should be large enough for where they appear on the page
Small images stretched large will look blurry
Image sizing guidance is secondary to overall quality; images should not be resized solely to meet recommended dimensions if they already display clearly and appropriately (added 04/10/26)

Best practice: Provide images that are at least 2× the expected display size .

Effective Date: February 1, 2026 Last Updated: April 10, 202 6

Image Size: At-a-Glance (updated 04/02/26)

These values represent recommended ranges, not enforced limits. Images may be used outside of these dimensions when they are high quality, properly oriented, and appropriate for the layout.

Do not resize images solely to meet these values.

Geo Pages (GEOs)

Sun, 01 Feb 2026 15:05:26 GMT

Geo Pages (GEOs)

Hibu Policy

Geo Pages (GEOs) are intended for businesses that operate from one or more physical locations. GEOs target nearby towns or cities whose residents may reasonably travel to the business’s location.

GEOs may be used only when the client has not purchased Service Area Pages (SAPs) and do not require Local Ranking. GEOs must follow the eligibility, content, structural, SEO, and editorial standards defined in this guideline.

Product Fit & Writer Responsibility

While GEOs are designed for location-based businesses and SAPs are designed for service-area businesses, SAPs may be sold to businesses that operate from a physical location. When this occurs, writers are expected to acknowledge the business’s physical location and adjust SAP copy accordingly, while still following SAP structural and SEO requirements.

This guideline defines when GEOs are appropriate and how they must be written. When SAPs are purchased instead, GEOs are not used, and the SAP content must be modified to accurately reflect the business’s location-based model.

Related: Service Area Pages and SAPs vs. Geos Comparison Table

Defintion

A Geo Page is a location-targeted page for brick-and-mortar businesses that serve customers from a fixed address. Each GEO Page focuses on a specific surrounding town and is written to highlight the business’s actual location while showing the extended area it serves. GEOs are individually written and edited, and each includes accurate geographic references without implying that the business is located in the target town.

Eligibility & Requirements

Up to 10 Geo Pages per business
Must have Hibu One (Local Ranking is not required)
Cannot be sold when SAPs are active or being purchased

Purpose / Why It Matters

Geo Pages improve visibility for businesses whose customers travel to them. A clear geographic strategy ensures:

Increased visibility for city-and-service searches in nearby towns
Stronger transparency aligned with Google’s EEAT framework
Accurate representation of the business’s true physical location
Improved trust and user experience for consumers evaluating travel distance

Structure & Generation

Each Geo Page must:

Include a unique geographic reference in body copy
Clearly state where the business is actually located
Clarify that the business serves the target town (not that it is located there)
Include location-specific SEO across:
Title tag
Meta description
H1
Body copy
Breadcrumbs do not display on GEOs.
Related Services links do not display on GEOs

Meta Description Tags

Meta descriptions for GEOs are written manually and should:

Follow the standard homepage meta style
Include Geo Town when relevant
Stay under 160 characters
Avoid implying physical location in the target town

A. Single-Location Brick-and-Mortar

Option 1
“Primary CTA [NOB] for your [keyword phrase] and related services throughout the [Regional Area Name].”
Option 2
“Visit [NOB] or call today for [keyword phrase] and more throughout the [Regional Area Name].”
Option 3
“Schedule your [form type] or call our team for [keyword phrase] across the [Regional Area Name].”

B. Multi-Location Brick-and-Mortar

Option 1
“Primary CTA [NOB] for your [keyword phrase] across all our [Location Count] locations throughout the [Regional Area Name].”
Option 2
“Visit [NOB] or call tday for [keyword phrase] supported by our locations throughout the [Regional Area Name].”
Option 3
“Schedule your [form type] or call our team for [keyword phrase] at any of our locations throughout the [Regional Area Name].”

Title and Meta Description Formatting (GEOs)

Title Tag Requirements (GEOs)

Format: GEO Keyword | City, ST | NOB
Example: Teeth Whitening | Drexel Hill, PA | Kim's Dental

If the title tag is too long:

Remove punctuation and vertical pipes
Remove NOB
Priority remains on GEO keyword + City, ST

GEO Page URL Structure

All Geo Pages must use the standardized GEO slug format.

The URL always begins with /location/ and follows this structure:

contact/[geo-keyword-term]-[city-st]

Approved examples:

/contact/teeth-whitening-bear-de
/contact/teeth-whitening-glasgow-de
/contact/teeth-whitening-newark-de

Navigation & Linking

GEO Pages must be accessible through site navigation and presented in a consistent, structured format. The placement of GEO links depends on whether the site uses the Additional Locations add-on.

Anchored GEO Section Requirements (All Sites)

Regardless of placement, the anchored GEO section must include:

A thin hero with the headline: “Additional Areas Served”
GEO links formatted using one of the following patterns, based on keyword context:
Standard format: “[Keyword Term] in [City, ST]”
Location-implied keyword exception: “[Keyword Term] Serving [City, ST]”
GEO links displayed in columns of five whenever possible

When the number of GEOs does not divide evenly, the Build Team is responsible for balancing the columns (for example, 7 GEOs displayed as 4 and 3).

Location-Implied Keyword Rule

If the selected keyword inherently implies a physical location (for example, “Chocolate Store” or “Dentist Office”), the “Serving [City, ST]” format must be used to avoid misleading users about the business’s physical address.

This rule applies to all GEO Pages, regardless of navigation placement.

Sites Without Additional Locations

When a site does not use the Additional Locations add-on:

GEO links are accessed through the Contact Us navigation item
A dedicated “Areas Served” sub-navigation item appears beneath Contact Us
The “Areas Served” link anchors to the GEO section located on the Contact Us page

In this scenario:

The Contact Us page serves as the primary destination for both contact information and GEO discovery
GEO Pages supplement the site without introducing location-based navigation

This is the standard GEO configuration for single-location sites.

Sites With Additional Locations

When a site uses the Additional Locations add-on:

GEO links are not placed under Contact Us
A dedicated “Areas Served” navigation item appears under the “Locations” or “Offices” menu
The “Areas Served” link anchors to the GEO section on the Location Category Landing Page

In this scenario:

A standalone Contact Us page is not used
Users are directed to select a location context first
GEO Pages remain accessible without conflicting with multi-location navigation patterns

The anchored GEO section on the Location Category Landing Page:

Mirrors the standard GEO presentation defined above
Displays up to 10 GEO Pages
Links directly to individual GEO Pages

GEO Hero Form Requirements

If a Geo Page includes a form placed in the hero section, the form title must clearly identify the lead as originating from a GEO Page. To ensure accurate tracking in the client’s dashboard, the standard “Hero Request Form” title must be updated to:

“GEO Hero Request Form”

The hero form must be temporarily unhidden , the word GEO added to the beginning of the form title, and then the form must be re-hidden .

A grayed-out form title confirms it is correctly hidden.

The CW is responsible for updating this form title.

This ensures:

GEO leads are identifiable in the client dashboard
Reporting separates GEO form fills from other page types
Accurate attribution for area-based lead generation

Writing Guidance

Geo Pages must:

Clearly identify the actual location(s)
Clarify that the business serves the target town, not that it is located there
Reinforce physical location accuracy to avoid misleading users and violating EEAT best practices

Encouraged phrasing

“While our office is located in New Rockbridge, we proudly serve clients in Concord.”
“With locations in Cranston, Warwick, and East Greenwich, we’ve been serving the Landsdowne area for over 25 years.”
“Our Portsmouth office supports customers in Londonderry and the surrounding region.”

Avoid

“Located in [Geo Town]” if untrue
Any language that suggests a nonexistent physical office
Copy-pasting content between GEOs

Duplicate Content Controls

Each GEO Page is individually edited to avoid duplication through:
Unique geographic references in body copy
“Located in HQ City, serving Geo Town” phrasing
Manual review and editorial edits
Page-specific SEO tags
No copy/paste content reuse across GEOs

Effective Date: February 1, 2026 Last Updated: February 7, 202 6

Geo Pages (GEOs): At-a-Glance

Contact Us Forms

Sun, 01 Feb 2026 14:51:54 GMT

One (1) contact form is included by default on the Contact Us page or non-Multi Location pages.
By default, the template displays the form title and button label as “Send Us a Message.”
Clients may request alternate wording such as “Contact Us,” “Request Information,” or “Get in Touch.”
It is expected that the Hibu Build Team updates both the form title and the button label so they match.
May include additional fields upon request (dropdowns, checkboxes, etc.), except where HIPAA restrictions apply ( see details) .
Sensitive Data Restrictions : No form may request medical, financial, or other sensitive information. ( view list )
Healthcare Businesses :
Message/long-text fields must be excluded.
Applies to doctors, dentists, pharmacies, therapists, nursing homes, counselors, and insurance providers handling medical/life/health/dental. ( see details) .
Tracking & Integrations : Third-party tracking and integrations (e.g., Google Ads, Sheets, Webhooks) may be connected to this form. ( view details )

Contact Us Form

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Balancing Copy Blocks with Icons

Sun, 01 Feb 2026 14:49:34 GMT

What Is It?

Copy blocks with icons are small content features that pair an icon with a short piece of text — usually a title, a brief description, and sometimes a “Learn More” button.

There are two layout types commonly used across Hibu websites:

Three-column layout: Each block is stacked vertically, with an icon above the copy.
Two-column layout: Each block pairs an icon on the left with text on the right, side by side.

Both layouts present key information clearly and visually, helping users scan the page quickly.

Hibu Policy

All icon-based copy block sections must appear balanced and visually consistent. When the total number of copy blocks doesn’t divide evenly by three, designers and copywriters should adjust the layout so the final row still looks intentional and complete. Never leave an unbalanced row that breaks the visual rhythm of the section.

Balancing Copy Blocks with Icons

Why We Do It

A balanced layout creates a stronger first impression and supports how users naturally read and navigate a page.

When a section ends with an incomplete row — for example, one or two copy blocks sitting off to one side — it can look uneven and distract from the message. Adjusting the layout or using an image to fill space keeps the design looking polished, intentional, and professional.

This approach ensures that every website section maintains the same visual rhythm, no matter how many copy blocks it contains.

How To Use the Visual Guide

Review the examples below to find the layout type and number of copy blocks that matches your page. Each example shows how to rebalance the section when the last row isn’t full — by centering, stretching, or adding an image where needed.

Use these graphics as your reference when deciding how to arrange or adjust copy blocks with icons.

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Common to ALL Hibu One Smart Forms

Sun, 01 Feb 2026 14:48:58 GMT

All forms on Hibu websites share the following core elements:

Form Submission Notifications : Configured in the Performance Dashboard. Any number of contacts may receive notifications via email, text, and web push.
Email Subject Line : Submitted emails display as “New Form Fill Submission.”
Error Message : By default reads “Oops, there was an error sending your message. Please try again.”
Confirmation Message : By default reads “Thank you for contacting us. We will get back to you as soon as possible.” (editable on request).
Thank You Page : Forms may redirect to a thank-you page on request.
A free thank-you page may be added when requested or when determined necessary by an Elite Analyst.
This page is already included as a hidden page with indexing turned off .
Title tag should be updated to: “Thank You | NOB.”
A meta description is not required.
reCAPTCHA :
Added by default to all forms to protect against spam and speed up the submission process.
The reCAPTCHA icon appears in the bottom-left corner only when a visitor interacts with the form (clicks into a field).
The icon disappears after submission or page refresh.
Position and display (icon or text) can be adjusted in form settings.
reCAPTCHA cannot be disabled.
Tracking & Integrations
Third-party tracking and integrations (e.g., Google Ads, Sheets, Webhooks) may be connected to this form. ( view details )
Hibu will not set up accounts, generate, or retrieve third-party code.
Sensitive Data Restrictions : No form may request medical, financial, or other sensitive information. ( view list )
Field Type Alignment & Validation
All template and section forms include built-in validation for standard field types (e.g., phone, email, zip, date, time).
When adding a custom form, Hibu team members are expected to select the correct field type so the validation applies properly. For example:
Phone → Phone field
Email → Email field
Zip/Number → Number field
Date/Time → Date or Time field
Message/Question → Long text field

Common to All Hibu One Smart Forms

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Location, Hybrid, and Service-Based Businesses

Sun, 01 Feb 2026 14:47:46 GMT

Location, Hybrid, and Service-Based Businesses

Hibu works with a wide range of business types, each of which serves customers differently. Some businesses rely on customers visiting a physical location, others travel to the customer, and many operate with a combination of both models. Because of these differences, how location, service area, and geographic information are presented across a website must be handled intentionally.

This guide outlines the three primary business models Hibu supports— location-based , hybrid , and service-based —and explains how each should approach geographic details across key site elements, including the header, footer, Contact Us page, title tags, and meta descriptions. Choosing the correct model ensures consistency, accurate expectations for users, and proper alignment with SEO and listing requirements.

Location Businesses

A location business is one that customers physically visit. You go to them.

Examples of location-based businesses include, but are not limited to (per questionnaire):

Restaurants (dine-in, carryout, curbside, bar, club)
Retail stores (gifts, carpet, shoes, clothing, jewelry, furniture)
Personal services (hair and nail salon, barber, spa)
Fitness and exercise (gym, yoga studio, martial arts)
Religious institutions (church, synagogue, mosque)
Medical practices ( doctor, dentist, urgent care, chiropractor, physical therapist, psychologist, psychiatrist)
Professional services (lawyer, accountant, insurance, realtor)
Auto services (body shop, auto repair, car wash, car dealer)
Pet care (vet, pet store, pet groomer, pet boarding/kennels)

Geo Usage in Header / Footer / Contact Us

Header: Use Yext to display City, ST
Footer: Use Yext to display the physical address (with Get Directions)
Contact Us: Use Yext to display the physical address (with Get Directions)

Unless the client specifies otherwise, location-based businesses that offer virtual services (such as Zoom or telehealth) should still be approached with their physical location as the primary means of contact (e.g., Visit Us if defined as the primary CTA).

Use the City, ST exactly as entered into Yext for the location title tag.

Hybrid Businesses

A hybrid business is one that does both: it has a physical location and offers services where customers may not always visit the location. You go to them, but they may come to you, too.

Examples of hybrid businesses include, but are not limited to (per questionnaire):

Businesses with showrooms (carpet, tile, cabinets, kitchen/bath)
Dine-in restaurants that also deliver

Unless the client specifies otherwise, hybrid businesses that deliver, install, or offer in-home estimates should still be approached with their physical location as the primary means of contact .

Note: If a service area is indicated on the questionnaire, add the service area to body copy where applicable.

Geo Usage in Header / Footer / Contact Us

Header: Use Yext to display City, ST
Footer: Use Yext to display the physical address (with Get Directions)
Contact Us: Use Yext to display the physical address (with Get Directions)
Add service or delivery area to body copy where applicable

Geo in Header / Footer / Contact Us

Header - Use Yext widget with city, state
Footer - Use Yext widget with service area
Contact Us - Use Yext widget with service area

Geo in Header / Footer / Contact Us

Header - Use text box to add local service area
Footer - Use Yext widget with service area
Contact Us - Use Yext widget with service area

Service Businesses

A service-based business travels to the customer’s home or office within a defined geographic area. They go to you.

Examples include, but are not limited to (per questionnaire):

Contractors (roofers, asphalt, landscapers, electricians, exterminators, painters)
Towing services
Mobile services (mobile car wash, mobile physical therapist, pet groomer)
Maid or janitorial services
Food trucks
Catering services
Entertainment services (party clowns, magicians, bounce houses, party rentals)

Quick Decision Guide: Choosing the Correct Business Type

How to Apply This Guide

If customers visit the business: Treat it as a Location-Based or Hybrid business
If the business travels to the customer: Treat it as Service-Based , unless a showroom or storefront exists
When in doubt: Default to the primary customer interaction (where the customer expects to go or be served)

Correct classification ensures:

Consistent geo usage across the site
Proper header, footer, and Contact Us configuration
Accurate title tag and meta description formatting
Alignment with Google listing and service area requirements

Three or More Physical Locations

Do not display multiple locations in the header.

When a business has three or more physical locations:

Header GEO should not list cities
Use a generalized regional reference only if supported by Yext
Otherwise, header may omit GEO entirely

Related Definitions

For additional context, see:

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Introduction to Hibu One Smart Forms

Sun, 01 Feb 2026 14:46:40 GMT

Hibu One Smart Forms are designed to collect leads, inquiries, and requests efficiently while maintaining consistency, usability, and compliance across all websites. Every form, whether it’s a standard Contact , Request , Hero , or Custom form follows shared setup standards and validation rules to ensure smooth performance and accurate submissions.

This section outlines the foundational elements that apply to all Hibu One Smart Forms — including how submissions are handled, how form fields are validated, and the policies that govern tracking, integrations, and data sensitivity.

Before reviewing individual form types, it’s important to understand:

The four standard form types — Contact , Request , Hero , and Custom — each serve a distinct purpose and follow specific setup rules.
Rules of thumb for form design and layout — covering field size, required indicators, and placement for optimal user experience.
Sensitive data restrictions , which define what information can and cannot be collected through Hibu-managed forms.

Together, these guidelines create a consistent, secure, and conversion-focused experience for users and clients across all Hibu One Smart Websites.

Introduction to Hibu One Smart Forms

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Call or Text Button

Sun, 01 Feb 2026 14:40:51 GMT

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)

call or Text Button (Textable RCF)

Hibu One Smart Site Rules

The Call or Text CTA appears only in two locations on a Hibu One Smart Site:
The desktop header , displayed as a CTA lead-in before the main phone number
The mobile header button , displayed as “Call or Text”
The Call or Text CTA must not appear anywhere else on the site, including:
Body content
Callouts
Coupons
Footer CTAs
Any secondary elements
When a visitor clicks Call or Text, a pop-up appears offering:
Call Us — triggers the device’s native calling application to dial or cancel
Text Us — opens the device’s native SMS/text application so the user can start a message
The Call or Text feature must always use the primary business phone number listed in Business Information (typically connected through Yext).
No alternative numbers, personal numbers, or off-platform numbers may be used.
If multiple numbers exist, the Call or Text pop-up must use the business’s designated primary line .
The text within the Call or Text header CTA is standardized as “Call or Text.”
This wording is not changed per client preference.
This CTA must remain short, clear, and immediately recognizable as a dual-path contact option.

Client Expectations

Texting availability: Because Hibu One call tracking lines are textable by default, clients do not need to take any action to enable SMS capability.
Usage boundaries: The Call or Text feature is intentionally limited to header areas to avoid duplicative CTAs and maintain a clean conversion path.
Consistency: This is a standard Hibu One feature; removing or altering it is not recommended unless a compliance issue requires it.
Message content: Text conversations occur directly between the customer and the business. Hibu does not capture, store, or monitor the messaging thread.

Effective Date: February 1, 2026 Last Updated: February 9, 202 6

Assistant RCF

The Assistant RCF is not part of the text/call feature.
The goal is to capture contacts visiting the clients Hibu Website via texting START or calling the Assistant RCF.
Sending a normal text to the Assistant RCF does not allow us to send that contact marketing information.
The Assistant RCF appears throughout the site ONLY if a Listing RCF is not provisioned.
It is permissible for the Assistant Banner to appear on a site even if there is a listings RCF in the header etc.
Since the Assistant RCF is not part of the texting feature, it would not be used in the engagement menu if the Listing RCF is not provisioned.

Privacy Policy Replacement Policy

Sun, 01 Feb 2026 14:31:08 GMT

Definition

Hibu One Smart Sites include a default, system-managed privacy policy and footer provided by Hibu. When a client works with third-party tools that collect user data (such as forms, SMS opt-ins, chat tools, or call tracking), the client may request to replace the Hibu privacy policy with their own.

Hibu does not modify its privacy policy content. Instead, the Hibu policy may be replaced with client-supplied policy content following a defined process.

Privacy Policy Replacement Policy

Client Request And Intake Process

Initial Client Request

When a client asks to update or modify the privacy policy:

Explain that Hibu’s privacy policy cannot be edited for legal reasons
Confirm that Hibu can replace the Hibu policy with a client-owned policy
Request the client’s policy in Word or PDF format only

No third-party tools should be implemented until the client’s policy is provided and live.

Assisting Clients Without A Privacy Policy

If the client does not already have a privacy policy:

Direct them to a free privacy policy generator
Recommended resource:
https://www.freeprivacypolicy.com/free-privacy-policy-generator/
Clarify that these tools are external and client-managed
Hibu does not author or validate legal policy content

Privacy Policy Page Creation Standards

Once the client’s policy is received:

Page Setup Requirements

Create a new standalone page using the thin hero layout
Page must:
Be hidden from navigation
Have No Index enabled
Title Tag: Privacy Policy | [Name of Business]
Meta Description: Protect your personal information with [NOB]’s privacy policy. Learn how we collect, use, and safeguard your data.

Footer Replacement Process (Escalations Required)

Hibu Smart Sites display a system-managed footer that includes links to Hibu-owned policies and “Powered by Hibu.”

To replace this footer content:

Submit an Escalations request to update the Copyright Widget
The Escalations designer will:
Replace “Company Name” with Privacy Policy
Link to the new client privacy policy page
Center-align the text
Set font size to 9pt

Hibu copywriters and designers must not manually edit footer policy content.

Policy Content Rules

All policy content must be supplied by the client

Hibu does not write, edit, or generate:

Privacy policies
Terms & conditions
ADA or compliance language

Policy pages may be:

Separate pages per policy, or
Combined on a single page (client preference)

Any client policy page does not count toward the site’s purchased page total

Designer / QA Checklist

Before closing the request, confirm:

Privacy policy page exists and is correctly formatted
Title tag and meta description are present
No Index is enabled
Footer link points to the correct page
Footer text is centered and legible across devices
No legacy Hibu policy text remains visible

Key Clarification

The Hibu-powered footer is dynamically managed and updated by Hibu. Any replacement of policy links or “Powered by Hibu” text must go through Escalations and cannot be handled directly within the editor.

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Service Internal Page Layout

Sun, 01 Feb 2026 14:18:36 GMT

Service Internal Page Layout

Below is breakdown of what sections of text are included in the Service Internal Page Layout.

Below that, is an example of an internal page using this layout.

Knowing what sections are included in each layout type will allow you to:

Choose the correct internal layout for each website
Anticipate what sections may need additional editing

It's not just about fixing a problem; it's about choosing a pool service that offers lasting solutions. Here's how Pool Tech stands out from the crowd:

We possess over 70 years of combined experience in pool repairs
Our non-invasive methods and advanced equipment enable us to detect even the smallest leaks
We are a locally owned business - we understand the unique needs of Mesquite residents
We offer competitive pricing without compromising on quality

Don't let a leaking pool ruin your day. Contact Pool Tech now and let our experts take care of your pool repair needs.

When you choose Pool Tech, you're not just picking a pool repair service. You're choosing a partner who will be there when your pool needs it most. We're proud to offer a range of special features that set us apart:

We provide an estimate over the phone, saving you time and hassle
Our business was founded in 1982, and we've weathered all sorts of pool repair challenges
We offer manufacturer warranties, giving you peace of mind with your repair
Our workmanship comes with a 1-year warranty – a testament to our confidence in our service quality

Don't let your pool problems get any worse. Call Pool Tech now and feel the difference of dealing with the true professionals.

Recent Reviews

Your Reliable Partner for Pool Repairs is Here

Why Choose Us

Ready to get your pool back in pristine condition? Get in touch with Pool Tech today. Our team in Mesquite, TX, is waiting to provide prompt, expert service. Simply give us a call, or if you prefer, fill out our contact form , and we'll be in touch as soon as possible. Your pool is in safe hands with Pool Tech.

Link #1
Link #2
Link #3

When it comes to pool repairs, time is of the essence, and Pool Tech is ready to get started! Located conveniently in Mesquite, Texas, our team of Residential Appliance Installers - certified by the State of Texas - is prepared to tackle your pool issues head-on. So why wait? Give us a call right now and let us get your pool back to its best.

Contact Us

Why Choose Pool Tech for Your Pool Repairs?

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Theme Colors & Theme Text

Sun, 01 Feb 2026 14:13:58 GMT

Definition

The Site Theme panel allows designers to configure global colors, text styles, buttons, backgrounds, and image behavior. These theme-level settings establish how content appears throughout the site and ensure predictable styling across Desktop, Tablet, and Mobile.

Theme settings are accessed in Editor 2.0 → Side Panel → Theme , where the canvas automatically scales to help designers view full-page changes.

Theme Colors & Theme Text (Global Styling Rules)

Overview

Theme Colors and Theme Text define the global visual system for every Hibu One Smart Site. These settings determine the site’s color palette, typography hierarchy, and baseline styling behavior across all widgets and layout containers. Adjusting theme settings updates the entire site at once, ensuring consistency, reducing design time, and supporting long-term maintainability.

Purpose / Why It Matters

Theme-driven design ensures Hibu One Smart Sites remain consistent and efficient to update. Using the theme:

Keeps colors and typography uniform
Allows site-wide changes through a single update
Reduces manual styling work and long-term maintenance
Prevents inconsistent overrides that lead to rework
Supports accessibility and responsive layout
Ensures system widgets inherit correct styling
Maintains predictable behavior across breakpoints

When colors or text styles are overridden manually on individual widgets, later changes become time-consuming, error-prone, and require element-by-element cleanup.

Theme Colors

What Theme Colors Are

Theme Colors define the global color palette for the site. Designers can configure up to 20 colors , apply them to widgets, and update all connected elements instantly through the theme. Theme Colors appear in Theme → Colors .

How Theme Colors Work

Any widget linked to a theme color updates automatically when the theme color changes.
Designers can create colors manually, enter HEX/RGB values, or generate a palette from the client’s logo.
Colors can be renamed or replaced without breaking their connection.

Theme Color Assignments

Black (B) — Global black / Do Not Change
White (W) — Global white / Do Not Change
Primary Brand (P)
Secondary Brand (S)
Accent Brand (A)
Header Background (W)
Header Text (B)
Footer Background (S)
Footer Text (W)
Navigation Background (P)
Navigation Text (W)
Thin Hero / Recent Reviews Background (S)
Engagement Menu (S)
Review Stars (yellow)
Why Choose Background (S)
Why Choose Text (B)
Why Choose Icon (B)
Button Primary (P)
Button Secondary (S)
Open Slot — Available for template-specific needs

Additional Notes

Theme-driven changes cascade globally; manual overrides do not.
Designers should finalize theme settings early to avoid rework.
Content inheritance and responsive behavior improve when text remains connected to theme styles.
Theme-based color use supports accessibility and brand consistency across all Smart Sites.

Default Text vs. Paragraph Text

Editor 2.0 distinguishes between two key baseline text types:

Default Text (DFLT)

Applies to text not assigned a heading or paragraph style.
Used by system widgets (e.g., navigation text).
Includes link colors and link interaction states.
Serves as the typography “fallback” for unstyled text.

Paragraph Text (PAR)

The intended styling for content inside the Text Widget.
Should be used for all body copy, descriptions, and readable content.
Provides consistent spacing, readability, and hierarchy.

Why the Difference Matters

Using Paragraph Text for body content ensures consistency and readability, while Default Text maintains styling for system text and general-purpose elements.

Theme Color Legend

Theme Colors are connected to specific components throughout the Smart Site templates. The values below represent the standard Hibu One mapping, showing which color controls which part of the site. The abbreviations indicate the thematic role of each color:

(P) – Primary Brand
(S) – Secondary Brand
(A) – Accent Brand
(W) – White
(B) – Black

Theme Text

What Theme Text Is

Theme Text controls typography across the entire site. This includes:

Default Text (DFLT)
Paragraph Text (PAR)
Headings H1–H6
Link appearance (default, hover, clicked)
Font families, sizing, weights, spacing, alignment
Mobile/desktop text sizing
Optional Scale Text behavior (Editor 2.0)

Theme Text appears in Theme → Text .

Text Behavior and Overrides

How Theme Text Applies

Theme Text updates all elements connected to the theme.
Changes affect both existing content (unless individually overridden) and future widgets.
Heading sizes can adjust globally; heading colors will only update globally if not overridden.

Override Limitations

Manual text overrides—such as recoloring an individual heading widget—break the connection to the theme. This means:

Future theme changes will not update that element.
Restoration requires manually editing each overridden widget.
Overrides should remain rare and intentional.

Guidelines for Using Theme Colors & Text

Use Theme Settings Whenever Possible

Theme Colors and Theme Text should be the foundation for all:

Headings
Paragraph text
Buttons
Icons paired with text
Backgrounds and accents
System widgets

Avoid Manual Widget-Level Overrides

Manual overrides should only be used when a specific design pattern truly requires it. Excessive overrides:

Disrupt global styling
Increase maintenance time
Introduce inconsistencies
Create errors when updates are requested

Document Any Required Overrides

If a designer must override a theme style—color, font, size, or text treatment—they must leave a brief note or assumption explaining why the deviation was necessary.
This supports Amends, QA, and future design continuity.

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Title / Meta - SAP and GEO Pages

Sun, 01 Feb 2026 13:58:19 GMT

Title / Meta - SAP and GEO Pages

Hibu Policy

Every Service Area Page (SAP) and GEO Page on a Hibu One Smart Site must include:

One unique title tag built to the approved formula for that page type
One unique meta description written in the homepage meta description style

Definition

Title tags and meta descriptions are HTML elements that control how a page appears in search engine results pages (SERPs) and when shared on social platforms.

The title tag acts as the headline.
The meta description acts as supporting copy.

Together, they function as a mini advertisement for the page — the pre-click version of the on-page experience. If the user does not click, the rest of the page experience does not occur.

Service Area Pages (SAPs) are dynamically generated pages that target specific cities or towns within a business's service territory. Title tags for SAPs are generated automatically through the PSAP's Collection connection and must be managed at the formula level, not edited individually.

GEO Pages are manually built pages that target a specific city, state, or geographic location. Unlike SAPs, GEO page title tags and meta descriptions are written directly.

Rules & Guidelines

Note:

The SAP keyword in the title tag and meta description should not be changed or adjusted beyond making it plural or adding a hyphen if needed. This keyword is based on what was purchased for local ranking and should remain unchanged. added 4/1/2026
E.g.: "Remodel Contractor" cannot be changed to "Remodeling Contractor"
However, "Remodel Contractor" COULD be changed to "Remodel Contractors"

SAP Directory Page (Serving Area Page)

Title Tag Formula (Multi-Location Businesses):

[Service] Near You in [Region] | [Key Services] + [Optional Modifier]

[Business Type] Locations in [Region] | [Primary Services]

Examples:

Dental Office Near You in the Denver Metro Area | Pediatrics

Dental Locations in the Denver Region | Braces & X-Rays

Meta Formula

Find a [service/business type] in (the) [Region] with [Business Name]. Visit one of our nearby locations for [top services].

Example:

Find a dental office in the Denver Metro Area with Caring Dental. Visit one of our nearby locations for family, pediatric, and senior dental care.

Service Area Pages (SAPs)

Title Tags

The approved formula is: Keyword | Geo Area | NOB

SAP title tags are dynamically generated through the Directory Page's Collection connection. The output follows the formula above automatically.

Do: Connect the Page Meta Title field in the PSAP to the correct Collection field
correct field is: Title - Keyword
e.g.: Embroidery - Keyword
e.g.: Landscaping - Keyword (added 4/7/26)
Do not: Make manual edits to individual SAP title tags.
Do not: Edit or rewrite at the page level. All changes must be made at the formula level.

If the generated title tag is too long:

Remove punctuation and vertical pipes first.
Then remove the NOB.
Give priority to the keyword and City, ST.

Meta Description

SAP meta descriptions are also dynamically generated. They should be edited for clarity and character count. Three approaches work well:

Primary CTA opening: Primary CTA [NOB] for your specific keyword phrase. Motivating factor or phrase, motivating factor or phrase.

Visit or call opening: Visit NOB or call to schedule appointment/service/etc. for your specific keyword phrase. Motivating factor or phrase, motivating factor or phrase.

Schedule / request opening: Schedule / request your ________ (form type — appointment, case review, estimate, consultation, etc.) or call to speak with our staff / team / representatives / doctors / lawyers, etc. for your specific keyword phrase. Motivating factor or phrase, motivating factor or phrase.

These are starting points, not rigid formulas. The description must read naturally and serve the user.

Purpose / Why It Matters

Title tags and meta descriptions:

Drive the first conversion: the click.
Signal relevance to search engines.
Influence click-through rate (CTR).
Establish consistency between the search listing and on-page content.
Support conversion-first messaging before a user ever reaches the site.

In many cases, the search result is the first and only impression a user receives. These elements must be written intentionally.

Current Display Standards

Search engines do not impose a strict technical character limit. However, they do have what is considered an optimum range. This is what informs Hibu's character-length standards.

Title Tags

Google typically displays up to ~60 characters on desktop before truncating.
Ideal performance range: ~50–55 characters.
Maximum upper boundary: 60 characters.
Writing target: 55 characters.

Going to 56–60 characters is acceptable when necessary. The goal is clarity and control, not arbitrary enforcement.

Meta Descriptions

Desktop display typically truncates around ~155–160 characters.
Mobile truncates earlier.
Maximum limit: 160 characters.
The most important information should appear in the first ~100–120 characters.

Front-loading key information reduces the impact of truncation.

Examples:

Basement Remodel | Delaware County | ACE Construction

Call ACE Construction for all your home improvement needs. Offering free estimates if you hire us and a 10 year warranty on all labor.

Visit or call Lansdowne Dental for all your orthodontic needs. Walk-ins are welcome. We offer sedation dentistry.

Schedule your consultation with Johnson Attorneys at Law to review your slip and fall case. Over 30 years of experience. We make hospital visits.

GEO Pages

Title Tag

The approved formula is: Product / Service Keyword | City, ST | NOB

Use the City, ST or Geo Location of each GEO Page for its title tag.

Do: Use the specific product or service keyword relevant to the page.
Do: Use the pipe character ( | ) to separate each component.
Do: Use the standard two-letter state abbreviation.
Do: Target 55 characters; stay within the 60-character hard limit.
Do not: Use any separator other than the pipe character.

If the title tag is too long:

Remove punctuation and vertical pipes first.
Then remove the NOB.
Give priority to the keyword and City, ST.

HVAC Repairs | Drexel Hill, PA | Joe's Plumbing

Roadside Assistance | Kent County, DE | Joe's Towing

Meta Description

GEO page meta descriptions follow the homepage meta description style. Three approaches work well:

Primary CTA opening: Primary CTA [NOB] for your specific keyword phrase, specific keyword phrase, specific keyword phrase. (As used on homepage meta description.)

Visit or call opening: Visit NOB or call to schedule appointment/service/etc. for your specific keyword phrase, specific keyword phrase, specific keyword phrase. (As used on homepage meta description.)

Schedule / request opening: Schedule / request your ________ (form type — appointment, case review, estimate, consultation, etc.) or call to speak with our staff / team / representatives / doctors / lawyers, etc. for your specific keyword phrase, specific keyword phrase, specific keyword phrase. (As used on homepage meta description.)

These are starting points, not rigid formulas. The description must read naturally and serve the user.

Effective Date: February 1, 2026 Last Updated: April 1, 202 6

Prohibited & Restricted Verticals

Sun, 01 Feb 2026 13:53:03 GMT

Definition

Hibu maintains a list of Prohibited and Restricted verticals to ensure every Hibu One Smart Site complies with brand safety, legal standards, and platform policies.

These rules apply to all website content, advertising, and eCommerce functionality.

Prohibited = Hibu will not build or host websites for these products or industries under any circumstances.
Restricted = Hibu may build and host a website for this business as long as the Hibu One eCommerce store is not used to sell the restricted products.
These businesses may include a link to a verified third-party store (e.g., Shopify, PayPal, Square, or another external checkout platform).
The Hibu One 10-product store cannot include restricted products, nor can any “Buy Now,” “Shop Online,” or “Add to Cart” buttons connect to the Hibu store.

Prohibited & Restricted Verticals

Prohibited Verticals

Hibu will not create, host, or promote websites or content for:

Explosives or bomb-making materials
Pornographic or sexually explicit content of any kind
Human trafficking or escort services involving transactional sex or implied sale of persons
Illegal substances or activities
“Hate speech,” discriminatory, or inflammatory content (e.g., KKK, extremist groups)

Restricted Verticals

Hibu may build websites for these industries under the following restrictions:

1. Weapons & Explosives

Restricted - No online sales through the Hibu store; external links permitted
Fireworks
Replica or imitation firearms marketed as real
Self-defense weapons such as stun guns, tasers, or pepper spray
Prohibited - Hibu will not create, host, or promote website
Explosives or bomb-making materials

2. Controlled Substances & Vaping

Restricted - No online sales through the Hibu store; external links permitted
THC, CBD, hemp, vape, and related products
Vape juice or e-liquids containing nicotine
Cannabis dispensaries (medical or recreational) — informational only
No online sales through the Hibu store; external links permitted

3. Adult-Oriented Businesses

Restricted - No online sales through the Hibu store; external links permitted
Adult entertainment, escort, or dating services (must be professional, tasteful, and non-graphic)
Fetish, bondage, or sexual wellness products — may be shown but not sold via the Hibu store
All imagery must be from the neck up ; no pornographic or sexually suggestive content
Prohibited - Hibu will not create, host, or promote website
Pornographic or sexually explicit materials

4. Health & Medical

Restricted - No online sales through the Hibu store; external links permitted
Unlicensed or “miracle cure” treatments
Stem cell therapy, IV drips, or other high-risk health claims
Unverified supplements, including weight-loss or muscle-building products
Allowed:
Plastic surgery or medical aesthetic practices (before-and-after images permitted with assumed patient consent)

5. Illegal or Questionable Products

Restricted - No online sales through the Hibu store; external links permitted
Counterfeit goods, imitation brands, or replicas
Hacking tools, spyware, or surveillance products
Prohibited - Hibu will not create, host, or promote website
Personal data sales or human trafficking

6. Gambling & Betting

Restricted - No online play, gambling, or wagering; External links permitted
Sports betting, fantasy sports, and casinos — allowed only for informational or brick-and-mortar purposes

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Alt Text Tags

Sun, 01 Feb 2026 13:52:54 GMT

Definition

Alt text (alternative text) tags are used within an HTML code to describe the appearance and function of an image on a page.

Purpose / Why It Matters

Adding alt text tags to images * is first and foremost a principle of web accessibility. Visually impaired users rely on screen readers—assistive software that reads on-screen content aloud—to understand images through their alt text tag.
Alt text tags will be displayed in place of an image if an image file cannot be loaded.
Alt text tags provides better image context / descriptions to search engine crawlers, helping them to index an image properly.

* Any png, jpg, jpeg, gif, svg, webp uploaded is defined as an image.

* The a lt text tag is not required for background images, since these images are not read by screen readers.

Alt Text Tags Tips

Describe the image as specifically as possible. Alt text is, first and foremost, designed to provide text explanations of images for users who are unable to see them.
Keep it (relatively) short. The most popular screen readers cut off alt text at around 125 characters, so it's advisable to keep it to that character count or less.
Use your keywords. Alt text provides another opportunity to include targeted keywords on a page, and thus another opportunity to signal to search engines that the page is highly relevant to a particular search query. While the first priority should be describing and providing context to the image, if it makes sense to do so , include a keyword and/or name of business in the alt text of at least one image on the page.
Avoid keyword stuffing. Google won't "dock points" for poorly written alt text, but there could be consequences if the alt text is stuffed with too many or irrelevant keywords. Again, focus on writing descriptive alt text that provides context to the image and, if possible, includes a targeted keyword, and leave it at that.
Don't include "image of," "picture of," etc. in alt text. It's already assumed your alt text is referring to an image, so there's no need to reiterate it.

When to Use an Alt Text Tag

Examples

Client Logos

Enter NOB logo as alt tag for the Hibu client logo. The client logo is the only instance when you add "logo" to the alt text.

Optimal Alt Text Tags Formatting

The best format for alt text tag is sufficiently descriptive but doesn't contain any spammy attempts at keyword stuffing. If you can close your eyes, have someone read the alt text to you, and imagine a reasonably accurate version of the image, you're on the right track.

Not-so-good alt tag = dog

This alt text can be better because it's not very descriptive. Yes, this is an image of a dog, but there's more to be said about this image.

Not-so-good alt tag = dog running
This alt text is better. Yes, it is an image of a dog running, but there's still more to be said about this image.

Ideal alt tag = Border Collie running on beach

This alt text is the ideal alternative because it is far more descriptive of what's in the image. This isn't just a dog or a dog running; it's a Border Collie running on a beach.

Ideal alt tag = hammer nail into a roof shingle

Not-so-good alt tag = hammer and nail

Not-so-good alt tag = hammer nail into a roof

alt text tag = OnTrack Accounting logo

alt text tag = Nittoli's Pizzeria logo

alt text tag = Dali Painting logo

Badges / accreditation logos (usually associated with a row directly above the footer or on contact us page)

Transcribe all readable text on the image.

Icons (SVG, png, and, on occasion, jpg, gif, webp)

Do not add alt text for decorative icons , such as those used in the hero, “Why Choose Us,” reviews, footer, engagement sections, or callouts. Adding alt text to purely decorative icons introduces unnecessary noise for screen readers and does not improve SEO or accessibility.

alt text tag = Best of the Best Dentists

alt text tag = EcoTherm Insulation

alt text tag = The National Trial Lawyers Top 100 Trail Lawyers

Alt-Text

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Internal Page Linking

Sun, 01 Feb 2026 13:37:17 GMT

Internal Page Linking

Why Is Internal Linking Important?

Internal linking not only helps users navigate through the website, but also plays a significant role in improving search engine visibility.

Definitions:

In-text hyperlinks - Embedded links within the body of the text to relevant pages using anchor text
Anchor text - Anchor text refers to the clickable text within a hyperlink that provides a relevant description of the destination page it links to

Hierarchy:

When deciding what text to hyperlink, destination page importance should be considered in the following order:

Offers - we want users to quickly and easily find the deals that will convert them into customers
Service / product pages - we want users to easily find other related services on the site
Utility pages - this will help users find relevant reviews, images, and other elements that might be of interest
About pages - these links will help users find information about the business and its offerings

Challenges of In-Text Hyperlinks on Mobile Devices:

There are some disadvantages to in-text hyperlinks, primarily on mobile devices. These disadvantages can negatively affect the user’s experience, so it is important to keep them in mind when determining where to create hyperlinks.

Small screen size: Mobile screens are smaller, making it harder to click accurately on in-text hyperlinks.
Fat finger problem: Users may accidentally tap the wrong link due to the limited precision of touchscreens.
Readability and distraction: In-text hyperlinks can disrupt the flow and readability of the text, distracting users from the main content.
Slow loading times: Clicking on in-text hyperlinks may lead to longer loading times, especially on mobile devices with slower connections.
Accidental activation of links: Users may unintentionally activate in-text hyperlinks while scrolling or navigating, resulting in unintended page visits.

To mitigate these drawbacks, ensure proper spacing and avoid excessive hyperlinks. Quality and relevance are more important than quantity. Be cautious not to overwhelm users with too many links.

Best Practices to Follow:
Finding opportunities to add in-text hyperlinks to your copy requires a strategic approach. Here's a step-by-step process to help you:

1. Review your content: Thoroughly review your website's content, including different pages like the homepage, product/services pages, about us page, FAQ, gallery, finance, etc. Look for mentions of topics that could benefit from internal linking, including:

Mentions of offers
Mentions of warranties
Mentions of related services and products
Mentions of biographical information, if expanded upon elsewhere

2. Use mobile view to place the links: This will help ensure that links are not crowded and that mobile users have an optimal experience when interacting with the site.

3. One link per topic: Only add one in-text hyperlink for each relevant topic per page. You don't need multiple links for the same topic within your copy.

4. One link per text block: to avoid cluttered site copy, particularly in mobile view, it is important to place only one link per text block (paragraph, bulleted list, or long sentences that are their own paragraph). This will help mitigate some of the issues that might arise as discussed in the Disadvantages section below.

5. Try to place important links above the fold: If possible, link to offers and service pages close to the top of the page. This way, users won’t have to scroll very far before they reach links that might be relevant to their needs.

Remember, the primary goal of internal linking is to enhance user experience and help search engines understand the relevance and hierarchy of your website content. By following these best practices, you can create a well-optimized internal linking strategy that benefits both your users and your SEO efforts.

Built-In Internal Linking (Already in Place)

In addition to in-text hyperlinks added within page copy, Hibu One Smart Sites include internal linking by default through structural elements, including:

Breadcrumb navigation , which reinforces page hierarchy and parent–child relationships
Core page–related links (for example, related services or next-step links), which guide users to relevant pages based on intent

These elements provide foundational internal linking across the site and help search engines understand structure and relevance without requiring manual linking within copy.

When identifying opportunities for additional in-text hyperlinks , teams should treat those links as supplemental , not a replacement for the internal linking already provided through breadcrumbs and related links.

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Reviews Widgets: Display Rules, Sources, and Placement Standards

Sun, 01 Feb 2026 13:27:53 GMT

Reviews Widgets: Display Rules, Sources, and Placement Standards

Hibu Policy

Hibu One supports a standardized Reviews widget is a standardized Hibu One component that displays customer ratings and review content sourced from:

Hibu Reviews
Google Reviews
Facebook Reviews

Reviews (star rating and review count) will display in the header, homepage, category landing pages, and right gutter only when a client has:

Three (3) or more total reviews , and
An overall rating of 4.0 or higher
If either threshold is not met, review stars and counts will not display in those areas.
The dedicated Reviews page will display all eligible reviews regardless of star rating or review volume.
Only the Hibu Reviews widget is supported in the header. Third-party review widgets are not permitted in the header area.

If the client requests removal of any version of the Reviews widget, Hibu may remove the widget with the understanding that doing so may negatively impact conversion.

Purpose / Why It Matters

Reviews are a core trust signal. Placement in high-visibility areas—especially the header—directly supports credibility and conversion.
Internal research and performance data show measurable conversion lift when reviews are displayed prominently in the header.
The Hibu Reviews widget is performance-optimized and structured to maintain schema integrity, speed, and consistency across devices.
Removing reviews may reduce trust signals and conversion performance. Teams must clearly communicate this risk when requests are made.

Third-Party Review Widget Policy

Hibu Policy

Only the Hibu Reviews widget is supported in the site header.
Third-party review widgets (including Google, Facebook, or other externally embedded platforms) are not permitted in the header under any circumstance.

Rationale

Third-party review widgets:

Load dynamic external scripts
Can negatively impact page speed, especially on mobile
May interfere with structured data and schema
Introduce visual inconsistency across devices

The Hibu Reviews widget is performance-optimized and aligned with Hibu One standards.

Allowed Placement

Third-party review widgets may appear on the dedicated Reviews page only.

They are not supported in:

Header
Homepage recent reviews
Category landing page recent reviews
Right gutter widgets

Reviews Widget Placements

1. Header (Desktop, Tablet, Mobile)

Displays overall star rating and total review count.
Visible only when the 3-review minimum and 4.0+ rating threshold are met.
Only the Hibu Reviews widget is permitted in this area.
Third-party widgets are not allowed in the header.

2. Homepage & Category Landing Pages (“Recent Reviews”)

Displays the two most recent reviews.
Requires 3+ total reviews and 4.0+ overall rating.
If thresholds are not met, reviews do not display.
If the client requests removal, the widget may be removed.

3. Right Gutter (Core Service/Product Pages)

Displays shuffled reviews from varying time periods.
Refreshes dynamically across page loads.
Requires 3+ total reviews and 4.0+ overall rating.
May be removed upon client request.

4. Dedicated Reviews Page

Displays all review sources in chronological order.
No minimum review count requirement.
No rating threshold requirement.
If one review exists, one review displays.
If the overall rating is below 4.0, it still displays here.
This page reflects the full review dataset without front-end threshold restrictions.

Effective Date: February 1, 2026 Last Updated: February 25, 202 6

Review Source & Inclusion Rules

Included Sources

Hibu Reviews
Google Reviews
Facebook Reviews

On the Reviews page:

Reviews appear in chronological order.
Hibu reviews are marked with a purple Hibu icon.
Google reviews display a Google icon.
Facebook reviews display a Facebook icon.

Negative Review Handling

Negative Hibu reviews are not displayed.
Negative Google and Facebook reviews may appear.
All Google and Facebook reviews (positive and negative) count toward the total review count and overall rating.

Review Star Color Standards

Default Standard

Yellow or gold remains the default and recommended star color. It is the industry standard and provides strong visibility and recognition.

Approved Alternative Colors

When deviating from yellow or gold, the star color may be:

Blue (or variation of blue)
Green (or variation of green)
Purple (or variation of purple)
Orange (or variation of orange)

These colors are permitted only if:

The exact shade used exists within the client’s established color palette.
The same shade is used consistently across the entire site.
The color maintains sufficient contrast against the background.

Do not introduce a new variation of a color if a different shade of that color already exists in the brand palette.

Black and White Usage

White stars may be used only on dark backgrounds.
Black stars may be used only on light backgrounds.
Contrast and accessibility standards must be maintained.

Restricted Colors

The following are not permitted:

Red
Pink
Maroon
Burgundy
Any variation of red or pink tones
Pale or low-contrast colors
Colors that closely match the background

Implementation Requirement

When changing the review star color, the update must be made in the site’s Theme Colors using the designated placeholder for review stars (Color #14).
All review placements (header, homepage, category pages, right gutter, and Reviews page) must reflect the same color.
It is expected that the Hibu design team will rename any updated image or asset files and apply appropriate alt text where applicable.

Template - Do Not Delete

Sun, 01 Feb 2026 13:15:52 GMT

H3

Designers may use a client’s logo before the Digital Content Release Agreement is signed only when there is reasonable, visible evidence that the client already owns and publicly uses that logo. This allows site builds to continue without delay while still protecting Hibu from improper or unauthorized use.

Headline

H3

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Title / Meta - Contact / Location Pages

Sun, 01 Feb 2026 13:08:09 GMT

Title / Meta - Contact / Location Pages

Hibu Policy

Every contact and location page on a Hibu One Smart Site must include:

One unique title tag following the approved formula — which applies regardless of business type
One unique meta description determined by the primary and/or secondary CTA as defined on the client questionnaire

Definition

Title tags and meta descriptions are HTML elements that control how a page appears in search engine results pages (SERPs) and when shared on social platforms.

The title tag acts as the headline.
The meta description acts as supporting copy.

Together, they function as a mini advertisement for the page — the pre-click version of the on-page experience. If the user does not click, the rest of the page experience does not occur.

Contact and location pages serve a specific functional purpose: they direct prospective customers to reach out or visit. The title tag and meta description for these pages are written to support that action directly.

Rules & Guidelines

Title Tag — All Business Types

The approved formula for Contact and Location Pages is: Contact NOB | City, ST

The approved formula for the Location Category Landing Page is: NOB Locations/Offices/etc. | Primary Geo | [Space Permitting] Secondary Geo

The title tag formula is the same regardless of business type. Location/Hybrid and Service-based businesses use the same structure.

Do: Use "Contact" as the opening word.

Do: Use the pipe character ( | ) to separate each component.

Do: Use the standard two-letter state abbreviation.

Do: Target 55 characters; stay within the 60-character hard limit.

Do not: Use any separator other than the pipe character..

Do not: Vary the formula by business type.

Meta Description — All Business Types

The meta description is determined by the primary and/or secondary CTA as defined on the client questionnaire. Three approaches work well:

Primary CTA opening: Primary CTA [NOB] for your specific keyword phrase, specific keyword phrase, specific keyword phrase. (As used on homepage meta description.)

These are starting points, not rigid formulas. The description must read naturally, reflect the business's actual CTA, and serve the user.

Meta Desc:

Primary CTA [NOB] for your specific keyword phrase, specific keyword phrase, specific keyword phrase. (as used on homepage meta description)
-OR-
Visit NOB or call to schedule appointment/service/etc for your specific keyword phrase, specific keyword phrase, specific keyword phrase. (as used on homepage meta description)
-OR-
Schedule / request your _________ (form type - appointment, case review, estimate, consultation, etc.) or call to speak with our staff / team / representatives / doctors / lawyers, etc.

Purpose / Why It Matters

Title tags and meta descriptions:

Drive the first conversion: the click.
Signal relevance to search engines.
Influence click-through rate (CTR).
Establish consistency between the search listing and on-page content.
Support conversion-first messaging before a user ever reaches the site.

In many cases, the search result is the first and only impression a user receives. These elements must be written intentionally.

Current Display Standards

Search engines do not impose a strict technical character limit. However, they do have what is considered an optimum range. This is what informs Hibu's character-length standards.

Title Tags

Google typically displays up to ~60 characters on desktop before truncating.
Ideal performance range: ~50–55 characters.
Maximum character limit: 60 characters.
Writing target: 55 characters.

Going to 57–60 characters is acceptable when necessary. The goal is clarity and control, not arbitrary enforcement.

Meta Descriptions

Desktop display typically truncates around ~155–160 characters.

Mobile truncates earlier.

Hard limit: 160 characters.

The most important information should appear in the first ~100–120 characters.

Front-loading key information reduces the impact of truncation.

Examples

Contact Big Marty's Flooring | Nishloo, TX

Visit Big Marty's Flooring for your home or office carpeting, hardwood, laminate, vinyl, and tile floors needs.

Contact Pauline's Hair and Nails | Bear, DE

Visit Pauline's Hair and Nails or call to schedule an appointment for your next hair cut, color, wax, manicure, or pedicure.

Contact Anti Pest Co. | Tri-State Area

Call or schedule online your residential and commercial pest, wildlife, bird, bed bug, and termite control service.

Contact Dewey, Cheatem & Howe | Mews, CT

Schedule your free case review online or call to speak directly with a representative from our firm.

Effective Date: February 1, 2026 Last Updated: April 1, 202 6

Title / Meta - Core / Product / Service Page

Sun, 01 Feb 2026 13:00:17 GMT

Title / Meta - Core / Product / Service Page

Hibu Policy

Every core, product, and service page on a Hibu One Smart Site must include:

One unique title tag built to the approved formula for the applicable business type
One unique meta description that includes specific keyword phrases, the Name of Business, and at least one motivating factor or offer

Definition

Title tags and meta descriptions are HTML elements that control how a page appears in search engine results pages (SERPs) and when shared on social platforms.

The title tag acts as the headline.
The meta description acts as supporting copy.

Together, they function as a mini advertisement for the page — the pre-click version of the on-page experience. If the user does not click, the rest of the page experience does not occur.

This guideline covers the approved formulas for core pages, product pages, and service pages within the Hibu One Smart Site product. All three page types follow the same formula.

Rules & Guidelines

Title Tag — Location/Hybrid Business

The approved formula is:

Product / Service Keyword (or phrase) | (Space permitting) Product/Service Keyword (or phrase) | City, ST | NOB (Space permitting)

Hierarchy

Primary keyword and Geo location / City, ST are "must haves"
If there is room for addition information:
Add a relevant secondary keyword first
If there is still room, add the NOB (updated 4/13/2026)

Do: Use the specific product or service keyword for the page — not the core business keyword used on the home page.

Do: Use the pipe character ( | ) to separate each component.

Do: Use the standard two-letter state abbreviation in the geo modifier.

Do: Target 55 characters; stay within the 60-character hard limit.

Do not: Use any separator other than the pipe character.

Do not: Repeat the home page title tag on a core, product, or service page.

Do not: randomly choose a secondary keyword. Ensure that it is relevant to and present on they page. (added 4/9/2026)

Title Tag — Service-based Business

The approved formula is:

Product / Service Keyword (or phrase) | (Space permitting) Product/Service Keyword (or phrase) | Geo Area | NOB (Space permitting)

Do: Use the specific product or service keyword for the page

Do: Use the geographic area descriptor definined on the questionnaire

Do: Target 55 characters; stay within the 60-character hard limit.

Meta Description — All Business Types

Meta descriptions for core, product, and service pages should include the Name of Business (NOB), relevant keyword phrases, and at least one motivating factor or offer. Two approaches that work well for this page type are:

Action-verb opening: [Action Verb] keyword, similar keyword at [NOB]. Motivating factor. CTA (space permitting). — This approach works well for transactional pages where user intent is to purchase or hire.

Question opening: Ask a question that includes a keyword or two. [NOB] answers the question. — This approach works well when the page addresses a specific problem or question a prospective customer is likely to search.

These are starting points, not rigid formulas. The description must read naturally and serve the user.

Regardless of approach:

Do: Include the NOB within the description.

Do: Include at least one motivating factor and/or offer (e.g., financing available, no extra fees, free estimate).

Do: Write in complete sentences using sentence case.

Do: Place critical messaging within the first ~110–120 characters.

Do: Target a length of 150–160 characters.

Do not: Use vague or generic language that does not reflect specific services or offers.

Do not: Repeat the title tag verbatim as the meta description.

Do not: Write for search engines first. Write for humans first; search engines second.

Purpose / Why It Matters

Title tags and meta descriptions:

Drive the first conversion: the click.
Signal relevance to search engines.
Influence click-through rate (CTR).
Establish consistency between the search listing and on-page content.
Support conversion-first messaging before a user ever reaches the site.

In many cases, the search result is the first and only impression a user receives. These elements must be written intentionally.

Current Display Standards

Search engines do not impose a strict technical character limit. However, they do have what is considered an optimum range. This is what informs Hibu's character-length standards.

Title Tags

Google typically displays up to ~60 characters on desktop before truncating.

Ideal performance range: ~50–55 characters.

Acceptable upper boundary: 60 characters.

Writing target: 55 characters.

Going to 57–60 characters is acceptable when necessary. The goal is clarity and control, not arbitrary enforcement.

Meta Descriptions

Desktop display typically truncates around ~155–160 characters.

Mobile truncates earlier.

Ideal range: 150–160 characters.

Critical messaging should appear in the first ~110–120 characters.

Front-loading key information reduces the impact of truncation.

Examples

Location/Hybrid Business

Title Tag: Product / Service Keyword (or phrase) | City, ST
Meta Desc:
[Action Verb] keyword, similar keyword at [NOB]. H3 Motivating factor. CTA (space permitting)
-OR-
Ask a question that includes a keyword or two. [NOB] answers the question.

Plants | Flowers | Garden Center | Franklin, TN

Shop for perennials, annuals, shrubs, bagged stone, soil, and mulch at Tweezer’s Gardens. Open 7-days a week. Local delivery available.

Chapter 7 Bankruptcy Lawyer | Springfield, MO

Are you in need of an experienced Chapter 7 bankruptcy lawyer? Call Gordon and Page Attorneys at Law to schedule your free case review.

New Tire Installation and Service | Nampa, ID

Buy new tires for your vehicle at Mike's Auto Center. Every install comes with maintenance for the life of the tire. Open daily until 6 pm. Towing available.

Children’s Eye Exams | Cranston, RI

Looking for an eye doctor for your child? Wilson's Eye Care provides eye exams and care for kids of all ages. Seeing new patients. Same-day appointments.

Dentures | Media, PA | Parker Dentistry

Looking for new or replacement dentures? Parker Dentistry provides dental exams, orthodontics, and denture care. Seeing new patients. Same-day appointments.

Service-based Business

Title Tag: Core Business Keyword (or phrase) | Geo Area
Meta Desc:
[Action Verb] keyword, similar keyword at [NOB]. H3 Motivating factor. CTA (space permitting)
-OR-
Ask a question that includes a keyword or two. [NOB] answers the question.

24/7 Emergency Roof Repair Services | East Texas

Are you in need of an emergency roofer? Carini Roofing provides 24-hour emergency roof repair for any unfortunate situation. Financing options are available.

Water Heater Repair and Replacement | Aberdeen, WA

Contact Harry Hood Plumbing today for water heater service. 24/7 service. No extra fees for emergencies, nights, weekends.

Pressure Washing Services | San Bernardino Area

Hire Reba Exteriors to power wash your home's deck, siding, roof, walkway, or your business's exterior. Call today for a free estimate.

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Ten-Product DIY Online Store

Sun, 01 Feb 2026 12:48:31 GMT

Overview

The Ten-Product DIY Online Store is a limited eCommerce option available for Hibu One Smart Sites. It is designed for clients who want a very small online store and are willing to fully manage setup, products, and operations themselves.

This offering is intentionally constrained. It supports up to 10 products and does not scale beyond that limit.

Ten-Product DIY Online Store

Hibu Policy

Hibu may add the Ten-Product Online Store to a Hibu One Smart Site by request , either:
During the initial site build, or
After the site has already been published
Hibu’s role is limited to adding the store functionality to the site.
All store setup is 100% DIY and managed by the client / merchant.
Hibu does not configure products, categories, pricing, shipping, taxes, payments, or promotions.
The online store does not count toward the total page count of the website.
At this time, there is no option to add more than 10 products or SKUs .

Client Responsibilities

The client / merchant is fully responsible for:

Product creation and management
Categories and organization
Pricing and inventory
Shipping and tax rules
Payment gateway setup
Order management
Ongoing maintenance and updates

If the client has questions about store setup, Hibu will direct them to the Website Help Center .

Important : The Website Help Center documentation is written for non-Hibu clients and includes features that are not available in the Ten-Product store. Clients should expect differences.

What In the Store Is (and What's Not)

Store Limits

Products: 10
Product Categories: 2

Shopping Experience

Responsive storefront (desktop, tablet, mobile)
Single-product widgets
Products in cart visibly marked in product lists
Real-time shipping estimates (IP-based)
Guest checkout or account creation (configurable)
Address book for returning customers
Media-rich product descriptions
Required acceptance of Terms & Conditions
Next / Previous product navigation
Automatic price adjustment for product options
Fast content delivery via CDN

Catalog & Product Management

Onboarding wizard
Product options (dropdowns, radio buttons, text, date picker, file upload, checkboxes)
Unlimited product images
Automatic image thumbnail generation
Products may exist in more than one category
Product types and attributes
Multi-currency support

Shipping & Tax

Unlimited delivery zones
Shipping configuration wizard
Flexible shipping and tax rules
Real-time shipping quotes (UPS, USPS, FedEx, and others)
Real-time shipment tracking

Orders & Payments

Customizable order email notifications
Order history for clients and administrators
Multiple notification recipients
Payment and shipping status tracking
Invoice printing
Order comments
Low-stock notifications

Supported Payment Gateways

PayPal (multiple options)
Square
Strype

Not Included in the Ten-Product Store

The following capabilities are not supported :

More than 10 products or SKUs
Inventory tracking and stock control
Discount coupons or promotions
Sales pricing or volume discounts
Facebook storefronts or social selling
POS integration
Marketplace exports (Amazon, eBay, Google Shopping, etc.)
API-based integrations for orders or products
Advanced analytics or remarketing
Wishlist or favorites
Digital goods (e-goods)
Affiliate programs

Why This Offering Exists

The Ten-Product DIY Online Store exists to:

Support simple eCommerce needs without expanding scope
Provide a low-maintenance option for clients comfortable with DIY tools
Maintain performance, reliability, and support boundaries
Avoid positioning Hibu One as a full eCommerce platform
This is a convenience feature , not a comprehensive commerce solution.

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Title / Meta - Home and Category Landing Pages

Sun, 01 Feb 2026 12:44:15 GMT

Title / Meta - Home

Hibu Policy

Every home page and category landing page on a Hibu One Smart Site must include:

One unique title tag built to the approved formula for the applicable business type
One unique meta description that includes specific keyword phrases and at least one motivating factor or offer

Definition

Title tags and meta descriptions are HTML elements that control how a page appears in search engine results pages (SERPs) and when shared on social platforms.

The title tag acts as the headline.

The meta description acts as supporting copy.

Together, they function as a mini advertisement for the page — the pre-click version of the on-page experience. If the user does not click, the rest of the page experience does not occur.

This guideline covers the approved formulas for home pages and category landing pages. Both page types follow the same formula.

Rules & Guidelines

Title Tag — Location/Hybrid Business

The approved formula is: Core Business Keyword (or phrase) | City, ST | NOB

Do: Use the pipe character ( | ) to separate each component.
Do: Use the standard two-letter state abbreviation in the geo modifier.
Do: Target 55 characters; stay within the 60-character hard limit.
Do not: Use any separator other than the pipe character.
Do not: Omit any of the three required components.
Do not: Use a geo area or regional descriptor in place of a specific City, ST for this business type.

Title Tag — Service-based Business

The approved formula is: Core Business Keyword (or phrase) | Geo Area | NOB

Do: Use a regional or geographic area descriptor that reflects the business's actual service territory (e.g., South Florida, Tri-State Area, Palm Valley, CA Area).
Do: stay within the 60-character hard limit.
Do not: Use a specific City, ST format in place of the appropriate Geo Area for this business type.
Do not: Omit any of the three required components.

Meta Description — All Business Types

Do: Include a minimum of two specific keyword phrases.
Do: Include at least one motivating factor and/or offer (e.g., free estimate, no extra fees, call today).
Do: Write in complete sentences using sentence case.
Do: Place critical messaging within the first ~110–120 characters.
Do: Target a length of 160 characters.
Do not: Use vague or generic language that does not reflect specific services or offers.
Do not: Repeat the title tag verbatim as the meta description.
Do not: Write for search engines first. Write for humans first; search engines second.
Do not: Include any extensions to the NOB like LLC or Inc. in any title tag or meta description.

Purpose / Why It Matters

Title tags and meta descriptions:

- Drive the first conversion: the click.

- Signal relevance to search engines.

- Influence click-through rate (CTR).

- Establish consistency between the search listing and on-page content.

- Support conversion-first messaging before a user ever reaches the site.

In many cases, the search result is the first and only impression a user receives. These elements must be written intentionally.

Current Display Standards

Search engines do not impose a strict technical character limit. However, they do have what is considered an optimum range. This is what informs Hibu's character-length standards.

Title Tags

Google typically displays up to ~60 characters on desktop before truncating.
Ideal performance range: ~50–55 characters.
Acceptable upper boundary: 60 characters.
Writing target: 55 characters.

Going to 57–60 characters is acceptable when necessary. The goal is clarity and control, not arbitrary enforcement.

Meta Descriptions

Desktop display typically truncates around ~155–160 characters.
Mobile truncates earlier.
Ideal range: 150–160 characters.
Critical messaging should appear in the first ~110–120 characters.

Front-loading key information reduces the impact of truncation.

Examples

Location/Hybrid Business

Carpet and Tile | Nishloo, TX | Big Marty's Flooring

We offer a large selection of home or office carpeting, hardwood, laminate, vinyl, and tile floors. Next-day installations. Call for a free in-home estimate.

Auto Repair Shop | Bloomfield, AZ | The Manic Mechanic

Our services include domestic and foreign repair, oil changes, brakes, and tires. AAA-certified ASE technicians. Request your appointment today.

Personal Injury Attorney | Mews, CT | Dewey, Cheatem & Howe

Our firm represents victims of auto accidents, slip and falls, and medical malpractice. You don't pay if we don't collect! Call today for a free consultation.

Italian Restaurant | Jefferson, NY | Moon Pizza

We specialize in New York-style and gourmet pizza, hot and cold subs, and salads. Dine-in, carryout, or delivery. Daily specials. Open until 11 pm every day.

Service-based Business

Landscaper | South Florida | Clark's Happy Yards

We specialize in residential and commercial landscape design, hardscaping, and lawn care. Discounts for seniors and military. Call for your free estimate.

Plumber | Palm Valley, CA Area | Speedy 24/7 Plumbers

We offer 24/7 residential and commercial emergency plumbing services. No extra fees for emergencies, nights, or weekends.

Exterminator | Tri-State Area | Anti Pest Co.

We provide residential and commercial pest, wildlife, and termite control. Monthly and quarterly maintenance plans available. Call now for a free estimate.

Edge Cases & Clarifications

Business operates in multiple cities or regions. The title tag should reflect the primary city or primary service area. Category landing pages follow the same formula and should reflect the primary city or service area unless the page is specifically geo-targeted to a different location.

Business name contains a city or geo reference. If the NOB already includes a city name (e.g., "Dallas Plumbing Co."), the geo modifier must still appear (e.g. "Dallas, TX").

Very long NOB or keyword phrase. If components cannot be reconciled within 55 characters, adjust while staying under the 60-character hard limit. If over 60 characters, remove pipes and then punctuation. If possible, reword the keyword to something similar and shorter. The NOB should not include extensions like LLC or Inc. If the hard limit still cannot be met, leave an assumption and leave the title tag long.

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Editor 2.0 — Platform Overview

Sun, 01 Feb 2026 01:37:20 GMT

Definition

Editor 2.0 is a component-based website-building experience that brings layout structure, visual design settings, connected data, and responsive controls into a single editing environment. It organizes content using a clear hierarchy, applies theme-driven styling, and ensures that every element behaves predictably across Desktop, Tablet, and Mobile.

Editor 2.0 — Platform Overview

Overview

All Hibu One websites are built using Duda’s Editor 2.0. It provides the canvas, structural tools, content elements, and styling controls that shape how pages are designed, organized, and displayed across all devices. The editor includes the core components teams work with every day: Sections, Columns, Inner Columns, Widgets, Breakpoints, the Design Panel, the Layers Panel, Themes, and system-controlled areas such as headers and footers.

Purpose / Why It Matters

Editor 2.0 defines the foundation for how Hibu One websites are created, structured, and maintained. A clear understanding of the editor supports:

Consistent design patterns across all Smart Sites
Predictable responsive behavior at each breakpoint
Efficient builds using templates and reusable structures
Fewer layout or alignment issues during and after launch
Accurate use of connected data and theme settings
Proper handling of locked, system-controlled elements
Strong, stable performance and long-term maintainability

Shared understanding of the editor ensures Design, Build, QA, Support, Copy, and Product teams work within the same framework and deliver a consistent, high-quality site experience.

Structure & Layout

Sections define major horizontal regions; Columns and Inner Columns define layout structure; Widgets are the building blocks of all content.
Layout changes made at the Desktop breakpoint cascade downward unless overridden at smaller breakpoints.
Manual spacing (e.g., empty widgets used for spacing) is prohibited; approved padding and margin tools must be used.

Breakpoints

Editor 2.0 uses three breakpoints: Desktop, Tablet, and Mobile.
Content changes (adding/removing widgets, editing text, replacing images) apply to all breakpoints.
Layout changes (alignment, spacing, size, visibility) may be set per breakpoint but must maintain overall design integrity.

Theme & Global Controls

Theme Colors and Theme Text define global styling defaults.
All elements should use theme-driven styles unless a rule explicitly specifies an override.
Color and font consistency must be preserved across all site pages.

Connected Data

Business Info, Business Text, Business Images, and Collections must be used when applicable.
Pages requiring dynamic or repeatable content must reference connected data to ensure consistency and scalability.

System-Locked Areas

Headers and Footers cannot be replaced or structurally modified.
Breadcrumbs follow established rules for placement, visibility, and styling.

What Editor 2.0 Is Not

It is not a custom-code environment.
It is not an open, freeform layout tool—structure and hierarchy must be maintained.
It is not a direct HTML/CSS editing platform; such changes are restricted and controlled.

Additional Sections

Key Concepts

Sections : Structural containers that define vertical stacking of major content regions.
Columns & Inner Columns : Layout containers that organize content horizontally and vertically.
Widgets : Individual pieces of content or functionality (text, image, button, form, list, layout element).
Design Panel : Styling controls for spacing, alignment, backgrounds, borders, layout, and responsive adjustments.
Layers Panel : A hierarchical map of all content on the page—critical for troubleshooting layout issues.
Floating Menu : Quick-access actions for editing, rearranging, duplicating, or configuring individual elements.
Themes : Centralized system controlling global colors and typography.

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Restaurant Menu Pages

Sun, 01 Feb 2026 01:35:06 GMT

Restaurant Menu Pages

Restaurant websites require a menu experience that is fast, intuitive, and easy to browse — especially on mobile. For this reason, Hibu One Smart Sites follow a single-page anchored menu structure , where all menu categories (Appetizers, Breakfast, Lunch, Soups, Entrées, Kids’ Menu, Desserts, Cocktails, etc.) are presented on a single Menu Page , each as its own section.

This approach ensures:

Users can scroll or jump quickly between menu categories
All menu content loads at once (ideal for mobile behavior)
Clean navigation without cluttering the site with unnecessary pages
Compliance with Hibu’s rule prohibiting category landing pages that have only one subpage

The Homepage acts as the category landing page for all restaurant menu content.

Why We Do Not Create Separate Pages for Each Menu Category

While it is technically possible to create a unique page for every menu category (e.g., an Appetizers Page, a Drinks Page), this is discouraged and unnecessary for the majority of restaurants.

Why a single Menu Page is preferred

Better mobile UX — diners scroll and browse quickly rather than loading separate pages
Cleaner navigation — avoids long, unwieldy dropdowns in the Menu navigation
No repetitive backtracking — users stay on one page and jump by anchor
Faster decision-making — diners expect a full-menu view similar to digital ordering apps
Reduced page bloat — multiple thin pages dilute SEO value
Simpler content updates — all menu edits occur in one place

However, we will create individual menu pages if requested.

If a client specifically asks for separate pages (e.g., “Lunch,” “Dinner,” and “Drinks” as standalone pages), we will build them.

But clients should understand that:

It creates more pages to manage
It lengthens the navigation
It slows down mobile browsing
It does not improve SEO

The single-page anchored model remains the recommended and default format unless the client explicitly chooses an alternate structure.

Menu Page Structure

Restaurant menus must follow the order used by the restaurant itself. This is the primary rule.

Always follow the client’s menu order.

If the restaurant’s printed or PDF menu lists categories in a specific sequence, the Menu Page must mirror that structure exactly. This ensures:

Familiarity for returning customers
Accuracy across platforms (dine-in menu, take-out menu, and website)
A consistent brand experience

When the menu order is unclear or inconsistent use the following “default order” as a fallback guide:

1. Starters & Shareables

Appetizers
Small Plates
Soups
Salads
Shareable Platters

2. Signature Specials

Chef’s Recommendations
Seasonal Features
Limited-Time Offers

3. Mains

Each of these is a top-level section , not a sub-section of “Mains,” and you can position them in any order appropriate to the restaurant (e.g., Lunch before Dinner, Sandwiches before Entrées, etc.)

Lunch Plates
Optional subsets:
Midday Combos
Lighter Options
Lunch-Only Specials
Sandwiches & Burgers
Optional subsets:
Burgers
Chicken Sandwiches
Specialty Sandwiches
Bowls & Grain Dishes
Optional subsets:
Protein Bowls
Rice / Grain Bowls
Salad Bowls
Pizza & Flatbreads
Optional subsets:
Specialty Pizzas
Build-Your-Own
Flatbreads
Entrées / Dinner Plates
Optional subsets:
Steaks / Seafood
Chicken
Vegetarian / Vegan
House Specialties
Pasta Dishes
Optional subsets:
Classics
Specialty Pastas
Baked Pastas

4. Sides & Add-Ons

À-la-carte sides
Premium upgrades
Sauces & enhancements

5. Brunch / Breakfast (If Served)

Classic Breakfast
Brunch Items
Benedicts / Omelets
Morning Specials

6. Kids Menu

Kids Entrées
Kids Drinks
Kids Desserts

7. Desserts

Cakes / Pies
Ice Cream / Gelato
Specialty Sweets

8. Drinks

Non-Alcoholic
Beverages (soft drinks, tea, coffee)
Specialty drinks (lemonades, mocktails)
Alcoholic
Cocktails
Beer
Wine
Spirits / Whiskey List (optional)
Happy Hour Menu (optional separate section)

9. Catering & Family Style (Optional)

Party trays
Large-format entrées
Catering packages

Alternate Menu Hierarchies

While the default ordering works for many restaurants, certain cuisines follow established menu hierarchies that differ from the standard American format. When a restaurant’s printed menu or POS system reflects a cuisine-specific structure, that hierarchy should be used.

To support consistency, we provide reference layouts for several common restaurant types—such as Italian, Mexican, Pizzerias, Bar & Grill, Breakfast-focused restaurants, and others.

These guides outline the typical category order and naming conventions used within each cuisine and should be followed whenever the client’s own materials are unclear, incomplete, or inconsistent.

Homepage Menu Preview Blocks

Each menu category—such as Appetizers, Lunch, Entrées, Sandwiches & Burgers, Soups & Salads, Kids’ Menu, Desserts, or Cocktails—must have its own preview block on the Homepage.

Each block includes:

A headline (e.g., “Appetizers”)
A supporting image or icon , depending on the selected design style
A brief 1–2 sentence description
A “View Menu” button linking to the correct anchored section on the Menu Page

Image / Icon Requirements

If the client provides usable images, those should be used.
If no images are provided, the designer selects a representative stock image that clearly relates to the category.
If the chosen design uses icons instead of images , designers use consistent icon styles aligned with the theme.

These elements help create a clean, scannable visual overview of all menu categories.

Handling Non-Menu Core Pages

The structure above assumes that a restaurant has no additional core pages beyond its Menu Page. However, some restaurants offer high-value services that require their own standalone pages, such as:

Private Dining
Catering Services
Reservations Information
Events & Banquets
Gift Cards
Special Promotions or Seasonal Menus

When these pages exist, they must be treated as core pages.

This means:

They are not utility pages.
They must be surfaced on the Homepage , using a preview block similar to the menu category blocks.
Each block links directly to its respective standalone core page.
They appear alongside the menu category blocks to preserve the Homepage’s role as the Category Landing Page.

Example: Private Dining Block

Headline: Private Dining
Supporting image or icon
Short description of the service
Button: View Private Dining → /private-dining

This ensures that all core offerings—menu-based or service-based—are discoverable from the Homepage and properly represented in the site’s information architecture.

Homepage as the Category Landing Page

Under Hibu’s rules, a Category Landing Page must have at least two associated pages. Because all restaurant menu categories live on a single Menu Page, that page cannot serve as its own category landing page.

Therefore:

The Homepage acts as the Category Landing Page for all restaurant menu content. The Homepage must present one preview block per menu category, each linking to its corresponding anchor on the Menu Page. These blocks help diners quickly understand the restaurant’s offerings and ensure that the Homepage fulfills its role as the top-level category hub.

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Duda

Sun, 01 Feb 2026 01:24:11 GMT

Who Duda Is

Duda was founded in 2010 with a simple mission: make it easier for professionals to build fast, responsive, modern websites without sacrificing control. Over the years, Duda has become one of the leading agency-focused builders in the industry.

They’re not a hobbyist tool. They’re not a “drag-and-drop for beginners” system. They are a platform built for scale — the kind used by digital agencies, enterprise partners, and companies who manage tens of thousands of sites at once.

One fun note: The company name “Duda” was inspired by The Big Lebowski — specifically the easygoing confidence of “The Dude.” It’s fitting; the platform is built to take whatever you throw at it, adapt, and keep rolling.

Duda

Who Duda Is, and Why They Matter to Hibu

Hibu builds all Hibu One websites on the Duda platform — a professional-grade website system designed specifically for agencies, not DIY consumers. Duda gives us the foundation we need to produce high-quality, scalable websites that stay modern long after launch. Our clients get better websites, and our teams get a more reliable editor, better tools, and a platform that evolves alongside our product.

Our Relationship With Duda

Hibu’s partnership with Duda goes back nearly a decade:

2016–2019: Next Gen Sites
Our first Duda-powered sites. This was the beginning of using a component-based editor, reusable templates, and modern responsive design.
2019–2024: Smart Sites
We expanded, standardized, and matured our build process. This era brought more automation, more structured design, and stronger internal tooling.
2024–Today: Hibu One Smart Site
Leveraging Duda’s Editor 2.0, improved connected data, stronger performance, and a more scalable architecture — giving us the most consistent and adaptable system we’ve ever had.

We’ve been working with Duda since the beginning, and that long-term familiarity is part of what has shaped Hibu’s website product direction.

Why Duda Matters to Hibu

Duda allows Hibu to focus on what we do best: building results-driven websites, adding our own smart features, and delivering a managed service at scale. Because the platform is so strong underneath, our teams can spend more time on the things that matter — design quality, content accuracy, performance, connected data, and client results.

In short: Duda gives us the foundation.

Hibu turns that foundation into a full digital product.
It’s a partnership that’s made our websites stronger year after year — and it’s one of the reasons Hibu One Smart Sites continue to evolve, improve, and outperform.

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Client Logo Use Before Release Agreement

Sun, 01 Feb 2026 01:00:40 GMT

Hibu Policy

Designers may use a client’s logo before the Digital Content Release Agreement is signed only when there is reasonable, visible evidence that the client already owns and publicly uses that logo . This allows site builds to continue without delay while still protecting Hibu from improper or unauthorized use.

Purpose / Why It Matters

This policy balances build efficiency with legal and brand protection.

It ensures:

Sites can progress on schedule
Branding remains consistent with the client’s existing presence
Hibu minimizes risk around intellectual property and trademark misuse

Confirming visible, real-world usage protects both the client and Hibu.

Client Logo Use Before Release Agreement

Acceptable Assumptions

A logo may be used prior to the signed release if one or more of the following is true:

Existing Website Use

The logo appears on the client’s current or previous website.

Social or Listing Use

The logo appears on verified profiles or business listings controlled by the client (e.g., Google Business Profile, Facebook, Yelp).

Real-World Branding

The logo appears on physical or offline branding, including:
Company vehicles
Storefront or building signage
Yard signs, banners, printed materials

Uniforms and Staff Branding

The logo appears on employee uniforms, shirts, hats, or safety gear in publicly available images.

Previously Provided by Client

The client provided the same logo during a prior Hibu engagement or service.

When Not to Assume

The logo must not be used without a signed release if:

It includes imagery trademarked by another organization (sports teams, franchises, major brands)
Branding across sources is inconsistent or unclear
A third party—not the client—supplied the file, and ownership cannot be validated

Definition

A “client-owned logo” is any branding asset that the client is already using in public-facing materials—online or offline—and can be reasonably confirmed as their active business identity. When this usage is clearly documented, the logo may be used during the build phase prior to receipt of the signed Hibu Digital Content Release Agreement.

Required Designer Assumption

When using a logo under the acceptable assumptions, the designer must document:

“I used the client’s logo based on the following evidence: [specific sources].”

Examples:

“Logo appears on existing website and Google Business Profile.”
“Logo visible on truck signage and employee uniforms.”

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Audio Files

Sun, 01 Feb 2026 00:42:06 GMT

Definition

Audio includes sound-based files such as podcasts, songs, interviews, and tutorials. These files may be hosted directly on the site or embedded from supported audio platforms.

Rules & Guidelines

Maximum of 20 audio clips per site .
Supported sources: SoundCloud , Mixcloud , and MP3 uploads .
Maximum file size: 50 MB per audio file .
No background autoplay is allowed.
Hibu renames all uploaded audio files.
Clients must provide final, web-ready audio.
Audio may be added in two ways:
Uploaded audio : stored in the site’s Media Manager; width-only display control.
Embedded audio : added from SoundCloud or Mixcloud using the Audio widget.
Platform-based design options vary and may affect layout or styling.
For consistent design, all embedded audio on a site should use the same platform.

Audio Files

Hibu Policy

Hibu One Smart Sites support audio either through files uploaded to the Media Manager or through approved third-party embeds. When clients supply audio, Hibu can add it to the site by uploading the file or embedding it from SoundCloud or Mixcloud. External audio is only available in the location where it is placed and does not appear in the Media Manager.

It is expected that the Hibu design team will rename all uploaded audio files and apply alt text or descriptions where applicable.

Effective Date: February 1, 2026 Last Updated: February 1, 202 6

Service Area Pages (SAPs)

Sun, 01 Feb 2026 00:04:14 GMT

Service Area Pages (SAPs)

Hibu Policy

Service Area Pages (SAPs) are designed primarily for businesses that travel to their customers . SAPs may also be used for brick-and-mortar businesses that customers visit only when the business has Local Ranking + Hibu One and has not purchased Geo Pages. SAPs follow a dynamic page-generation model, must meet strict eligibility criteria, and must use standardized URL structure, metadata rules, and editorial guidelines.

Note: SAPs support up to 150 cities per keyword and a 60-mile radius —which is typically broader than what is appropriate for brick-and-mortar businesses. When a business requires local visibility but has only one or a few locations, Geo Pages are preferred , and Geo Pages do not require Local Ranking.

Related: Geo Pages and SAPs vs. Geos Comparison Table

Definition

A Service Area Page (SAP) is a dynamically generated, location-specific page created for businesses that travel directly to the customer’s location. SAPs are built from a Parent Service Area Page (PSAP) and then dynamically populated using Collections to create individualized pages for each target City, ST. SAPs may also be used for brick-and-mortar businesses that customers visit only when the business has Local Ranking + Hibu One and has not purchased Geo Pages.These pages are structured to appear in local search results for service-and-city combinations (e.g., “AC repair in Berwyn”).

Rules & Guidelines

Eligibility & Requirements

Must have Hibu One + Local Ranking
Must be a business that travels to customers
SAPs may be added to brick-and-mortar businesses only if:
The business has Local Ranking
The business has not purchased Geo Pages
SAPs support up to 150 cities per keyword
Default radius: 60-mile radius

SAPs and Geo Pages cannot be used together.

Purpose / Why It Matters

SAPs help service-area businesses expand their reach beyond their primary city of operation. SAPs support:

Broader local search coverage across multiple Cities
Increased visibility in service-and-city search queries
Scalable deployment of high-volume, dynamically generated pages
Centralized, controlled updates through PSAP edits
Accurate geographic targeting using dynamic text insertion

SAPs give traveling businesses consistent visibility across dozens—even hundreds—of Cities within their service radius.

How SAPs Are Generated

Parent Service Area Page (PSAP)

All Service Area Pages (SAPs) originate from a single Parent Service Area Page (PSAP).

Each primary keyword or service category is assigned its own PSAP.
For example, “Kitchen Remodeling” and “Bathroom Remodeling” are created as separate PSAPs , even when they exist on the same site and serve the same geographic areas.

Writers generate the core PSAP content via the Copy Writing Tool, including:

Page copy
Title tags
Meta descriptions

Dynamic Generation

For each city selected under a PSAP:

Generic area names are included as “City, ST.”
The Copy Writing Tool connects each City, ST to the appropriate PSAP collection
All SAPs inherit updates made to their associated PSAP
The primary keyword or service category should appear in the first H3 subheading on the page (added 4/9/2026)

SAPs are not individually edited. Each PSAP controls all content for its related SAPs.

Content Requirements

SAPs are for businesses that travel to the customer . Language must reflect service coverage—not physical presence.

Use:

“Proudly serving Berwyn, PA, and surrounding towns.”
“We come to you—serving homeowners across Berwyn and nearby communities.”
If SAPs are added to a brick and mortar
Include a unique geographic reference in body copy
Clearly state where the business is actually located
Clarify that the business serves the City, ST (not that it is located there)
“While our office is located in New Rockbridge, we proudly serve clients in Concord.”
“With locations in Cranston, Warwick, and East Greenwich, we’ve been serving the Kent County area for over 25 years.”

Avoid

“Located in [Geo Town]” if untrue
Any language that suggests a nonexistent physical office
Breadcrumbs do not display on SAPs.
Related Services links do not display on SAPs

Editing & Support

Clients may add or remove towns at any time through Support.
Content changes are made to the PSAP , not individual SAPs.
CWs must ensure all dynamic content is connected and functioning correctly.

Meta Description Tags

Meta descriptions for Service Area Pages function differently than title tags:

Only one meta description is used for the entire SAP set.
This description is added at the PSAP level in the copywriting tool and is inherited by every SAP.
CW are responsible for editing the meta description for clarity and character count .
SAP meta descriptions do not include individual city or town names.
They reflect the broader service region (ex header / main hero geo) , not a specific city–state pair.

Note: Meta descriptions do not directly influence SEO rankings. Their purpose is to increase click-through rate by providing a clear, compelling summary in search results. Because SAPs dynamically insert city and state into the title tag and on-page content, the meta description must stay general to the region — for example, “throughout the South Jersey area” or “across the DFW metroplex.”

For this reason, meta descriptions differ depending on whether the business travels to the customer or customers travel to the business.

A. Meta Description Patterns — Service-Based Businesses - Businesses that travel to the customer: HVAC, plumbers, electricians, landscapers, etc. Use one of the following patterns at the PSAP level:

Option 1
“Primary CTA [NOB] for your specific keyword phrase, specific keyword phrase, specific keyword phrase throughout the [broader service region] .”
Option 2
“Schedule your _________ (appointment, estimate, consultation, etc.) or call to speak with our team about your [keyword phrase] and related services throughout the [broader service region] .”

B. Meta Description Patterns — Brick-and-Mortar - Single Location.

Option 1
“Visit [NOB] for [keyword phrase], [keyword phrase], and [keyword phrase] at our [HQ City] location, proudly serving the [broader service region] .”
Option 2
“[NOB] provides trusted [keyword phrase] from our [HQ City] office, supporting customers throughout the [broader service region] .”

C. Meta Description Patterns — Brick-and-Mortar - Multiple locations.

Option 1
“Visit [NOB] for your specific keyword phrase, specific keyword phrase, specific keyword phrase at any of our [#] locations, serving the wider [broader service region] .”
Option 2
“Call [NOB] for your specific keyword phrase, specific keyword phrase, specific keyword phrase at our [#] locations throughout the [broader service region] .”

Title and Meta Description Formatting (SAPs)

The following metadata rules must be followed exactly.

Title Tag Requirements

SAP title tags are dynamically generated using the Collection connected to the PSAP.

To support this:

The Page Meta Title field must be connected to the appropriate Collection field (Title - KW01, Title - KW02, etc), in the PSAP
The Page Meta Title box will appear blank in the page settings UI — this is correct and intentional.
The CW is responsible for the connecting the title tag field.
QAE will confirm that this has been done correctly.

Dynamic title tags will follow the SAP formula:

Format: Keyword | City, ST | NOB
Example: Basement Remodel | Media, PA | ACE Construction & Roofing

Note: No manual editing of individual SAP title tags

SAP Hero Form Requirements

If a Service Area Page includes a hero-placed form, the form title must identify that the lead originated from an SAP. Update the standard “Hero Request Form” to:

“SAP Hero Request Form”

To apply correctly:

Unhide the form
Update the title to include SAP
Re-hide the form
The grayed-out form title confirms it is hidden and properly updated

The CW is responsible for updating this form title when preparing or editing the PSAP.

This ensures:

SAP leads are identifiable in the client dashboard
SAP submissions are distinguished from other form fills
Accurate attribution for Local Ranking performance

SAP Page URL Structure

All Service Area Pages must use the standardized SAP slug format. The URL always begins with /contact/ and follows this structure:

contact/[sap-keyword-term]/[city-st] (/city-st is dynamically inserted into slug)

Approved examples:

/contact/fence-repair-services-service-area
/contact/roof-repair-service-area
/contact/ac-repair-service-area

Notes:

“Services-service-area” is acceptable where required by the keyword structure
Keywords should use slug format (lowercase, hyphenated)

Navigation & Linking

Service Area Pages are accessed through their own dedicated SAP Directory Page , hence forth, Directory Page , which lists and hyperlinks all the services area pages alphabetically by City, ST. The Directory Page has its own unique title tag, meta description, and page URL. By default, the Directory Page uses the template-defined slug:

/serving-area

This Directory Page is linked directly from the Contact Us / Locations page.

SAPs do not appear in the Tier 1 (global) navigation.
SAPs are accessible from the Contact Us / Locations Page through a sub-nav labeled “Serving Area”
In the site footer, the phrase “and surrounding areas” is displayed:
When SAPs are active, “and surrounding areas” is hyperlinked to the serving area page ( /serving-area ).
When no SAPs are included, the phrase still appears but is not hyperlinked.

Metadata

SAP Directory Page (Serving Area Page)

Title Tag Formula (Multi-Location Businesses):

[Service] Near You in [Region] | [Key Services] + [Optional Modifier]

[Business Type] Locations in [Region] | [Primary Services]

Examples:

Dental Office Near You in the Denver Metro Area | Pediatrics

Dental Locations in the Denver Region | Braces & X-Rays

Meta Description Formula

Find a [service/business type] in (the) [Region] with [Business Name]. Visit one of our nearby locations for [top services].

Example:

Find a dental office in the Denver Metro Area with Caring Dental. Visit one of our nearby locations for family, pediatric, and senior dental care.

Effective Date: February 1, 2026 Last Updated: February 7, 202 6