MetaGenius AI

MetaGenius AI Custom Instructions: Brand Voice Guide

Custom instructions are one store-wide field of up to 500 characters. They shape meta titles, descriptions and product descriptions, but they don't currently reach alt text, FAQs, keyword ideas or Blog Writer posts.


Key takeaways

  • One field per store. Up to 500 characters, set in Settings. There's no separate version for each collection or product type.
  • It reaches meta tags and product descriptions. That includes the homepage, Auto-Fix meta tags and Autopilot meta tags.
  • It doesn't reach alt text. In the current code, alt text, FAQs and keyword ideas take only the language setting. Blog Writer takes language and tone.
  • Some rules can't be overridden. Titles are cut to 60 characters and descriptions to 155, and a set of overused AI words is replaced after generation.
  • Saved tags don't change by themselves. New instructions only affect what you generate from then on.

MetaGenius custom instructions are one store-wide field that steers meta titles, meta descriptions and product descriptions, and doesn't reach alt text. We make MetaGenius AI, and this guide comes from reading how the app's code stores and uses that field, because a good instruction depends on knowing where it goes.

Generic advice on brand voice prompts assumes the model reads your rule and follows it everywhere. Here, the field reaches some outputs and not others, and a few limits run after the model has finished, so no instruction can move them.

The examples below are untested starting points. We haven't measured their effect on clicks or rankings, so judge them on the copy they produce.

How MetaGenius custom instructions work

The field lives in Settings, on the same card as the output language and tone. It's optional, it holds up to 500 characters, and it's stored once per store. It applies to Free, Starter and Pro alike.

When you generate a meta title and description, the app builds the AI's instructions in this order: its own SEO rules, the current date, the language, your tone, and finally your text. It then sends the product details separately: title, type, vendor, tags, price, store name and up to 500 characters of the description.

Those details vary by screen, which limits what a rule can do. Collections, blog posts and pages send only a title and their text. Autopilot leaves out the price. A rule like "name the fabric" can only work when the fabric appears in what was sent, so fill in the source data first.

That order has two practical effects. Your text arrives on top of a long set of existing rules, so it works best as additions and preferences, not as a replacement for them. And it's guidance to a language model, not a setting in a form. It may not be followed every time, which is why review stays part of the job.

Where it applies, and where it doesn't

This is the table to read before you write anything. It reflects the generation code as of November 2026.

What each MetaGenius AI output receives
OutputLanguageToneCustom instructions
Meta titles and descriptions (products, collections, blog posts, pages)YesYesYes
Homepage SEOYesYesYes
Auto-Fix and Autopilot meta tagsYesYesYes
AI product descriptionsYesYesYes
Blog Writer postsYesYesNo
Image alt textYesNoNo
Product and page FAQsYesNoNo
Keyword ideasYesNoNo

The alt text row matters most, because the help text under the field in Settings currently says "every title, description and alt text". In the code, the field isn't passed to the alt text generator.

So a rule such as "always name the fabric" won't affect your AI-generated alt text. Alt text is written from the product's own data: title, type, tags, options and description. If the fabric is in that data, it can appear; if not, the app leaves it out, since it doesn't look at the image.

For Blog Writer, edit the draft against your brand rules before you publish it. For FAQs, you can review and edit the text before saving when you generate for a single product.

What your instructions can't override

Some rules run in code after the model replies, so asking for something different has no effect. Others are firm prompt rules that your text would be competing with.

Limits on meta titles and descriptions
If you ask forWhat happens
Titles over 60 characters, or descriptions over 155The app asks the model to retry once, then cuts at a word boundary if it's still too long.
Words like "elevate" or "unleash"A list of overused phrases is replaced with plainer words after generation.
A year at the end of each titleTrailing years are removed after generation, unless the year sits inside the phrase, as in "2026 Calendar".
Claims not in the product dataA second model checks meta tags and product descriptions against the product data and rewrites what it doesn't support. A code check then removes unsupported health, skincare, child-development, spec and quality claims.

