The Odoo 19 website builder: pages, blocks, SEO, forms and leads

The Odoo 19 Website app is a Community module that builds pages from drag-and-drop blocks, manages SEO per page, and writes form submissions straight into the same database as your CRM, helpdesk and recruitment. Its real advantage over a separate CMS is not design but data: a contact form becomes a lead with its source and page views attached. Set up the domain, languages and tracking before building pages, and plan redirects before you migrate an existing site.

What the Odoo 19 Website app covers

The core website module is LGPL (Community). It gives you the page editor, themes, menus, multi-website, page visibility rules, redirects, visitor tracking and SEO tools. Separate Community modules add the parts most businesses need next:

• Contact Form (website_crm) turns form submissions into CRM leads or opportunities.
• Blog (website_blog) for posts, tags and tag categories.
• Newsletter Subscribe Button (website_mass_mailing) to collect mailing list sign-ups.
• eCommerce, Events, Online Jobs and eLearning for their own page types.

Some neighbours are Enterprise-only, such as Website Appointments and publishing Knowledge articles. Odoo Online and Odoo.sh give you hosting and a domain mapping; on-premise, you run the web server and certificates yourself (see part 3).

Website settings to configure before building pages

Open Website > Configuration > Settings. The settings that are painful to change later are near the top:

• Domain: the web address this website answers on. With multi-website, each website gets its own.
• Languages: the languages the site offers and the Default one. Use Install new languages first if a language is not active in the database.
• Website Identification: the site name and favicon.
• Tracking & SEO: Plausible or Google Analytics, Google Search Console verification, a CDN, Robots.txt, a Default Social Share Image and the cookies bar, including an option to block third-party tracking services until consent.

Building pages with blocks, menus and visibility

Pages are built in the editor from blocks: drag a block from the Blocks panel, then adjust it in Style and set colours and fonts under Theme. Keep a small, consistent set of blocks. A site that uses every block type in the library looks like a demo.

The Site menu in the editor holds the tools you use daily: Menu Editor, Content > Pages for the list of every page, and under This page, Properties, Optimize SEO and the HTML / CSS Editor.

Each page's properties control its URL, whether it is indexed, publication, and visibility. There are four visibility options: Public, Signed In, Restricted Group and With Password. Restricted Group is useful for dealer price lists or partner resources without building a portal.

SEO settings and redirects in Odoo 19

Optimize SEO works page by page. It lets you set the title and meta description, add keywords and see where each keyword is used (title, description, H1, H2, content), choose the social share image, check for broken links, and hide the page from search results. The dialog also has a Fill with AI option for the meta fields; treat its output as a draft and edit it.

Odoo generates /sitemap.xml for published pages automatically. The work that actually matters is redirects. Under Website > Configuration > Redirects, each rule has an action:

404 Not Found
301 Moved permanently
302 Moved temporarily      (default)
308 Redirect / Rewrite

For pages that have moved for good, including migrations from WordPress or an old Odoo site, change the action to 301. Leaving the 302 default in place is a mistake we see often on Odoo sites after a relaunch.

Website forms that create CRM leads

The form block submits into a model you pick. With the relevant apps installed, the actions include Send an E-mail, Create an Opportunity, Create a Task, Create a Ticket, Apply for a Job and Create a Customer. You can add fields from the target model, mark them required, and hide fields with preset values.

For lead forms, set the Sales Team and Salesperson on the form itself so leads land with the right people. If you leave them empty, the website's default sales team and salesperson apply. Leads from the website get the UTM medium "Website" unless the form says otherwise, and are linked to the website visitor, so the salesperson can see the page views that led to the enquiry.

Protect public forms against spam with Google reCAPTCHA or Cloudflare Turnstile, both available as Community modules. Lead scoring and assignment then follow the CRM set-up in part 6.

The blog, multi-language content and launch order

The Blog app supports several blogs on one site, posts with their own SEO settings, and tags grouped into tag categories, all managed from Website > Content > Blog Posts and Configuration > Blog. Translating a post or page uses the editor's translate mode for each installed language, with the URL prefixed by the language code.

1. Settings: domain, languages, analytics, cookies bar, robots.txt.
2. Theme, header, footer and menus.
3. Core pages, with SEO titles and descriptions written as you go.
4. Forms wired to CRM, with sales team, salesperson and spam protection.
5. 301 redirects from every old URL that had traffic.
6. Blog and translations once the core site is live.

Launch with fewer pages and working forms rather than more pages and a contact form that emails a shared inbox. The next part covers what to do with the contacts you collect: email marketing, automation and events. For a migration from another platform, talk to us about the redirect map first.