How BlogPosting Schema Works on Wix
Wix automatically injects a basic BlogPosting schema on posts created through its native Wix Blog app. When a store owner publishes a post, Wix populates standard fields — headline, datePublished, dateModified, author, and image — drawn from the post's metadata. This happens server-side without any manual markup, which covers the minimum requirements for Google's rich result eligibility.
The limitation is that Wix's auto-generated schema is fixed. You cannot edit the raw JSON-LD output through the Wix dashboard. Fields like articleBody, keywords, description, publisher logo details, and mainEntityOfPage are either omitted or populated in ways that don't match richer editorial setups. For ecommerce stores that use their blog to drive organic traffic and conversions, that gap matters — especially for AI-driven search surfaces that extract structured data to answer queries.
What Wix Auto-Generates vs. What It Omits
Wix Blog posts automatically output the @type BlogPosting, along with headline (mapped from the post title), image (from the featured image), datePublished, dateModified, and author name. The publisher field pulls from the site name in Wix's SEO settings. These fields satisfy basic schema validation in Google's Rich Results Test.
What Wix does not auto-generate: articleBody (the full text of the post as a schema property), keywords, description as a distinct schema field separate from the meta description, wordCount, and a properly structured logo inside the publisher object. It also does not support multiple authors or the speakable property. For stores producing long-form buying guides or comparison posts designed to appear in AI overviews, these missing fields reduce the schema's utility.
Wix also does not allow direct editing of the site's <head> on a per-post basis through standard dashboard controls. The Velo (formerly Corvid) code environment is the path around this — but it requires developer access and is not available on all Wix pricing plans.
Adding Custom BlogPosting Schema via Wix Velo
Velo is Wix's JavaScript development environment. It allows injection of custom JSON-LD into the page <head> using the wixSeo.setStructuredData() API. A store developer can write a script that fires on blog post pages, pulls the post's title, body excerpt, publish date, author, and cover image through Wix's dataset or dynamic page APIs, and assembles a complete BlogPosting JSON-LD object — then injects it at render time.
The practical sequence: enable Velo in the Wix editor, create a masterPage.js or page-level code file scoped to blog post dynamic pages, use the wix-blog-backend module to retrieve post data, construct the schema object with all desired properties, and pass it to wixSeo.setStructuredData(). This replaces or supplements the auto-generated schema. Critically, test the output using Google's Rich Results Test after publishing — Velo-injected schema is rendered server-side and is fully crawlable.
One constraint: wixSeo.setStructuredData() accepts an array of schema objects, so adding BlogPosting does not break any existing Product or BreadcrumbList schema Wix already injects on ecommerce pages. Keep schema arrays additive, not replacement-based, unless you are intentionally overriding a duplicate type.
Third-Party SEO Apps on the Wix App Market
The Wix App Market includes SEO apps — most prominently SEOmatic and similar tools — that offer schema management without requiring Velo coding. These apps typically provide a UI to define schema templates for blog post pages, letting store operators fill in fields like articleSection, keywords, and description without touching code. The app injects JSON-LD through Wix's approved app embed mechanism.
The tradeoff with third-party apps is rendering reliability. App-injected schema that loads via client-side JavaScript rather than server-side rendering can be missed by crawlers that do not execute JavaScript fully. Verify any app-generated schema appears in Google Search Console's URL Inspection tool under 'Page indexing' > 'Detected structured data' — not just in the browser's DOM after JS execution. If the schema is absent in GSC but present in the browser, the injection method is client-side and unreliable for indexing purposes.
Matching BlogPosting Schema to Wix Store Content Strategy
Wix stores that publish product guides, how-to posts, and category-level educational content benefit most from complete BlogPosting schema when those posts include explicit articleSection values that match the store's product taxonomy. For example, a kitchenware store's post on cast iron care maps its articleSection to the same category label used in the store's Product schema. This creates topical coherence across schema types on the same domain — a signal AI search engines use when assembling cited sources.
The author field deserves attention. Wix Blog defaults to the account name of whoever published the post. For stores with multiple contributors or a brand byline strategy, use Velo to set the author as a Person schema with a name and — if available — a URL pointing to an author profile page on the site. An E-E-A-T signal at the schema level reinforces the editorial credibility that AI overviews and Google's helpful content systems evaluate.
Actionable Steps for Wix Store Operators
Start by auditing what Wix already generates. Paste five blog post URLs into Google's Rich Results Test and note which BlogPosting fields are present and which are missing. Compare against the full BlogPosting spec on schema.org — specifically headline, image, datePublished, dateModified, author (with Person type), publisher (with logo), description, articleBody, and keywords.
If the missing fields include articleBody, description, and keywords, enable Velo and implement the wixSeo.setStructuredData() injection on dynamic blog post pages. If Velo is unavailable on the current plan, evaluate whether upgrading to a Business plan (which includes Velo) is justified by the organic traffic volume the blog generates. For stores driving five figures or more in monthly revenue from blog-assisted conversions, the plan cost is not the constraint — the structured data gap is.