Those limits are sensible defaults, not a verdict on what Google shows. Google says it can change the title link and choose its own snippet. Our guides to meta title best practices and the meta description character limit cover the length side.

How to write instructions the model can follow

The wrong way is to describe your brand. "We're a warm, authentic, design-led family business" gives the model adjectives, and the tone setting already does that job. A useful instruction names something a reader could check in the output.

Vague instructions and checkable rewrites
VagueCheckable
Sound premiumNo exclamation marks. Never use "cheap", "deal" or "bargain".
Use our terminologyWrite "trainers", never "sneakers".
Be compliantNever say a product treats, cures or prevents any condition.
Mention our benefitsMention that delivery is free over £50 where space allows.
  • Lead with the rule you'd regret most. You only get 500 characters, so legal and terminology rules come before style.
  • Don't ban the search term. If shoppers search for "backpack", a rule requiring "rucksack" may cost you the phrase they use. Check the Search Console Performance report before banning a word.
  • Keep offers durable. A sale line stays in saved tags until someone regenerates or edits them. Leave out end dates and seasonal promotions.
  • State only what's true store-wide. The rule applies to every item you generate, so "made in Portugal" is a problem if only half the range is.
  • Write for meta tags as well as descriptions. The same field feeds a 60-character title and a longer product description, so "tell the founding story" won't fit.

Example instructions to adapt

Each of these hypothetical stores' rules fits within the limit. Replace every detail with facts about your own store.

MetaGenius AI meta title and description editor with character counts and a Google result preview
Listing artwork of the editor. Check each example's output in the Google preview before you save it.

Example 1: an apparel brand in the UK

Use British spelling and write "trainers", never "sneakers". No exclamation marks, "must-have" or "perfect". If the fabric is in the product details, name it. Leave the store name out of titles when it would push out the fabric or fit.

Example 2: a quiet luxury jeweller

Short, calm sentences, with the material and setting ahead of adjectives. Never use "cheap", "deal", "bargain" or "affordable". No calls to action with "hurry" or "now". End descriptions with "View the piece" or "See the details".

Example 3: a supplement store

Never claim a product treats, cures or prevents any condition. Never use "clinically proven" or "doctor recommended". Describe the ingredients, format and serving size only if they are in the product details. Use "may support" only when the product details do.

Treat that third one as a seat belt, not a sign-off. A language model can still produce a claim you can't make, so in regulated categories every line still needs your usual compliance review.

Example 4: a store with a real delivery offer

Where space allows in descriptions, mention free UK delivery on orders over £50. Do not mention it in titles. Do not mention returns, warranties or awards. Use metric sizes first.

The field's own placeholder suggests "Always mention free shipping", but the base prompt says proof points must come from the provided context, so the two can pull against each other. Check whether your line appears consistently, and remember you'd need to regenerate or edit tags if the threshold changes.

Example 5: a German-language store

Address the reader as "Sie", never "du". Write "Rucksack", not "Backpack". Keep English product names as they are. Avoid English marketing words where a normal German word exists.

Pair this with German as the output language in Settings. The app asks the model to write natively in that language, but it doesn't choose between formal and informal address for you. We haven't compared results from writing instructions in English against writing them in German, so try both on a few products.

What we saw when we tested an instruction

On 2 November 2026 we ran the app's generation code directly on sample products, not real stores and not through the app's screens.

One run used this instruction: "Use British spelling. Never say cheap or affordable. Mention the material in the title when it is listed." This run used the code from before that day's fact-check change, and we haven't repeated it on the new code yet.

Sample products with and without the instruction (code before 2 November 2026)
Sample productWithout the instructionWith the instruction
Linen dressTitle already named the European linen; description ended "Choose your colour"Title named the European linen; description ended "Choose your colour."
Kids rain boots"Kids Rain Boots – Natural Rubber, Pull Handles | Puddle Co"The same title, word for word

