Skip to Content

Website SEO Protection: eCommerce

by
Odoo

$ 99.00

v 18.0 Third Party
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies • eCommerce (website_sale)
• Website (website)
• Discuss (mail)
• Invoicing (account)
Community Apps Dependencies
Lines of code 38
Technical Name website_seo_protection_ecommerce
LicenseOPL-1
Websitehttps://www.ganemo.co
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies • eCommerce (website_sale)
• Website (website)
• Discuss (mail)
• Invoicing (account)
Community Apps Dependencies
Lines of code 38
Technical Name website_seo_protection_ecommerce
LicenseOPL-1
Websitehttps://www.ganemo.co

Technical Specification for AI & LLM

This Odoo module 'website_seo_protection_ecommerce' is an automatic companion to 'website_seo_protection' and 'website_sale'. It verifies that the SEO crawler protection guard correctly allows all standard eCommerce routes (products, categories, shop, cart, checkout, payment confirmation) while still blocking excessive bot-generated URLs. Auto-installs when both website_seo_protection and website_sale are present. Contains only automated test cases — no UI, no new models. Compatible with Odoo 18 (Enterprise, Odoo.SH, Ganemo Online). Multi-language support for English and Spanish included.

Enterprise (Odoo.SH, Ganemo Online or Ganemo.SH)
English & Spanish Included

SEO Protection

eCommerce Route Safety Validator

Automatically validates that your SEO crawler guard never blocks eCommerce product pages, categories, the shopping cart, checkout or payment routes. Installs silently alongside website_sale.

What We're Solving

----------------

Over-Aggressive Bot Guards

SEO protection rules that are too strict can accidentally block legitimate eCommerce URLs such as product detail pages, category listings, cart operations, or the checkout flow — hurting conversions and user experience.

Automated Safety Net

This companion module adds a dedicated test suite that runs automatically, confirming that all critical website_sale routes are always accessible even when the SEO protection layer is active.

Setup & User Manual

Step-by-Step Configuration & Operational Guide

Step 1 — Prerequisites

Before installing this module, ensure the following Odoo applications are already active in your environment. Missing any of them will prevent the auto-install from triggering.

website_seo_protection

The core SEO crawler guard module from Ganemo. This is the module that actually intercepts and blocks malicious bot patterns. It must be installed first.

Where to find it: Apps → Search "Website SEO Protection" → Install.

website_sale

The standard Odoo eCommerce module. It enables the /shop storefront and all product/checkout routes that this companion validates.

Where to find it: Apps → Search "eCommerce" → Install (or confirm it is already installed).

Step 2 — Installation

This module installs itself automatically (zero manual effort in most cases). Below are both paths:

Path A: Automatic Installation (Recommended)
  1. Install website_seo_protection from the Odoo App Store.
  2. Install or confirm website_sale (eCommerce) is already active.
  3. Odoo detects both dependencies are met and automatically installs website_seo_protection_ecommerce in the background.
  4. Go to Settings → Installed Apps and search "eCommerce Protection" to confirm the green checkmark appears.
Path B: Manual Installation

Use this if the automatic trigger did not fire (e.g., dependency was updated after installation):

  1. Activate Developer Mode: Settings → General Settings → Activate the developer mode (bottom of the page).
  2. Go to Apps and click Update App List (this refreshes the app registry).
  3. Search for "Website SEO Protection: eCommerce".
  4. Click Install.
  5. Odoo will install the module and run any pending migrations.

Step 3 — What Happens After Installation

This module is a pure test companion. It has no visible UI, no settings screens, no new menus, and no new models. Here is exactly what it does:

  • Registers a set of automated HTTP integration tests under the post_install tag.
  • Each test simulates a public-user HTTP GET request to a critical eCommerce route.
  • The tests assert that routes like /shop, /shop/cart, and /shop/checkout return accessible responses (HTTP 200), never a 403 or 404 produced by the SEO guard.
  • At least one regression test confirms the SEO guard still blocks malicious appointment crawler trap URLs — ensuring the guard wasn't disabled or weakened.

Step 4 — Routes Validated by Tests

The following table lists every eCommerce route covered by this companion module's automated test suite:

