How ImageObject Schema Works on Wix
Wix hosts and renders pages through its own managed platform, which means store owners have less direct control over the document head than on a self-hosted platform. ImageObject implementation on Wix runs through one of two paths: the built-in SEO settings panel, which covers common cases automatically but with limits, or Velo, Wix's custom-code development platform, for anything the built-in panel does not reach.
This two-path structure is different from Shopify's Liquid-editable theme files or WooCommerce's open template system, where a site owner with modest coding ability can usually edit the relevant file directly. On Wix, the built-in panel and Velo are the only two levers available, which shapes what is realistically achievable without developer involvement.
Wix's Built-In SEO Settings and Their Limits
Wix's Advanced SEO panel and its Product schema settings for Wix Stores generate baseline structured data automatically, including a Product block with a basic image reference. That automatic output does not expose fields like license, creditText, or creator through the standard settings interface. Stores that need those richer ImageObject properties, or that want ImageObject schema on inline diagrams inside blog content, need to go beyond the built-in panel.
The built-in panel is a reasonable starting point for a store that only needs baseline Product schema and has no inline diagrams to worry about. It falls short specifically for stores publishing long-form content with in-body diagrams, since that use case sits entirely outside what the panel was built to automate.
Adding Custom ImageObject Schema via Velo
Velo is Wix's built-in custom-code layer, giving site owners JavaScript-level access to page behavior and, relevantly here, the page's head content. Through Velo, a developer can inject a custom <script type="application/ld+json"> block containing a full ImageObject object with contentUrl, caption, width, height, license, and creator, independent of whatever the built-in SEO panel already outputs.
Velo code can be scoped to a single page or applied sitewide through a masterPage file, which matters for ImageObject specifically since most stores need different image schema on every product and blog page rather than one identical block repeated everywhere.
Injecting JSON-LD Through Velo's SEO API or Custom Head HTML
Wix exposes both a dedicated SEO API within Velo for structured data and a general custom-code panel (under Settings, Custom Code) for injecting arbitrary head HTML sitewide or per page. Either path can carry a JSON-LD ImageObject block. The SEO API is the more maintainable route for schema specifically, since it is designed for structured data rather than general script injection.
The general custom-code panel is the fallback for cases the SEO API does not cover cleanly, such as a fragment-anchored ImageObject block for an inline diagram inside a specific blog post. Either approach ends in the same result: a JSON-LD script block reaching the page's rendered head.
Known Constraints on Custom Schema on Wix
Wix's managed rendering pipeline means custom code additions, including JSON-LD injected through Velo, should be verified with Google's URL Inspection tool rather than assumed to render identically to what appears in the Velo editor. As with any platform where JavaScript can add content after initial page load, confirm the schema is present in what Googlebot actually receives, not just what the browser preview shows.
Wix Stores plans also vary in which SEO features are exposed. Confirm the store's current plan actually includes the Advanced SEO panel before assuming the built-in baseline output described above applies, since lower-tier plans may expose less of it.
Actionable Steps to Audit and Fix ImageObject Schema on Wix
Check the homepage, a product page, a blog post with an inline diagram, and any FAQ page through Google's Rich Results Test. Note what the built-in SEO panel already outputs versus what's missing. For gaps, particularly license and creditText fields, or ImageObject schema on content-page diagrams the built-in panel does not touch at all, use Velo to inject the missing JSON-LD, then re-verify with the URL Inspection tool to confirm Googlebot sees the same result.