Skip to content

Troubleshooting ​

Documentation scope: Guild 0.1.x pre-release builds. The exact public release version will be confirmed in the changelog before Theme Store publication.

Start with the affected page in an unpublished theme preview. Confirm the Shopify Admin data exists, then check the relevant Guild setting, then isolate recent app or custom-code changes. For suspected theme bugs, an unpublished, unmodified duplicate is the clearest comparison when practical.

Do not test risky removals or app changes directly on the live theme.

Use this guide to resolve common setup and content issues in Guild. It is a self-service path, not a requirement before contacting support. Start with the simplest cause first: missing content, an unset link, uneven images, app output, or a setting that only applies in a specific layout.

If the main symptom is that a menu, product, collection, filter, recommendation, metafield, localization option, search result, article, popup, or app-provided item is missing, start with Why content is missing for a source-data and preview-context checklist.

Fast triage ​

Before changing code, identify which layer most likely owns the problem:

What you seeCheck first
Content, menu items, products, collections, policies, metafields, filters, recommendations, Markets, or languages are missingShopify Admin and the relevant Shopify configuration or app data.
A Guild section, block, setting, layout, or built-in interaction does not behave as documentedThe matching Guild setting and preview state, then Guild support if it still looks wrong.
The issue started after enabling an app, app embed, Custom HTML, Custom Liquid, or edited theme fileAn unpublished duplicate without that change, then the app/code owner if the issue disappears.
Checkout, payments, shipping, taxes, customer accounts, or another Shopify platform surface behaves differentlyShopify Help Center or Shopify Support, unless the problem is clearly in Guild-rendered storefront output.
The issue started immediately after a Guild updateCompare the previous and updated copies before reapplying customizations, then report a suspected update regression if built-in behavior changed.

If ownership is unclear, open a Guild support request with the affected page and a short description. You do not need to diagnose the owner yourself before asking for help.

Images are cropped ​

Many sections use image containers with aspect ratio controls. Cropping can happen when the image shape does not match the selected layout, especially in editorial sections where a wide room scene is reused in a tighter card or mobile stack.

Try this:

  • Choose images with similar proportions for repeated cards, logos, and comparison layouts.
  • Adjust the section or block aspect ratio.
  • Use images with the main subject near the center.
  • Check the mobile preview, since mobile layouts may crop differently.

Images look inconsistent in grids ​

Cards, logos, media blocks, and collages work best when images are prepared consistently. Mixed supplier images, transparent product cutouts, and lifestyle photos can sit awkwardly together unless the section settings and source images are reviewed as a set.

Try this:

  • Use the same image dimensions for items in the same grid.
  • Use simple backgrounds for logos.
  • Keep important text out of images when possible.
  • Review mobile layout and slideshow settings.

Spacing or layout feels too tight ​

Spacing is controlled globally and per section. When a page feels crowded, check whether the problem is the global rhythm, one section's padding, or content that is simply too long for the layout.

Try this:

  • Review global Section spacing on desktop and Section spacing on mobile.
  • Review section padding and bottom spacing.
  • Review global Box padding if boxed content or cards feel cramped.
  • Use Divider when the extra space or separator belongs inside a flexible content section.
  • Use Spacer only when one specific page area needs extra room between sections.

A menu or navigation item is missing ​

Guild selects menus and controls their storefront layout, but menu items are created in Shopify Admin.

Try this:

  • Confirm the menu exists in Content > Menus or the current Shopify navigation area.
  • Confirm Header or Footer selects the intended menu.
  • Check that the menu item links to a published product, collection, page, policy, or valid URL.
  • Review nested menu depth and desktop/mobile previews.
  • If a mega menu is involved, test the underlying Shopify menu first without promotional mega-menu blocks.

Buttons and link blocks usually need both a label and a destination.

Try this:

  • Confirm the button label is not empty.
  • Confirm the button link is set.
  • If the button controls a popup, confirm the target popup matches the popup handle.
  • If the button should submit or reset a form, do not enable popup control on that button.
  • If a link opens in a new tab unexpectedly, check Open link in new tab.

Product shipping does not update after variant selection ​

Variant-aware delivery copy depends on metafield setup and the Product shipping advanced settings.

