For an important Odoo Website service page, review three separate things: what the page says, which visitors can reach it, and what the published page tells search engines. An editor can prepare good copy and still leave the page unpublished or carry over an unrelated description from a duplicated page.
This checklist covers a manually created static service page in Odoo 20 Website. Product, shop and blog pages may use different controls. References were checked on 18 November 2026; confirm your installed version and any theme or module changes. The workflow and example are editorial recommendations, not a report of a customer audit or a promise of rankings.
Give the page a clear job before editing its settings
Write a one-sentence brief naming the service, intended buyer and next step. Ask the service owner to approve the actual scope and exclusions. If the business only handles planned maintenance, the page should not imply emergency coverage simply because a suggested keyword sounds attractive.
Keep a page record with its owner, approved facts, language, intended address and contact destination. Use it when reviewing the visible heading, body, buttons and metadata. This prevents several people from independently describing slightly different services on the same page.
Separate factual review from copy editing. A clearer sentence does not establish a capability, service area or turnaround time. When a statement cannot be confirmed, ask the owner to resolve it before publication rather than hiding the uncertainty in small print.
Check the static page's address and access
In Odoo 20, Website → Site → Properties exposes Page URL, In Menu, Published, Indexed and Visibility for static pages. The page documentation also describes Redirect Old URL when changing an address. Treat these as separate decisions: public access, menu placement and search-indexing permission are not interchangeable.
Record the intended values before changing them. For a public service page, check that the anonymous visitor can open the final URL. If an existing address must change, assign someone to check the old address too. Avoid casually renaming an established page while performing a copy-only update.
In a database with several websites, verify the intended website as well as the path. Odoo's multiple-website documentation explains that page assignment can be changed from the Pages list. Ask the administrator to resolve an unexpected domain or website assignment; changing the page's words will not fix it.
Use Optimize SEO, then review the result
Open the page and use Website → Site → Optimize SEO for its meta title and description. Odoo's SEO guide describes this editor and its preview. Write a title that identifies this specific service and a description that accurately summarizes what the visitor will find.
Review the visible main heading separately. It may use a natural reading style while the meta title stays compact, but both should describe the same offer. Remove leftover company names, duplicated boilerplate and unsupported superlatives. Have a colleague identify the service from the title alone, then compare that interpretation with the page.
The preview is not an exact promise of the Google result. Google's title-link guidance explains that its title selection uses several sources. Its snippet guidance says descriptions can come from page content or the meta description. Judge the fields by accuracy and usefulness, not a guaranteed appearance.
Describe the image that is actually there
Odoo's SEO documentation identifies the image Description field as the image's alternative text. Check the resulting alt text on the published page. Google recommends useful image descriptions without keyword stuffing.
Describe the relevant scene, diagram or information. Do not use a stock photograph's alt text to claim that it shows your employees or a completed customer project. Keep the usage permission and credit with the asset. Check the crop on a phone: an image that works at desktop width may hide the part the caption discusses.
Follow one fictional service page through review
Fictional example: a maintenance company is preparing a page for planned pump inspection. Its approved brief excludes emergency repairs. The editor chooses “Planned pump inspection” as the visible heading and drafts a description explaining the information needed to request a scope discussion.
A reviewer spots “24-hour repairs” left in the duplicated page's meta description and an image description naming another service. Both are corrected before publication. The reviewer then opens the public page, follows its enquiry button and checks that the destination is relevant. This demonstrates a review method; it does not describe an actual Lava customer or a measured SEO result.
Separate editorial acceptance from technical acceptance
| Reviewer | Check | Evidence to retain |
|---|---|---|
| Service owner | Scope, exclusions and next step match the real offer | Approved brief and outstanding questions |
| Editor | Heading, copy, metadata and image text agree | Final page reference and review date |
| Website administrator | The intended domain and public route work | Anonymous page and link checks |
| Developer or technical reviewer | Rendered metadata, canonical and indexing directives are appropriate | Checked HTML and any issue requiring a template fix |
Odoo documents an automatically generated /sitemap.xml with a 12-hour cache. Allow for that cache when checking a new page, and investigate persistent omissions. Google's sitemap guidance makes clear that submission is a hint, not a guarantee of crawling or indexing.
Save the checks with the page record and assign any unresolved item. For Arabic and English counterparts, use the separate bilingual acceptance checklist. To discuss an Odoo page workflow, explore Lava's Odoo services and SEO services, or contact us with the page, installed version and publishing difficulty.
