Connect Shopify
Install both Fabric apps, then show your enriched content on your product pages.
Only an organization owner can open Settings → Connections or Settings → Publishing.
A published Shopify store uses two Fabric apps, installed in that order. The first reads your catalog and writes your enriched content back onto your products as metadata. The second, Fabric Structured Data, reads that metadata and puts the content on the page. Install only the first and the content is written but no page shows it; install only the second and it has nothing to show.
1. Connect your store
This is the app that reads and writes. Connecting it asks Shopify for permission to update your products, which is the permission a later publish spends.
You return to Fabric with the card reading Installed. Fabric is verifying the connection, and then your store, the date it connected and its last sync once that check passes.
Note
A greyed-out Connect Shopify button reads "Not enabled for this brand. Ask Fabric to enable Shopify import." Fabric registers your store with Shopify before you can connect it, so that one is ours to clear rather than yours.
2. Wait for publishing to be enabled
Fabric turns publishing on for your store once the connection above is verified. Until then Settings → Publishing says publishing isn't set up yet, and nothing on your side changes that. Contact Fabric if you expected it to be ready.
3. Turn on rendering in your theme
Fabric Structured Data is the second app. Its app embed is off until you turn it on, and the setting belongs to the theme rather than the store, so installing the app is only half of it.
If the card asks you to contact Fabric instead of offering an install, the app has not been issued for your store yet.
The embed adds your FAQ content to product pages as schema.org JSON-LD. Product schema is a second toggle on the embed, off by default: most themes already output a Product node, and two Product nodes on one page can cost you Google's product rich result. Turn it on only if your theme has none.
Note
Publishing a new theme turns the app embed off. App embeds are saved per theme, so turn it on in the new theme before you publish it.
4. Choose what Fabric writes
Settings → Publishing decides what a publish may change on your products. Fabric starts with the option that changes nothing a shopper reads.
| Setting | What a publish writes | Default |
|---|---|---|
| Enriched metadata | Structured data for AI assistants, stored alongside your products. Nothing a shopper reads changes. | On |
| Product fields | Replaces your own copy with Fabric's enriched version. Choose Product description, SEO title and description, or both. | Off |
| Image alt text | Replaces the alt text on your product images. | Off |
Turning off a setting stops the next publish from writing that field. It does not restore what an earlier publish already wrote.
5. Show the content as text on the page
The app embed adds structured data, which search engines and AI assistants read but shoppers do not see. The Fabric Specs & FAQ app block puts the same content on the page as text.
It shows specifications and the questions and answers Fabric wrote, as collapsible sections you can set to open all, first-only or closed. Product details are a fourth section, off until you turn it on. Keep FAQ schema on the app embed turned on alongside it, so the visible text and the structured data match.
Note
Fabric Specs & FAQ replaces the older Fabric Specifications and Fabric FAQ blocks. If either is still on the template, remove it or its content appears twice.
6. Check that it worked
Select products in Catalog and choose Publish, then open one of the products you published
and view the page source. A working install has at least one Fabric tag in the <head>:
<script type="application/ld+json" data-fabric-structured-data="faq">No tag means the app embed is off in the published theme, or that product has no enriched content yet. If you added the Fabric Specs & FAQ block, you will also see its heading on the page itself. Fabric cannot read your theme, so the page is the only place this answer exists.
Every publish a brand has run is listed under Catalog → Publish history, with what each one wrote, skipped and failed.
Related
- Destinations — what else you can publish to, and who has to approve.
- Publishing over the API — run the same publish from your own code.