Hostinger Website Builder

Hostinger Website Builder is a product of Hostinger, a privately held global hosting company (Lithuanian-founded, HQ registered in Cyprus). The builder began life as Zyro (launched 2019 as a Hostinger-backed side project), fully merged into and rebranded as Hostinger Website Builder by April 2024; Zyro sales/service are discontinued.

Launched 2019 as Zyro, a Hostinger-incubated drag-and-drop builder; rebranded/merged into Hostinger Website Builder by April 2024. Reporting the original product launch year per SiteVersus convention.

Fully hosted, managed drag-and-drop site builder bundled with Hostinger hosting plans. Distinct from Hostinger Horizons (AI "vibe coding" app builder) and from Hostinger's separate WordPress/shared hosting products.

A dedicated /website-builder/pricing URL returns a 404; pricing is presented inline on the main Website Builder product page.

No permanent free tier; Hostinger offers a 14-day free trial of paid plans instead.

Premium Website Builder plan, promotional price shown for long-term (48-month) commitment; includes a free custom domain for the first year. Regular (non-promo) list price is $11.99/mo; renews at $10.99/mo after the first term. See pricing.renewal_pricing_differs.

Business Website Builder plan, marked "Most Popular" on Hostinger's own pricing table; promotional price at 48-month commitment. Regular list price $18.99/mo, renews at $16.99/mo.

Business Website Builder is the cheapest plan with ecommerce (sell up to 1,000 products, 0% platform transaction fee); the Premium plan cannot sell online.

Confirmed intro-vs-renewal gap on official pricing: Premium promo $2.99/mo (48-month term) renews at $10.99/mo; Business promo $3.79/mo renews at $16.99/mo, both roughly 3-4x the promotional rate. Promotional prices also require paying for the full multi-year term upfront (e.g., $143.52 or $181.92 at once), not a low recurring monthly charge.

Drag-and-drop editor built around sections and pre-designed blocks/elements within a fixed template structure; not a fully freeform absolute-position canvas.

Click-to-edit text and elements directly on the canvas, consistent across desktop and mobile browser editing.

Automatic backups/versions are created on publish and on each subsequent update (kept for 30 days), viewable and restorable from a backup manager panel. This functions as version history, though Hostinger's own docs frame it as "backups" rather than a dedicated undo/history feature, and there's no confirmed granular in-session undo stack.

Could not confirm continuous autosave-while-editing from official docs; confirmed automatic backup snapshots occur on publish/update (see editor.undo_revision_history), but whether in-progress edits autosave before an explicit save/update action was not verified in official sources.

Mobile editing works via a responsive browser-based editor (no separate app required, described by Hostinger as feeling app-like) that supports full page building, plus a dedicated Hostinger mobile app (iOS/Android) for analytics, basic content edits, and blog post management; deeper design/ecommerce management remains desktop-oriented.

Confirmed: once a template is chosen and the site created, you cannot switch to a different template while keeping content structure. Changing designs requires building a new site with the new template and manually re-adding/transferring content (or disconnecting/reconnecting the domain), a known limitation shared with several hosted builders (e.g., Wix).

Editorial judgment: AI site generation (describe your business, get a starter site) plus a simple drag-and-drop block editor make first-site setup fast for non-technical users; the tradeoff is very limited advanced control (no template switching, no robots.txt/canonical, basic collaboration), which keeps the learning curve low precisely because there's less to learn.

Hostinger consistently advertises "300+" designer-made templates across ~20 categories (portfolio, business, ecommerce, blog, resume, wedding, restaurant, etc.) on its own marketing pages.

Could not confirm from official Hostinger docs in this research pass whether arbitrary custom font file upload is supported (vs. a curated font library only). Flagging null rather than guessing; the built-in font library is extensive but a dedicated custom-font-upload feature page was not found.

Site is auto-optimized for mobile, but the builder provides a distinct, separately editable mobile version/view (adjust layout, hide elements, reorder) rather than a single fully-automatic responsive render or a full multi-breakpoint system with cascading custom breakpoints.