Try this:

  • Open Product shipping, enable Show advanced options, and confirm Update by variant is enabled.
  • Confirm the variant metafield namespace and key match the Shopify metafield definition. The initial values are custom and delivery_estimate.
  • Add a value to every variant that needs its own message.
  • Confirm the configured product metafield contains the intended fallback. The initial product key is custom.shipping_and_delivery.
  • Test a real option combination that resolves to a variant.
  • Repeat the test in an unpublished, unmodified copy if an app or custom script replaces product content.

Guild shows the selected-variant value first, then the product fallback. It does not calculate delivery dates from inventory, incoming stock, preorder status, or continued selling.

Product color swatches show product images instead of colors ​

In Product variants > Buttons and swatches > Swatches, Guild uses the visual data Shopify provides for each option value. A value prefers a Shopify swatch color, then a Shopify swatch image, then matching variant imagery. This fallback prevents a blank visual control when a product has imagery but no usable native swatch.

If a product should show color chips but shows product photos instead:

  • Confirm the product has the most specific applicable Shopify product category.
  • In the product's variant options, confirm the Color option is connected to a compatible Shopify color category metafield instead of being an unconnected custom option.
  • Confirm each connected color entry has the intended color swatch data in Shopify.
  • For blanket and throw products, use Shopify's Blanket color category metafield when the assigned category exposes it.
  • Save the product and reload the storefront product page before changing theme code.

If other products using the same Guild Variants block show color chips correctly, a one-product mismatch is usually product/category-metafield data rather than a theme rendering defect.

Shopify XR button is missing ​

Shopify XR needs a product model, a Product gallery, a configured Button, and device support.

Try this:

  • Add a Shopify 3D model to the product.
  • Keep Product gallery in the same Product surface as the Button.
  • Open Buttons > Button > Show advanced options and set Action behavior to Shopify XR.
  • Configure the normal Button label and/or icon. A practical setup is View in your space with the 3D model icon.
  • Test on a compatible iOS or Android device. Shopify hides the live action when the device does not support the AR experience.
  • Do not use this action inside a product card.

The Theme Editor always renders a visual Button preview, even without a product model, so merchants can configure its appearance. That preview does not activate Shopify XR. If the live XR action is the only item in a Button group and cannot be shown, Guild suppresses the empty group.

Forms are not submitting as expected ​

Contact and newsletter forms depend on the form type, field setup, Shopify settings, and the live storefront submission flow. For Shopify's native submission, sender-email, and spam-filtering behavior, see Shopify's contact page documentation.

Try this:

  • Check that required fields are filled in.
  • Review each input, select, textarea, choice group, and hidden field.
  • Check the success message.
  • Test contact forms on a real storefront or theme preview URL. Localhost preview is useful for layout, but Shopify submission, success/error state, and hCaptcha/CAPTCHA behavior should be checked through Shopify.
  • For contact forms, review Shopify store email settings.
  • For newsletter forms, review Shopify customer and email marketing settings.
  • Check whether an app or custom script is replacing the native form submit path. Guild contact forms are designed around Shopify's native contact form flow, not an AJAX-only replacement.

Forms added through Custom HTML, Custom Liquid, or an app do not automatically inherit Guild's native validation, success/error messages, accessibility semantics, spam protection, delivery setup, or support coverage. The code author or app provider owns the submission endpoint, validation, consent, data handling, and form-specific troubleshooting. Test those forms separately in a duplicate theme.

Search results look incomplete ​

Guild's Search results page can show products, articles, and pages. It also includes result type links for All, Products, Articles, and Pages.

Try this:

  • Confirm the searched products, pages, and articles are published and searchable in Shopify.
  • Check the spelling and try a broader term.
  • Check whether Products, Articles, or Pages is active; switch back to All to see mixed results.
  • If the query has many results, use the next page, Load more, or the infinite-scroll manual fallback depending on the selected Pagination mode.
  • If JavaScript is blocked, submit the search form and use the native links. Search is designed to keep native form, type-link, and pagination fallbacks.
  • Test again in an unpublished duplicate theme with search or merchandising apps and custom code disabled.

Guild Search can show Shopify storefront filters for eligible result scopes when Shopify provides filter data. Search sorting is not included. Swatch or image filter presentation depends on Shopify Search and Discovery data, and Collection list links remain merchant-selected supporting links rather than query-matched search results.

Search filters are missing or do not update ​

Search filters depend on Shopify storefront filter data and the active result scope.

