Website as an asset: an array of narrow pages against one landing page

A landing page does one job well: it launches a campaign for a specific offer and tests demand. An array of narrow pages does a different job: it covers the whole shape of demand, in all its variety, at a lower cost per inquiry. The difference between the two is not size. It is what you are building. A landing page is a shop window for one question. A site made of many relevant pages is an asset that, over time, brings people in without a monthly budget.

The landing page itself is not the problem. The problem is that it so often stays the permanent model for years. For a foreign company selling into Russia this is almost the default: the Russian page was built to test the market, the test went well enough, and nobody went back to build the site the test justified. While everything rests on one page and paid traffic, the business misses organic demand across a wide set of queries and stays exposed to any shock in the channel. Below is how to assemble an asset out of a set of pages rather than a pile, and in what order.

A window for one question or a map of all demand

When each meaningful segment of demand has its own page answering exactly that query, a visitor lands on their answer, the share of target actions rises, and the cost per inquiry falls. A single generic landing page has to average its message and loses on both measures at once. That is the basic argument for the array: relevance to the query is one of the strongest levers of conversion, and the array delivers it where a landing page physically cannot.

Yandex sharpens this argument. Its ranking of commercial queries leans hard on how well a page matches a query and on how visitors behave once they arrive. A translated site that keeps the English structure, with one broad services page and a contact form, gives Yandex nothing to match against the narrower Russian queries people type. Google will sometimes rank a strong domain for a query it has no dedicated page for. In Yandex that is a weaker bet, and for a foreign domain with no Russian link history a very weak one.

The array has a trap of its own, though. The number of pages is not the goal. A hundred empty pages built around rearranged words will not lift conversion and will only dilute the weight of the site. In Yandex the penalty is explicit: Webmaster excludes pages it rates as low-value from the index, and a page per keyword permutation will keep appearing and disappearing from search month after month. An asset is not a count. It is the coverage of real facets of demand with pages good enough to hold. So the question is never “how many pages” but “which ones, and in what order”.

The order in which to build pages

The sequence of landing pages is not chosen by intuition. It is derived from the structure of the keyword set. You take the cleaned semantics, tag words by meaning, roll the tags up into groups, and compute cross-cutting figures for each cluster: total search frequency, the number of unique queries, and once statistics accumulate, clicks, spend and conversions.

Clusters are sorted by contribution to the result, and in that order the developer receives a prioritised brief rather than a flat “make pages” list: which pages to create first, why those, how to order the sections, the menu items, the filters and the tag cloud.

One practical device matters more in Russia than at home. For launch you do not take the whole keyword set, only the top by contribution. It is common to find that a small share of clusters, once synonyms are collapsed into a single spelling, accounts for the bulk of traffic and conversions. That share goes into the priority brief. Collapsing synonyms is where Russian differs from English in a way translation hides: the same product is searched with case endings, with the brand name in Cyrillic and in Latin, and with local trade terms that no dictionary maps to your catalogue name. Merging those into one cluster shrinks the list and makes the page workload manageable. Skipping this step is how a foreign company ends up with four thin pages for what is, to a Russian buyer, one query.

What to put into advertising at all

Before building pages it helps to know what you will sell on them. What goes into advertising is not a gut decision. It is the result of taking the product matrix apart. First, a map of what can be shown at all: the width of the range, its depth, seasonality, the capacity to ship the required volume, adjacent and cross-category segments, and the entry points into the matrix.

For a company selling into Russia from abroad, that map has extra columns: which items can actually be delivered here, at what lead time, through which payment routes, and whether certification for the category is in place. A page that ranks well for a product you cannot ship to a Russian address manufactures refusals.

Then comes a filter by money. Priority goes to the locomotive items: high average order value, often bought together with other items, the largest total revenue and profit, repeat purchases by the same customer. To get there you ask the owner for monthly and weekly figures: sales count and share, revenue, profit, average order value across the business and against the locomotive. Only on top of that do you layer usage scenarios and the buyer’s stage of awareness: the pain has just appeared, they have learned something, they have been choosing for a while, they are looking for where to buy. The work runs in descending order of reach and contribution to business figures, not of personal fondness for a product.

