Amazon Generic Keywords: The Backend Search Terms Field, Rule by Rule

Amazon’s “generic keywords” field is the backend search terms box: a hidden text field on each listing, edited in Seller Central under Inventory → Manage All Inventory → Edit → Product details tab. Build it to a 249-byte budget in the US — that is the number an Amazon staff account gives on Amazon’s own public seller forums — separate words with single spaces, and never repeat a word that already appears in the title, bullets, or brand field. Data checked 2026-07-23.

That is the short answer. The rest of this page exists because most of what circulates about this field is unsourced and some of it is wrong. Every rule below is either quoted from a page Amazon publishes openly, or explicitly labelled as practitioner folklore Amazon has never documented — and where the two conflict, we say so.

To find the keywords, see Amazon keyword research; for the visible copy, listing optimization; for how relevance becomes rank, the Amazon SEO guide.

Where the Generic Keywords Field Actually Lives

Amazon calls the attribute generic_keyword. The Seller Central UI labels it “Generic keyword”; help pages and vendor tools call the same field “search terms” or “backend keywords”.

Per Amazon’s own public seller blog (sell.amazon.com, checked 2026-07-23), the path is: Seller Central → Inventory → Manage All Inventory → find the listing → Edit → Product details tab → “Enter your keywords in the Generic keyword field.”

Two things follow from that placement. It is per-listing (per-ASIN) data — every child variation carries its own field, and variation families routinely end up with a populated parent and empty children — that variation behaviour is practitioner-reported, not something Amazon documents. And it is catalogue data, not customer-facing copy: in Amazon’s wording, “these keywords are not visible to customers, but they can still help a product rank for specific searches.” Nothing here is read by a shopper, which is why its rules differ from a bullet point’s. Bulk edits run through an inventory file or the Listings API rather than the UI.

The Byte Limit: What Amazon Actually Says

This is the number everyone quotes and almost nobody sources. Every figure we could trace to a page Amazon itself publishes, with its status:

The number to build to. “Less than 250 bytes” and “249 bytes” are one rule stated two ways — 249 is the largest whole number below 250. But Amazon’s own staff state the ceiling inconsistently (bytes twice, characters once), so the defensible answer is: build to 249 bytes and you satisfy every published version. These figures apply to the US marketplace, with UK/EU noted separately; we make no claim about JP, IN, or category-level exceptions.

Amazon’s canonical help pages here — “Use search terms effectively” and “Keyword attributes explained” — sit inside Seller Central. Checked 2026-07-23: requesting “Use search terms effectively” without a session returns HTTP 200 and no redirect, but the response is only an application shell carrying a sign-in prompt — the help text itself renders client-side inside a logged-in account. Neither page is quoted here first-hand.

How to find your limit instead of trusting a blog

Since the ceiling varies by marketplace and possibly category, read it out of your own account rather than adopting a number from an article — including this one.

1. Open the field in the listing editor. Sellers report that Seller Central warns beside the Generic keyword box when content is too long for that listing’s marketplace and category; the wording of that warning is practitioner-reported, not quoted from an Amazon page.
2. Read the category template. Download your category’s inventory file template and open the Data Definitions tab; it states the maximum length for generic_keyword.
3. Let the error tell you. A flat-file upload over the ceiling returns Amazon error 97779 — “Please reduce your generic keyword length to less than generic_keyword bytes”, with the real number substituted. The submission is rejected, not trimmed. (Error text per third-party listing-error references, not quoted from an Amazon page.)

How Bytes Are Counted

Bytes are not characters. The field is stored as UTF-8, where a character costs one to four bytes depending on what it is — which matters enormously outside plain English.

Amazon’s UK guidance states the base case: “Bytes correspond to 1:1 for alphanumeric characters (for example a-z, A-Z, 0-9).” An accented Latin character (é, ü, ñ) costs two; a CJK character costs three. A Japanese listing therefore has room for roughly a third of the words.

Two counting details worth stating plainly:

• Spaces occupy the budget. The limit applies to the stored string and separators are part of it. Amazon does not spell this out, so it is practitioner-reported rather than documented — but it is the assumption every byte counter makes, and the safe one.
• Count in UTF-8, not in your editor’s character count. “231 characters” tells you nothing once accents are involved.

Leave a margin: building to ~240 bytes rather than exactly 249 costs one short keyword and removes any dependence on whose counter is right.

What to Put In, and In What Order

Amazon frames the field as overflow, not a second listing: “Use this section as a spillover for keywords you want to include if you run out of room or if they don’t fit naturally in other parts of the product detail page” (sell.amazon.com, checked 2026-07-23). Fill the budget in this order:

1. Synonyms and alternative product names you used nowhere visible (flask, canteen, tumbler, thermos for a water bottle).
2. Abbreviations and expansions — pj / pyjamas, oz / ounce. Amazon recommends including “synonyms, abbreviations, and alternative names for products” (sell.amazon.com, checked 2026-07-23); whether its matcher bridges an abbreviation to the full word on its own is not documented, so budget for both forms when both get searched.
3. Regional and spelling variations — aluminum / aluminium, grey / gray, leak proof / leakproof.
4. Second-language terms for your marketplace — Spanish on amazon.com, say, if a real share of your buyers search that way. Amazon publishes no guidance either way on this; budget carefully, since accents cost double.
5. Unused long-tail from your keyword map — terms that would have made the title or bullets unreadable.

