Where to Direct Traffic: Homepage, Catalog, or Service Card

The page must match the campaign's objective

Traffic shouldn't just be sent to the website. The homepage introduces the service and its areas, the catalog helps choose a promotion format, and the service card explains the terms of a specific order. A mistake in choosing the landing page isn't always visible in the visit counter: there are clicks, but streamers don't open the right section, don't go to contacts, and don't leave a request.

For a streaming project, the difference is especially noticeable. A channel owner may be looking for viewers for an upcoming stream, chat activity, views on a broadcast recording, clicks to the community, or clip promotion. These are different tasks, and the visitor must land at the point where their request is already accounted for.

Match the link to the text in the source

The more specific the promise in the traffic source, the narrower the landing page should be. A general link in a profile, a partner review, or a mention of the service in a video can lead to the homepage. A post about channel promotion formats is better directed to the catalog. A link from a publication with the words "viewers for a live stream" should open the card of the corresponding service.

Don't send a visitor from a post about promoting a Twitch stream to a general section with services for music, short videos, and other social networks. They should immediately see that the page relates to their platform and task. Otherwise, part of the audience will leave before viewing the terms, and the campaign statistics will get mixed up with interest in other areas.

The homepage is suitable for getting acquainted with the service

The homepage is for an audience that hasn't yet chosen a promotion method. For example, a streamer saw a link in another channel's description, came from a general recommendation on social media, or clicked an address from a profile. They may know they want to grow their channel but haven't yet decided whether they need viewers for a stream, chat activity, VOD views, or support for related social networks.

The homepage should clearly show streaming-related areas: promotion of live streams, the channel, broadcast recordings, clips, chat, and the project's external accounts. If the needed category is hidden in a menu or lost among unrelated services, the page doesn't fulfill its role as an entry point.

What to check on a homepage for streamers

The homepage doesn't have to describe every service in detail. Its job is to quickly show where to go next. A visitor should be able to find the section for their platform within a few clicks, understand the difference between services for a stream and for a channel, and then open the appropriate card.

• A separate path to services for broadcasts, rather than a single block with all types of promotion.
• Clear names: stream viewers, chat activity, recording views, clip promotion.
• A link to the catalog or a thematic category next to the description of the area.
• Navigation to a contact method for those who need a non-standard campaign scenario.
• A brief indication of what data is usually required: a link to the channel, stream, recording, or profile.

The downside of the homepage is too much choice. Someone who has already come for promotion of a specific stream has to find the right format among other sections on their own. For a precise request, this is an extra step and less transparent analytics.

When not to send traffic to the homepage

The homepage is a poor fit for publications with a specific offer. If the announcement says the service helps attract traffic to a streamer's page or viewers to a broadcast, the visitor expects to see the terms of exactly that format. A general showcase with dozens of areas looks like a mismatch between the link and the message.

The homepage is also inconvenient for testing demand for a single service. A visitor may open the catalog, go to another section, or close the page. From such clicks, it's hard to tell whether they were interested in the specific format that was advertised in the post or integration.

The catalog is needed for comparing promotion formats

The catalog suits a streamer with a clear task but no ready-made solution. For example, a channel is preparing for a series of streams, and the owner is choosing between promoting viewers, chat activity, views on past broadcasts, and external clicks to the community. They already know the platform but want to compare the available options.

The catalog is better built not only by service names but also by the content workflow scenario. Within the streaming section, it's useful to separate services for live streams, recordings, the channel, and clips. Then the visitor doesn't confuse a one-time campaign before a broadcast with the task of developing a content archive.

What a streaming services catalog should contain

A catalog for attracting traffic shouldn't consist of identical cards with generic wording. It's important for a streamer to immediately see what type of content the service is intended for, whether it suits an already running stream or requires preparation in advance, and what data needs to be provided to launch.

• Separation into live streams, channel pages, broadcast recordings, clips, and external social networks.
• A short description of the result being tracked: page visits, views, clicks, audience activity.
• An indication of whether the format suits a one-time launch, regular content, or a series of streams.
• A link to the card with restrictions, requirements, and contact options.
• A filter by platform if the service works with multiple streaming and social platforms.

The downside of the catalog is that the visitor still has to choose. If the differences between items aren't explained, they may open several pages, fail to understand which service matches their plan, and postpone contacting. The catalog doesn't replace the card when the source has already named a specific format.

The catalog is useful for traffic from reviews and roundups

A review like "how to prepare a channel for a stream" usually mentions several tasks: design the profile, bring an audience to the stream, gather chat activity, promote recordings. Such material shouldn't lead to a single card, because some readers are looking for a different tool. A catalog or a thematic page with streaming services would be more appropriate.

The same principle works for a link in a community's pinned post where the author recommends the service in general. The user comes not with a ready-made order but with a desire to explore the options. In the catalog, they can go to the needed scenario without returning to the homepage.

The service card is needed for precise intent

The service card is suitable when the traffic source has already explained what exactly is being offered. For example, a link is placed in a video description after a phrase about promoting a stream recording. A post announcing a stream may contain a link to the page for attracting traffic or viewers for a broadcast. In this case, the catalog creates an extra choice, and the homepage diverts attention.