Try this:

  • Configure the relevant filters in Shopify Search and Discovery.
  • Test a query that returns products with meaningful filter values.
  • Use All or Products. Article-only and page-only result scopes do not show product filters.
  • Check active-filter removal, Clear all, price-range values, and disabled/zero-count values.
  • Test the native filter form with JavaScript disabled, then test AJAX-enhanced updates.
  • For swatch or image filters, confirm Shopify exposes the corresponding presentation data.

Guild does not add Search sorting. If results appear in an unexpected order, review Shopify search behavior rather than looking for a hidden theme sorting control.

Search AJAX, Load more, or Infinite scroll is not updating ​

Search AJAX, Load more, and Infinite scroll are progressive enhancements. Native search form submission, result type links, and pagination links should still work when JavaScript is unavailable or interrupted.

Try this:

  • Check the browser console for JavaScript errors from apps, custom code, or browser extensions.
  • Confirm the Search section Pagination mode is set to Load more or Infinite scroll when testing those behaviors.
  • For infinite scroll, confirm Automatic loads before button fallback is not already exhausted; after the limit, continue with the manual Load more results link.
  • Test the same query with Paginated mode to confirm Shopify's native result pages work.
  • Test with JavaScript disabled to confirm the native fallback path still reaches the next page.
  • If the problem appears only after products are appended, also test product-card Quick view and product links after using Load more.

Collection filters, sorting, or pagination look wrong ​

Collection pages use Shopify collection data, Shopify storefront filters, and native pagination links with optional AJAX enhancement. Filter output depends on the collection and the filter data Shopify provides. For platform filter setup, see Shopify's Search & Discovery filter documentation.

Try this:

  • Confirm the collection has products.
  • Confirm Shopify Search & Discovery filters are configured for the store. Adding a Filter or Color filter block in the theme does not create the Shopify filter; it only presents a matching filter returned by Shopify.
  • Confirm products have the tags, options, metafields, prices, vendors, or availability states used by the filters. Use filter.p.vendor for the native vendor filter and the exact Shopify parameter returned for the color option, commonly filter.v.option.color.
  • Check whether active filters are narrowing the grid to no products; remove active filters or use Clear all filters.
  • Change Pagination mode between Paginated, Load more, and Infinite scroll to isolate native pagination from AJAX enhancement.
  • Test the collection with JavaScript disabled to confirm the native form and link fallback still works.
  • If swatch or image filters look empty, check whether Shopify provides swatch colors, swatch images, or filter value images for those filter values.

Country or language selector is missing ​

Guild uses Shopify localization data; it does not create markets or translations.

Try this:

  • For Country selector, confirm Shopify Markets makes more than one country or region available to the Online Store.
  • For Language selector, confirm more than one storefront language is published.
  • Confirm the relevant Country selector or Language selector block is added in a supported utility area such as Header or Footer content.
  • Preview the storefront in the intended market and language rather than relying only on an editor placeholder.
  • Save and refresh the theme editor after changing Markets or published languages.

A selector that has only one available choice may correctly remain hidden. Configure the Shopify source first; contact Guild support only when multiple valid options exist and the documented selector still does not render in an unmodified theme.

Cart quantities, prices, or totals are not updating ​

Cart quantity changes normally update line totals and cart totals automatically when JavaScript is available. Guild also keeps a native cart form fallback, so the behavior can differ if JavaScript is blocked, an app changes the cart form, or a browser extension interrupts requests.

Try this:

  • Change quantity with the plus and minus controls and wait for the cart to refresh.
  • Check that line totals, discounts, the cart summary, and the cart count update together. Unit prices usually stay the same when only quantity changes.
  • If JavaScript is disabled, use the Update control to submit quantity, note, or attribute changes.
  • Test again in an unpublished duplicate theme with custom code and cart apps disabled.
  • If only a specific product fails, check variant inventory, selling plans, unit pricing, and product-form line item properties in Shopify admin.
  • If free-shipping messaging looks wrong, confirm that the theme threshold is greater than 0 and matches the store's actual Shopify shipping rules. Set it to 0 to disable the theme-side message. Checkout remains the source of truth for shipping discounts.

Checkout terms or accelerated checkout buttons look different ​

Cart summary uses configurable Checkout button, Order notes, Terms checkbox, Gift wrapping, and optional Divider blocks. Accelerated checkout is configured inside Checkout button. When visible Order notes or Terms checkbox is required, accelerated checkout is hidden because dynamic payment buttons cannot always be gated reliably by theme JavaScript. For platform-level payment-button behavior, see Shopify's accelerated checkout documentation.

