FAQPage Schema on Wix: What the Platform Actually Provides
Wix does not generate FAQPage schema automatically for accordion or FAQ sections built with its native drag-and-drop editor. When a Wix store owner adds a Wix FAQ widget or a collapsible text section to a product or landing page, the rendered HTML contains no JSON-LD markup by default. Search engines see plain text questions and answers, not structured data that qualifies for FAQ rich results in Google Search.
The platform does offer a dedicated FAQ app — Wix FAQ — within the Wix dashboard. This app creates a standalone FAQ page and, in certain configurations, injects JSON-LD structured data. However, the schema it produces is tied to that dedicated page type and does not automatically propagate to product pages, collection pages, or custom landing pages where FAQ content is equally valuable for ecommerce SEO.
The Wix FAQ App: Capabilities and Hard Limits
The Wix FAQ app generates a page at a URL like yourstore.com/faq and allows categorized question-answer pairs managed from the dashboard. When the app is active, Wix injects FAQPage JSON-LD into that specific page's head. The schema references the questions and answers stored in the app's database, and Google can parse this markup to generate FAQ rich results — the expandable Q&A dropdowns that appear directly in search results.
The critical limitation for ecommerce operators is scope. Product pages built with Wix Stores templates do not pull schema from the FAQ app. A store with 500 product pages cannot use the FAQ app alone to add product-specific FAQ schema at scale. Each product page requires its own structured data, and the FAQ app provides no mechanism to inject per-product JSON-LD dynamically.
The app also caps the number of questions per category and offers no API endpoint that a developer can query to push schema elsewhere. Operators running conversion-focused landing pages entirely outside the FAQ app structure have no native Wix path to FAQPage schema on those pages.
Injecting FAQPage Schema via Wix Custom Code
Wix provides a Custom Code section under Settings → Advanced → Custom Code. This tool allows JavaScript or raw HTML including JSON-LD script tags to be injected into the head, body start, or body end of all pages, specific pages, or pages matching a category. For FAQPage schema, the correct placement is the document head as a JSON-LD script block with type 'application/ld+json'.
For a static FAQ page, a developer pastes a hand-written JSON-LD block with the FAQPage @type, mainEntity array, and individual Question and acceptedAnswer objects into the Custom Code field scoped to that page. This approach works reliably and passes Google's Rich Results Test. The limitation is maintenance: every time a question or answer changes on the page, the JSON-LD block requires a manual update in a separate location, creating a synchronization problem at scale.
Wix's Custom Code injection does not support dynamic variables or references to page content. The schema block is static text. A store with 200 product pages, each needing unique FAQ schema, must create 200 separate Custom Code entries — one per page — because Wix Custom Code cannot read Wix CMS data to populate the JSON-LD dynamically.
Wix Velo: The Developer Path to Dynamic FAQPage Schema
Wix Velo (formerly Corvid) is Wix's JavaScript development environment, available on paid plans. Velo allows developers to write server-side and client-side code that interacts with Wix CMS collections, fetch external data, and manipulate the DOM. For FAQPage schema, Velo enables a dynamic solution: store FAQ question-answer pairs in a Wix CMS collection, then write a Velo page-level script that reads those records and injects a properly formatted JSON-LD block into the page's head at render time.
The implementation pattern uses the wixWindow.trackEvent or, more reliably, the $w.onReady callback combined with dynamic DOM insertion to append a script tag containing the generated JSON-LD. Google's crawler processes Wix pages with JavaScript rendering, so client-side injection is generally parsed, but server-side rendering via Velo's backend functions is more dependable for crawler discovery. This is a non-trivial development task requiring Velo familiarity, but it is the only scalable native path to dynamic FAQPage schema across many Wix product pages.
Third-Party Schema Apps in the Wix App Market
Several apps in the Wix App Market add structured data capabilities beyond what Wix provides natively. Apps in the SEO and schema category — search the Wix App Market for 'schema' or 'structured data' — typically provide a UI for entering FAQ question-answer pairs and handle JSON-LD injection without requiring custom code. These apps vary in the page types they support, the schema types they cover, and whether they integrate with Wix CMS collections for dynamic population.
When evaluating a schema app for Wix, confirm whether it supports FAQPage specifically (not just Product or BreadcrumbList schema), whether it allows per-page FAQ customization for product pages, and whether it reads from existing Wix CMS data or requires duplicate data entry. Duplicate data entry creates the same synchronization problem as the manual Custom Code approach. An app that connects to a CMS collection where FAQ content already lives eliminates that maintenance burden.
Actionable Implementation Path for Wix Store Operators
For a single FAQ landing page, use Wix Custom Code to inject a static JSON-LD FAQPage block scoped to that URL. Write the schema manually, validate it with Google's Rich Results Test, and document the update process so the code block stays in sync when answers change. This covers the most common ecommerce use case — a standalone shipping, returns, or product-category FAQ page — with no app cost and no development dependency.
For product-level FAQ schema at scale, the realistic options are Wix Velo with a CMS-backed dynamic injection script or a third-party schema app that supports per-product FAQ markup. Velo is the more flexible long-term path if development resources exist; an app is faster to deploy if they do not. In either case, prioritize the highest-traffic product pages first, validate schema with Google Search Console's Rich Results report after deployment, and expand coverage incrementally based on indexing results.