Skip to main content
Upcoming discountNext discount: 10% off — today 19:00.starts in--:--:--Get a quote →
Client Login
Home News What Is Genre Embedding? How Many Text Types Sit on a Single Page?

Digital Products and Accessibility 5 August 2026

What Is Genre Embedding? How Many Text Types Sit on a Single Page?

A product page is not a single text. Inside it there is a description, a specification, a legal notice and a customer review. Each is a different genre and calls for a different translation decision.

When you say you want an e-commerce product page translated, the other side asks for the word count. That page, though, is not a single text. It holds text from at least five different genres, and each of them asks for a different approach.

Contents

Genre embedding is the concept that names this nesting. One genre sits inside the structure of another; the containing genre counts as primary and the genre lodged within it as secondary (Martin 1995, p. 24; Bhatia 1997).

This article explains how to tell embedded genres apart, which translation approach suits each of them, and why projects commissioned with a single set of instructions run into trouble.

Genre embedding and hybrid genres: several genres in one structure

Genres that house instances of other genres within their structure are called complex or hybrid genres. Most digital products fit that description, because a shared shell and variable content sit together.

The shell is generally the same: the interface, the terms of use, the help pages. The content varies. On a social network, a privacy policy, usage guidelines, interface copy and the photographs, videos or comments produced by users all sit side by side.

How open genres are to embedding varies. A corporate food company site can host both a recipe and a contract; a shooter game cannot host a recipe. Not every genre, in other words, accepts every secondary genre.

This difference in flexibility bears directly on your translation plan. With flexible genres you cannot know in advance what you will find; working out the scope means going through the pages one by one.

A hybrid structure also blurs the distribution of responsibility. Interface copy is written by the product team, legal text by the legal department, promotional copy by marketing. When translation is handed to a single supplier, an attempt is made to melt these three voices into one style, and all three usually suffer.

Embedded genres on a product page

The table below summarises the embedded genres on a typical product page and the translation approach that suits each of them. Five different approaches on the same page is an ordinary state of affairs.

Embedded genreCommunicative purposeSuitable approach
Product descriptionTo persuadeRewriting to purpose
Specification listTo informDirect rendering, bound to terminology
Delivery and returns informationTo remove uncertaintyAdaptation to local practice
Legal notice and contractTo state obligationsDirect rendering, with legal sign-off
Customer reviewTo convey experienceLeaving it raw, or machine translation

Projects that try to replace this table with a single instruction lose on both counts. Legal text translated in marketing language creates risk; a product description translated in legal language does not sell.

That is why splitting the translation package into sections, naming the genre in the file names and writing separate instructions for each section is basic practice. It costs an hour of preparation.

Product descriptions: the embedded genre that goes wrong most often

Product descriptions carry both a persuasive and an informative function. That duality is the feature most often lost in translation. The lively appeal of the source text turns into a technical list in the target language; the page informs but does not sell.

The second problem is repetition. Within one product family, hundreds of descriptions resemble one another. That resemblance lowers the cost of translation, but repeating the same pattern for every product makes the text monotonous. Comparing three products, the user cannot see the difference.

The third problem is measurements and units. When sizes, volumes, power ratings and warranty periods are not converted into their local equivalents, the description stays technically correct but is of no use to the user. That conversion is not a translation job but a data job.

The right arrangement is to split descriptions into two layers: technical data that does not change, and promotional copy that can. The first layer is fed from the database, the second is rewritten. Without this separation, you pay for a full translation of every product.

A privacy policy, terms of use and a distance sales contract are genres embedded in the main genre but governed by rules of their own. In these sections the language is bound to legislation and reflects the difference in power between producer and user.

Comparative studies show that the structure of terms and conditions pages, and the formulas used in them, differ markedly between languages and markets. A word-for-word translation, then, may not produce the document the target market expects.

The mistake we see most often in practice is a text written to the source market’s legislation being translated and published. The text is linguistically flawless but does not contain the information the local regulation expects.

The right order is this: first have the text drafted to local requirements, then have it translated. Translation is no substitute for legal compliance. This article is for general information and is not legal advice.

Customer reviews: the embedded genre you do not write

The reviews, ratings and questions produced by users are embedded genres too. What sets them apart is that the source text is not under your control. The volume cannot be foreseen, the level of language varies, and the content grows every day.

Human translation is therefore rarely workable for reviews. The common solutions are to leave them raw, to offer machine translation on request, or to translate only the reviews that readers have found most helpful.

Whichever option you choose, the decision has to be visible. Sites that do not state that a review has been machine translated end up owning poor translation as though it were their own copy.

