Odoo Website Builder: design pages, themes, forms and SEO without code

What the Odoo website builder actually is

The Odoo website builder (the Odoo Website app) is the tool for creating and managing a website in Odoo. It provides tools to design, publish, and maintain web pages without advanced technical skills, customize layouts, add multimedia, and integrate with other Odoo apps to expand functionality.

Official Odoo Website documentation is organized around three areas: Web design (building blocks and website themes), Structure (website pages, menus, and search engine optimization), and Configuration (domain names, Google Search Console, a cookies bar, translations, multiple websites, forms spam protection, and CDN).

For an SME, this matters because the website is not a separate tool sitting next to your ERP—it is part of the same Odoo database. A form filled in by a visitor can create a CRM opportunity, a Helpdesk ticket, or a Project task directly, with no middleware to maintain. The same product master that drives inventory and POS can power the shop catalog when eCommerce is installed.

Practitioners often discover the Website app only after they already run Odoo for finance or warehouse. The practical upside is the reverse of a typical SaaS website stack: instead of bolting CRM and inventory onto a storefront later, the storefront already shares contacts, stock, prices, and orders with the rest of the business.

Odoo markets Website as free forever on the One App Free plan for Odoo Online (hosting, support, and maintenance included; no ads). A free custom domain registration is offered for the first year on eligible Online databases (one new domain per client), after which renewal follows the registrar rate via Odoo’s Gandi partnership—confirm current eligibility on the domain-names documentation before planning a launch budget.

The drag-and-drop editor and building blocks

Building blocks (also called snippets) are how users design and lay out pages in the Odoo website builder. To add one, open a page, click Edit, then drag and drop the desired building block into place. When you click a Categories block, a popup lets you pick a template for that category; a search bar in the Insert a block popup helps find a specific snippet.

There are two types of block: Categories blocks (containers / structure) and Inner Content blocks. Inner Content blocks—such as videos, images, social media buttons, and embed code—can only be placed inside Categories blocks. Some blocks, like the Products block, require their respective application or module (such as eCommerce) to be installed first. You can also add blocks on the login page by opening /web/login from the site.

Most blocks support Grid or Cols layouts from the Style tab. Grid lets you reposition and resize elements by drag-and-drop; Cols sets how many elements sit per line (mobile defaults to one column for readability—toggle the mobile icon in the editor to adjust). Backgrounds can use color, image, video, or shape overlays; turquoise borders resize vertical spacing; chevrons reorder blocks or columns.

Operator tips that save rework: save a finished block with the floppy-disk icon on the Style tab so it reappears under Custom in Categories; create anchor links with the link control on a block so menus and CTAs jump to a section; duplicate blocks before experimenting so live pages stay stable. Odoo 19 continues the blocks model with updated snippet templates, clearer labels/tags on dynamic snippets in the selection dialog, and marketing-oriented sections (headers, testimonials, pricing, carousels). Treat partner “what’s new” posts as orientation and verify behavior against the current building-blocks documentation.

Themes, colors and responsive layout

In the Odoo website builder you can switch themes at any time from the Theme tab of the editor (Edit, then Theme, then Switch Theme). Hovering a theme shows an extended preview, and clicking applies it. If no theme is chosen at first-run setup, the default theme is used.

