Telegram RegisterThe public register of Telegram

Channel

SEO HR, digital-вакансии, офис и удалёнка

@seohr

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Polls · Citations · Telegram's recommendations · Cite this entry

24,765subscribers

+150 since we began measuring on 5 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001017371671
TypeChannel
Username@seohr
DescriptionРазместить вакансию: t.me/seohr/911 Благодарить: t.me/seohr/999 Норм зп: @over100 Резюме: @digitalcv Разработчикам: @devshr Разовая работа: @digitaltender Поболтать: @hr_chat Опросы: t.me/seohr/3742 Навигация: t.me/seohr/3134 РКН: seoch.at/uhGygv/
Created21 March 2016measured — cross-checked against a third-party dataset (TGDataset)
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/seohr

Topic

Job listings — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 100% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@over100/333029 Jul 2026, 09:30 UTC@seohr/11929 · this entry29 Jul 2026, 11:00 UTC0.981.5 hours
@over100/33566 Aug 2026, 12:46 UTC@seohr/11955 · this entry6 Aug 2026, 14:00 UTC0.9874 minutes
@over100/332327 Jul 2026, 13:02 UTC@seohr/11914 · this entry27 Jul 2026, 14:00 UTC0.9858 minutes
@over100/33483 Aug 2026, 13:30 UTC@seohr/11942 · this entry3 Aug 2026, 15:00 UTC0.971.5 hours
@over100/332123 Jul 2026, 13:42 UTC@seohr/11902 · this entry23 Jul 2026, 15:00 UTC0.9777 minutes
@over100/334331 Jul 2026, 11:29 UTC@seohr/11937 · this entry31 Jul 2026, 13:00 UTC0.971.5 hours
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@over1007 (7/7 hand-verifiable sample passed)0.971.5 hours@over100 (70)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 1 of the 7 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 19 comparable posts for this entry, running 23 July 2026 to 6 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @over100. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

24,61524,76524,6905 August 2026 — 24,615 subscribers6 August 2026 — 24,615 subscribers6 August 2026 — 24,617 subscribers7 August 2026 — 24,623 subscribers8 August 2026 — 24,647 subscribers8 August 2026 — 24,646 subscribers9 August 2026 — 24,701 subscribers11 August 2026 — 24,725 subscribers12 August 2026 — 24,752 subscribers12 August 2026 — 24,765 subscribers5 August 202612 August 2026
10 measurements spanning 7 days, net +150. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 24,593–24,788 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 23:4724,765+13
12 Aug 2026, 02:5424,752+27
11 Aug 2026, 02:3124,725+24
9 Aug 2026, 23:3324,701+55
8 Aug 2026, 22:2824,646-1
8 Aug 2026, 01:3724,647+24
7 Aug 2026, 05:0124,623+6
6 Aug 2026, 02:5024,617+2
6 Aug 2026, 02:0324,615no change
5 Aug 2026, 22:0624,615first reading

Engagement

24 posts held, back to 23 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 21 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
6.63%
avg views ÷ 24,765 subscribers
Avg views / post
1,640
23 posts measured
Reaction rate
0.785%
reactions ÷ views · ER floor
Posts in window
24
of 24 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 21 of 23 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 12 August 2026
Posts held24 (23 July 202612 August 2026)
Views total37,756
Reactions total276
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 11:54 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
164
Videos
6
Links
3,460

Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Reaction mix

276 reactions across 21 posts, in 10 distinct kinds. The most used accounts for 44.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💩12244.2%
👎3312.0%
👍279.78%
🤡269.42%
🤔217.61%
❤‍🔥207.25%
😁134.71%
🔥124.35%
🌚10.362%
🤬10.362%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 21 of the 24 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 276reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 24 most recent posts we hold, published 23 July 2026 to 12 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Telegram Stars

Stars received
91
across the posts below
Posts paid on
3
of 23 we hold a reading for · 13%
Most on one post
68
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @seohr. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 24 most recent posts we hold for this entry, published 23 July 2026 to 12 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

12 Aug 2026, 11:00 UTC774 views29 reactionsread 13 August 2026

