> For the complete documentation index, see [llms.txt](https://www.locksmith.guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.locksmith.guide/faqs/more/i-am-getting-an-already-taken-error-when-trying-to-create-a-metafield-definition-for-seo.hidden.md).

# I am getting an "already taken" error when trying to create a metafield definition for seo.hidden

How to get past this Shopify error when attempting to create the seo.hidden metafield definition for products

{% hint style="info" %}
The Locksmith app has the ability to automatically manage the seo.hidden metafield for locked products in your store. [More information about that here](/tutorials/more/automatically-hide-from-sitemaps-and-manage-seo-metafield.md).\
\
If you've toggled this setting on at any point, but still wish to create a definition for this metafield, this guide can help.
{% endhint %}

Shopify allows you to create metafield definitions for products, and other content, in your store, even if the metafield already exists on your products. This is typically done by viewing your unstructured metafields and pressing the "Add definition" button. You can find more general information on creating metafield definitions [in this Shopify guide](https://help.shopify.com/en/manual/custom-data/metafields/metafield-definitions).

For reasons unknown, Shopify has decided to exclude the `seo.hidden` metafield from this list, even if some of your products have this metafield.

There is a simple trick to get around this.

1. Go to the "Product metafield definitions" page. It should look something like this:

<figure><img src="https://277214568-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MUeGWHuijBPr8Og1Gta%2Fuploads%2FCimJaiDSCVjl74DcRyFu%2FScreenshot%202024-11-13%20at%2023.42.37.png?alt=media&amp;token=92a8aee2-d385-47c9-aebf-a29117638cb8" alt=""><figcaption></figcaption></figure>

2. In the URL bar for your browser, paste add in the following *to the end of the already existing URL*:

<pre><code><strong>/migrate/seo/hidden
</strong></code></pre>

You should end up with something like:

{% code overflow="wrap" %}

```
https://admin.shopify.com/store/YOUR-SHOP-URL/settings/custom_data/product/metafields/migrate/seo/hidden
```

{% endcode %}

3. You'll be brought to the page to create a definition for `seo.hidden`. Change the type to "Integer" all other settings are up to you.

<figure><img src="https://277214568-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MUeGWHuijBPr8Og1Gta%2Fuploads%2FhOs0oQGROFvhOJD25SAL%2FScreenshot%202024-11-13%20at%2023.46.21.png?alt=media&amp;token=f1b66f45-d8eb-454a-a16c-b2e10a6d1fcb" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.locksmith.guide/faqs/more/i-am-getting-an-already-taken-error-when-trying-to-create-a-metafield-definition-for-seo.hidden.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.