` and `<meta name="description">` in `<head>` 2. Or paste the URL into [metatags.io](https://metatags.io/) to preview how it will appear on Google If a page doesn't use your default template, check whether a [Custom meta tags rule](https://file+.vscode-resource.vscode-cdn.net/Users/hooman/Vibe%20working/Avada/products/avada-seo-suite/userguide/search-appearance/meta-tags/custom-meta-tags.md) is overriding it — rules always take precedence over Default. ### Multi-language templates <a href="#multi-language-templates" id="multi-language-templates"></a> If your store is published in multiple languages, use the **language selector** at the top right of the Meta tags screen to switch. Each language has its own Default templates — you'll need to write (or AI-generate) them separately for every language. Languages must first be published in **Shopify Admin → Settings → Languages** to appear in the selector. ### How to add metafield to meta tags? 1. In Shopify admin, click Settings <figure><img src="https://154471318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPf5QlibAKQnTygXuMIzw%2Fuploads%2F1tzq3KMZAtQlGDWvwTn5%2Fselect%20settings.png?alt=media&token=d2e5eb0d-9284-4d99-9ddd-04cc09f34013" alt=""><figcaption></figcaption></figure> 2. Select **Custom data** <figure><img src="https://154471318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPf5QlibAKQnTygXuMIzw%2Fuploads%2FhZ6CSSScvmr3yWLHhRko%2Fselect%20custom%20data.png?alt=media&token=3506674a-cde8-45b2-90e9-9ac352f24305" alt=""><figcaption></figcaption></figure> 3. Select which page (Products, Collection, Blogs) you want to add metafield to <figure><img src="https://154471318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPf5QlibAKQnTygXuMIzw%2Fuploads%2FFoUNOMlMQDqBOTY6Mi9I%2Fselect%20page%20to%20add%20metafield%20to.png?alt=media&token=671a5e7d-536d-4930-9801-9657f4268b5b" alt=""><figcaption></figcaption></figure> 4. Click **Add definition** to add new metafield <figure><img src="https://154471318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPf5QlibAKQnTygXuMIzw%2Fuploads%2Fd4eMU3yYVKD4b6j1M86q%2Fadd%20definition%20metafield.png?alt=media&token=b89d4c0f-6a98-473c-806d-ffd1aac21b26" alt=""><figcaption></figcaption></figure> 5. Build your metafiled and click **Save** <figure><img src="https://154471318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPf5QlibAKQnTygXuMIzw%2Fuploads%2FEkphCF0UOJ11xiChHI8Y%2Fadd%20collection%20metafield%20definition.png?alt=media&token=109efc89-5f59-4840-a0c6-cbd9ee562f3e" alt=""><figcaption></figcaption></figure> 6. In app, go to Search appearance -> Meta tags. Go to page type you want to add to metafield to. \ Click `</>` to add your metafield. <figure><img src="https://154471318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPf5QlibAKQnTygXuMIzw%2Fuploads%2FMcP8WCmoVgJsGty0R9K5%2Fselect%20metafields.png?alt=media&token=5b73d720-d92c-4cc4-846d-9198b12d8c54" alt=""><figcaption></figcaption></figure> --- # Agent Instructions: 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: ``` GET https://docs.avada.io/seo-suite-help-center/search-appearance/meta-tags/default-meta-tags.md?ask=<question> ``` The question should be specific, self-contained, and written in natural language. 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.

# Default Meta Tags > Previously called "Meta tags basic". Your existing settings are preserved. {% hint style="info" %} **Who can use this feature?** * This feature is available for all users. {% endhint %} Default meta tags let you set a single template that applies to every page of a type — all Products, all Collections, or all Blog posts with [dynamic variables](https://docs.avada.io/seo-suite-help-center/search-appearance/meta-tags/variables). Instead of writing a unique meta title and description for each product manually, you define the format once and let the app fill it in with dynamic data for every page. {% hint style="info" %} If you're using Meta tags basic, you can still set unique content for one page by using [custom meta tags](https://docs.avada.io/seo-suite-help-center/search-appearance/meta-tags/custom-meta-tags-details). {% endhint %} ### Where to find it Go to **Search appearance → Meta tags**. The screen has three tabs at the top — **Product**, **Collection**, **Blog post**. Each tab contains a **Default meta tags** card. > Homepage meta tags are not configured here. Go to **Shopify Admin → Online Store → Preferences** to set the homepage title and description. ### Set up a template