Route Description Expected HTTP Status Guard Behavior
/shop Main product catalog listing 200 Must NOT be blocked
/shop?page=N Paginated shop (e.g., page 2+) 200 or 404 (no products) Must NOT receive X-Robots-Tag: noindex from our guard
/shop?domain=... Shop with datetime-like query parameter Any response except 404 by guard Guard must not trigger on non-appointment paths
/shop/cart Shopping cart 200 Must NOT be blocked or redirected
/shop/checkout Checkout flow 200 or redirect Must NOT be blocked (conversion-critical)
/appointment/page/2?domain=... Crawler trap (regression test) 404 Guard MUST still block — regression validation

Step 5 — Running Tests Manually (For Developers)

If you want to validate the test suite explicitly in your environment (e.g., after a version update or a config change in website_seo_protection), follow these steps:

On Odoo.SH or a local Odoo server:
$ odoo-bin \ --test-enable \ --test-tags /website_seo_protection_ecommerce \ --stop-after-init \ -d your_database

All 5 test methods should pass. If any fail:

  • test_shop_not_blocked fails: The SEO guard is intercepting /shop — check the guard's URL pattern configuration.
  • test_shop_with_domain_not_blocked fails: The guard is matching on query parameters beyond the path — review the regex in website_seo_protection.
  • test_layer1_still_blocks... fails: The SEO guard was weakened or misconfigured — the appointment trap is no longer being blocked.

Global Ready | Multi-Language Support

This module is fully translated into English and Spanish (en_US, es_ES, es_PE, es_MX), ensuring a professional experience for international organizations.

English Spanish

Why Choose Ganemo?

----------------

Ganemo is the world's leading Odoo App developer and a multi-award-winning Gold Partner. For over 5 years, we have been recognized as the #1 seller of high-quality apps on the Odoo App Store. Trusted as the "Best Partner" in USA, Mexico, Chile, Spain, Colombia, Ecuador, and Peru, we deliver robust, secure, and localization-compliant solutions for global businesses.

Get a Quote & Resolve Commercial Doubts

Join thousands of satisfied clients on Odoo. Contact our sales team directly.

QR WhatsApp

Official WhatsApp

Fastest response time.

COPY
LINK
https://wa.me/18286726150

+1 (828) 672-6150

QR Sales Email

Sales Email

For commercial inquiries.

COPY
ADDR
leads@ganemo.com

leads@ganemo.com

QR Book Demo

Book a Demo

Let's explore your needs.

COPY
LINK
ganemo.co/appointment/5

Schedule Meeting

Need More? We Do It All

Professional Odoo Services

ERP Implementation

Transform your business with a full Odoo implementation. We analyze, configure, and train your team to maximize productivity. From Accounting to Inventory, we handle the complexity so you can focus on growth.

Module Dev & Migration

Need a custom feature? Or stuck on an older version? We develop high-performance custom modules and migrate your existing code to Odoo 18 with zero data loss. Expert developers at your service.

QA / User Testing Scenarios

Enterprise Validation Plan

Scenario 1: Auto-Installation Verification

Validates that the companion auto-installs when dependencies are present.

  1. In a fresh database, install website_seo_protection and website_sale.
  2. Go to Settings → Installed Apps and search for "SEO Protection: eCommerce".
  3. Expected: Module appears with status Installed — without any manual installation step.
  4. Remove website_sale temporarily and re-check: the companion should also be uninstalled or marked as not applicable.
  5. Re-install website_sale → companion reappears automatically.

Scenario 2: Main Shop Page Accessible to Public Users

