Playbook · Updated November 16, 2026

Search and sharing for Throttle Builder pages

How your Throttle Builder pages appear in search and when shared: titles, descriptions, share images, hiding a page, the sitemap and what your developer does.

This guide explains what you can set for how your Builder pages appear on Google and when someone shares a link, and which parts your developer has to connect.

What you can set

There are two places.

For the whole site, open Site, then Search and sharing:

  • Page title template. How every page title is written. {page} is the page’s name and {store} is your store name. The example under the field shows the result. The default is {page} – {store}, so an About page becomes “About us – Meridian”.
  • Default description. The one or two sentences search results may show under a title, for every page that has none of its own. Up to 300 characters, and one per language.
  • Default share image. The picture shown when a page is shared and it has none of its own.

For one page, open Pages, then Settings on that page:

  • Address. The page’s web address. See custom pages.
  • Search title. Replaces the page name in search results. Leave it empty to use the page name.
  • Search description. Up to 300 characters. Leave it empty to use the site’s default.
  • Share image. Leave it empty to use the site’s.
  • Hide this page from search engines. Tick it for a page that should be reachable by link but not found on Google, such as a thank-you page.

Write each search title and description for a person reading a list of results: say what is on the page, in plain words.

What your store does with them

Your store applies what you set, once your developer has set up the Builder page route:

  • The title of each page is its search title (or its name when you set none), written through the page title template.
  • The description is the page’s search description, or the site’s default description.
  • The share image is the page’s, or the site’s default.
  • A page you hide from search engines is marked so, and Google leaves it out.
  • Every page gets a canonical link, which tells search engines the one address a page lives at. It is the store’s address plus the page’s address.

Your store does not add structured data (the extra markup some search results use for ratings or prices). If you want it, ask your developer to add it.

The sitemap

A sitemap is the list of pages you want search engines to find. Your developer adds one line to your store (the builderSitemap helper) and your published pages are listed with when each last changed. Draft pages are never listed, and neither are pages you hid from search engines. If your store has no sitemap yet, ask for one: it speeds up how quickly Google finds new pages.

Pages that move

When you change a page’s address, Builder remembers the old one. Visitors and search engines that use the old address are sent to the new one permanently, so links and rankings carry over. See custom pages.

Every page, built ahead or not

How a page gets built depends on how your store is delivered (see the delivery modes guide):

  • On Build-time, every page of a release is built when the store is built. Search engines always get a finished page.
  • On Live, a page is built when it is first visited and kept. Search engines get a finished page too. The first visit to a page you have just published may be a little slower.

A short checklist

  1. Set the title template and a default description under Site, Search and sharing.
  2. Give each important page its own search title and description.
  3. Add a default share image, about 1200 by 630 pixels.
  4. Check your store has a sitemap and that it lists your Builder pages.
  5. Hide pages that should not be found on Google.

For your developer

  • The page read answers a seo object next to the document: title, description, shareImage (a frozen image with its URL and sizes, or null) and noindex, already in the page’s locale. builder.pages.get(slug) returns it on the page, in live and in build mode.
  • createBuilderPage().generateMetadata applies it: the title is seo.title (else the page name) through the site’s titleTemplate, the description is seo.description over the site default, openGraph and twitter images are the page’s share image over the site default, robots: { index: false } is set for noindex, and the page has a canonical link and openGraph.url. A [locale] route also gets alternates.languages and x-default.
  • It needs two options. storeUrl is the store’s own origin (https://shop.example.com; NEXT_PUBLIC_SITE_URL in the create-store template). The Builder does not publish it, so without it a page has no canonical. mediaOrigin is the same value you give loadSite; without it there is no og:image.
  • The canonical is the site’s page route plus the slug (routes.page, /pages/{handle} by default), so the home page is /pages/home. A store that serves home at / passes pagePath: (page) => (page.pageType === 'home' ? '/' : page.path), to both createBuilderPage and builderSitemap.
  • A [locale] route (app/[locale]/pages/[handle]) prefixes the canonical with /<locale>. Do not combine the locale option of createBuilderPage with a locale route: with locale set, the canonical is not prefixed.
  • No structured data (JSON-LD) is emitted. Add it in your own metadata if you want it.
  • builderSitemap({ storeUrl, locale?, localeRoute?, pagePath? }) needs storeUrl (an http(s) origin), or it returns an empty list and warns. It skips pages set to noindex using the page list’s own noindex, so it makes no per-page reads, in live and in build mode. A Worker that predates the field is checked with one read per page. localeRoute: true lists each page once per site locale under /<locale>; set it only for a [locale] route, and not when the page route has a locale option.
  • See Rendering Builder pages and the SDK.