Theme colors consist of three main colors plus two light and dark colors. The editor offers Solid or Custom (#HEX or RGBA) color picking and auto-generates Color Presets from a chosen palette, so brand alignment does not require custom CSS for most SMEs. Odoo’s product page also emphasizes free-to-use Unsplash imagery, shapes, animations, and device-aware visibility controls so you can hide or show blocks on mobile versus desktop.

All Odoo-provided website themes are built on the Bootstrap CSS framework to ensure responsive layouts across desktop, tablet, and mobile, which supports SEO. This is worth flagging for SMEs that have heard Bootstrap associated with older site-builders: here it is the foundation of every official theme, including current ones.

Design-quality debates online often compare Odoo themes to pure design tools such as Webflow. Webflow (and similar builders) can win on pixel-level art direction; Odoo’s advantage is not “prettiest template library” but operational coherence—one theme system, one product catalog, one CRM, one inventory. Agencies that care only about portfolio visuals often stay on design-first platforms; operators who need stock, quotes, and support in the same system choose the integrated builder.

Static vs dynamic pages, templates and AI generation

The Odoo website builder supports two page types: Static pages (fixed content such as the homepage, manually created with definable URLs) and Dynamic pages (content generated automatically from database data, for example /shop or /blog, or when publishing a product or blog post). Dynamic pages are managed differently from static pages.

Page-creation templates are grouped by type: Basic (multi-purpose, including a blank page), About, Landing Pages, Gallery, Services, Pricing Plans, Team, and Custom templates—a saved page promoted to a template via its properties. Reusing a strong page as a custom template is one of the fastest ways to keep multi-page sites consistent after launch.

The Odoo website builder also includes an AI webpage generator. When creating a new page, toggling AI Generate Text and entering a short description and a tone (Concise, Professional, Friendly, Persuasive, or Informative) produces page content via Create with AI. The AI app does not need to be installed on the database, and the feature is not available for the Blank page type. Official marketing also positions AI as a copy sidekick: generate from a prompt or improve existing text with tone controls—still review for accuracy and brand voice before publish.

In the Optimize SEO flow, Odoo also exposes Fill with AI to generate a meta title, description, and keyword suggestions for the page—useful as a first draft, not a substitute for a human check against one clear H1 and real on-page wording.

Pages must be published to be visible to visitors, toggled from Unpublished to Published in the upper-right corner. Pages can also be published or unpublished from page properties, or in bulk from Website > Site > Pages via Actions > Publish or Unpublish. On Odoo 19, operators can also hide the header and/or footer on specific pages (useful for focused landing, event, or blog layouts) and customize portal login, sign-up, and password-reset pages to match brand.

The Form block: turning submissions into Odoo records

The Odoo website Form block collects information from visitors and, if applicable, creates records in the database. The default submission sends an email. Depending on installed apps, additional record-creating Actions become available from the Style tab on the form:

Apply for a Job (Recruitment), Create a Customer (eCommerce), Create a Ticket (Helpdesk), Create an Opportunity (CRM), Subscribe to Newsletter (Email Marketing), or Create a Task (Project)—plus other models via More models. You can add fields (including Existing Field values from the database and property fields), set Type/Label/Required, placeholders, default values, visibility, and animations. On Success can redirect to a Thank you page (or another URL), show a message, or do nothing so the visitor stays on the form page.

This is the core reason an SME running Odoo tends to build its site in the Odoo website builder rather than a standalone CMS: the same form can feed sales pipeline, support, marketing, or project delivery without writing integration code. Configuration for spam protection, CDN, and Google Search Console lives under the Website Configuration area.

Hybrid tip from official docs: if marketing stays on WordPress or another CMS, you can still embed an Odoo form via iframe—strip header/footer on a dedicated Odoo page so only the form remains, generate embed markup, and drop it into the external site so submissions still write CRM or Helpdesk records natively.

With eCommerce installed, product pages and the shop are dynamic pages over the same product and inventory data—not a second catalog you re-export nightly. Order handling then continues in Odoo sales/inventory rather than in a disconnected storefront admin. Teams that already sell on Shopify often still keep Shopify for front-end merchandising and use Odoo as the ERP of record for multi-location stock; pure Odoo Website + eCommerce is the path when you want one admin for catalog, checkout, warehouse, and accounting.

What changed in Odoo 19 Website (operator view)

Odoo 19 keeps the same Website mental model (blocks, themes, SEO, multi-website) while refreshing the front end and editor. Partner technical summaries describe an OWL-framework migration aimed at faster live editing and rendering, richer text toolbars (inline styles, floating toolbar, improved media alignment), expanded snippet libraries (team, testimonials, service highlights, configurable contact forms), and clearer labels for dynamic snippets in the insert dialog.

SEO and accessibility: documentation already covers microdata for products, events, forum posts, and contact addresses; partner guides for 19 also emphasize automated validation for missing meta tags/alt text, heading hierarchy, and contrast—plus “more intelligent URLs.” Use these as release-note signals and verify on your database version rather than assuming every checkbox appears in every edition.

UX controls operators actually use: hide header/footer per page for landing focus; customize portal auth pages; navbar alignment that can differ on mobile vs desktop; carousel scrolling modes; parallax zoom options; improved blog grid/full-width layouts. eCommerce-adjacent releases add payment providers (partner lists commonly include Nuvei, Paymob, DPO, Redsys among others), Google Merchant Center, and print-on-demand connectors such as Gelato—confirm availability for your localization and plan.

Bottom line for upgrade planning: if you are still on older Website themes with heavy custom QWeb, budget regression testing for snippets and portal. If you are on standard blocks, Odoo 19 is mostly a quality-of-life and SEO hygiene upgrade—not a new product category.

Customer portal, appointments, live chat and other lead engines

Odoo Website is rarely “just pages.” Logged-in customers can use the portal to view quotations, sales orders, invoices, deliveries, and support tickets from the same database your team uses—critical for B2B where AP departments need self-serve invoices and delivery tracking without email tennis. Independent comparisons call this out as a WordPress weak spot unless you assemble a plugin stack.

Adjacent Website apps extend the same surface: Appointments for self-service booking, Live Chat with chatbots and canned responses for sales/support, Blog and Forum for content communities, eLearning for courses, Events for ticketed or multi-track conferences (Odoo 19 partner notes highlight dedicated event landing pages, speaker profiles, and multi-slot booking). Each app installs into the same UX shell, so navigation and contacts stay coherent.

Lead engines that beat a pretty homepage alone: Form → Create an Opportunity with clear UTM-aware landing pages; Live Chat for high-intent visitors; Appointments for demos; eCommerce checkout that creates real sales orders and stock moves. Practitioner chatter around Odoo Website consistently pushes “website as lead engine inside ERP,” not “another theme marketplace.” If you only need a brochure, a lighter builder is cheaper in attention; if every click should become a record, Odoo’s stack is the point.

Odoo Website vs WordPress, Shopify, Wix and Webflow

Search traffic for “odoo website builder” usually comes from people comparing Odoo to the default SME website stack. The useful comparison is not “which editor is cutest” but which platform owns product data, leads, and fulfillment after the page is live.

WordPress (often with WooCommerce) remains the default for content-heavy marketing sites and plugin ecosystems—twenty years of SEO plugins, theme builders, and developer availability. Shopify is the default for pure eCommerce brands that want a hosted storefront and a huge app market, with plan-based card rates and extra platform surcharges when you use third-party gateways. Wix and similar freemium builders optimize for speed-to-pretty-site. Webflow optimizes for design control. Odoo Website optimizes for sites that must talk to ERP, CRM, inventory, helpdesk, and accounting in one database.

Independent 2025–2026 comparisons draw a consistent line: WordPress wins when content marketing and design flexibility are the product; Shopify wins when commerce is the whole business and you want a store live this week; Odoo wins when inventory, CRM, manufacturing, B2B pricelists, or multi-app operations matter more than a pure design sandbox. Odoo still has payment-processor fees when you accept cards—but it does not sit on Shopify-style platform transaction surcharges for third-party gateways; card rates come from the payment provider you configure. Odoo’s list pricing is user-based after free tiers (commonly cited Standard around ~$19.90/user/month in 2026 partner comparisons—always verify on odoo.com/pricing), so high-volume sellers often compare percentage fees versus user seats rather than “subscription vs free.”

Hybrid is often the smart middle path: keep WordPress (or Webflow) for the brand content engine at yourdomain.com, and put Odoo on shop. or portal. for catalog, customer portal, and form→CRM. Share design tokens for visual consistency; wire marketing forms to Odoo when possible so leads do not die in a mailbox.

Choose Odoo Website when the homepage, contact form, and shop must share one customer and stock record with sales and warehouse. Choose Shopify or WordPress when the website is primarily a growth channel and the ERP can stay a separate system with connectors. Choose Webflow when design fidelity is the product and operations live elsewhere. Skip Odoo Website as a “free Wix alternative” if you have no operational complexity to unify—setup depth without back-office payoff is overhead.

SEO: titles, descriptions, redirects, sitemap and checklist

The Odoo website builder’s Optimize SEO tool (Website > Site > Optimize SEO) lets you edit the page’s title tag and meta description, with a search-results Preview card. Changing a blog post title or product name auto-updates its URL, and the old URL remains functional via an automatic 301 redirect to preserve SEO. Fill with AI can draft meta title, description, and keyword suggestions; use the Broken Link field to replace invalid URLs so crawlers and visitors do not hit dead ends.

Odoo’s SEO documentation recommends using only one H1 title per page and distinguishes in-text keywords (which appear in visible content and affect ranking, edited in the page itself) from meta tags (edited in the Optimize SEO pop-up). The hidden <meta name="keywords"> tag is noted as ignored by major search engines with little or no SEO impact—use the Keywords field mainly to audit how terms appear in H1/H2, title, description, and body, plus related Google searches.

Images matter for speed and accessibility: Odoo automatically compresses uploaded images and converts them to WebP (documented behavior on official themes and uploads; introduced from Odoo 18.0 onward and present in 19.0) to improve page speed. Add meaningful alt text (Description on the image) so crawlers can index images and assistive tech has context. Third-party themes may not compress as efficiently as official ones. Set a social share image per page or a site default under Website Configuration > Tracking & SEO so Open Graph previews are not stuck on a logo.

Structured data: Odoo implements schema.org microdata for events, eCommerce products, forum posts, and contact addresses so product pages can surface price and rating-style rich results where Google supports them. Multilingual sites get automatic hreflang and x-default tags on language variants—quality-check translations rather than relying on machine output alone.

Odoo generates a /sitemap.xml of site URLs, cached and updated about every 12 hours; large sites get a sitemap index split in 45,000-URL chunks per the sitemaps.org protocol. Each entry can include loc, lastmod, and priority. Toggle Indexed off on pages you do not want in the sitemap. robots.txt is served at /robots.txt and is editable under Website Configuration > Settings (SEO section)—use Disallow carefully; Google notes that robots.txt alone does not always remove a page from results if other sites link to it. For staging/test databases, putting a random Domain value under Website Info injects a noindex robots meta so draft sites do not compete with production.

Partner write-ups for Odoo 19 also describe stronger SEO/accessibility validation (meta completeness, heading hierarchy, contrast) and smarter URLs—confirm what your build version exposes in the editor before promising automated WCAG audits to stakeholders. Migration note from Odoo docs: moving an existing site into Odoo does not automatically destroy SEO if you keep content quality, map old URLs to new ones with redirects, and monitor Search Console—traffic dips in the first days are normal.

Performance and Core Web Vitals on Odoo sites

Page experience still matters in 2026. Google’s Core Web Vitals remain a baseline quality signal: Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS), with commonly cited “good” thresholds around LCP ≤ 2.5s, INP ≤ 200ms, and CLS ≤ 0.1 at the 75th percentile of real users. Perfect scores are not a ranking silver bullet, but chronically poor vitals hurt both SEO and conversion.