Custom CSS can be added via the Custom code integration field (placed in the document <head> using <style> tags); available without an explicit higher-plan gate documented, though it does require a published site with a connected domain in practice for most custom-code use cases.

Custom JavaScript can be embedded via the same Custom code / Embed code mechanism (script/iframe/noscript tags placed at end of body, or head-targeted with a data-render-head attribute); no plan-specific gate was documented for this feature itself.

Editor includes native style controls covering colors, fonts, buttons, and animations as part of standard site customization.

Site-wide style settings (colors, fonts, buttons) are configurable at the site level and applied across pages, though this is template-bound rather than a formal design-token system.

Editorial judgment: the block/section-based editor, combined with a hard template lock-in (no safe template switching) and a curated template library, makes this one of the more constrained builders in the comparison set, closer to Squarespace/Weebly than to freeform tools like Wix Editor or code-first platforms.

Website Builder plans bundle managed Hostinger hosting; there is no unbundled "builder-only" SKU.

The builder produces a site that runs only on Hostinger's platform; no mechanism exists to self-host or export the built site to run elsewhere (see ownership.design_export).

Fully hosted SaaS builder; all infrastructure and optimization (CDN image handling, WebP conversion, etc.) is automatic and, for Website Builder specifically, explicitly cannot be modified by the user (in contrast to self-managed WordPress/PHP hosting on the same platform, where such settings are togglable). No plugin/theme/core update surface is exposed to the site owner.

Hosting plans include CDN as part of the bundled infrastructure per Hostinger's own hosting plan feature lists.

Unlimited free SSL certificates included on all plans.

No static HTML/asset export of the built site; leaving the platform requires manual content copy (text/images) or a lossy export to WordPress that drops style, layout, store, integrations, forms, and SEO settings (see ownership.design_export).

May 2026 CrUX data via HTTP Archive CWV Technology Report API (technology 'Hostinger Website Builder'): combined 58.5% (desktop 1,124/1,440 = 78.1%, mobile 4,546/8,258 = 55.0%). Mobile-heavy sample pulls the combined figure down. Legacy 'Zyro' tag is stale (last data April 2023) and excluded.

Hostinger's CDN automatically converts images to WebP ('approximately 30% smaller than JPEG without losing quality') and automatically determines the best image width/quality for desktop vs. mobile; for Website Builder specifically this is unconditional and cannot be modified by the site owner (unlike WordPress/PHP hosting on the same CDN, where it is a togglable setting). Note: format conversion and compression happen at the CDN delivery layer, not the editor/media-library level.