Try this:

  • Check the order, visibility, and settings of the Cart summary blocks in the theme editor.
  • Test standard checkout with required Order notes empty and completed, and with Terms checkbox selected and unselected.
  • Turn off the relevant Required field or Required option setting if accelerated checkout buttons should remain visible on the cart page.
  • Review payment methods in Shopify admin if payment icons or dynamic checkout providers are missing.

Gift wrapping or the gift message is not saved ​

Gift wrapping and its optional message are stored as cart attributes. They do not add a wrapping product, price, or automatic fulfillment rule.

Try this:

  • Confirm the Cart summary contains the Gift wrapping block and that Enable gift message is enabled when the message field is needed.
  • Select or clear the checkbox, enter a message when applicable, and wait for the cart update before leaving the page.
  • With JavaScript disabled, use the native Update control to submit the cart form.
  • Check the resulting order attributes in Shopify admin.
  • Test in an unpublished duplicate theme without cart apps or custom scripts if another integration rewrites cart attributes.
  • Use a compatible paid gift-wrap product or app workflow when the selection must add a charge.

Product materials, care, dimensions, or other details are missing ​

Guild can render product descriptions, pages, dynamic sources, and supported metafields, but it does not create the underlying product information.

Try this:

  • Confirm the information exists on the product, page, or metafield in Shopify Admin.
  • Confirm the product template contains the intended Description, Product disclosures, Product shipping, Text, Content source, Accordion item, or metafield-connected block.
  • Check that the dynamic source points to the correct metafield definition and that the current product has a value.
  • Preview a product that actually contains the data; template-editor placeholders do not prove live product data exists.
  • If valid supported data exists but does not render in an unmodified Guild template, contact support with the product URL, template name, field/metafield used, and a redacted screenshot.

These sections use different data sources. Related products use Shopify recommendation data. Complementary products may require manual setup in Shopify Search & Discovery. Recently viewed products depend on products viewed earlier in the same browser.

Try this:

  • Preview a real product page rather than an unrelated template or empty product fixture.
  • Confirm the selected Product source matches the section you intend to build.
  • For related products, confirm the recommended products are active and available to the Online Store sales channel. Shopify may not return recommendations for every product or store state.
  • For complementary products, review the product's complementary-product setup in Shopify Search & Discovery.
  • For recently viewed products, view several other product pages in the same browser, then return to a page that includes the section. A first visit or cleared/blocked browser storage can correctly produce an empty section.
  • Test without recommendation apps, privacy extensions, or custom product-form code in an unpublished duplicate theme.
  • Contact Guild support only when valid source data or same-browser history exists but the documented Guild section still fails to render it. Include the product URL, template, selected Product source, setup details, browser, and visible result.

Product descriptions look inconsistent ​

Product descriptions can include rich text from Shopify admin.

Try this:

  • Use headings, lists, and paragraphs consistently in product descriptions.
  • Avoid pasted formatting from external editors when possible.
  • Keep tables and very wide content limited, since they may not fit well on mobile.
  • Use Tabbed content or FAQ accordion for long supporting information.

Popups are not showing ​

Popup sections are managed in the popup group.

Try this:

  • Confirm the Popup section exists in the popup group.
  • If it should appear automatically, check Open automatically and Delay.
  • If it should open from a button, check popup control settings and the target popup.
  • If it disappeared after testing, review Remember dismissal and Dismissal duration.
  • If customers cannot close it, review Require confirmation to close and Show close icon.

Announcement bar close behavior is unexpected ​

Announcement bar presets can use a Content list with a section-level close button.

Try this:

  • Confirm the Content list has Show close button enabled.
  • If the bar should stay hidden after closing, enable Remember dismissal and choose a dismissal duration.
  • If testing in the theme editor, remember that dismissal memory is not written in design mode. This lets merchants close the bar while editing without permanently hiding it in the editor.
  • If the bar does not reappear on the storefront, clear the browser's local storage or wait for the dismissal duration to expire.

Countdowns are not showing the expected time ​

Countdowns use start and end date/time settings.

Try this:

  • Confirm End date and time is filled in. A blank end date intentionally hides the countdown on the storefront.
  • Confirm the end date and time are in the future.
  • Check whether a start date is set.
  • Check Show on weekdays if the countdown is only meant to show on selected days.
  • Review which units are enabled: days, hours, minutes, and seconds.
  • Review the storefront after the deadline to make sure expired promotion content is handled correctly.

Tabs or accordions are missing content ​