The interface copy around the review section, on the other hand, is your responsibility: the filters, the rating labels, the report buttons. In most projects these short texts are forgotten and stay in the source language in the middle of the page.

Question and answer sections fall into the same group. The answers the seller gives are corporate copy and under your control; they are not the language of the user who asked the question. Treating the two as a single block leaves the corporate answers unchecked as well.

Genre repertoire and add-on genres

The set of genres that a community or an environment uses regularly is called a genre repertoire (Orlikowski and Yates 1994, p. 542). The repertoire of a software project contains the product itself, help content, the promotional site, social posts, legal documents and installation videos.

Some of these are add-on genres: they depend on another genre in order to exist. Without the product there is no promotional site for it and no promotional post about it.

The idea of a repertoire is the most practical tool there is for working out scope. In volunteer localisation work, participants have been documented translating not only the main content but also project descriptions, status updates and participation guidelines.

Draw up the same list for your own project. Most teams have the product translated but forget the email templates, the store descriptions and the social posts. Those belong to the same repertoire.

Notification copy holds a special place on this list. Notifications are very short, rarely more than a sentence, and they reach the user outside the product. A single notification left in the source language can, on its own, undo the impression made by a flawlessly translated interface.

Social posts, for their part, call for a separate decision about style. Using a formal tone in a product’s interface and a familiar one in its posts is not an inconsistency; it is a difference of genre. It only has to be a conscious distinction, set down in writing in the style guide.

Supergenre and subgenre: giving the right name in the brief

In genre sets, the general category is called the supergenre and the branches beneath it subgenres. The corporate website is a supergenre; the hotel website and the food industry website are its subgenres.

The distinction is useful when you write the brief. There is a serious difference between saying I want a corporate website translated and saying I want a hotel chain website translated. The second also covers expectations such as the booking flow and the cancellation terms.

Naming the subgenre lets the supplier study the right reference examples. When it is not named, the supplier applies the most generic template and does not notice the sections particular to your sector.

A single added sentence can noticeably reduce the number of revision rounds. On our services page we list what a brief should contain.

The Türkiye context

In Türkiye, the legal genres embedded in e-commerce pages are tightly bound to legislation. The preliminary information form and the distance sales contract are inseparable parts of the page. A product page arriving from abroad may not contain these genres at all.

Personal data texts are in the same position. A privacy notice is not a translation of the privacy policy used in the source market; it is a separate document drawn up to local regulation. Confusing the two is a common and costly mistake.

In customer reviews, the variety of abbreviation and spelling in Turkish puts machine translation under strain. If you are going to offer automatic translation for the review section, test the output on a sample; it does not give the same result in every language pair.

What does this mean for you?

Telling embedded genres apart raises translation quality and also lets you spread your budget correctly. Not every text needs the same care; what you need is to know which text deserves which care.

  1. Open one typical page of yours and mark the different genres in it one by one.
  2. Write down the approach for each genre: rewriting, direct rendering or leaving it raw.
  3. Plan the legal sections as a compliance job rather than a translation job, and position legal sign-off within the process.
  4. Make a decision about user-generated content and make that decision visible to the user.
  5. List your product repertoire: emails, store copy, social posts, notifications.

Once you have completed these five steps you will have a realistic scope. If you share that scope through our quotation form, we can propose a separate approach and a separate timescale for each genre.

Frequently asked questions

What does genre embedding mean?

Genre embedding is one genre sitting inside the structure of another. A corporate site may contain a recipe, a contract, a news item or a customer review. The containing genre is primary and the genre lodged within it is secondary.

What is a hybrid genre?

Genres that house instances of other genres within their structure are called hybrid or complex genres. Social networks are the typical example: a privacy policy, usage guidelines, interface copy and user-generated content sit together on the same platform.

Are all embedded genres translated in the same way?

No. Legal texts ask for a more direct rendering, marketing copy is open to rewriting, and customer reviews are usually left raw or offered with machine translation. Three different approaches can be applied on the same page.

What is a genre repertoire good for?

It lets you see all the genres around a product together: the product itself, the promotional site, help content, social posts and legal documents. Listing the repertoire brings to light the pieces that have been left outside the translation scope.

Sources

  • Jiménez-Crespo, M. A. (2024). Localization in Translation. Routledge, pp. 138–140.
  • Orlikowski, W. J. and Yates, J. (1994). Genre repertoire. Administrative Science Quarterly, 39(4), p. 542.
  • Bhatia, V. K. (2004). Worlds of Written Discourse. Continuum.
Share

Document ready? See your price in minutes

Get an Instant Quote
See your price in 2 minutes Get an Instant Quote
Chat on WhatsApp