Your FAQ Widget Can Now Live on Your Own Domain — Native Embeds for WordPress, Shopify & Wix

eOdessa's FAQ widget no longer requires a subdomain like faq.yourdomain.com. It now embeds directly into your existing WordPress, Shopify, or Wix site as native, crawlable content on your own root domain — via a real plugin, a real app, or a documented backend snippet, depending on the platform. That distinction, root domain versus subdomain, is the entire point, and it's worth explaining why.

What actually changed

Previously, publishing an eOdessa FAQ meant hosting it at a subdomain: faq.mydomain.com. That subdomain is technically "your" content, but search engines and AI crawlers frequently treat subdomains as distinct properties from the root domain — they don't automatically inherit the authority, backlink profile, or crawl priority of www.mydomain.com. Content published there has to earn its own trust signals from scratch.

The new capability changes where the content physically lives. Instead of a separate subdomain, the FAQ renders as part of the page a visitor is already on — mydomain.com/faq, or wherever you place it — using one of three platform-specific integrations:

• WordPress — a shortcode
• Shopify — a real app using Shopify's App Proxy
• Wix — a documented Velo backend snippet

Each is built differently because each platform's extensibility model is different. We matched each platform's actual capabilities rather than forcing one integration pattern everywhere — and we're explicit below about where one option is structurally stronger than another.

Why domain-level placement matters for AI citation

Mechanism, not marketing: AI answer engines and Google's crawlers build authority signals per hostname. A subdomain is its own hostname. Content on faq.mydomain.com has to independently accumulate the crawl trust, internal-link equity, and citation history that mydomain.com has already built up — often over years. Content on mydomain.com/faq inherits that trust immediately, because it's the same hostname the crawler already indexes and trusts.

This is also a structured-data and E-E-A-T question, not just a hosting detail. FAQ content that lives on your primary domain sits next to your existing schema markup, authorship signals, and backlinks — all of which AI systems weigh when deciding whether to extract and cite a passage. Content isolated on a subdomain is read in a weaker context, even when the words on the page are identical.

How it works on WordPress: a shortcode

WordPress sites use a shortcode, WordPress's native mechanism for embedding dynamic content inside a page or post:

Drop that into any page or post, and the FAQ renders inline, on your domain, indexed as part of that page. The plugin is available for download from the FAQ page in your eOdessa dashboard, with an install button that walks through activation.

By default, the rendered FAQ adopts a clean, WordPress-theme-style look — neutral typography and spacing that reads as "part of your site" out of the box, rather than an obviously embedded widget. If your theme has more specific requirements, you can supply your own CSS to override the defaults: a native-looking default, plus an escape hatch for anyone who needs an exact brand match.

Shopify and Wix: two different ceilings

Shopify and Wix both let the FAQ live on the merchant's own domain — but the mechanism, and how close each gets to true server-side rendering, is different for each. We built to what each platform's developer tooling actually supports, rather than promising equal depth everywhere.

How it works on Shopify

Shopify is the deepest integration of the three, because Shopify gives third-party apps a mechanism built exactly for this: App Proxy. An app proxy lets a merchant's store forward requests on a chosen path — say, mydomain.com/apps/faq — to our server, which renders the HTML at request time and returns it in the shop's own theme context.

The practical result: the FAQ page is server-rendered, fully crawlable, and requires no client-side JavaScript to display its content. A crawler requesting that URL gets complete HTML on the first request — not a placeholder that only populates after JavaScript runs. That's the same rendering guarantee Shopify recommends for storefront components like reviews, calculators, and configurators that need to be both dynamic and SEO-visible.

How it works on Wix — and where we're drawing an honest line

Wix does not have a third-party mechanism equivalent to Shopify's App Proxy. There's no way for an external app to server-render a path under the merchant's domain the same way, so we're not claiming there is one.

The closest SEO-safe option on Wix is a Velo backend snippet — Velo is Wix's own development platform, and backend code written in Velo runs on Wix's servers rather than in the visitor's browser. The site owner pastes a short, documented snippet into their site's backend code, and it fetches and renders the FAQ content server-side on that page.

It's a smaller lift than the Shopify app, and it's genuinely SEO-safe — the content is present in the initial HTML, not injected by client-side JavaScript after load. But it's a snippet the site owner installs manually, not a packaged app from a marketplace. If Wix opens an equivalent third-party server-rendering mechanism in the future, we'll build to it.

Where to get it

1. Open the FAQ page in your eOdessa dashboard.
2. Download the plugin or app for your platform — WordPress, Shopify, or Wix.
3. Install and paste the shortcode (WordPress) or connect the app (Shopify), or paste the documented snippet into your site's backend code (Wix).
4. Optionally add custom CSS if you want the widget to match your theme exactly rather than use the default WordPress-style look.