👤GEO / AIO-специалист (LLM SEO), удалённо, частичная занятость/подряд, B2B SaaS в сфере самозанятых, любой город О компании: 🔸B2B SaaS-платформа для работы с самозанятыми и внештатным персоналом. 🔸Основной канал привлечения — SEO, сейчас усиливаем присутствие в ответах ИИ-ассистентов и AI Overviews. Обязанности: 🔸Мониторить цитируемость бренда и продуктовых страниц в Google AI Overviews, Яндекс Нейро, ChatGPT, Perp

💩25❤‍🔥1👍1🤔1🤡1

12 Aug 2026, 09:00 UTC780 views10 reactionsread 13 August 2026

👤SEO-специалист (Middle), удалённо, digital-агентство AdsON О компании: 🔸Агентство комплексного интернет-маркетинга AdsON, на рынке с 2015 года. 🔸Работаем с бизнесами в России и за рубежом. 🔸Запускаем проекты с нуля и прокачиваем текущие: B2B, B2C, услуги, немного e-commerce. 🔸Кроме SEO ведём контекст, контент, продвижение на картах и сквозную аналитику. 🔸Мы растём и сейчас ищем самостоятельного SEO-специалиста в ко

💩7❤‍🔥1👍1🔥1

10 Aug 2026, 07:00 UTC≈1,450 views35 reactionsread 13 August 2026

👤SEO/GEO-специалист, удалённо, на part-time фриланс, Appbooster О компании: 🔸Appbooster — adtech-компания с собственной технологической экосистемой. 🔸С 2013 года на рынке мобильного маркетинга, помогаем приложениям расти в AppStore, Google Play и других сторах. 🔸Среди клиентов: SkyEng, Додо, Lamoda, Литрес, Купибилет и другие федеральные бренды. Интро: 🔸Основной задачей будет продвижение нашего сайта и платформы на

💩26🤡4👍2❤‍🔥1🔥1🤔1

6 Aug 2026, 14:00 UTC≈1,980 views9 reactionsread 13 August 2026

👤Перформанс-специалист (Middle/Senior), удалённо, Яндекс Go, инхаус О компании: 🔸Яндекс Go — крупнейший в РФ сервис заказа такси, который включает в себя также Доставку, Самокаты, и другие сервисы Яндекса. 🔸Наша команда занимается привлечением пользователей, водителей и клиентов в сервисы. 🔸Ищем перформанс-маркетолога на B2B проекты. Пишите, если видите в перформанс-маркетинге не просто запуск кампаний, а сильный ры

💩6❤‍🔥1👍1🤔1

5 Aug 2026, 09:00 UTC≈2,000 views4 reactionsread 13 August 2026

👤Middle/Senior SEO-специалист (iGaming), удалённо О компании: 🔸Мы — affiliate-компания, которая уже почти 5 лет строит и масштабирует digital-проекты. 🔸Ищем специалиста, который не просто «двигает ключи», а умеет находить нестандартные пути в iGaming выдаче. Задачи: 🔸Анализ SERP и поиск уязвимых мест конкурентов. 🔸Тестирование гипотез и внедрение нестандартных подходов. 🔸Построение и оптимизация эффективных линкбил

❤‍🔥1👍1💩1🤔1

4 Aug 2026, 11:36 UTC≈2,050 views42 reactionsread 13 August 2026

👤SEO junior, удалённо О компании: 🔸Привет! Мы — динамичная SEO-компания, специализирующаяся на создании и продвижении сайтов в поисковых системах. 🔸В связи с активном расширением компании ищем SEO Junior с небольшим опытом работы под Google. 🔸Штат 100+ человек. 🔸Наш фокус - iGaming-ниша. Чем предстоит заниматься: 🔸Базовый технический аудит. 🔸Проверка контента по регламенту. 🔸Сбор СЯ + кластеризация. 🔸Формирование Т

👎28🤔6🤡4👍2❤‍🔥1🤬1

3 Aug 2026, 15:00 UTC≈1,850 views4 reactionsread 13 August 2026

