Weebly

Acquired by Square, Inc. in June 2018; Square rebranded to Block, Inc. in December 2021. Weebly's own help center maintains a 'Weebly and Square FAQ', and Weebly signup now routes through Square account creation.

Founded by David Rusenko, Chris Fanini, and Dan Veltri at Penn State; private beta launched September 2006.

Proprietary, closed-source hosted SaaS; no source code is distributed or licensed.

Square directs genuinely new ecommerce-focused signups to Square Online instead; Weebly is positioned for legacy/simple use cases, not growth.

Shopping cart and 'unlimited items' are included even on Free, unusually generous vs. competitors that gate ecommerce entirely behind paid tiers.

Personal plan: $13/mo billed annually; $16/mo if billed month-to-month. Cheapest plan that allows a custom domain.

Professional plan: $15/mo annual ($20/mo month-to-month); adds advanced site stats, branding removal, and password protection; positioned as the mainstream tier.

Ecommerce (shopping cart, unlimited items) works on every plan including Free; $13/mo Personal is the cheapest tier that pairs it with a custom domain. All non-Performance plans still carry a 3% transaction fee on top.

Free and Personal plans both display Square/Weebly ads; branding removal starts at Professional.

Standard annual-vs-month-to-month spread (e.g., Personal $13/mo annual vs $16/mo month-to-month); no evidence of an intro-rate-that-jumps-at-renewal beyond this.

Applies to annual (non-month-to-month) paid plans; cancel within 30 days of activation or renewal for a full refund.

Drag-and-drop 'elements' (text, photo, video, etc.) are placed within stacked full-width sections; not a fully freeform canvas like Wix or Webflow.

Click-to-edit text and elements directly on the canvas.

Could not verify a page/site-level version-history or rollback feature from official sources; only a manual ZIP 'Archive' backup exists (not true revision history). Setting null rather than guessing.

Editor saves changes automatically as you work; a manual Publish step pushes changes live.