Amazon’s formatting instruction is short and specific: “Use all lowercase letters and separate words with spaces only. You can also skip articles and prepositions” (sell.amazon.com, checked 2026-07-23). No keyword order effect is documented anywhere by Amazon — the sequence above is a budgeting priority, not a ranking one.

One connection worth making: starting 27 July 2026, titles in most categories are capped at 75 characters. Most of the displaced keyword material belongs in Item Highlights rather than here — but the squeeze makes an audited, non-redundant generic keywords field more valuable, not less.

Five Rules Everyone Repeats — Sourced or Debunked

A sixth, for completeness: repeating a word inside the field itself is explicitly discouraged — “Do not repeat words within the search terms field.” Whether a repeat is merely wasteful or actively harmful is not documented.

What Is Prohibited, and What Happens

Amazon’s News_Amazon staff account published a prohibited list on the US Seller Forums (post: “Optimize your search terms”; publicly readable, checked 2026-07-23). Verbatim, the prohibited categories are:

• “Your brand or other brand names” — including your own brand, already captured in the brand field.
• “Temporary statements such as ’new’ or ‘on sale now’”
• “Subjective claims such as ‘best’, ‘cheapest’ or ‘amazing’”
• “Profanity or abusive terms”
• “ASINs”

On consequences, Amazon’s “Use search terms effectively” help page — login-gated, so cited here as reproduced in public Amazon forum threads — states that prohibited terms may result in ASIN suppression and may put account health at risk. A suppressed listing sells nothing, whatever its rank would have been.

One distinction sellers collapse: competitor brand terms are prohibited in this field, yet are a permitted targeting option in Amazon Ads. Different system, different rules.

Auditing an Existing Listing’s Field

A five-step pass. Run it on your top sellers first.

1. Export what’s actually in there. Pull the current generic_keyword value for every ASIN via an inventory report or the Listings API — reading them one at a time in the UI hides the pattern.
2. Count the bytes, in UTF-8. Flag anything at or above your ceiling, and anything suspiciously empty: an unfilled field on a live ASIN is the most common first-audit finding.
3. Diff against the visible copy. Tokenise the title, bullets, description and brand, then subtract that set from the field. Every surviving overlap is wasted budget by Amazon’s own statement.
4. Screen against the prohibited list. Search for competitor brands, your own brand, ASIN-shaped tokens (B0 plus eight alphanumerics), and superlatives. These carry suppression risk, so they come out first regardless of budget.
5. Refill, then watch rank. Replace what you removed with synonyms and unused long-tail. Nothing on the page looks different afterwards, so rank movement is your only feedback — change this field alone if you want that signal to be readable.

Do / Don’t Checklist

Frequently Asked Questions

What are Amazon generic keywords?

“Generic keywords” is the Seller Central name for the backend search terms field — hidden, per-listing text that helps Amazon match your product to shopper queries but is never shown to customers. Edit it under Inventory → Manage All Inventory → Edit → Product details tab, per Amazon’s public seller blog, checked 2026-07-23.

Is the limit 249 bytes or 250 bytes?

Both numbers come from Amazon staff posts on Amazon’s own public seller forums: 249 bytes for the US, “limited to 250 bytes” for the UK/EU — the same ceiling stated two ways, since 249 is the largest whole number under 250. Build to 249 bytes and you comply with every published version. Checked 2026-07-23.

Do spaces count toward the byte limit?

Almost certainly yes — the limit applies to the stored string and spaces are part of it. Amazon does not document this, so treat it as practitioner consensus rather than a published rule, and leave a few bytes of margin.

Should I add misspellings to my backend keywords?

Amazon’s guidance says no: “Include spelling variations, no need for misspellings. Our systems compensate for common customer misspellings” (Amazon staff, UK Seller Forums, checked 2026-07-23). Spend the bytes on genuine variations instead — regional spellings, hyphenation, abbreviations.

What happens if I exceed the byte limit?

A flat-file upload is rejected with error 97779 rather than trimmed; in the UI, Seller Central warns beside the field. The widely repeated claim that Amazon silently de-indexes the entire field when you go one byte over traces to a 2018 seller-forum discussion and is not confirmed by any Amazon page we could read.

Can I put competitor brand names in the generic keywords field?

No. Amazon’s staff-published prohibited list names “Your brand or other brand names” explicitly, and prohibited terms are described as risking ASIN suppression and account health. Competitor brand targeting is permitted in Amazon Ads — that is a separate system with separate rules.

Conclusion

Two rules do most of the work here, and both come from Amazon directly: stay inside the byte ceiling (249 in the US, counted in UTF-8), and never spend a byte on a word that already appears in the title, bullets, or brand field. The ordering debates, the plural question, the misspelling habit — all either unconfirmed or worth less than those two.

Audit before you rewrite, screen against the prohibited list before you save, and change this field alone so the rank signal stays readable. Then take the keywords it could not hold back to your keyword map, and put the visible ones to work in your listing optimization pass.