Unpublished events will no longer appear in search engine results. This ensures that only content marked as published is visible to the public, helping to avoid premature exposure and keeping the website content clean and intentional.
auto_awesome What this module does
AI-generated from the code · Odoo 14.0Adds a robots noindex/nofollow tag to unpublished event pages on your website, so search engines do not list events that are not yet published.
This module changes how your website behaves for search engines when visitors open an event page that is not published yet.
When an event page is displayed and that event is not marked as published on the website, the page now includes a special instruction for search engines telling them not to index the page and not to follow its links. Published events are not affected, so they can still be found normally in search results.
- The change is applied at the website page level, so it works on any event page rendered through the website.
- It relies on the event's published status: only events that are not published receive the instruction.
- No new menus, buttons, reports or settings screens are added; the behaviour is automatic.
- It does not change the event data itself, only the information sent to search engines.
The module depends on the website event features and touches the website layout template, which is the common page structure used by website pages. In practice, this helps avoid premature exposure of events that are still being prepared, while keeping published events visible to search engines.
Depends on
Text generated by AI (DeepSeek) from reading the Odoo 14.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 14.0
Confirmed on 2026-11-03 in branch 14.0 of OCA/event.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.