Odoo helps the load path with automatic image compression and WebP conversion, Bootstrap-responsive official themes, optional CDN configuration, and (for shop-heavy sites) eCommerce performance settings. Partner notes for Odoo 19 also cite OWL-framework front-end work aimed at snappier live editing and page rendering—still validate on your theme and hosting tier.

You still own content discipline: oversized hero videos, unoptimized third-party scripts, and heavy custom assets will tank LCP no matter which builder you use. Website performance is tied to the Odoo instance (Odoo.sh plan resources or self-hosted capacity); traffic spikes need capacity planning more like an application host than a pure static marketing CDN.

Practical performance playbook for Odoo Website: use official or well-built themes; prefer compressed WebP-friendly images with dimensions that match display size; lazy-load below-the-fold media where the editor allows; limit third-party tags on first paint; test mobile with PageSpeed Insights or CrUX/Search Console after publish; and keep mega-menus and carousels from shifting layout (CLS). For multi-region traffic, configure a CDN in Website configuration rather than serving all static assets from a single distant origin.

If you already run a high-traffic marketing stack on Webflow or a headless front end, keep it when design and edge performance are the product. If the bottleneck is overselling, manual stock sync, or leads stuck in a mailbox, fix that with Odoo Website + CRM/eCommerce integration before chasing another theme pack.