Tabs and accordions only show useful items when their content is filled in.

Try this:

  • For tabs, add a heading, title visual, or content to each Tab item.
  • For accordions, add a heading and answer content to each Accordion item.
  • Use shorter tab labels on mobile.
  • If using page-sourced content, confirm the selected page has published content.

Mobile layout looks different ​

Mobile layouts often stack content, change spacing, or crop media differently from desktop.

Try this:

  • Use the mobile preview in the theme editor before publishing.
  • Enable stacking for columns when needed.
  • Shorten headings, tab labels, and button text.
  • Review mobile body size, heading scales, and section spacing.
  • Use images that still work when cropped vertically or horizontally.

Product stock messages are not showing ​

Product inventory messages and low-stock badges depend on Shopify inventory data.

Try this:

  • Confirm inventory is tracked for the product or variant in Shopify admin.
  • Confirm the selected variant is available and has a positive inventory quantity.
  • Review Low stock threshold and Inventory display in the product card or product inventory block.
  • Test products with multiple variants, because each variant can have a different stock state.
  • Avoid showing stock counts for pre-order or backorder products unless that behavior is intentional.

RTL layout needs review ​

Guild can switch page direction for RTL locales, but the storefront still needs rendered QA with real content.

Try this:

  • Enable the target language in Shopify admin and preview the storefront in that locale.
  • Review header, footer, product cards, slideshows, forms, popups, and cart pages.
  • Check that carousel arrows, utility separators, and directional icons still make sense.
  • Review long translated labels and button text on mobile.
  • Test with real translated product and collection content before making public RTL support claims.

A section is not showing ​

Try this:

  • Confirm the section is added to the correct template.
  • Confirm the section has visible content or blocks.
  • Check whether the section is part of the popup group rather than the page body.
  • Review any start date, end date, weekday, or visibility-related settings.
  • Save and refresh the theme editor preview.

An app block or app embed is missing or looks wrong ​

Shopify controls app-block availability and the app controls its own settings, output, scripts, and data. Guild controls only the supported insertion points and surrounding theme layout.

Try this:

  • Confirm the app is installed and enabled for the current theme.
  • Check App embeds in the theme editor when the app uses a global embed.
  • Add the app block only inside a section that allows Shopify app blocks.
  • Review the app's own setup, product targeting, and account connection.
  • Test the page with the app disabled in an unpublished duplicate theme to determine whether the underlying Guild layout works.
  • Contact the app developer when only the app-owned output fails. Contact Guild support when the documented app-block insertion point is missing or broken in an unmodified theme.

An issue appeared after updating Guild ​

Try this:

  • Keep or republish the previous theme if the live storefront is materially affected.
  • Read the Guild changelog and update guide.
  • Compare the affected page in the updated unmodified theme before reapplying apps or custom code.
  • Record the previous and new Guild versions.
  • Test product forms, cart, navigation, collection filters, search, forms, popups, and mobile behavior related to the change.
  • When reporting a suspected update regression, include both versions, the affected URL, reproduction steps, recent app/code changes, and whether the issue appears before customizations are reapplied.

A third-party embed is not loading ​

Third-party embeds, including Instagram posts, TikTok videos, X/Twitter posts, maps, booking widgets, and review widgets, are controlled by the provider that supplies the embed code. Guild can place trusted embed code through Custom HTML or Custom Liquid, but the provider controls the embedded script, availability, cookies, and rendered output.

Try this:

  • Confirm the embed code still works in the provider's own preview or documentation.
  • Check whether the provider requires a public post, profile, or account setting.
  • Remove the embed and test whether the page layout issue disappears.
  • Test in a duplicate, unmodified copy of Guild.
  • Contact the provider or app developer if only the embedded content fails.

Custom social embeds are not native Media block types in the current MVP scope. Use the Media block for images, hosted video, YouTube/Vimeo, Google Maps, and supported 3D model media.

Custom code caused an issue ​

Custom HTML, Custom Liquid, external scripts, and app-injected code can affect layout, accessibility, performance, and theme behavior. For Shopify's platform model for app blocks and app embeds, see Shopify's theme app documentation.

Try this:

  • Duplicate the theme before making code changes.
  • Remove or disable the custom code and test again.
  • Test the issue on an unmodified copy of Guild.
  • Contact the code author or app developer if the issue only happens with custom code or a third-party app.

Custom code is not included in standard theme support unless support explicitly confirms otherwise.

