Amazon Backend Keywords Explained:

The Difference Between KDP Search Terms and Vendor Keywords (Vendor Central, Amazon Advantage, ONIX, onixEDIT, and Manual Entry)

Backend keywords are an important but often misunderstood part of Amazon book metadata. They help Amazon understand what a book is about so it can surface the title in relevant searches. However, how these keywords are entered and structured differs significantly between Kindle Direct Publishing (KDP) and Amazon Vendor systems such as Vendor Central or Amazon Advantage. Publishers also encounter additional differences depending on whether metadata is delivered through ONIX feeds, tools like onixEDIT, or entered manually in the Vendor Central catalog.

Understanding these differences is critical for publishers, because the same keyword strategy cannot simply be copied across platforms. The systems handle keyword formatting, character limits, and ingestion differently.

At Amplify Marketing Services, backend keyword development is part of our Amazon metadata optimization services for publishers, delivered either as a standalone project or as part of an ongoing Amazon Ads and optimization retainer.

What Amazon Calls Backend Keywords

Amazon typically refers to backend keywords as Search Terms in KDP and Keywords or Subject Keywords in Vendor systems and ONIX feeds. In the broader SEO world, they are sometimes described as off-page keywords, but Amazon itself generally uses the terms “Search Terms” or “Keywords.”

Regardless of the name, they serve the same purpose: providing additional discoverability signals that are not visible on the product page. These keywords help Amazon understand themes, topics, and audiences that may not appear directly in the title, subtitle, or description.

For example, a cookbook titled The Beginner’s Guide to Baking Bread may benefit from backend keywords like:

• artisan bread

• sourdough baking

• bread baking recipes

• home baking techniques

These phrases help Amazon connect the book to related searches without cluttering the visible metadata.

Backend Keyword Differences: KDP vs Vendor Central vs ONIX

This comparison highlights the major structural differences between Amazon publishing systems:

Backend Keywords in KDP

KDP has the most rigid structure for backend keywords. Publishers are given seven search term fields in the KDP dashboard. Each field allows up to 50 characters, with an overall limit of roughly 250 bytes across all fields combined.

Because of these limits, keyword phrases must be concise. The best practice is to use space-separated keyword phrases, not comma-separated lists.

Example of a KDP search term field: historical mystery amateur sleuth cold case investigation

Amazon automatically parses the individual words and phrases within the string.

Amazon recommends avoiding several types of terms in these fields:

• Subjective phrases such as “best book”

• Time-sensitive statements such as “new”

• Brands that you don’t have authorization to use

• See Amazon’s complete list here

Because the space is limited, publishers should focus on phrases that expand discoverability rather than repeating existing metadata.

Backend Keywords in Vendor Central and Amazon Advantage

Vendor Central and Amazon Advantage operate differently from KDP. Instead of seven structured search term boxes, keyword entry may occur through:

• Manual editing within Vendor Central

• Catalog flat-file uploads

• ONIX metadata feeds

Character limits are generally less restrictive. Vendor Central keyword fields may allow several hundred characters, though Amazon’s indexing system still tends to normalize keyword data internally.

Formatting best practices remain similar to KDP. Space-separated phrases work best.

Example of a Vendor keyword field: small business marketing startup strategy entrepreneurship leadership business growth

Because Vendor systems are more flexible, publishers can include additional discovery phrases related to audience, topic, and reading intent.

Using ONIX to Supply Keywords

Many traditional publishers deliver metadata through ONIX feeds, which provide structured metadata updates to retailers.

In ONIX, keywords are usually supplied using Subject Scheme Identifier 20, which represents keyword phrases.

Example ONIX structure:

<Subject>

<SubjectSchemeIdentifier>20</SubjectSchemeIdentifier>

<SubjectHeadingText>small town mystery</SubjectHeadingText>

</Subject>

Each phrase is submitted as its own SubjectHeadingText entry rather than combined into a single keyword string.

This approach allows publishers to provide a broader set of keyword signals while maintaining structured metadata.

Using onixEDIT

onixEDIT is a widely used tool for managing and exporting ONIX metadata.