Multi-website, translations and configuration

Beyond the page editor, Odoo Website configuration covers domain names, Google Search Console, cookies consent, translations, multiple websites, form spam protection, and CDN setup—the operational layer that turns a design demo into a production property.

Multiple websites can live on one database (common for multi-brand or multi-company SMEs). Creating another website requires domain planning: each site is associated with a domain in Website configuration, and Odoo Online multi-website setups map custom domains per website with DNS pointing at the database. Each website must have its own homepage—you may not reuse one homepage across several websites. Mis-mapping domains is a frequent support issue—assign each public hostname to exactly one website record. eCommerce features (products, categories, pricelists, payment providers) can be scoped per website; multi-site product publishing has known UX limits (select one site or all, not an arbitrary subset) that partners sometimes solve with custom modules—plan catalog governance early.

Translations: install languages on the database first, then enable them for the website under Configuration > Settings so visitors can switch locale. Odoo emits hreflang tags for multilingual pages automatically; treat each language path as content you still need to quality-check, not only machine-translate.

Spam protection on forms, cookie bars for privacy regimes, and Search Console verification belong in the go-live checklist alongside SSL/domain cutover. None of these replace a solid information architecture, but skipping them is how good designs fail compliance or inbox hygiene on day one.

When not to use Odoo Website—and a go-live checklist

