Hibu DashBoard

Hibu Alternate Domain and 301 Redirect Strategy

A smooth Hibu Smart Site migration safeguards every customer touchpoint. By wiring the legacy domain into the Hibu alternate domain slot and deploying page-level 301 redirects, businesses keep organic visibility, incoming calls, and revenue right where they belong.

TLDR

Point the old domain to the Hibu alternate domain feature, enable path-level 301 redirects, and maintain the booking pipeline without disruption. The technique retains rankings, preserves backlinks, and protects user journeys throughout the domain migration.

Root-Level Forwarding Pitfalls

Most registrars forward only the base URL. Deep links fall through the cracks, triggering crawl errors. When shoppers land on missing pages, trust erodes and conversions slip away.

Typical 404 Scenarios After a Domain Swap

  • /services/hydro-jetting
  • /blog/plumbing-tips
  • /contact

Search engines react by dropping these paths from the index, dragging click-through volume down with them.

Alternate Domain Function in Hibu

The Hibu alternate domain slot connects up to ten domains, applying path-preserving 301 redirects automatically. Every historic URL travels straight to its updated counterpart, and an SSL certificate spins up without manual effort.

Ten-Domain Capacity and Practical Uses

Brand variants, retired TLDs, promo microsites—bolt them all onto the primary Smart Site to funnel equity into one authoritative hub.

Building a URL Inventory

Begin by crawling the legacy site, then merge that output with Google Search Console exports. Flag any path that once drew clicks or attracted backlinks. Prioritise the list so you handle the highest-value pages before launch and clean up the niche outliers after go-live.

Crawl Tools for Extraction

Screaming Frog and Sitebulb surface every reachable URL, while Search Console fills gaps by revealing pages no longer linked internally but still visible in search.

Prioritisation Criteria

Weight each line by sessions, inbound links, and conversion history. High-impact pages graduate to the first redirect batch; minor assets wait until core traffic is safe.

DNS Records for Seamless Redirects

Once Hibu support activates the slot, replace existing DNS values so traffic resolves to Smart Site infrastructure.

Required A-Records and CNAME Values

  • A @ → 199.180.140.11
  • A @ → 199.180.140.12
  • CNAME www → live.websites.hibu.com.

Use a 300-second TTL during rollout for quick propagation, then restore your typical value after traffic stabilises.

SSL Auto-Provisioning Timeline

As soon as the domain resolves, visiting any page triggers an automated certificate request. The lock icon appears in under three hours—no CSR, no waiting on third-party validation.

Google Change of Address Workflow

Search Console must verify ownership of both domains before the move. Once verified, submit the Change of Address form to transfer link signals to the Smart Site and speed re-indexing.

Change of Address - Google Search Console

Domain Re-Verification Methods

Add a DNS TXT record for the fastest confirmation, or upload the HTML tag if server access is still available. GA4 tag verification works in a pinch when DNS changes aren’t feasible.

Move Request Submission Steps

Inside the old property, open Settings, choose Change of Address, enter the new domain, confirm that 301 redirects fire correctly, then send the request. Google begins consolidating signals within a few days.

Post-Migration Monitoring Tasks

For the next 30 days, keep a close eye on crawl stats, index coverage, and keyword trends. Early intervention prevents minor redirect gaps from snowballing into lost revenue.

Index Coverage Signals

The “Excluded” bucket in Search Console should shrink. If “Not Found” spikes, you’ve missed paths that still need mapping.

Link Equity Tracking

Sample a handful of top backlinks in Ahrefs or Moz to confirm they now land on the Smart Site. If any still hit the registrar forwarder, fix the record or add an explicit redirect.

XML Sitemap Refresh Schedule

Generate a fresh sitemap after the final redirect wave, then resubmit it to Search Console. The updated map nudges crawlers toward new canonical paths.

Search Console Alert Filters

Enable messages for crawl issues, DNS errors, and security events. Real-time notifications let you patch problems long before users feel the impact.

FAQs: Hibu Alternate Domain and 301 Redirects

Can multiple alternate domains coexist? Yes. Smart Site accepts up to ten without conflict.

Do redirects preserve UTM parameters? Query strings pass through intact, so campaign tracking stays reliable.

How long does SSL issuance take? Usually less than three hours once DNS resolves to Hibu.

Will Google flag duplicate content? Path-level 301s consolidate signals, preventing duplication concerns.

Is extra hosting required? No. All redirects live within the Hibu platform; registrar settings are the only prerequisite.

Sources