The card is especially useful for campaigns with a limited scenario: a launch before a specific stream, promotion of a new clip, attracting clicks to a channel page after a collaboration. The visitor sees the terms, understands what materials to prepare, and can go straight to contacting.

What to include in a stream service card

The card should answer the channel owner's practical questions. A generic text about promotion isn't enough: they need to understand what the service relates to, when to use it, what links to provide, and how to track the campaign's progress. Terms and restrictions are better placed next to the description rather than moved to a separate section of the site.

• What the service is intended for: a stream, channel, broadcast recording, clip, or social media page.
• What link is needed to launch: the channel address, a specific broadcast, VOD, or publication.
• Whether the format suits a scheduled stream, an already published recording, or a permanent channel page.
• What actions can be tracked after launch: clicks, page views, clicks on contacts, or inquiries.
• Platform restrictions and content availability requirements.
• A link to the catalog if the visitor needs not one format but a set of services for the channel.

Downsides of the card for a cold audience

The card is too narrow for someone who has just heard about the service and doesn't yet understand what formats exist. A streamer clicks a general recommendation and immediately lands on the service page for stream viewers. They may not learn that options for recordings, chat activity, or clip promotion are available.

The card shouldn't be chosen just because it has an order form. If the source talks about comprehensive channel development and the page is dedicated to a single action, the expectation won't match the content. For a cold audience, links to the catalog and clear navigation to related formats are useful, but this doesn't remove the main downside: the page remains narrow.

Example of page selection and UTM tagging

Suppose a streamer releases a video about preparing a channel for weekly streams. In the video itself, they talk about several tasks: attracting an audience to broadcasts, working with a recording archive, and growing external social networks. The link from the description can lead to the streaming services catalog, because the video's viewers are at the stage of choosing a format.

The address can be tagged like this: site.ru/streaming?utm_source=video&utm_medium=description&utm_campaign=weekly_streams. The tags don't affect the visitor but help separate this click from a link in a profile or an ad post. Tag names are chosen according to your own system; the main thing is to use it consistently across all campaigns.

How to separate links for a single campaign

The same streamer can place several links with different entry points. In the description of an overview video — the catalog. In a pinned comment under a video about promoting recordings — the service card for VOD. In the channel profile — the homepage. Then the statistics will show not only the number of visits but also which context better leads the user to the next action.

• Link from the profile: the homepage with a profile source tag.
• Link from an overview of several formats: the streaming services catalog.
• Link from a post about a single stream: the service card for that task.
• Link from a partner integration: the page discussed in the integration, not the general website address.

The downside of having many links is that they need to be managed carefully and tags shouldn't get mixed up. If the same source is tagged differently for no reason, comparing campaigns will become inaccurate.

Traffic source and the appropriate page

• A general recommendation of the service, a link in a profile, a partner review — the homepage.
• An article about ways to promote a stream, a roundup of tools, a video about channel growth — the catalog.
• A post about viewers for a stream, a publication about promoting a clip or recording — the card of a specific service.
• A campaign for a debut stream, a collaboration, or a separate launch — a dedicated landing page if the standard card isn't enough.

A dedicated landing page has a downside: after the campaign, it needs to be maintained, links updated, and outdated terms removed. Creating one for ongoing general traffic is usually unnecessary if the homepage, catalog, or card solves the task.

Check the user's path before launching traffic

Attracting traffic reveals landing page problems faster but doesn't fix them. Before launching, open the link on a smartphone and a computer, check loading, the form, links to the catalog, and contacts. For a streaming service, additionally make sure the user can provide a link to the channel, stream, or recording in the required format.

• The page headline matches the topic of the post, video, or ad.
• The platform and content type are visible before scrolling through a long text.
• Contacts, the form, and links to related services work correctly.
• The terms don't contradict the text in the traffic source.
• From the card, you can go to the catalog, and from the catalog, you can return to the needed category.
• The tagged link opens the same page as the regular address.

Evaluate actions after the click, not just visits

For the homepage, a useful action would be going to the streamers section or opening the catalog. For the catalog — viewing the card of the needed service, applying a filter, going to the terms or contacts. For the card — submitting the form, clicking a messenger, requesting details, or providing a channel link.

If there is traffic but users don't go beyond the first screen, the reason may be an unsuitable source, an unclear headline, slow loading, or the wrong page. Don't change everything at once. First check that the link and the ad match, then the navigation, and after that — the content of the card or catalog.

Test one hypothesis at a time

To compare the catalog and the card, use the same source and text that's similar in meaning. For example, two similar posts about promoting a stream recording can be directed to different pages with separate tagged links. Don't change the post wording, visuals, terms, and landing page at the same time: then you won't be able to tell what influenced the visitors' actions.

Artificial or uninterested visits aren't suitable for such a test. They may increase the counter but won't show how real streamers choose a service, read the terms, and proceed to contact. To evaluate a landing page, the actions of an audience that might actually need the promoted format are what matter.