Fudge for Shopify

Screenshot one store page in a real browser on desktop and/or mobile and return the images. Pass `draft` to see a Fudge draft. `fullPage` captures top to bottom. Takes 15–60 seconds; up to 50 captures per store per day.

Check catalogue data coverage across published products, collections, pages and articles: taxonomy, SEO fields, product type, vendor, description, images, alt text and optionally GTIN and MPN. Without `type`, totals and per-field coverage; with `type`, the items missing fields, a page at a time. The first call scans the live catalogue and can return status "scanning". Results are kept for an hour.

Check one live store page’s server HTML for SEO and structured data: title, meta description, canonical, noindex, headings, Open Graph, JSON-LD, lang, viewport, image alt text, mixed content and word count.

Measure a store page with Google PageSpeed Insights: Lighthouse score and lab metrics, real-visitor Core Web Vitals and the largest improvement opportunities. Each device takes 10–30 seconds; results are cached for an hour. On a password-protected store, only real-visitor data is available.

Check the live store’s crawlability for search and AI: robots.txt rules, /llms.txt, sitemap.xml, password protection and whether products are publicly reachable.

Create a link the merchant opens to connect another Shopify store. Use when they ask to add a store. The link works once within 10 minutes.

Create a new blog article in a Fudge draft. It can be previewed in the draft and goes live when the merchant publishes.

Create a new hidden collection in a Fudge draft. It is deleted if the draft is discarded and goes live when the merchant publishes. Use only when the merchant asks.

Create a new Shopify page in a Fudge draft, optionally with its own template. It can be previewed in the draft and goes live when the merchant publishes.

Create a new hidden product in a Fudge draft, with options, variants, prices and media. It is deleted if the draft is discarded and becomes active when the merchant publishes. Use only when the merchant asks.

Start a new Plan for a goal the merchant has agreed and no existing Plan covers, with a title, areas, milestones and an optional brief. Schedules and recurring work are approved in Fudge.

Create a document inside an existing Plan, such as .plans/<slug>/brief.md, or with `replace` rewrite a whole document that was just read.

Delete a theme file from a Fudge draft, or stage removal of an item by its .entities path. Fudge refuses deletions that would break references. Publishing applies the removal; until then it can be undone.

Change products, collections, pages, articles, blogs and their metafields in a Fudge draft with sparse patches, many items in one call. - Name only the fields you change; nested objects such as seo merge per key. - Rows with an "id" (variants, options, media) merge by id; omit "id" to add a row; {"id": …, "_delete": true} removes one. Variants and media live at .entities/product/{id}/variants.jsonc and media.jsonc. - Lists such as tags take a full array or {"add": […], "remove": […]}. - Metafields: .entities/product/{id}.metafields with {"namespace.key": {"type": …, "value": …}}; "value": null removes one. Changes to existing items are staged for the merchant’s review. Items the draft created change in Shopify at once.

Change part of a theme file or .entities document in a Fudge draft by replacing exact text, without line numbers. Fudge validates the result and refreshes the preview.

Change part of a store document, such as a Plan’s brief or the design guide, by replacing exact text. Fails if the text is gone or the document has changed since it was read.

