Explore

Creating Metafields & Metaobjects

Without res.theme we had an opportunity to find a way to optimize our search, site functionality, and collection management

Pain points included: poor search functionality, unclear objective of “ecom category” section, messy tagging infrastructure for faceted search

⁠

Old context into faceted search and collection management in res.theme⁠

⁠

Why does it matter?

Metafields and Metaobjects helped us leverage Shopify’s native language to classify our information more seamlessly, without the need to create a thousand tags. While tags can be used to create metafields/metaobjects, it can be streamlined, limited, and pushed further.

Optimize SEO

Metadata is tagged to the ecom listing itself, so it’s more easily identifiable in SEO and search

I.e if you search red on Tucker’s site it’ll show all the products that have the metaobject red. Before, you would only see it if the title included red.

There are google implemented metafields built in with google analytics but more research needs to be done here

Easy to use for internal tracking or external functionality

We have the framework in

create.ONE⁠

already but it needs to be upgraded significantly. Learning how Shopify does theirs may help us identify the “What” and “How”

It’s essentially what the “ecommerce category” button is technically a Category metafield in create.ONE; it classifies styles on the backend to. The infrastructure is there, but there needs to be insight into the what and how to use it in conjunction w/ Shopify.

This could be used to create faceted search and even automatic collections without added effort.

Assuming this is also the goal of the tagging tab in the launch styles card

⁠