Tests that the primary catalog route is fully accessible.

  1. Open a browser in incognito mode (simulating a public/anonymous user).
  2. Navigate to /shop.
  3. Expected: Product listing page loads with HTTP 200 — no redirect to /web, no 403, no 404.
  4. Open browser DevTools → Network tab → confirm there is no X-Robots-Tag response header from the server.
  5. Navigate to /shop?page=2 → page loads (or returns 404 if only one page of products exists — either is acceptable as long as it is not our guard's 404).

Scenario 3: Individual Product Pages Load Correctly

Validates product detail pages are never accidentally blocked.

  1. From the /shop listing, click on any product to open its detail page (URL pattern: /shop/product-slug).
  2. Expected: Product detail page renders completely with images, description, price, and an "Add to Cart" button.
  3. Repeat for 3 different products to rule out edge cases.
  4. Check browser DevTools → Headers: no X-Robots-Tag: noindex should appear (that header is only for confirmed bot trap URLs).

Scenario 4: Category Filter Pages Accessible

Ensures product category landing pages (primary SEO targets) are never blocked.

  1. Create a product category in eCommerce → Configuration → Product Categories.
  2. Navigate to /shop?category=1 (replace 1 with the actual category ID).
  3. Expected: Filtered product listing loads — only products from the selected category appear.
  4. Now test with a datetime-like query parameter appended: /shop?domain=('create_date','>=',datetime.datetime(2026,3,12,0,0,0))
  5. Expected: The server does NOT return 404 from the guard — the URL contains /shop (not /appointment), so the guard ignores it entirely.

Scenario 5: Cart & Checkout Flow Unaffected

Validates the full purchase funnel is accessible after SEO protection is active.

  1. Add at least one product to the cart from /shop.
  2. Navigate directly to /shop/cart.
  3. Expected: Cart page loads with item(s) listed. HTTP 200. No guard interference.
  4. Click Proceed to Checkout. Confirm URL changes to /shop/checkout.
  5. Expected: Checkout page renders completely with address form and payment options.
  6. Verify no X-Robots-Tag or unusual redirect appears at any step of the checkout flow.

Scenario 6: Payment Confirmation Page Accessible

Ensures post-purchase confirmation is never blocked — critical for payment provider callbacks.

  1. Complete a test purchase using the "Wire Transfer" payment method (no real transaction needed).
  2. After confirming the order, note the URL — typically /shop/payment/confirmation?tx_id=N or similar.
  3. Expected: Confirmation page loads with order summary. No guard-triggered 404 or redirect.
  4. Using a different session (incognito), simulate a payment provider callback by directly accessing the confirmation URL with a token.
  5. Expected: URL is accessible — payment provider integrations are never interrupted by the SEO guard.

Scenario 7: Appointment Crawler Trap Still Blocked (Regression)

Ensures that installing website_sale did not weaken the SEO guard's bot blocking capability.

  1. Using curl or a browser, access the following simulated bot trap URL:
    /appointment/page/2?domain=('end_datetime','>=',datetime.datetime(2026,3,12,14,12,29,664830))
  2. Expected: Server returns HTTP 404.
  3. Check the response headers: X-Robots-Tag: noindex must be present.
  4. Confirm /shop is still accessible in the same browser session — the guard is targeted, not global.
  5. Pass criteria: 404 on the trap URL + 200 on /shop simultaneously.

Scenario 8: Google Search Console Validation

Enterprise-grade validation — ensures search engine crawlers can properly index the eCommerce store after SEO protection is active.

  1. In Google Search Console, use the URL Inspection tool.
  2. Enter your store's /shop URL and click Test Live URL.
  3. Expected: Google reports the page is indexable — no blocked resources, no crawl errors caused by the SEO guard.
  4. Repeat for a product detail page (e.g., /shop/my-product) and a category filter URL.
  5. Expected: No "Blocked by robots.txt", no "Redirect error", no HTTP error codes — all pages are marked as Discovered and indexable.
  6. Review the Crawl Stats report: confirm the guard is not causing a spike in 404 errors for /shop paths.

FAQ & Troubleshooting

Common Resolutions

This module didn't auto-install — why?

Cause: Auto-install only triggers when both website_seo_protection and website_sale are installed and detected simultaneously by Odoo's dependency engine.

Fix: Go to Settings → Activate Developer Mode → Apps → Update App List, then search for "Website SEO Protection: eCommerce" and install manually.

My product page returns 403 or redirects to /web?

Cause: The SEO guard's URL pattern may be matching /shop/product-slug paths in addition to /appointment paths — this indicates a misconfiguration in website_seo_protection.

Fix: Open the website_seo_protection controller configuration and verify the regex pattern is anchored to /appointment — not a global path matcher. Contact Ganemo support if unsure.

Does this module add any settings, menus, or UI?

Answer: No — absolutely none. This is a pure test companion. It has zero visible impact on the Odoo UI.

Detail: It registers automated HTTP integration tests that run during Odoo's test pipeline. No new models, no new views, no configuration screens, no new security groups.

Is this compatible with multi-website setups?

Answer: Yes. The SEO guard and this companion fully support Odoo's multi-website architecture.

Detail: The HTTP tests run against the active website's routes (using Odoo's URL dispatch), meaning they validate whichever website is primary. For multi-website setups where each site has its own domain, test each site independently using Odoo's test runner with the appropriate domain configuration.