Search what Fudge knows about this store: memory guides, Plans, projects, findings, recommendations, recorded changes and past conversations. Pass `about` (a URL, Shopify GID or fudge:// ref) for everything related to one thing. Conversation results say whether the work is a draft, was published or was only discussed.

Find longer search phrases containing a seed keyword, with volume, difficulty and intent. Changes nothing and uses no credits; each store has a daily limit.

Read the store’s design guide: colours, typography, spacing, components and brand voice. Use when designing or reviewing pages. With no guide yet and a distinctive theme, this starts a one-time extraction.

Get Google search volume, difficulty, intent, CPC and 12-month history for specific keywords in one country. Missing values are unknown, not zero. Changes nothing and uses no credits; each store has a daily limit.

List the Google searches a domain ranks for in one country, with position, URL, volume, difficulty and estimated traffic. Defaults to this store; pass a competitor’s domain to compare. Changes nothing and uses no credits; each store has a daily limit.

Read Google’s live first results page for one search in one country: ranked results, features, AI Overview citations, People Also Ask and related searches. Changes nothing and uses no credits; each store has a daily limit.

Read the latest run of one free diagnostic: status, report link and, once complete, the score and top fixes. Reading starts nothing. `waitSeconds` waits up to 50 seconds for a running report.

Read the findings and recommendations Fudge has saved for this store, most important first; narrow by area, subject, kind, date or text. With `ref`, one record in full with its sources and measurements. An empty list means nothing is saved yet. This never starts an investigation.

Read a store’s overview: business context, standing memory, Google connection, work waiting on the merchant, Plans, top recommendations and recent results. With `area`, that area’s findings, Plans, work, outputs and headline numbers. Use for a brief or before planning work.

Measure the store, or a product, collection, page, article or URL given as `subject`. `metrics` returns headline values with their previous period, definition and source. `breakdown` returns ranked rows such as queries, landing pages, channels, AI assistants, devices, countries, products or discount codes. With neither, returns what exists for the subject. Periods default to the 28 days ending three days ago against the 28 days before. Google Analytics, Search Console and Shopify are separate measurements.

List the store’s current offers: Fudge offers, active Shopify discounts, native bundles, shipping rates by zone and free-shipping thresholds. Use for an offers or average-order-value review.

List the audits Fudge can run for this store, three diagnostics and eight agent reviews, with any existing result. Listing starts nothing.

List the Shopify stores this connection can use.

List Fudge work for this store, including work started in Fudge or another assistant. `view: "needs_you"` returns what is waiting on the merchant. `query` searches past work.

Ask Fudge to do work for this store: build or revise a page, article or other draft, investigate, or answer a question. Without `ref`, starts a new conversation; with `ref`, continues that work. Uses the store’s Fudge credits. `requestId` makes retries deliver once. Publishing always needs the merchant’s own approval in Fudge.

Open Fudge Home for a store: work waiting on the merchant, the next recommended step and the four growth areas. Use when the merchant asks to open Fudge or see their store at a glance.

Read a file in a Fudge draft: a theme file, a theme folder listing, or a content document under .entities (list with .entities/product?query=…). Lines are numbered; long files return `line_offset`. Theme files return a `revision`. Append #info to see where a theme file is used.

Read one of Fudge’s reference articles by path, such as seo/audit.md. Without a path, lists them all.

Read a store document by path: Plans (.plans), playbooks (.playbooks), memory and design guide (.memory), brand kit (.brand) and projects (.projects). Omit `path` to list top-level folders; a folder path lists its documents.

With `ref`: one work item’s live state, progress, latest result, what it is waiting for, and draft or publication state with links; `waitSeconds` waits up to 50 seconds. With `about` (a URL, path, Shopify GID, theme file or fudge:// ref): what has changed there, by `view` current, history or summary. `about: "fudge://store"` is the store-wide timeline.

Add a change made outside Fudge to the store’s timeline, such as ads, prices, apps, email, shipping or theme edits in Shopify, so later results can be attributed. Fudge’s own publishes are recorded automatically.

Save a lasting rule, decision, correction or learning to store memory. Use when the user states how things should be done from now on, not for one-off requests. Duplicates change nothing; a contradiction comes back as a conflict.

Prepare a finished draft for the merchant’s publish decision. Returns the link to Fudge’s review page, what will change and whether publishing needs a plan. This does not publish; only the merchant can, in Fudge.

Run Fudge’s free AI Readiness report: whether AI assistants can find and recommend the store’s products, with a score and prioritized fixes. Takes about 3 minutes and waits up to 45 seconds. Returns a run in progress or a result from the last 24 hours unless `fresh` is true.

Run Fudge’s free AI shopping catalogue report: categories, structured data, product details and whether buyer searches find the right products. Takes 2–4 minutes and waits up to 45 seconds. Returns a run in progress or a result from the last 24 hours unless `fresh` is true.

Run Fudge’s free Shopify Knowledge Base report: 15 shopper questions with the exact answers, gaps and conflicts with published information. Takes 2–5 minutes and waits up to 45 seconds. Returns a run in progress or a result from the last 24 hours unless `fresh` is true.

Find the store’s products, collections, pages and articles by name or handle, or list them by type. Matches singular, plural and partial words, and returns close matches when nothing matches every word.

Search Fudge’s Lookbook of analysed ecommerce stores, pages and patterns. Describe the shopper problem or page element, not a brand. Use when the merchant wants to see how other stores solve something.

Find theme files in a Fudge draft. With `pattern`, search contents by regular expression; without it, list files matching `paths` globs.

Search Fudge’s reference articles on SEO, AI discovery, conversion, merchandising, content, store design and analytics. Returns matching paths and excerpts.

Send the Fudge team a problem with its tools, a capability you needed, or feedback the merchant asked you to pass on.

Record the merchant’s answer from the preview consent card, with the answer code only that card receives.

Show 3–8 Lookbook references as a gallery of screenshots, best first, each with a one-sentence note on why it suits this store.

Show a Fudge draft in the side panel with its screenshot, saved time, change count and links. Without a ref, lists recent drafts.

Ask the merchant, with a card, whether new products and collections in a draft may be previewed by direct link on their live store. Use when a result says previewing needs their consent.

Show Fudge items to the merchant as rows that open in Fudge: work, Plans, findings, recommendations, reports, products and pages.

Open a private Fudge draft to build in directly. Fudge copies the live theme into a draft with its own preview. Give a short title and the storefront `page`, or `work` to continue existing work. `requestId` makes retries create one draft. Use for precise changes you make yourself; needs a Fudge plan that includes building.

Start Fudge’s free AI store builder for someone with a store idea but no store yet. It works out a name, logo and brand, then shows store concepts on Fudge’s website. Returns a link for them.

Start Fudge’s free website redesign for a Shopify store, which generates three homepage concepts on Fudge’s website. Use when the merchant wants new design directions for their whole site. Returns a link for them.

Stop Fudge’s reply running on one work item. With `runId`, stops only that run. The draft and anything already saved stay.

Create a new theme file in a Fudge draft, or with `replace` rewrite a whole file. New theme filenames include the draft’s file prefix, except templates, config and locales. Every sections/*.liquid file needs a {% schema %} with a non-empty "name".