Skip to content

Which kind of site is yours

Geoffy needs a catalogue — a list of products, with facts about each one. Where that list comes from is the only thing that differs between the two kinds of custom-built site, and it decides which door you set up through.

Shopify behind your storefront No commerce platform
Your catalogue is your Shopify products, already synced your own product pages, read by a crawl
You set up under your connected store your Geoffy workspace
handle is the Shopify product handle the segment your product URL pattern captures
Before publishing generate from the synced product review what the crawl read back, then publish
What costs money generating and publishing generating and publishing. Connecting, proving ownership, checking the mount and crawling your catalogue are all free

No commerce platform: what happens in the dashboard

If nothing sits behind your storefront, Geoffy builds your catalogue by reading your own pages. You do this once, in the dashboard, before any of the code on these pages matters:

  1. Geoffy reads your sitemap and proposes URL patterns that look like product pages — for example /products/:handle. You are choosing a shape, not listing products.
  2. You confirm or correct the pattern. The segment it captures becomes each product's handle, which is the value you will pass to the component on your product page.
  3. Geoffy crawls the matching pages and records what it could read about each product.
  4. You review what it found, product by product, including the canonical URL each page declares.
  5. Then you publish the ones worth publishing.

Nothing, except what you pass as handle to <GeoffyProduct>. With Shopify behind you that is the Shopify product handle — the same value you already query the Storefront API with. Without a commerce platform it is the segment your product URL pattern captured, and Geoffy shows you the handle it recorded next to each crawled product, so you can copy it rather than guess.

See the product page.