Documentation
How to build Google Shopping, Meta, Wine-Searcher and Vivino feeds from your Commerce7 catalog, and how AI Visibility makes your wine pages readable to ChatGPT, Perplexity and Claude.
1. Requirements
Before you start:
- An active Commerce7 account with admin access
- This app installed from the Commerce7 App Store
- Accounts in Google Merchant Center and/or Meta Commerce (or partner tools) where you will paste each feed URL
- Products with SKU and price on variants you want in Google/Meta-style feeds
- For AI Visibility: the website where your Commerce7 wine pages live, on WordPress, Cloudflare, PHP, Node.js or any builder (through hosted wine pages)
2. What this app does
The app has two jobs, both built from your Commerce7 catalog through the Commerce7 API.
Shopping Feed. You include or exclude each product, add optional per-channel titles and descriptions, and the app writes public XML files on this server. You copy each URL into Merchant Center, Meta or a partner once. Feeds rebuild every hour, and Rebuild feeds runs one right away.
AI Visibility. The app checks what AI crawlers see on your wine pages and builds readable wine content for them, which an install on your website puts into each wine page. See AI Visibility.
It does not replace Merchant Center or Meta configuration; it supplies the feed files those systems consume.
3. Feed setup
Install & open
Install AI Visibility & Shopping Feed from the Commerce7 App Store and open it from your admin. You’ll see Overview, Products, Feed URLs, Settings, Diagnostics, Help and AI Visibility.
Choose products
On Products, use the toggle to include items. Use search, filters, and bulk actions as needed.
Optional overrides
Expand a row to set Name and Description per channel (Google, Meta, Wine-Searcher, Vivino). Leave blank to use your Commerce7 title/teaser plus wine helpers from Settings.
Rebuild
Click Rebuild feeds in the header (or enable auto-rebuild). Check the status banner for confirmation.
Copy URLs
On Feed URLs, copy each XML link into Merchant Center, Meta Commerce, or partner onboarding flows.
Fetch in Merchant Center
Schedule or trigger a feed fetch in Google/Meta after each rebuild — updates are not always instant on their side.
4. Screens & tabs
| Tab | Purpose |
|---|---|
| Overview | Counts, feed health, last build snapshot, activity log, get-started checklist. |
| Products | Toggles, filters, bulk actions, four-channel overrides, Preview Google fields (JSON: link, mobile, images, size, color, prices, GTIN, categories). |
| Feed URLs | Copy endpoints; local inventory & store code at the bottom of the page. |
| Settings | Rules, categories, wine field helpers — applied on the next rebuild. |
| Diagnostics | Checks the generated feed files, Google readiness and partner field notes. |
| AI Visibility | Check what AI crawlers see, preview the wine content, install it on your website and manage site keys. |
| Help | Short in-app guide; this page is the full reference. |
5. Products & overrides
Each row shows stock status and whether the product is in the feed. Expand to edit channel-specific names and descriptions. Use Preview Google fields to see merged title/description and the same key attributes Merchant Center will receive (mobile link, extra image, bottle size, wine color, prices, GTIN, categories).
6. Feed URLs & channels
- Google Shopping — primary Merchant Center feed
- Local inventory — only after you set a store code (see below)
- Facebook / Meta — catalog ads
- Wine-Searcher / Vivino — confirm field requirements with each partner
Each URL includes your tenant id — use only your own links.
7. Settings & rules
Feed rules can skip products in XML (bundles, GTIN required, volume bands, tag exclusions, club-only tags). Categories set default Google/Meta category strings. Wine helpers append vintage, varietal, or region when overrides are empty. Save each section, then rebuild.
8. Local inventory
If you use Google local inventory, enter your Google store code in the card at the bottom of Feed URLs, save, and rebuild. Until a code exists, the Local inventory URL stays disabled.
9. AI Visibility
Commerce7 draws wine pages in the browser with JavaScript. The HTML your server sends has an empty #c7-content area, and AI crawlers such as OAI-SearchBot (ChatGPT), PerplexityBot and Claude-SearchBot read that HTML without running JavaScript. On most Commerce7 sites they find the wine pages empty. AI Visibility checks what they see and puts your wine details into those pages.
We can set it up for you. AI Visibility is included in the app, and the AI Visibility tab is there for every store. You can install it yourself with the options below, or email 7labs@dmitru.com with your website address and we install it on your website and connect it for a one-time $150, arranged by email.
The check
Run check loads your home page, your busiest wine collection and two wine pages as each AI crawler and as a normal browser. Each result is marked Fix, Improve, Note or Good and says what to do.
| Finding | What to do |
|---|---|
| AI crawlers see an empty wine page | The wine name is not in the page's HTML. Install AI Visibility content (below). |
| Your site refuses OAI-SearchBot (or another search crawler) | A firewall, host or Cloudflare setting blocks it. On Cloudflare, open the AI crawler settings (AI Crawl Control, or "Block AI bots" under Security) and allow the Search group. |
| robots.txt tells a crawler not to read your wine pages | Edit robots.txt so search crawlers may read your product pages. |
| No Product structured data, or titles that do not name the wine | AI Visibility adds Product JSON-LD, a title and a description when a page has none or a generic one. |
| No sitemap lists your wine pages | AI Visibility serves /wine-sitemap.xml and can add it to robots.txt. |
We send each crawler's user agent from our own server. Sites that also check where a crawler connects from, which is common for Googlebot, may treat the real crawler differently. You can run a check once a minute, up to 30 times a day.
Wine content
Built from your Commerce7 products: name, notes, wine details and price, plus Product structured data, a wine sitemap and an llms.txt. Only products available on the web are included. Allocation and club wines say who can buy them and show no price. Nothing is added that is not in Commerce7. The content rebuilds with the hourly feed run, and Rebuild from Commerce7 runs one right away. Preview what crawlers will read shows one wine's content, head tags and structured data.
Install options
| Your site | How it is installed |
|---|---|
| WordPress | A small plugin from the tab. Paste a site key in Settings, AI Visibility. Works next to any Commerce7 plugin or theme, and updates arrive as normal plugin updates. |
| Cloudflare | A Worker for any site whose domain runs through Cloudflare (orange cloud). The tab gives the code and the routes; the key goes in a secret named C7AI_SITE_KEY. Only wine pages and the two wine files reach it, and the free Workers plan includes 100,000 requests a day. |
| PHP | One file loaded before your site's own code, for Drupal, Craft CMS or custom PHP. |
| Node.js | One module for Node.js 20 or later: Express middleware, a wrapper for Request and Response frameworks, or entry() for pages you render yourself, such as in Next.js. |
| Hosted wine pages | For Squarespace, Wix, Webflow or any other site: readable wine pages on your own subdomain, such as wines.yourwinery.com. See below. |
| Script tag | One line in your site's header code. Adds structured data for Google and Gemini only. ChatGPT, Perplexity and Claude crawlers do not run scripts, so it does not help them. |
Every option gives people and crawlers the same page. Commerce7 replaces the content when the page loads, so visitors see your normal shop. None of them touch Commerce7 scripts, cart, checkout, account pages or tracking.
Hosted wine pages
Add the address in the tab, then add the two records it shows at your DNS provider: a CNAME from the subdomain to this app and a TXT record at _c7ai. plus the subdomain. If your DNS is on Cloudflare, set the CNAME to DNS only (grey cloud). New records can take a few hours to show up; click Check to test. HTTPS is set up once both records are in place. Each wine page links to its page in your shop, where people buy. Link to the address from your website, for example in the footer, so crawlers find it. Up to three addresses per store.
Site keys
Each website install gets its own key, created on the tab and shown once. A key can read your wine content and nothing else. Revoking it stops updates to that site right away, and the site drops the content at its next hourly check.
Your privacy policy
The WordPress plugin, Cloudflare Worker, PHP file and Node.js module fetch wine content from our server to yours. Your visitors never connect to us, and nothing about them reaches us. Two options are different:
- Hosted wine pages are served by our server, so visitors who open them connect to it.
- The script tag makes each visitor's browser load a script and the wine's data from
feed.dmitru.com.
For those two, our server sees the visitor's IP address and browser, as any web server does. It holds the IP address in memory for about a minute to limit abuse and stores nothing about the visitor. Neither option sets cookies or sends visitor data to anyone. If your privacy policy lists the services your website uses, you can add:
Our website loads wine information from 7Labs (feed.dmitru.com), which helps search engines and AI assistants read our wine pages. To deliver it, 7Labs receives your IP address and browser details. It does not set cookies or store this information.
10. Scenarios
- DTC shipping — Include products; copy Google + Meta URLs; configure Merchant Center / Meta.
- Pickup + retail — Store code + local inventory feed in Merchant Center.
- Club / allocation — Restrict with club tag rules in Settings.
11. What to avoid
- Skipping Rebuild after catalog or settings changes
- Using another tenant’s feed URL
- Expecting Merchant Center to update without a scheduled/triggered fetch
- Expecting compliance from overrides alone — alcohol and shipping rules remain your responsibility in each channel
12. Troubleshooting
- Nothing in feed — Toggle products on; check SKU/price; review rules.
- Low health score — Improve images, descriptions, GTINs; read issues on Overview.
- Rebuild errors — Read the banner message; verify app install and API access.
- Stale UI in Commerce7 — Hard-refresh the app iframe or re-open the app.
- No AI Visibility tab: reload the app from Commerce7. If it is still missing, email 7labs@dmitru.com.
- Check still says the wine page is empty after installing: make sure the site key is saved in the install, clear your site's page cache, then run the check again.
- Check says your site refuses a crawler: allow it in your firewall, host or Cloudflare AI crawler settings. AI Visibility cannot help a crawler that is blocked.
13. FAQ
Do I need to rebuild after every change?
Yes, if you want XML files to reflect the latest data — unless you’ve enabled auto-rebuild after edits.
Can I use Wine-Searcher and Vivino without Google?
You can copy only the URLs you need. Validate partner requirements during onboarding.
Will AI Visibility get my wines recommended by ChatGPT?
It makes your wine pages readable to the crawlers ChatGPT, Perplexity and Claude use, which has to happen before an assistant can mention a wine. Nobody can promise what an assistant recommends.
Is AI Visibility cloaking?
No. People and crawlers get the same HTML, and Commerce7 replaces the wine content when the page loads.
Where is the full XML field list?
See the project docs/FEED-SPECS.md for developers, or ask your technical contact.
14. Technical reference
XML formats and channel notes: repository files FEED-SPECS.md and PRODUCT.md. Support: 7labs@dmitru.com
← App home · Open the full UI from Commerce7 → Apps