Why Hide the SeaText Block on Desktop: UX Strategy and Implementation

Hiding the SeaText block on desktop is a deliberate UX choice. On larger screens, you often have more space for navigation, sidebars, and multiple conversion elements. A persistent widget that works well on mobile can overlap with desktop menus, cover important content, or simply add noise when visitors are already engaged with a richer layout. The SeaText Odoo integration includes a "Hide on Desktop" toggle in the Visibility section precisely for this reason — so you can show the widget where it helps most (mobile) and remove it where it might hurt (desktop).

What changes if you don't hide it

Leaving the block visible on desktop can create three problems. First, visual clutter: desktop users scan pages differently than mobile users, and an extra fixed element competes with headlines, product images, and primary CTAs. Second, overlap risk: the widget may sit on top of sticky headers, cookie banners, or chat launchers, making those elements hard to reach. Third, diluted focus: if you already run a desktop-specific chat, quiz, or calculator, two simultaneous prompts confuse the visitor and split attribution data.

How the visibility toggle works in Odoo

In the Odoo Website editor, after you drag the "Embed Code" module into a page, you open the right-panel editor, paste the SeaText snippet, and then open the Visibility section. There you'll find a checkbox labeled "Hide on Desktop." Checking it adds a CSS media query that sets display: none for viewports above the tablet breakpoint. The block still loads in the DOM — so the script initializes — but it never renders on desktop. This means SeaText's reading telemetry and personalization agents still collect data; only the UI element is suppressed.

When to show vs. hide: a decision framework

1. Audit desktop layout. Open the page at 1440px width. Note every fixed or sticky element (header, chat, cookie bar, side rail).
2. Map conversion goals. List the primary action you want on desktop (demo request, add to cart, newsletter sign-up).
3. Check for conflict. Does the SeaText block occupy the same visual zone as any primary CTA? If yes, hide it.
4. Test mobile-only hypothesis. Run a two-week test: widget on mobile only. Compare mobile conversion rate and engagement metrics against the prior period.
5. Re-evaluate. If mobile lifts but desktop drops, keep the hide. If desktop also benefits from the widget (rare), consider a desktop-specific variant instead.

Trade-offs: mobile-first widget vs. desktop parity

Criterion	Hide on Desktop	Show on Both
Visual clarity	Clean desktop layout; no overlap risk	Consistent brand presence; possible clutter
Data collection	Telemetry still runs; UI hidden	Full UI + telemetry everywhere
Conversion focus	Desktop CTAs get undivided attention	Widget may distract from primary goal
Maintenance	One toggle; no code changes	Same, but more QA across breakpoints
Edge case	Tablet users in landscape may lose widget	Widget appears on all sizes

Takeaway: Choose "Hide on Desktop" when desktop already has a strong conversion path. Choose "Show on Both" only if the widget is the primary conversion mechanism on every device.

Practical scenarios where hiding helps

• Sticky header + chat launcher: The SeaText block sits bottom-right; the chat launcher sits bottom-right. On desktop they collide. Hide the block; keep the launcher.
• Side-rail navigation: B2B sites often use a left rail. A right-side widget narrows the content column, pushing copy below the fold. Hide on desktop; let mobile users get the full-width experience.
• Multi-step form wizard: Desktop visitors are in a guided flow. An extra prompt breaks momentum. Hide the block until the thank-you page.
• High-density product grids: Category pages with 4-column grids leave little whitespace. A floating block covers product cards on hover. Hide it.

Limitations and when this advice doesn't apply

• Single-page apps with client-side routing: The Odoo visibility toggle relies on server-rendered CSS classes. If your desktop view is hydrated after initial load, the media query may not apply until a re-render. Test in your framework.
• Custom breakpoints: Odoo's "Hide on Desktop" uses its default breakpoint (~992px). If your design system uses 1200px or 1024px, the widget may appear on devices you consider desktop. You'll need custom CSS.
• Accessibility requirements: If the widget provides critical functionality (e.g., language selector for non-English visitors), hiding it on desktop may violate WCAG 2.1 AA. Provide an alternative access path.
• A/B testing the widget itself: If you're testing widget copy or position on desktop, you must show it. Use SeaText's split-URL agent instead of the visibility toggle.

Key facts

Fact	Detail	Source
Visibility control location	Odoo Website editor → Embed Code module → right panel → Visibility section → "Hide on Desktop" checkbox	S1
Effect of toggle	Adds CSS media query to hide block on desktop viewports; script still loads	S1
Installation prerequisite	SeaText AI account required; each domain needs separate account	S1
Security restriction	Development URLs (localhost) restricted; valid real domain required	S1
Multi-site usage	One SeaText account per website/domain	S1

Terminology

• Embed Code module: Odoo's block for inserting raw HTML/JS snippets.
• Visibility section: Odoo's responsive display controls (Hide on Desktop, Hide on Mobile, etc.).
• Reading telemetry: SeaText's millisecond-level tracking of scroll, dwell, and re-read behavior.
• Breakpoint: The viewport width at which CSS media queries switch layouts.

FAQ

Does hiding the block on desktop stop SeaText from collecting data?

No. The JavaScript snippet still loads and runs; only the visual element is hidden via CSS. Reading telemetry, personalization signals, and conversion relay continue to function.

Can I hide the block on tablet but show on mobile and desktop?

Odoo's native toggle only offers "Hide on Desktop" and "Hide on Mobile." For tablet-specific control, add custom CSS targeting your tablet breakpoint (e.g., @media (min-width: 768px) and (max-width: 1024px)).

What if my desktop conversion rate drops after hiding the widget?

Run a controlled A/B test: 50% of desktop traffic sees the widget, 50% doesn't. Measure primary conversion (not just clicks on the widget). If the no-widget variant wins, keep it hidden.

Is there a performance cost to loading the script but hiding the UI?

Negligible. The script is ~30 KB gzipped and loads asynchronously. The DOM node exists but remains display: none, so no layout or paint cost occurs on desktop.

Can I show a different widget variant on desktop instead of hiding?

Yes. Create a second SeaText account for the desktop variant, generate its snippet, and place it in a separate Embed Code module with "Hide on Mobile" checked. This gives you independent copy, positioning, and testing on each device class.

How do I verify the hide is working?

Open the page in Chrome DevTools, toggle the device toolbar to a desktop viewport (e.g., 1440×900), and inspect the widget container. It should have display: none or be absent from the rendered tree. Then switch to a mobile viewport (e.g., 375×667) and confirm it appears.

Does SeaText charge extra for multi-device visibility rules?

No. The visibility toggle is part of the Odoo module and SeaText's standard script. Pricing is per domain/account, not per visibility configuration.

Further reading and comparison sources

These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.

• css - Hide a div on desktop - Stack Overflow
• How can I hide a text block that's over an image on desktop view only?
• How to Hide and Show Block Elements? - Spectra

Learn more

Visit the website for more information.