👤Специалист-архитектор по технической поддержке (Customer Support Lead), гибрид, Москва, Москва-Сити, AstraTech О компании: 🔸Мы стартап и строим ИИ-продукты в medtech: B2B-платформу для мониторинга здоровья сотрудников в тяжёлых промышленный индустриях. 🔸Ищем специалиста, который доработает Customer Support Department: инфраструктуру, процессы и AI-автоматизацию для круглосуточной поддержки продуктов. Обязанности:

❤‍🔥1👍1👎1🤔1

3 Aug 2026, 12:46 UTC≈1,760 views4 reactionsread 13 August 2026

👤Media Buyer, удалённо, Aso Market Интро: 🔸Мы ищем опытного баер-специалиста, таргет-специалист с глубокими знаниями в Google Ads и Facebook, а также практическим опытом работы с Google Ads API и навыками быстрой разработки (вайбкодинг / ИИ-ассистированная разработка) для автоматизации рекламы на мобильные приложения. Чем предстоит заниматься: 🔸Автоматизация создания, настройки и запуска рекламных кампаний через Go

❤‍🔥1👍1👎1🤔1

31 Jul 2026, 15:00 UTC≈1,930 views3 reactionsread 13 August 2026

👤Менеджер digital-проектов / Project Manager, гибрид, Москва О компании: 🔸RTA — агентство digital-маркетинга, №1 в полном цикле digital-услуг по версии AdIndex, приглашает в команду Project Manager. Что предстоит делать: 🔸Вести digital-проекты и сопровождать клиентов внутри агентства; 🔸Координировать команды performance, media, mobile, influence, production и подрядчиков; 🔸Контролировать сроки, бюджеты, KPI и финан

❤‍🔥1👍1🤔1

31 Jul 2026, 13:00 UTC≈1,830 views7 reactionsread 13 August 2026

👤Head of SEO, удалённо Интро: 🔸Ищем Head of SEO / SEO-партнера с сильным практическим опытом в конкурентных нишах - человека, который умеет не просто управлять процессами, а строить систему роста органического трафика и дохода. Что нужно делать: 🔸Формировать и реализовывать SEO-стратегию под высококонкурентные ниши 🔸Управлять несколькими командами/департаментами 🔸Масштабировать проекты и запускать новые сайты/напра

❤‍🔥2👍1👎1💩1🔥1🤔1

31 Jul 2026, 11:11 UTC≈1,630 views3 reactionsread 13 August 2026

👤SMM-Менеджер, гибрид, Москва, НАЭКК и премия «Лучшая корпоративная книга» Что делать: 🔸Разрабатывать и реализовывать SMM-стратегию под цели бизнеса. 🔸Анализировать продукт, ЦА и конкурентов, выбирать приоритетные площадки (VK, Telegram, MAХ и др.). 🔸Составлять и вести контент-план. 🔸Производить контент, в том числе тексты, визуалы, видео. 🔸Готовить аналитику и отчёты: охваты, ER, конверсии, стоимость заявки/подписч

❤‍🔥1👍1🤔1

Showing the 12 most recent of 24 posts we hold for @seohr. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

29 Jul 2026, 18:06 UTCAnonymous Poll15 voters

Как сегодня у вас работал бот?

  1. ✅ Как обычно, не заметил разницы с предыдущими днями40%
  2. 🤔 Работал стабильно, но отвечал долго27%
  3. 🤬ООООООчень долго отвечал. Долго ждал контакта по вакансии7%
  4. ❌ не работал совсем, т.е не прислал ни одного контакта за день, хотя запросы были у меня27%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 24 most recent posts we hold, published 23 July 2026 to 12 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Citation-graph rank

Citation-graph rank — 213,163 of 1,176,251entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 10 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Finder.work: работа и вакансии
@theyseeku · 275,090
Telegram ranks this channel #19 of 96 here — alongside 95 others — read 10 August 2026
Удаленная работа - Вакансии
@onlinevakansii · 127,230
Telegram ranks this channel #48 of 91 here — alongside 90 others — read 13 August 2026

This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 12 August 2026 — this entry's latest reading, not the date you are reading this.

“SEO HR, digital-вакансии, офис и удалёнка” (@seohr), 24,765 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/seohr.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.