When publishers enter keywords in onixEDIT, each phrase is typically added as a Subject entry using the keyword scheme identifier. When the ONIX file is generated, those entries are automatically converted into XML elements.

The workflow generally looks like this: Publisher → onixEDIT → ONIX feed → Amazon ingestion

This system allows metadata managers to maintain keyword lists in a centralized metadata environment rather than entering them directly in retailer dashboards.

Entering Keywords Manually in Vendor Central

If metadata is not supplied through ONIX, keywords may sometimes be entered manually through Vendor Central.

The navigation path typically looks like this: Catalog → Items → Edit → Keywords or Search Terms

Unlike ONIX keyword entries, this field usually expects a single keyword string rather than separate structured entries.

Example: personal finance basics budgeting tips debt reduction retirement planning

Even though the field allows longer strings, the same keyword best practices apply: focus on meaningful phrases rather than repeating the same words excessively.

When Words Should (and Should Not) Be Repeated

Keyword repetition is sometimes misunderstood in Amazon metadata. Repeating a word within backend keywords is not inherently bad. In fact, repeating a core term across different meaningful phrases can help Amazon understand how a book relates to multiple search queries. For example, a baking book might include phrases such as bread baking, sourdough bread, artisan bread recipes, and bread baking techniques. In this case, the repeated word “bread” helps connect the book to several different reader search patterns.

What should be avoided is repeating the exact same phrase or repeating a word without adding new context. A keyword string like bread bread bread baking does not create additional discovery signals and simply wastes valuable keyword space.

The general rule is simple: repeat words when they help form new meaningful search phrases, but avoid redundant repetition that adds no new context.

Keyword Formatting Best Practices

Across both KDP and Vendor systems, several best practices consistently improve keyword performance.

Use multi-word phrases rather than single keywords. Two-to-four word phrases provide stronger search signals and better match reader search behavior.

Avoid duplicating words that already appear prominently in the title, subtitle, or series name unless they help form new, meaningful keyword phrases. Backend keywords should expand discoverability by introducing additional search terms and phrase combinations rather than repeating visible metadata without adding context.

Focus on reader intent. Good keywords often describe the problem the book solves, the topic it covers, or the audience it serves.

For example, a business book might include phrases like:

• startup strategy

• small business marketing

• entrepreneur leadership

• business growth planning

These phrases reflect real search queries readers might use.

Amazon’s indexing system extracts word combinations from keyword phrases rather than evaluating each term individually. Because of this, repeating a core topic word across different phrases can expand the range of searches a book may appear in. For example, phrases like small business marketing, small business strategy, and small business growth all reinforce the same topic while targeting different search behaviors. The key is ensuring that each phrase introduces a new combination rather than duplicating the same wording.

Case in Point

Although the underlying keyword strategy remains consistent across Amazon publishing systems, the way those keywords must be entered differs depending on whether a publisher is using KDP, entering metadata manually through Vendor Central or Amazon Advantage, or delivering metadata via ONIX. The following example illustrates how the same keyword strategy might be formatted across these different workflows using a Regency romance title as the example.

Final Takeaways

Backend keywords remain a valuable discoverability tool, but their implementation differs significantly between KDP and Amazon Vendor systems.

KDP requires tightly structured keyword phrases within strict character limits. Vendor systems provide more flexibility, especially when metadata is delivered through ONIX feeds or managed through tools like onixEDIT.

Regardless of the workflow, the goal remains the same: provide Amazon with meaningful keyword phrases that expand discoverability beyond what is already visible in the book’s metadata.

When used strategically, backend keywords help Amazon better understand a book’s topic, audience, and reader intent. This often means constructing keyword phrases carefully, sometimes repeating important terms across different phrase combinations so Amazon can associate the book with a wider range of relevant searches. Understanding how these signals work, and how they differ across KDP, Vendor systems, and ONIX metadata, is an important part of building a strong Amazon discoverability strategy.

At Amplify Marketing Services, we regularly help publishers optimize metadata for both new releases and backlist titles, including backend keyword development, category strategy, and product page improvements. This work can be delivered as a standalone metadata optimization project or as part of an ongoing Amazon Ads and optimization retainer, where improved metadata and advertising campaigns work together to increase visibility and sales.

Related Articles