4 measurements spanning 4 days, net +5. 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 3,190–3,198 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
12 Aug 2026, 00:54
3,197
+6
8 Aug 2026, 20:51
3,191
-1
7 Aug 2026, 23:00
3,192
no change
7 Aug 2026, 22:49
3,192
first reading
Engagement
19 posts held, back to 3 June 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
ERR · 30 days
40.3%
avg views ÷ 3,197 subscribers
Avg views / post
1,290
9 posts measured
Reaction rate
1.82%
reactions ÷ views · ER floor
Posts in window
9
of 19 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.
What these figures were computed from
Window
Rolling 30 days · latest post in window 6 August 2026
Posts held
19 (3 June 2026 – 6 August 2026)
Views total
11,600
Reactions total
211
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
7 Aug 2026, 23:00 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.
Reaction mix
561 reactions across 19 posts, in 2 distinct kinds. The most used accounts for 89.3% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
501
89.3%
👎
60
10.7%
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 19 of the 19 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 561reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 3 June 2026 to 6 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.
به یک نویسنده خانم برای نوشتن توضیحات محصولات آرایشی، بهداشتی و مراقبتی نیاز داریم.
استفاده از هوش مصنوعی، حتی برای نوشتن یک خط، باعث رد شدن محتوا خواهد شد.
لطفاً درخواست همکاری خود را با الگوی زیر ارسال کنید:
نام
نمونهکار، ترجیحاً در حوزه آرایشی، بهداشتی یا مراقبتی
هزینه پیشنهادی بهصورت کلمهای یا ماهانه
حجم محتوایی که میتوانید در روز بنویسید
پیام خارج از ساختار بالا بخاطر حجم درخواست ها با احترام بررسی نخواه…
ذهنتون رو درگیر سرچ والیوم نکنید چون اصلا نداره
اگر هم داشته باشه هم یوزر هاشون کیفیت سرمایه گذاری نداره
یه راهنمایی:
بیشتر در لایه ساختار، نالج و انتقال قدرت هست
یه نکته دیگه، کل این سایت با ai زده شده الان هم دارم روی ui ux ش کار میکنم چند ساعت دیگه احتمالا انلاین بشه:
قالب
اسکرپر
پلاگین
استراکچر
سیستم تبلیغات
سوالی که بهتره بهش فکر بشه:
توی این سایت بدون پست تایپ Business هم من میتونستم سایت رو بزنم
چه الزامی بود من یک پست تایپ بزنم که تارگتش ایران باشه؟
مثلا بهترین کافه های ایران
بهترین مکانیکی های ایران
بهترین کسب و کار + ایران
درصورتی که من بهترین کافه های تهران و.. رو داشتم؟
📌 اما بخش مهمتر، لینکسازی داخلیه.
در OPNEX لینکها نباید فقط بر اساس اشتراک کلمه ساخته بشن.
لینک باید از یک رابطه واقعی در دادهها به وجود بیاد.
مثلاً صفحه یک کافه در تهران میتونه به این ها متصل بشه:
👈 صفحه کافهها در کل کشور
👈 صفحه بهترین کافههای تهران
👈 صفحه رستورانها و کافههای تهران
👈 کافههای مشابه
👈 مکانهای مرتبط در همان شهر
این روابط الان در خود صفحات Place هم دیده میشه.
برای مثال، صفحه یک کافه به …
📌 در ادامه سری پست های سایت خوب سایتی هست که خودش خودشو سئو کنه:
احتمالاً این سوال پیش اومده:
🔶 این سیستم در عمل چه شکلیه؟
برای توضیحش میخوام سایت شخصی خودم رو بهعنوان کیس استادی باز کنم:
opnex.ir
قبل از اینکه وارد URL و لینک سازی داخلی بشیم، باید بفهمیم این سایت اصلاً چه دنیایی رو مدل میکنه.
فرض کنید کاربر جست و جو میکنه:
👈 بهترین کافه های کرج
👈 گل فروشی های مشهد
👈 تعمیرگاه خودرو در تهران
👈 آدرس و ش…
در رابطه با تغییر ریکورد از ایمپرشن و کلیک به نالج گرفت:
اصلا نباید اینکار رو کنید به خصوص در این عصر هوش مصنوعی که AI Overview میاد از رقیب های همین دیتا رو کامل تر از تو برمیداره و جستجوی عبارت های informational رفته سمت هوش مصنوعی.
گذشت زمانی که باید کامل راجع به یک چیزی حرف بزنی تا رتبه بگیری. واقعیت از اول هم اینطوری نبود اصلا!
یعنی برای اینکه تو "بروکر فارکس" بیای بالا لازم نیست عین همون الفبای قبلی رو درب…
در رابطه با پست آخر که با این مضمون بود که به نظر من کیورد ریسرچ سنتی منسوخ شده است برخی دوستان سوال داشتند برخی ها هم نقد کردن که قبل از پاسخ دادن این مورد رو در نظر داشته باشید که من عرض کردم "به نظر من" و شما هم میتوانید نظر خودتان را به نسبت تجربیاتی که دارین داشته باشید.
و اما بعد چالش اول:
Maryam.Bsr:
ب نظرم منافاتی هم نداره معمولا
همون روش وقتی درست پیاده بشه این اهداف هم محقق میشن
Abolfazl Fani:
دقیقا وقتی…
به نظر من کیورد ریسرچ به شکل سنتی خیلی وقته منسوخ شده.
اگر هنوز فرآیند سئو رو با پیدا کردن کیورد و ساختن لیست کلمات شروع میکنید، بهتره رویکرد رو تغییر بدید و وارد مسیرهای جدید بشید:
به جای کیورد ریسرچ 👈 EAV Research
به جای پیدا کردن کلمه 👈 Entity Research
به جای تمرکز روی سرچولوم 👈 Topic Research
به جای پیلار کلاستر 👈 Topical Map
به جای تولید محتوا برای کلیک و ایمپرشن 👈 تکمیل Knowledge Graph سایت
امروز بای…
بازتاب درست وضعیت سئو در سال گذشته با مشارکت شما 📊
وجود گزارش در هر حوزهای میتواند به تصمیمگیری بهتر و دقیقتر کمک کند. همچنین دید خوبی از وضعیت فعلی بازار به فعالان آن حوزه میدهد.
تریبون قصد دارد گزارشی از وضعیت بازار سئو در سال ۱۴۰۴ منتشر کند تا با کمک دادهها سال گذشته را بهتر ارزیابی کنید و برای آینده برنامهریزی کنید.
✅ اگر در حوزه سئو فعالیت میکنید، با پر کردن این پرسشنامه و ارسال آن برای همکاران خود در…
1️⃣نیاز رو پیدا کنید بعد بسازید:
کار تکراری کردن لازم نیست - اول بگردید شاید قبل شما کسی زده بود - خیلی دنبال کاری که برای همه جواب بده نباشید - اول اختصاصی های نیازت رو بساز
2️⃣ فول اتوماسیون بودن از نظر من یعنی اسپم
هر فرایندی ساختید مراحلی از اون رو طوری بسازید که انسان نظارت داشته باشه. مثلا در همین نمونه که فرستادم من به عنوان اپراتور میدونم چه خبر هایی از امارات به درد ایرانی ها میخوره همشون نیاز نیست باشند پس…
👍24
Showing the 12 most recent of 19 posts we hold for @seo_yek. 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.
Citation-graph rank
Citation-graph rank — 1,317,106 of 1,480,688entries 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.
Mentions
Named by 1 registered channel — 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
دانشگاه بازاریابی @iranmarketinguniversity · 106,312 Telegram ranks this channel #60 of 90 here — alongside 89 others — read 15 August 2026
This channel appears in 1 seed channel's Telegram-generated recommendation list 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_yek), 3,197 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/seo_yek.
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.