The Weebly mobile app was removed from the App Store and Google Play on December 1, 2025 (announced to customers by email, discussed on Square's official developer forum); sites are now manageable only via desktop browser.

Switching themes generally preserves page content and images (header images are the main exception); replacing an individual section layout, however, does wipe that section's content first.

Editorial: simple drag-and-drop, section-based model with minimal configuration; easier to pick up than Webflow or WordPress but slightly less immediate than Squarespace's more opinionated flow.

Weebly does not publish an official template count, and the public theme gallery (weebly.com/themes) requires login to browse; no countable public catalog like Wix or Squarespace. Third-party estimates range widely (50-350), so left null rather than guessing.

Not exposed as a native UI upload option; requires manually uploading font files (.eot/.ttf/.woff/.woff2) into the theme's Code Editor asset folder and referencing them in custom CSS; a developer workaround, not a point-and-click feature.

Themes are responsive by default with no visible per-breakpoint editing controls in the standard editor.

Available on all plans via Theme > Edit HTML/CSS (Code Editor).

JS can be added via the Embed Code element ('Add 3rd party embed code' is listed on every plan including Free in the official pricing table) and via site- or page-level header/footer code fields under Settings > SEO.

No native scroll/interaction animation tools in the core editor; animation (e.g., 'Animator', 'Anchor') is only available via third-party App Center apps.

No dedicated global design-tokens/style panel (like Squarespace's Style Editor); the official customization path for theme-wide changes is raw HTML/CSS editing via the Code Editor, with no structured global-styles UI documented.

Editorial: section-based editor with a fixed element set and no freeform canvas; flexibility beyond the theme's structure requires hand-written CSS/JS workarounds.

Closed hosted platform; the official backup/Archive doc confirms the only takeaway is a static ZIP that cannot be re-imported, with no supported path to run the site elsewhere.

Fully hosted SaaS with no self-hosting option (hosting.self_host_option is false); Square manages all platform software, security patching, and infrastructure, with no owner-facing update or maintenance responsibility.

Could not confirm a specifically-named CDN offering from official Weebly/Square sources; left null rather than assume.

Listed as 'Free SSL Security' on every plan including Free.

No published uptime SLA or guarantee found; Weebly's Terms of Service instead disclaim warranties that the service will be uninterrupted or error-free.

Settings > General > Archive emails a ZIP of static HTML/CSS/images, but explicitly excludes blog posts, store/product data, and some interactive elements (contact forms, slideshows); a partial static snapshot, not a full portable export.

May 2026 CrUX data via HTTP Archive CWV Technology Report API: 46.0% of 32,673 origins with good CWV (desktop 55.8%, mobile 40.7%). Report technology name: 'Weebly'.

Re-checked with the automatic/manual/no framing: Weebly's own image-optimization blog post instructs site owners to manually resize images before uploading and offers no mention of automatic server-side compression, resizing, or next-gen format (WebP/AVIF) conversion. That reads more like 'no' than 'automatic', but no official doc explicitly states images are left untouched either, so still unverifiable as a firm enum value. Left null rather than guess.

No official documentation found confirming srcset/sizes generation or automatic modern-format delivery; the official image-optimization guidance is entirely about site owners manually resizing files before upload, with no mention of server-side responsive-image handling. Same unverifiable gap as performance.image_optimization. Left null rather than guess.

Could not verify from official sources whether images are lazy-loaded by default. Left null rather than guess.

Official hosting page describes fully managed, distributed infrastructure with no owner-facing cache, CDN, or infrastructure controls documented.

The dashboard's Insights section is a genuine built-in analytics product, not a bolted-on widget: Traffic (page views, unique visitors, top pages, search terms, referring sites), Sales, and Marketing summaries, available on every plan. 'Advanced Site Stats' is called out as a distinct Professional-tier upsell in the pricing table, but the official Insights help doc describes a full traffic dashboard already present below that tier, so the free/basic tier is 'native', not merely 'basic'.

The official Insights help doc states unique-visitor and page-view counts are calculated using 'a front-end tracking method similar to the one used by Google Analytics', i.e. client-side/cookie-based tracking, not a cookieless server-side model. Weebly's own privacy documentation also directs site owners to install a third-party cookie-consent app (Cookiebot etc.) for GDPR compliance, confirming cookies are in play.

No native session-replay/recording feature in the official Insights dashboard or features page. Third-party App Center listings for tools like Smartlook and Mouseflow exist, but new App Center developer/app submissions have been frozen since February 2020 (per extensibility.app_marketplace_size), and no official Weebly-first-party session-replay app was confirmed, so scored as 'no' rather than 'app'.

No native heatmap feature in the official Insights dashboard or features page, and no first-party Weebly heatmap app could be confirmed on official sources given the App Center's frozen submission pipeline since February 2020.

Per-page 'Page title' and 'Page description' fields under SEO Settings for standard pages, product pages, blog posts, and storefront pages.

Native 301 redirect tool under Settings > SEO > Add Redirect; only works for pages that keep the same domain used previously.

Could not verify a manual canonical-tag override in official docs; Weebly likely auto-generates canonicals but no site-owner control was confirmed. Left null rather than guess.

Auto-generated on publish at /robots.txt, editable by the site owner; default allows full indexing.

Auto-generated and auto-updated at /sitemap.xml on every new page; referenced automatically in robots.txt.

No official documentation of automatic schema.org markup found; JSON-LD can be manually added via header/footer code injection or the Embed Code element.

No native multilingual/hreflang support; multilingual apps in the App Center (e.g., Weglot) are the only path, and none was confirmed to manage hreflang natively.

Could not verify explicit Open Graph tag controls (custom OG title/image) beyond the standard page title/description fields in official docs. Left null rather than guess.

No official documentation found confirming a per-page noindex toggle. Left null rather than guess.

Image Alt Tags and Captions are editable in the editor per official SEO guidance.

No native custom content types/collections (like Webflow CMS Collections); Weebly's dynamic content is limited to blog posts and store items. Workarounds involve external databases or misusing the blog as a generic content store.

Blog posts support categories and tags; store items support categories.

Blog posts can be scheduled to publish automatically at a chosen date and time via Post Options.

Could not verify a blog-post or page revision/rollback history feature from official sources. Left null rather than guess.

Multiple collaborators can be invited to edit a site; granular per-page restriction requires a paid plan.

Blog pages only (not site-wide); feed available at /feed/ off the blog page URL.

A Platform API (OAuth2, REST, webhooks) exists for third-party App Center apps, but new developer-account/app registrations have been paused since February 2020; not a general-purpose content API for site owners.

The Contact Form element is a standard drag-and-drop editor element (with Survey and RSVP variants) documented with no plan restriction; the official help topic describes adding, deleting, and customizing fields, plus Google reCAPTCHA and GDPR opt-in options, with entries emailed and stored on the dashboard. Consistent with the drag-and-drop editor itself being available on Free.

Distinct from the single shared-password site/page protection described in collaboration.staging_preview: Weebly's Membership feature (Professional and Performance plans) is a true native member system with individual sign-up/login, member groups/tiers, and per-page access restriction by member or group. Not as full-featured as Wix or Squarespace member areas (no native paid-membership tiers; members and store customer accounts can't be active simultaneously), but it is a first-party feature, not an App Center plugin.

Shopping cart, inventory management, and 'unlimited items' are built in on every plan including Free.

Listed as 'Digital Goods' on Personal plan and above.

Recurring/subscription payments are available via the App Center 'Payment Button' app (Stripe/PayPal subscriptions), not as a native checkout feature.

Store operates in a single currency at a time, set under Settings > Checkout; no native multi-currency checkout. Third-party currency-converter widgets only display an estimated conversion, they don't process multi-currency payments.

Via Square POS integration (Weebly + Square), given common ownership.

'Abandoned Cart Emails' listed only on Professional and Performance plans.

The Settings > General > Archive tool exports a ZIP of static pages/images, but excludes blog posts, store/product data, and some interactive elements. Store data can be separately exported as CSV.

Static pages can be archived as HTML/CSS, but the exported ZIP cannot be re-imported into Weebly or another builder, some elements (forms, slideshows) break outside the Weebly environment, and blog/store content is excluded entirely.

Official help documents unlocking the registrar lock and generating an EPP/authorization code to transfer a Weebly-registered domain to another registrar; externally-purchased domains can be connected or repointed freely.

No supported migration path; the official Archive export is a partial static snapshot that cannot be re-imported into Weebly or another host, and dynamic elements (forms, slideshows, blog, store) do not function outside Weebly.

The Platform API exists for App Center integrations (site data, ecommerce products) but new developer/app registrations have been paused since February 2020, and it is not positioned as a general full-content-access API for site owners.

Editorial: no self-hosting, only a partial static export that excludes blog/store data and can't be reimported anywhere, a frozen developer/app platform, and a vendor that is openly steering new users to a different product (Square Online). Migrating off Weebly means manually rebuilding.

OAuth2/REST Platform API exists for sites, blogging, and commerce, but is oriented toward App Center apps rather than direct site-owner use, and new developer registrations have been frozen since Feb 2020.

'Add 3rd party embed code' is listed on every plan including Free in the official pricing table; header/footer code injection is available under Settings > SEO.

No CLI or local dev tooling found in official developer documentation.

Third-party App Center apps (e.g., Automate.io) connect Weebly to 100+ apps; native Zapier support not separately confirmed.

Official features page lists the complete feature set (builder, ecommerce, themes, SEO, blogging, hosting) with no AI site-generation tool; Weebly has not adopted AI-assisted setup the way Wix (ADI) or Squarespace has.

No AI writing assistant anywhere on the official features page; consistent with Weebly's maintenance-mode status and lack of recent feature investment.

No AI image generation/editing tools in the officially documented feature set.

SEO tooling is limited to manual title/description/alt-text fields and a static checklist guide; no AI-driven SEO suggestions found.

Editorial: schema.org structured data is manual-JSON-LD only with no automatic markup (seo.structured_data), canonical tag control and Open Graph/social meta control are both unconfirmed from official sources (seo.canonical_control, seo.social_meta_og both null), and there is no llms.txt support or dedicated AI crawler controls (see ai.llms_txt, ai.crawler_control below). Combined with a notably poor 46.0% Core Web Vitals pass rate (performance.cwv_pass_rate), a maintenance-mode product with thin, inconsistent documentation, and zero native AI-era SEO investment (ai.seo_assist is false), Weebly sites carry real structural and technical headwinds against being reliably parsed, extracted, and cited by AI answer engines relative to platforms with automatic schema and confirmed OG/canonical control.

No mention of llms.txt generation or serving in official Weebly features, SEO, or developer documentation; consistent with the platform's broader lack of native AI investment (ai.site_generation, ai.copy_assistant, ai.image_tools, ai.seo_assist are all false).

No dedicated per-bot AI crawler toggle (unlike Square's other builder, Squarespace, which added a Settings > Crawlers 'Artificial Intelligence Crawlers' switch); Weebly site owners can only manage AI bots the same way as any other crawler, by manually editing the auto-generated, editable robots.txt file (seo.robots_txt_editable), which is a real but blunt lever rather than a purpose-built AI control panel.

Square (Weebly's owner) publishes an official MCP server at developer.squareup.com, but it is scoped strictly to the Square commerce API platform.(customers, orders, items, catalog, payments); it provides no access to Weebly site content, pages, or site management, and no Weebly-specific MCP server or AI-agent integration was found on official sources.

Free plan only allows inviting collaborators with full administrator access to the entire site; paid (Professional+) plans add page-level restriction, dashboard-only access, and disabling publish rights; still not a granular department/role system.

A single Square/Weebly account can hold up to 10 separate site slots, but each site is its own independent build with its own separate subscription; premium features (custom domain, branding removal, stats, etc.) must be purchased per site rather than shared across sites under one plan. Scored 'single' because there is no multi-site management under one subscription the way some platforms bundle it.

Multiple users can edit simultaneously; the editor shows which pages others are actively editing to avoid conflicts.

No native approval/review-before-publish workflow found; users have requested this in official comments without it shipping.

A Preview button next to Publish shows the draft site before going live (some features like ecommerce don't render in preview); no dedicated staging environment exists; the officially suggested workaround is publishing behind a site password.

The official collaborative-editing announcement documents the full collaboration feature set (invites, roles, concurrent editing) with no in-editor commenting/annotation; commenters requested review features without them shipping.

Could not verify an activity/audit log for team actions from official sources. Left null rather than guess.

Support windows are business hours (commonly cited as 6am-6pm PT daily), not 24/7.

Editorial: official help center content is inconsistent in depth, many pages are thin or redirect-heavy, and several help topics (robots.txt, payments) render as titles with little substantive body content; consistent with a product in maintenance mode with reduced documentation investment.

Only a manual, site-owner-initiated Archive/ZIP export (Settings > General); no automatic scheduled backup or one-click restore feature found.

No native multi-language site builder; requires third-party App Center apps (Multilanguage, Weglot, Localizer, Linguise).

No native translation management workflow; the official App Center listing shows multilingual support comes from third-party apps (Multilanguage, Weglot, Localizer) that run their own translation workflows outside Weebly.

Multilingual sites exist only via third-party App Center apps per the official listing; no native per-locale URL structure or hreflang management; localized SEO depends entirely on the chosen app's own handling.

Could not verify native RTL language/layout support from official sources. Left null rather than guess.