Will this module affect website performance or load time?

Answer: No. The module contains only test code, which is never executed in production — only when explicitly running the Odoo test runner.

Odoo loads test classes only in test mode (--test-enable). In a running production server, this module has zero runtime overhead.

My checkout page redirects to the login page — is the guard causing this?

Answer: Almost certainly not. The SEO guard only blocks specific /appointment crawler trap patterns. Checkout redirects to login are standard Odoo behavior requiring authentication.

Verify: Check if you are logged out. Add a product to cart and try checkout as a signed-in user. If still redirecting, check your website_sale configuration for required login settings.

I uninstalled website_sale — what happens to this module?

Answer: Odoo will automatically uninstall website_seo_protection_ecommerce when website_sale is removed, because it is a dependency. This is correct and expected behavior.

If you re-install website_sale, the companion will auto-install again alongside it — no data is lost since this module contains no stored data.

Can I use this module on Odoo Community Edition?

Answer: The module was designed and tested for Odoo 18 Enterprise (including Odoo.SH and Ganemo Online). Community edition compatibility is not guaranteed.

website_sale is available in Community, but certain route behaviors and test infrastructure may differ. Contact Ganemo support for a compatibility assessment.

My Google Search Console shows 404 errors for /shop URLs — is this module the cause?

Answer: This module itself cannot produce 404s — it has no controllers. However, if website_seo_protection has a misconfigured regex that matches /shop, it could produce this symptom.

Diagnose: Run the Odoo tests for this module (--test-tags /website_seo_protection_ecommerce). If test_shop_not_blocked fails, the guard is misconfigured. Contact Ganemo support with the test output.

How do I know the tests are actually running in my CI/CD pipeline?

Answer: The tests are tagged post_install, meaning they run after all modules in the init list are installed. They appear in the Odoo test log under the class name TestEcommerceSeoProtection.

Look for log lines like: TestEcommerceSeoProtection.test_shop_not_blocked ... OK. If you see "0 tests ran", confirm --test-enable is set and --test-tags /website_seo_protection_ecommerce is included.

Is the price correct? The module shows as free — why?

Answer: Yes, this is intentional. website_seo_protection_ecommerce is a free companion module. Its value comes as part of the website_seo_protection ecosystem.

It is automatically included when you purchase website_seo_protection — no additional license is required for this companion.

Commercial & Sales

For inquiries about licenses, demos, or partnerships.

QR WhatsApp
Official WhatsApp

Fastest response time.

COPY
LINK
https://wa.me/18286726150

+1 (828) 672-6150

QR Sales Email
Sales Email

For commercial inquiries.

COPY
ADDR
leads@ganemo.com
QR Book Demo
Book a Demo

Let's explore your needs.

COPY
LINK
ganemo.co/appointment/5

Technical Support

Existing customers regarding module functionality.

QR Technical Support
Help Desk

Exclusive channel for technical assistance and bug reports.

COPY
ADDR
help@ganemo.com

help@ganemo.com

Odoo Proprietary License v1.0

This software and associated files (the "Software") may only be used (executed,
modified, executed after modifications) if you have purchased a valid license
from the authors, typically via Odoo Apps, or if you have received a written
agreement from the authors of the Software (see the COPYRIGHT file).

You may develop Odoo modules that use the Software as a library (typically
by depending on it, importing it and using its resources), but without copying
any source code or material from the Software. You may distribute those
modules under the license of your choice, provided that this license is
compatible with the terms of the Odoo Proprietary License (For example:
LGPL, MIT, or proprietary licenses similar to this one).

It is forbidden to publish, distribute, sublicense, or sell copies of the Software
or modified copies of the Software.

The above copyright notice and this permission notice must be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.