AI assistant gives incorrect Guild guidance ​

If an AI assistant suggests settings, sections, blocks, or code that do not match your theme editor, give it the public Guild AI context file first. Generic Shopify advice can be useful, but it often misses Guild-specific section names, block structure, and support boundaries.

Try this:

  • Open Guild AI context.
  • Copy the Markdown into the AI assistant, or upload the file if your assistant supports file uploads.
  • Ask the assistant to use Shopify Admin and theme editor settings before suggesting custom code.
  • Ask it not to invent section names, block names, apps, metafields, or Liquid code APIs.
  • If the assistant still suggests code, duplicate your theme before editing code.

The AI context file is a setup aid. It does not replace Guild support, app support, or developer review for custom code changes.

Product details popup does not appear ​

Product details popup renders only on product pages. Confirm that it was added in the Popups section group, that its Popup handle matches the Button target, and that the current preview is a Product page with a valid product. Its saved configuration intentionally produces no storefront output on other page types.

When a Product gallery does not appear in the popup's leading-media area, check its block level. Only the first top-level Product gallery is promoted. A gallery inside Product Row, Product Column, Product Box, or Product visibility group intentionally stays inside that layout.

Quick view opens, but Add to cart does not work ​

Check:

  • whether the selected product variant is available;
  • whether the quantity follows the product's quantity rules;
  • whether the storefront has JavaScript errors from an app or custom code;
  • whether a required selling plan, gift card recipient field, line item property, or other Product-form control is incomplete;
  • whether the selected option intentionally opens an associated product or a full-page variant-data fallback.

Quick view uses the same Product blocks and Product controller as Product spotlight. When Shopify cannot safely resolve an associated-product or limited-variant transition inside the popup, the full product page is the expected fallback rather than an incomplete purchase state.

Blog category links, article lists, or Infinite scroll look wrong ​

Check:

  • the blog handle used by every category link;
  • that the linked article tags exist and are spelled exactly as configured;
  • that the expected articles are published in the current or selected blog;
  • whether Featured stories, Start here, and Latest articles are showing the same newest articles because they use the same blog source;
  • whether the Latest articles Pagination child is enabled and configured for the intended mode;
  • whether the issue also occurs without app code or custom scripts.

The starter template category links can use the current blog URL with Current blog tag buttons. Set each Blog tag to the intended tag path, or leave it blank when the button label should supply the tag path. Category links are ordinary navigation links, not dynamic filtering controls.

When testing pagination or Infinite scroll, check direct ?page=2 navigation, browser Back/Forward, no-JavaScript fallback, the final page, loaded-count output, and section reloads in the theme editor. If one Blog post list loads content into another instance or multiple lists move to the wrong page, contact Guild support with the Blog URL, Guild version, pagination mode, reproduction steps, and a recording.

Article date, author avatar, or previous/next navigation is missing ​

Check the Article page in a storefront preview rather than only inside a Blog card or Search result.

For Date:

  • Confirm an Article detail child is inside Article details and its Type is Date.
  • Choose Published date or Updated date in Date source.
  • Enable Show label only when the visible text should say Published or Updated.
  • Add two Date-type Article detail children when both dates are needed.

For Author:

  • Confirm an Article detail child uses Type: Author.
  • Confirm the Article has an author name.
  • Enable Show avatar.
  • Select Author image, connect a compatible dynamic image source, or confirm the Shopify author account has an image.
  • A missing author name suppresses the whole Author item, including the avatar.

For Article buttons:

  • Add Article buttons and configure each Article button with Previous article, Current blog, or Next article. Use [title] in Previous/Next labels when the destination title should appear.
  • Previous article and Next article sources resolve only on the current Article page. They intentionally do not resolve inside Blog cards or Search results.
  • The first or last article in a blog can have one missing boundary link. Guild omits that item rather than rendering an empty button.
  • Confirm the Article belongs to the expected Shopify blog before testing Current blog.

If the settings are correct in an unmodified copy of Guild but the output is still missing, contact support with the Article URL, theme version, screenshots of the block settings, and steps to reproduce the issue.

Guild's Newsletter form submits an email to Shopify's customer/newsletter form. An extra custom checkbox does not automatically become the technical condition that controls subscription. Use only wording and controls that match the store's real consent/privacy setup. For legal or market-specific requirements, use qualified advice and Shopify's current privacy/marketing tools.

Merchant documentation for the Guild Shopify theme.