Confirmed automatic device-appropriate image sizing ('images automatically adapt, slightly stretch or shrink, depending on your website visitor's device properties') plus automatic CDN-level WebP conversion and automatic width/quality selection per device. LQIP/blur-up placeholders and explicit srcset/sizes markup were not confirmed by name in official docs.

Could not confirm explicit official documentation of lazy-loading behavior for images/media specifically. Given automatic performance optimization is claimed broadly, lazy loading is plausible but not directly verified in official sources during this pass.

No official documentation found giving site owners direct cache-control configuration for Website Builder sites; caching/performance is handled automatically by the platform with no owner-facing controls identified.

Native Analytics panel (not just a GA integration) shows sessions over time, total sessions including bot traffic, unique visitors, sessions by country, and desktop vs. mobile breakdown, plus dashboard eCommerce metrics (Total Sales, Orders, Average Order Value). This is real built-in analytics but limited to traffic/geo/device/ecommerce summary stats, with no funnels, custom events, or traffic-source/referrer breakdown found, placing it above 'none' but below a full native analytics suite.

Hostinger's own support article states the built-in analytics tool 'doesn't require visitor's consent and is irrelevant to mention in your Privacy policy' because it doesn't collect personal data and is used only for traffic overview, not shared or connected with data from other websites, a direct official statement of cookieless/no-consent-banner analytics by default.

No official documentation, blog post, or public roadmap item mentions session recording/replay for Website Builder. The only user-behavior-adjacent tool is the AI Heatmap (see analytics.heatmaps), which explicitly does not track real sessions.

Hostinger's official 'AI website heatmap' tool is a standalone tool (alongside its other AI tools like image upscalers/logo makers), not embedded in the Website Builder editor, and it explicitly does NOT track actual user clicks or scrolls; it predicts attention hotspots on an uploaded screenshot using a model trained on real user behavior data. Closest enum fit is 'app' since it's a separate tool rather than in-product tracking, though it is prediction-based design guidance rather than real visitor heatmap telemetry, a materially different category than a typical bolted-on heatmap service.

Per-page and per-post meta titles/descriptions editable via SEO settings, with an AI SEO Assistant to help draft them; recommended title length up to 60 characters.

Per-page URL editing is available within SEO/page settings.

Confirmed via Hostinger's own support documentation on common Google Search Console warnings: Hostinger Website Builder has no built-in 301 redirect management. Hostinger's own guidance for fixing duplicate-content/canonical GSC warnings is to use a third-party workaround (Cloudflare Page Rules), not a native feature.

Confirmed via official Hostinger support content: canonical tag control is explicitly called out as not yet supported on Hostinger Website Builder, contributing to "Duplicate without user-selected canonical" warnings in Google Search Console, which Hostinger recommends resolving via external (Cloudflare) redirects instead.

Confirmed via official Hostinger support documentation: "Websites created with Hostinger Website Builder don't have robots.txt files." This is a documented, verified absence, not an assumption. Note this is distinct from the separate Hostinger Horizons product and from an opt-in llms.txt toggle, which IS available on Website Builder (Website Settings > General > Web2Agent > Enable LLMs.txt).

Sitemap auto-generated and auto-updated on every site update, available at domain.tld/sitemap.xml with no manual configuration required or offered.

No official Hostinger documentation found describing automatic or manual JSON-LD/schema.org structured data output for Website Builder pages, products, or blog posts. Given the platform doesn't support canonical tags or robots.txt either, this is consistent with a generally thin native technical-SEO layer; flagging as a verified-absence-by-omission rather than an explicit "not supported" statement, since no official source directly addresses it either way.

The built-in multilingual feature (duplicates pages/content per added language, plus an HTML lang attribute setting) does not include automatic hreflang tag generation per official/community-verified behavior; third-party tools (e.g., Linguise) are positioned specifically to add hreflang support that the native builder lacks.

SEO settings include preview image / social share controls alongside meta title and description per Hostinger's SEO settings documentation (referenced as "preview images" in related outdated-metadata support content).

Per-page "Hide from search engines" / search visibility toggle is available in page SEO settings; enabling it also removes the page from the sitemap.

Image alt text is configurable per image element as part of standard SEO settings.

Built-in blog engine with block-based post editor and categories; explicitly described by Hostinger as covering "blogging basics."

No official documentation of a custom content type / collections system (comparable to Wix CMS or WordPress custom post types) was found for Hostinger Website Builder; the platform's structured content is limited to fixed built-in types (pages, blog posts, store products).

Blog posts support an unlimited number of categories (multi-category assignment supported); however, official docs confirm blog post tags are NOT supported, a notable gap versus most competitors' full category+tag taxonomy.

Blog posts can be scheduled for future publication via a toggle in post General settings.

Automatic backups on publish/each update, retained 30 days, restorable from a version list; functions as a content revision/rollback mechanism (see editor.undo_revision_history for detail).

Could not confirm per-author attribution/profiles for blog posts (vs. simple multi-collaborator site access) from official docs in this pass. Collaborator access exists at the whole-site level (see collaboration.roles_permissions) but a distinct blog-author-profile system was not verified either way.

Could not confirm from official documentation whether Hostinger Website Builder blogs generate an RSS feed. Flagging null rather than guessing.

No official documentation of a public content API for Website Builder was found; the integrations support page lists only marketing/analytics script integrations (Google Analytics, Hotjar, Facebook Pixel, GTM, AdSense, AdMob, WhatsApp, custom code), not a content read/write API.

Native drag-and-drop contact form element/section built into the editor; submissions land in account email and are viewable in Website Settings > Form Submissions, with automatic integration into Hostinger Reach (email marketing tool). No official source states this is gated to a specific plan tier, unlike store/ecommerce features which are clearly Business-tier only.

Official support confirms per-page password protection exists (a single shared password per page, different passwords/designs per login area), but this is access-restriction, not true membership functionality (no individual user accounts, registration, or tiered access levels). With no plugin ecosystem (closed hosted builder) and no separate membership app confirmed, 'no' is the closest fit for genuine membership/gated-content support.

Built-in online store module included on the Business Website Builder plan and above; not a bolt-on plugin.

Digital product sales supported with automatic delivery/download email on purchase.

No native subscriptions/recurring billing support was confirmed for the standard Hostinger Website Builder store; recurring/subscription payment functionality is documented for the separate Hostinger Horizons product, not the Website Builder ecommerce module.

Confirmed limitation: a store can be set up with only one selling currency (tied to the connected payment gateway), not simultaneous multi-currency checkout.

No native point-of-sale capability; confirmed as a gap versus competitors like Shopify that offer built-in POS/omnichannel selling.

Native automated abandoned-cart reminder emails included in the store toolset.

Exporting to WordPress carries over regular pages, text, and images/files, but explicitly does NOT carry over site style/layout, the online store, integrations, forms, form submissions, or SEO settings. Otherwise, content must be copied manually (select/copy text, right-click-save images); there is no bulk structured export (e.g., CSV) confirmed for products/blog posts as some competitors offer.

Confirmed no mechanism to export the built site's design, layout, or code to run elsewhere; leaving the platform means manually recreating the design on a new system. Builder-to-builder account transfers are also confirmed unavailable (sites built with Website Builder or Horizons cannot even be moved between Hostinger accounts).

Domains registered or connected through Hostinger are portable subject to standard registrar transfer rules; the free first-year domain applies only to new registrations through Hostinger.

The built site cannot run off Hostinger's platform; this is the same architectural lock-in pattern as hosting.self_host_option and ownership.design_export.

No public content API exists for programmatic read/write access to pages, blog posts, or store data (see content.content_api).

Editorial judgment: no self-hosting, no design/site export, no template switching, a lossy one-way WordPress export path that drops store/forms/style/SEO settings entirely, and no full content API combine to make this one of the highest lock-in risk platforms in the comparison set, more restrictive than Wix (which at least offers CSV export of structured data) and comparable to or worse than Squarespace.

No official public API documentation for Hostinger Website Builder was found; Hostinger's developer-facing APIs (documented separately) cover hosting/VPS/DNS account management, not Website Builder site content.

No native webhook trigger/receiver system documented for Website Builder itself; any "webhook" workflows found in research referred to generic Zapier Catch Hook usage on the Zapier side, not a Hostinger-native webhook feature.

Custom HTML/CSS/JS embeddable via the Integrations > Custom code field (head-targeted for meta/link/style tags, body-end for script/iframe/noscript), no plan-specific gate documented.

No CLI or local development tooling exists for Website Builder; it is a browser-only hosted editor.

Zapier connectivity exists via generic webhook catch/send patterns (Webhooks by Zapier), rather than a dedicated official Hostinger Website Builder Zapier app with native triggers/actions. No official Make.com integration was confirmed.

AI website generator builds a full starter site (including product pages, forms, booking features per Hostinger's own description) from a natural-language business description.

AI text tools generate/edit page copy, product descriptions, blog posts (up to ~2,000 words, multiple tone options), and emails.

AI Image Generator (text-to-image) and AI Logo Maker; image generation became free (credit system removed) as of September 2025 per Hostinger's own product updates.

AI SEO Assistant helps generate SEO titles, meta descriptions, and keywords directly within SEO settings.

No robots.txt access, no canonical tag control, no structured data/schema markup found documented anywhere, and the llms.txt toggle (Web2Agent) is a single binary on/off switch with no configuration of what gets included, no per-page control, and no granular AI-crawler management. AEO fundamentally depends on crawlability control, structured markup, and canonicalization, none of which Website Builder offers beyond the one-click llms.txt flag; it has an emerging feature but lacks the technical SEO substrate that makes AEO durable.

Confirmed: Website Settings > General Settings > Web2Agent > toggle on 'Enable LLMs.txt', then publish. Hostinger's support article gives a dedicated Website Builder path distinct from its WordPress instructions.

Web2Agent is an enablement feature, not a control feature: it respects robots.txt/llms.txt standards but provides no interface for configuring robots.txt directives and no per-bot controls for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, or CCBot; it is a single on/off toggle for publishing the llms.txt discovery file, not a crawler access gate. Combined with the confirmed absence of any robots.txt access on Website Builder, there is no mechanism to differentiate between AI crawlers.

Hostinger does operate an official MCP server (hostinger/api-mcp-server), but it is scoped to general account/infrastructure management (Websites, VPS, Domains/DNS, Email Marketing, Subscriptions, Ecommerce) for sysadmin-style automation via AI coding assistants, not a Website-Builder-specific content/design MCP server with tools for building or editing Website Builder pages. Hostinger Horizons (a separate AI app-builder product) has its own distinct MCP integration; neither counts as a Website Builder feature.

Website collaborators can be invited to a single site, but confirmed to all share the same editing access level rather than granular per-role permissions (contrast with Hostinger Horizons, which does have Owner/Administrator/Editor/Viewer roles; that granularity is NOT present in the standard Website Builder).

Official current pricing page states Premium plan includes up to 3 sites and Business plan includes 50 sites, both hard numeric caps under one subscription, not uncapped.

Could not confirm true real-time simultaneous multi-user editing on the same site from official documentation. Flagging null rather than guessing.

No native editorial review/approval-before-publish workflow was found; all collaborators share the same edit/publish-level access (see collaboration.roles_permissions), which is inconsistent with a formal approval gate.

Editor supports a preview mode before publishing plus a backup/version history to roll back after the fact, but there is no confirmed separate persistent staging environment/URL distinct from the live site.

Could not confirm in-editor commenting/annotation functionality for Website Builder from official docs in this pass.

No confirmed audit log of who made which change; the backup/version system records save/update snapshots but official docs do not confirm per-collaborator attribution logging (contrast with Wix's Site History, which explicitly attributes changes to a collaborator's email).

Editorial judgment: Hostinger's Help Center has extensive, well-organized, and generally current articles covering the builder in detail (this research relied heavily on it), including candid documentation of the platform's own limitations (e.g., the GSC-warnings article plainly states no robots.txt/canonical support). That candor and coverage keep it out of "thin," but occasional stale/conflicting content (e.g., some articles conflate Website Builder with Horizons) caps it below "excellent."

Automatic backups created on first publish and on every subsequent site update, retained for 30 days, restorable via a backup manager in the editor sidebar; restoring loads the version into the editor, and changes go live only after re-updating.

Built-in multilingual feature: adding a language duplicates existing pages/content into that language for manual (or AI-assisted) translation; not automatic machine translation of the whole site out of the box.

Per-language content duplication provides a structured (manual) translation workflow; official docs note translation itself is manual or via external tools (Google Translate/DeepL) rather than one-click native machine translation, and products can also be managed per language.

Per-page HTML lang attribute is configurable, but automatic hreflang tag generation for multilingual pages is not natively supported (confirmed gap, see seo.hreflang); third-party tools like Linguise are marketed specifically to add hreflang and multilingual sitemap support that the native builder lacks.

Could not confirm from official Website Builder documentation whether the editor/output supports RTL (right-to-left) page layout for languages like Arabic or Hebrew. The Hostinger hPanel account dashboard is available in Arabic/Hebrew, but that is a control-panel localization, not confirmation of RTL site-content layout support in the builder itself. Flagging null rather than guessing.