Do not force Odoo Website when: (1) content marketing and long-form SEO are the growth engine and you have no need for shared inventory/CRM; (2) you need pixel-perfect marketing art direction with a large freelance designer pool; (3) you sell a tiny catalog with no warehouse, accounting, or service workflow to unify; (4) your team already runs a healthy Shopify/WordPress stack and the only pain is “we heard Odoo is free.” Free hosting does not erase implementation and content migration cost.

Do use Odoo Website when: you already run or are committing to Odoo for ops; physical goods need real-time stock on the storefront; B2B buyers need portal access to quotes and invoices; form→pipeline without Zapier is a requirement; multi-company or multi-brand sites should share one backend.

Go-live checklist (operator): map domains and SSL; set primary language + extra languages; configure cookies bar for your jurisdictions; enable spam protection on every public form; connect Search Console; set default social share image; run Optimize SEO on money pages (one H1, title, description, alt text); verify /sitemap.xml and robots.txt; publish only pages that should rank (Indexed on); load-test mobile LCP on homepage and top product/landing pages; train one non-developer editor on blocks + publish workflow; document who owns blog, product copy, and redirect requests after launch.

The Dynamics 365 equivalent: Microsoft Power Pages

The Microsoft ecosystem equivalent of the Odoo website builder is Microsoft Power Pages. Power Apps Portals was rebranded as Microsoft Power Pages in October 2022, and Power Apps portals Studio was retired effective February 26, 2024; all sites now open in the Power Pages design studio.

Power Pages is a low-code website builder in the Microsoft Power Platform. Its design studio is organized around four marquee workspaces—Pages, Styling, Data, and Set up—that focus on specific user jobs (page creation, theming, business data, and site set up including security and behavior). Like Odoo’s themes, the rendered pages are built on Bootstrap for responsive rendering.

The architectural difference is the important part for SMEs. Where Odoo’s Form block writes directly into Odoo apps (a CRM opportunity, an eCommerce customer, a Helpdesk ticket, a Project task, an Email Marketing subscription), Power Pages forms are data-driven configurations created from Microsoft Dataverse table forms—built in the Data workspace or from model-driven apps in Power Apps—and can be combined with lists to build a complete web application over Dataverse, extended with Power Automate and pro-developer tooling.

Power Pages is technically a Power Platform product rather than a Dynamics 365 app per se, but it is the recommended Microsoft-path builder for customer, partner, and self-service portals that need to expose D365/Dataverse data to external users. Both the Odoo website builder and Power Pages are Bootstrap-based, drag-and-drop builders; the choice is usually decided by which back office you already run.

Which fits an SME: Odoo Website, pure website tools, or Power Pages

If the SME already runs Odoo as its ERP/CRM, the Odoo website builder is the natural fit because forms create Odoo records directly and there is no second database to integrate. The site, the shop, the helpdesk, and the CRM share one data model—and the portal can expose orders and invoices without a custom customer app.

If the SME is invested in the Microsoft stack—Dynamics 365, Dataverse, model-driven apps, Power Automate—Power Pages is the consistent choice for external-facing sites and portals, because forms and lists bind to Dataverse tables and inherit Microsoft’s security and governance model.

If the SME is commerce-first with light back office, Shopify (or WordPress + specialized commerce) often ships storefront experiments faster; plan ERP connectors early if multi-warehouse inventory becomes the constraint. If the SME is design- or content-first with little operational depth, Wix, Webflow, or WordPress remain reasonable—and Odoo Website is overkill until ops complexity catches up.

Because Flectic implements both Odoo and Microsoft platforms and is platform-neutral, the recommendation is not which builder is universally better—both Odoo Website and Power Pages are capable, Bootstrap-based, drag-and-drop systems—but which one matches the systems your business already depends on. Our AI-Accelerated Delivery is designed to deliver either implementation up to 3x faster, with the website rollout tied to your CRM, sales, eCommerce, and service processes from day one.

Frequently asked questions