1. Select the tab for the page type you want to configure (Product, Collection, or Blog post) 2. Turn on the **Default meta tags** toggle 3. Enter a template in the **Meta title** field (e.g., `{{ product.title }} - {{ shop.name }}`) 4. Enter a template in the **Meta description** field 5. Watch the **Google preview** panel on the right update in real time 6. Click **Save** Repeat for the Collection and Blog post tabs to cover your whole store. #### Insert variables with @ Type `@` anywhere in the meta title or description field to open the variable picker. Pick a variable from the list and it's inserted at the cursor - no need to remember the exact syntax. You can also click the `` icon on the right side of any field to browse the full list of available variables, including Shopify custom metafields. See the full [variables reference](https://docs.avada.io/seo-suite-help-center/search-appearance/meta-tags/variables) for everything you can use. ### Tips for a good template * **Include the page-specific variable** (e.g., `{{ product.title }}`, `{{ collection.title }}`) so every page has unique content * **Add your store name** with `{{ shop.name }}` for brand recognition * **Keep titles around 50–60 characters** — Google truncates longer titles in search results * **Keep descriptions around 140–160 characters** — enough room for a benefit, a CTA, and a keyword * **Avoid keyword stuffing** — Google may ignore an unnatural description and generate its own from page content ### Save and verify After saving, open a product, collection, or blog page on your storefront and check the result: 1. Right-click the page → **Inspect** → look for `` and `<meta name="description">` in `<head>` 2. Or paste the URL into [metatags.io](https://metatags.io/) to preview how it will appear on Google If a page doesn't use your default template, check whether a [Custom meta tags rule](https://file+.vscode-resource.vscode-cdn.net/Users/hooman/Vibe%20working/Avada/products/avada-seo-suite/userguide/search-appearance/meta-tags/custom-meta-tags.md) is overriding it — rules always take precedence over Default. ### Multi-language templates <a href="#multi-language-templates" id="multi-language-templates"></a> If your store is published in multiple languages, use the **language selector** at the top right of the Meta tags screen to switch. Each language has its own Default templates — you'll need to write (or AI-generate) them separately for every language. Languages must first be published in **Shopify Admin → Settings → Languages** to appear in the selector. ### How to add metafield to meta tags? 1. In Shopify admin, click Settings <figure><img src="https://154471318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPf5QlibAKQnTygXuMIzw%2Fuploads%2F1tzq3KMZAtQlGDWvwTn5%2Fselect%20settings.png?alt=media&token=d2e5eb0d-9284-4d99-9ddd-04cc09f34013" alt=""><figcaption></figcaption></figure> 2. Select **Custom data** <figure><img src="https://154471318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPf5QlibAKQnTygXuMIzw%2Fuploads%2FhZ6CSSScvmr3yWLHhRko%2Fselect%20custom%20data.png?alt=media&token=3506674a-cde8-45b2-90e9-9ac352f24305" alt=""><figcaption></figcaption></figure> 3. Select which page (Products, Collection, Blogs) you want to add metafield to <figure><img src="https://154471318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPf5QlibAKQnTygXuMIzw%2Fuploads%2FFoUNOMlMQDqBOTY6Mi9I%2Fselect%20page%20to%20add%20metafield%20to.png?alt=media&token=671a5e7d-536d-4930-9801-9657f4268b5b" alt=""><figcaption></figcaption></figure> 4. Click **Add definition** to add new metafield <figure><img src="https://154471318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPf5QlibAKQnTygXuMIzw%2Fuploads%2Fd4eMU3yYVKD4b6j1M86q%2Fadd%20definition%20metafield.png?alt=media&token=b89d4c0f-6a98-473c-806d-ffd1aac21b26" alt=""><figcaption></figcaption></figure> 5. Build your metafiled and click **Save** <figure><img src="https://154471318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPf5QlibAKQnTygXuMIzw%2Fuploads%2FEkphCF0UOJ11xiChHI8Y%2Fadd%20collection%20metafield%20definition.png?alt=media&token=109efc89-5f59-4840-a0c6-cbd9ee562f3e" alt=""><figcaption></figcaption></figure> 6. In app, go to Search appearance -> Meta tags. Go to page type you want to add to metafield to. \ Click `</>` to add your metafield. <figure><img src="https://154471318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPf5QlibAKQnTygXuMIzw%2Fuploads%2FMcP8WCmoVgJsGty0R9K5%2Fselect%20metafields.png?alt=media&token=5b73d720-d92c-4cc4-846d-9198b12d8c54" alt=""><figcaption></figcaption></figure> --- # Agent Instructions: 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: ``` GET https://docs.avada.io/seo-suite-help-center/search-appearance/meta-tags/default-meta-tags.md?ask=<question> ``` The question should be specific, self-contained, and written in natural language. 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.