The instruction was followed, but it changed little, because the output already did those things. That is the test result you're looking for: a line that makes no visible difference is spending characters you could use on a rule that does. Output also varies between runs, so compare a few generations, not one.

One more detail from the code. Since 2 November, meta tags and product descriptions get a second fact-check pass, and that pass receives the product data and the language but not your instructions. It's told to change as little as possible, so most rules survive it, but check that wording rules such as spelling still hold in the saved text.

Test MetaGenius custom instructions for a few credits

Don't bulk-run a new instruction. Bulk meta runs save straight to your store, and the app has no undo. Use the single-product editor, which shows the generated text and a Google preview before you save.

  1. Choose five products: a best seller, a thin listing, a long product name, a different product type and one with a hard-to-avoid word from your banned list.
  2. Generate with no instructions. That's your baseline. Note the results before you discard them.
  3. Add one version of your rules and generate again. Then try a second version.
  4. Mark each result against your rules: followed, partly followed or ignored.
  5. Keep what changes the output. Delete any line that made no visible difference, and use those characters for something else.

The cost is easy to work out. Three versions across five products at 2 credits each is 30 credits, which fits within the Free plan's 50 a month. Each generation uses credits even if you don't save the result.

Tone preset or instruction?

The two settings do different jobs, and using both for the same thing wastes characters. The 5 tone presets are Professional, Friendly, Luxury, Benefit-focused, and Storytelling, and each one adds a single line about how the copy should feel. Your instructions are for everything specific to your brand.

Which setting to use for each job
What you wantUse
A general mood, such as polished or friendlyTone preset
Words to use or avoidCustom instructions
Spelling standard or form of addressCustom instructions
Output languageThe language setting, not the instructions field
A target phrase for one productNot this field. Instructions apply to the whole store.

Budget for changing your mind

Instructions affect new generations only, so a change of brand voice has a price. For a hypothetical store with 300 products, regenerating every meta title and description at 2 credits each is 600 credits. That's more than Starter's 250 in one cycle, and bulk runs replace saved text without a preview.

This is why the cheap test above comes first. It's far easier to settle the wording across five products than to pay for a second pass across a whole catalog. If you do change the rules later, consider regenerating only your top pages and leaving the rest until they next need work.

When instructions aren't enough

A 500-character field can stop the worst mismatches. It can't replace a writer on the pages that carry your brand. Our MetaGenius AI review suggests the split we'd use: write your top pages by hand, and let the app handle the long tail under your rules.

For where AI tags work and where they fall short, see our AI meta tag generator guide and our notes on writing meta descriptions that convert.

Keep a copy of the field in your own brand document, with a date beside each version. Then write down the one rule your brand would be embarrassed to see broken, make it the first line of your instructions, and generate five products to see whether it holds.

Frequently asked questions

Where do I set custom instructions in MetaGenius AI?
In the app's Settings, on the card for how the AI writes. It holds the output language, the tone and an optional custom instructions field of up to 500 characters, all saved together for the whole store.
Do MetaGenius custom instructions apply to image alt text?
Not in the current code. The alt text generator receives the product's title, type, tags, options and description, plus the language, but not the tone or custom instructions. Review alt text separately, and edit any wording your brand needs by hand.
Can I set different instructions for different collections?
No, there's one field per store. If a range really needs different rules, you can change the field, generate that range, and change it back. Bulk runs and Autopilot use whatever is saved at that moment, so take care with the timing.
Are custom instructions available on the Free plan?
Yes. Tone presets and custom instructions are on every plan, including Free. Generating with them costs the usual credits, for example 2 credits for a meta title and description.
Will changing my instructions update tags I've already saved?
No. Instructions are only read when text is generated. Saved titles and descriptions stay as they are until you regenerate them, which uses credits again, so test new wording on a few products first.

Test your brand rules on five products.

Install the Free plan, add your custom instructions in Settings, and generate tags for five products. No credit card is needed.

Install free
  • Free plan
  • 50 AI credits/month
  • 15 languages
  • No credit card