Shopify blog metafield missing? Prove the Blog or Article, value, and template.

Use this page when a blog landing page or article should show a saved custom field but the public output is blank or absent. A field on the Blog object is not automatically available on every Article, and an Article field is not a store-wide setting.

If the value belongs to a custom page, use the page metafield playbook. If a definition entry or reference is blank, use the metaobject entries diagnosis. Keep the resource proof narrow.

Open Settings → Custom data and inspect Blogs or Blog posts, depending on where the field should live. Record the exact namespace and key, such as custom.editor_note, plus the field type. The human label is not the identifier a theme reads.

Open the exact blog or article in Content and confirm the value is filled, saved, and still present after refresh. Check the handle, publication status, and whether a reference, list, rich text, or file needs type-specific rendering. A definition description or a value on a different article is not proof.

Identify the exact /blogs/handle or /blogs/handle/article-handle URL. In Online Store → Themes, verify the Current published theme and the blog or article template used by that URL. A custom JSON article template can differ from the default.

Check the section or block that should display the field. Preview URLs and draft themes can show a binding that production does not have. Save and publish only after the resource, handle, template, and source match.

For an Online Store 2.0 block, open the dynamic-source picker from the correct blog or article template and select the field with the recorded namespace and key. If the picker does not offer it, stop and recheck the resource, definition type, and theme schema instead of guessing.

For Liquid, verify the object matches the resource: blog.metafields.namespace.key for a blog-level field or article.metafields.namespace.key for an article-level field. Respect rich text, references, lists, and files. Check empty fallbacks, CSS visibility, and section conditions without exposing private admin data.

Open the exact blog or article URL in an incognito window, hard-refresh, and inspect the rendered DOM or page source. Record the blog handle, article handle, template, namespace.key, value type, theme build, and timestamp.

Classify the result: wrong resource, missing definition, empty value, wrong handle, wrong template, unconnected source, type mismatch, hidden section, or stale deployment. If preview works but production does not, the publish boundary is the first suspect. Clear only a relevant cache after those proofs pass.

Stay DIY if the work is one blog or article definition, one saved value, one published template, and one production render. You do not need another tool or a promise about results to complete that proof path.

Pay for the Latch AI Ops install when you want Nico to connect the stack you already use so storefront exceptions, lead capture, ops alerts, and a checkout-ready workflow are wired together. $997 USD one-time buys the install for one live Shopify store, with a 72-hour delivery window after collaborator access. It does not buy more orders, recovered revenue, a conversion guarantee, or a theme rebuild. Checkout is on Whop; owner passwords are not requested.