Content and promotion are one chain

Separating “the person who makes content” from “the person who promotes it for money” is excessive for a commercial site. The material is created precisely to become promotion and go into advertising. Splitting the roles breaks one chain and adds losses at the seam.

The working order ends up continuous. From competitors’ sites you collect semantics and meta tags as a list of topics and future pages. You split the semantics into unigrams and bigrams and plan content in descending order of each cluster’s reach. For each cluster of meaning you make everything at once: topic pages on the site, sets of posts leading to those pages, video in every size for every platform, and paid search and SEO pointing at the same pages. You ask the sales team what the inbound flow asks about and in what order, what tips a decision and what causes a refusal. You ask the owner what brings the most revenue and profit and where sales are slipping. The slipping segments get the emphasis, and all of it rolls up into a content strategy on at least a six-month horizon.

The Russian version of this chain has its own platforms, which is why a home-market content team rarely gets it right from a distance. Posts go to VK and Telegram rather than Meta’s networks, video is cut for VK Video and RuTube alongside YouTube, and paid search means Yandex Direct rather than Google. Even a heavy industrial topic is no obstacle: specifications and catalogues already exist, gaps are filled by specialist staff, and a production nomenclature changes slowly, so the base is stable. What has to be local is the language layer and the platform list, not the product knowledge.

An asset is also a reputation

There is a limit beyond which an array of pages is powerless. Ads and pages govern how many people see the offer and reach the point of decision. The decision itself is taken with external trust signals that you do not control directly: the public rating on maps and aggregators, reviews, scores. A sharp tilt toward negative cancels the intent that the page and the ad have just formed.

The model holds even for the most loyal customer. A person with years of purchase history, ready to come back out of habit, abandons the visit on seeing a mass of low ratings and goes to a competitor. The particular trouble is that the owner often has no idea of the scale, because nobody monitors the platforms.

For foreign companies in Russia the blind spot is wider. The platforms Russian buyers consult before they call are not the ones your home team watches: Yandex Maps and 2GIS for anything with a physical presence, review aggregators, and marketplace listings that a reseller may have created and that carry reviews of the reseller’s service under your brand name. A listing can exist, created by somebody else, with a rating you have never seen. So before increasing the budget and building new pages, check that the advertising leads people into a business whose external signals do not repel an audience that is already warm. An asset is more than pages. It is also what others say about you.

What to do with a site that is an asset

A short route:

• Decide what you sell. Take the product matrix apart and bring the locomotives forward by order value, revenue and profit, not the favourites. For Russia, add deliverability and payment to the same table.
• Build the order from the semantics. Rank clusters by frequency, traffic and conversions from a Wordstat-based set, not a translated one, and hand the developer a prioritised brief rather than a flat list.
• Start from the top. Take the share of clusters that produces most of the result and build those pages first.
• Stitch content to promotion. Plan pages, posts, video, SEO and paid search around the same clusters and the Russian platform set, not separately.
• Check the reputation. Look at the maps and aggregators through a customer’s eyes before pushing traffic at the pages.

A landing page helps you test a hypothesis quickly. Building nothing but landing pages for years means running all the time and never accumulating anything. An array of relevant pages, assembled from data on demand and on money, turns the site from a line of expense into an asset that keeps working when the ads are switched off.

I can show which pages would bring you the most inquiries and in what order to build them in a free review. How to connect that array to traffic as one system, site and campaign built together, is on the page about a website with Yandex Ads included.

Frequently asked questions

Sources

• Yandex Wordstat, query statistics used to build and cluster a Russian keyword set: wordstat.yandex.ru
• Yandex Webmaster help, indexing and page quality diagnostics: yandex.com/support/webmaster
• Russian version of this article on belokrylovo.ru: Сайт как актив: массив узких страниц против лендинга