Forwarded from AffPapa! Клуб спящих бизнесменов! Потрачено!
Скорей всего поеду на BROCONF 7.5 и вот почему!
Во первых надо по кое каким делам в МСК, но подстроил планы так что бы и на конфу заскочить ибо, кто не понял, это скорей всего последняя #BROCONF в РФ, во вторых она один день, не будет этой хуйни когда приходишь на второй день конфы а ты уже все блять видел, со всеми пообщался и просто ходишь уже хуй знает зачем ( однодневные конфы были велеколепны, но новички ихз не застали, раньше все конфы были 1 день )
Ну и самое важно, в связи с ситуацией со спонсорами и прочим и тем что это последняя Бро Конф в РФ оргни вьебывают прям люто бабки, по сути сейчас спонсорские пакеты как и на первой бро конф - отдаются по себесу, как и на первой орги просто вьебывают бабки что бы всех все устрпоило и было красиво, что бы 8 конфу уже помпезно анонсировать где то забугром!
Короче это точно не стоит пропускать, уверен она отработает в минус для оргнов, но нам то не похуй? для нас они сделают все на максимум просто что бы завершить эпопею с конфами в РФ на красивой ноте, и я это не пропущу! )))
Такие мысли вот!
Если что, билеты тут - https://mybroconf.ru промика не будет, найдёте сами, хотя и без него цены приятные! Промик можете спросить в чате Бро Конф @broconfchat
Во первых надо по кое каким делам в МСК, но подстроил планы так что бы и на конфу заскочить ибо, кто не понял, это скорей всего последняя #BROCONF в РФ, во вторых она один день, не будет этой хуйни когда приходишь на второй день конфы а ты уже все блять видел, со всеми пообщался и просто ходишь уже хуй знает зачем ( однодневные конфы были велеколепны, но новички ихз не застали, раньше все конфы были 1 день )
Ну и самое важно, в связи с ситуацией со спонсорами и прочим и тем что это последняя Бро Конф в РФ оргни вьебывают прям люто бабки, по сути сейчас спонсорские пакеты как и на первой бро конф - отдаются по себесу, как и на первой орги просто вьебывают бабки что бы всех все устрпоило и было красиво, что бы 8 конфу уже помпезно анонсировать где то забугром!
Короче это точно не стоит пропускать, уверен она отработает в минус для оргнов, но нам то не похуй? для нас они сделают все на максимум просто что бы завершить эпопею с конфами в РФ на красивой ноте, и я это не пропущу! )))
Такие мысли вот!
Если что, билеты тут - https://mybroconf.ru промика не будет, найдёте сами, хотя и без него цены приятные! Промик можете спросить в чате Бро Конф @broconfchat
Phoenix.ink — твои Google и Apple Developer аккаунты🟧 Смотри наличие @phoenixapps_store🟧 Забирай консоли @phoenix_seller_bot
Please open Telegram to view this post
VIEW IN TELEGRAM
Forwarded from AFF.TOP - про арбитраж трафика и CPA рынок!
This media is not supported in your browser
VIEW IN TELEGRAM
Meta ограничивает расходы на токены для сотрудников
Meta ввела внутренние лимиты на использование ИИ из-за резкого роста расходов: в 2026 году только на сотрудников заложены миллиарды долларов, а общий бюджет на ИИ-инфраструктуру оценивается в 130–145 млрд. Вывод простой: даже у Big Tech ИИ перестал быть бесплатной игрушкой и требует жёсткого контроля затрат.
➡️ Читайте на сайте: https://aff.top/blog/meta-ogranichivaet-raskhody-na-tokeny-dlia-sotrudnikov
🧠 Ещё больше инсайтов → в канале AFF.top
Meta ввела внутренние лимиты на использование ИИ из-за резкого роста расходов: в 2026 году только на сотрудников заложены миллиарды долларов, а общий бюджет на ИИ-инфраструктуру оценивается в 130–145 млрд. Вывод простой: даже у Big Tech ИИ перестал быть бесплатной игрушкой и требует жёсткого контроля затрат.
➡️ Читайте на сайте: https://aff.top/blog/meta-ogranichivaet-raskhody-na-tokeny-dlia-sotrudnikov
🧠 Ещё больше инсайтов → в канале AFF.top
Forwarded from AFF.TOP - про арбитраж трафика и CPA рынок!
This media is not supported in your browser
VIEW IN TELEGRAM
Claude Cowork, Claude Design объединили в один Claude
➡️ Читайте на сайте: https://aff.top/blog/claude-cowork-claude-design-obedinili-v-odin-claude
🧠 Ещё больше инсайтов → в канале AFF.top
➡️ Читайте на сайте: https://aff.top/blog/claude-cowork-claude-design-obedinili-v-odin-claude
🧠 Ещё больше инсайтов → в канале AFF.top
Q: How do I actually build a redirect map without missing pages?
Good question — guessing here is what tanks traffic. Here's a repeatable process.
Short answer: don't redirect from your sitemap, redirect from reality.
Long answer, in order:
— Pull old URLs from three sources, not one: your XML sitemap, a full Screaming Frog crawl, and your server access logs (last 90 days). Logs catch URLs nothing links to anymore but Google still hits.
— Add GSC's 'Pages' export and your top 500 by backlinks (from any link tool).
— Dedupe into one spreadsheet. Column A = old URL, column B = best new URL, column C = match confidence.
— Map one-to-one by content, never default everything to the homepage.
— Flag anything low-confidence for manual review.
Next step: get that combined list to ~95% coverage before you write a single redirect rule.
Good question — guessing here is what tanks traffic. Here's a repeatable process.
Short answer: don't redirect from your sitemap, redirect from reality.
Long answer, in order:
— Pull old URLs from three sources, not one: your XML sitemap, a full Screaming Frog crawl, and your server access logs (last 90 days). Logs catch URLs nothing links to anymore but Google still hits.
— Add GSC's 'Pages' export and your top 500 by backlinks (from any link tool).
— Dedupe into one spreadsheet. Column A = old URL, column B = best new URL, column C = match confidence.
— Map one-to-one by content, never default everything to the homepage.
— Flag anything low-confidence for manual review.
Next step: get that combined list to ~95% coverage before you write a single redirect rule.
Q: We moved domains 3 weeks ago and traffic is still down 20% — is that normal?
This worries a lot of people, so let's settle it.
Short answer: yes, completely normal at week 3 with clean redirects.
Long answer: across migrations I've tracked, even flawless domain moves dip 10-25% for the first few weeks while Google recrawls, swaps URLs, and re-evaluates. One textbook move (perfect 1:1 301s, Change of Address submitted) bottomed at -23% in week 2, was still -15% at week 4, crossed back to baseline at week 7, and finished +4% by week 10. Recovery is rarely linear — expect a slow grind, not a switch flip.
The danger is panicking and changing things mid-recovery, which resets the clock.
Next step: confirm your redirects are 301 and 1:1, then hold steady for 6-8 weeks before judging. Track recovery weekly, not daily.
This worries a lot of people, so let's settle it.
Short answer: yes, completely normal at week 3 with clean redirects.
Long answer: across migrations I've tracked, even flawless domain moves dip 10-25% for the first few weeks while Google recrawls, swaps URLs, and re-evaluates. One textbook move (perfect 1:1 301s, Change of Address submitted) bottomed at -23% in week 2, was still -15% at week 4, crossed back to baseline at week 7, and finished +4% by week 10. Recovery is rarely linear — expect a slow grind, not a switch flip.
The danger is panicking and changing things mid-recovery, which resets the clock.
Next step: confirm your redirects are 301 and 1:1, then hold steady for 6-8 weeks before judging. Track recovery weekly, not daily.
Forwarded from AffPapa! Клуб спящих бизнесменов! Потрачено!
This media is not supported in your browser
VIEW IN TELEGRAM
🔥 Приватные консультации по запускам Google ads и FB.
Масштабное обновление материала на сентябрь,без воды и паблика,свежий пак информации для опытных баеров(техничка,разбан,модерация,
связки,масштабирование и т.д)
Полный пак:
https://t.me/googleadsroi/164558
Отзывы:
https://t.me/+jnxGdX6GbjgxZTQx
Аккаунты гугл адс:
https://t.me/+VCIrjC36UiYyYjM0
Мой контакт:@TRAFF3
гарант+По промокоду( #affpapa ) скидка -10% на все услуги.
Please open Telegram to view this post
VIEW IN TELEGRAM
Forwarded from AFF.TOP - про арбитраж трафика и CPA рынок!
This media is not supported in your browser
VIEW IN TELEGRAM
Microsoft планирует вставлять рекламу в игры
➡️ Читайте на сайте: https://aff.top/blog/microsoft-planiruet-vstavliat-reklamu-v-igry
🧠 Ещё больше инсайтов → в канале AFF.top
➡️ Читайте на сайте: https://aff.top/blog/microsoft-planiruet-vstavliat-reklamu-v-igry
🧠 Ещё больше инсайтов → в канале AFF.top
Forwarded from AffPapa! Клуб спящих бизнесменов! Потрачено!
This media is not supported in your browser
VIEW IN TELEGRAM
Совсем скоро запуск ШЕСТОГО проекта на RU GEO от создателей APEX, EVA, KUSH, BANDA и LEEBET!
Please open Telegram to view this post
VIEW IN TELEGRAM
Q: We're finally moving HTTP to HTTPS — what's the full checklist so I don't break anything?
This trips people up because it feels small but touches everything. Take it in order.
Short answer: it's a site move in Google's eyes — treat it like one.
Long answer:
— Install the certificate, confirm it covers www and non-www (and any subdomains).
— Update all internal links, canonicals, and hreflang to https. Don't rely on redirects to fix internal links.
— 301 every http URL to its https twin, one-to-one.
— Fix mixed content: images, scripts, fonts still loading over http will throw warnings.
— Update your sitemap to https and resubmit.
— Add the https property in Search Console (it's a separate property).
— Update canonical tags, Open Graph URLs, and any hardcoded links in templates.
Next step: crawl the https site and confirm zero http URLs return 200 directly.
This trips people up because it feels small but touches everything. Take it in order.
Short answer: it's a site move in Google's eyes — treat it like one.
Long answer:
— Install the certificate, confirm it covers www and non-www (and any subdomains).
— Update all internal links, canonicals, and hreflang to https. Don't rely on redirects to fix internal links.
— 301 every http URL to its https twin, one-to-one.
— Fix mixed content: images, scripts, fonts still loading over http will throw warnings.
— Update your sitemap to https and resubmit.
— Add the https property in Search Console (it's a separate property).
— Update canonical tags, Open Graph URLs, and any hardcoded links in templates.
Next step: crawl the https site and confirm zero http URLs return 200 directly.
Q: We migrated months ago but our internal links still point at the old redirected URLs. Worth fixing?
A: Yes, and it's a satisfying cleanup. Short answer: internal links pointing to redirected URLs force an extra hop on every crawl and click, quietly wasting crawl budget you'd rather spend on real pages.
Long answer: Redirects are a safety net for external links you can't control. But your own menus, body links, and breadcrumbs you can control — and leaving them pointing at old URLs means Google crawls A→301→B every single time. It works, but it's sloppy, slows discovery of new content, and slightly dilutes signal. Most teams forget this because "the redirects handle it."
The fix:
— Crawl the live site and flag internal links that resolve through a 301
— Update them to point directly at the final URL
— Re-crawl to confirm zero internal redirects remain
Next step: run an internal-link audit and bulk-fix the worst offenders (nav and footer first).
A: Yes, and it's a satisfying cleanup. Short answer: internal links pointing to redirected URLs force an extra hop on every crawl and click, quietly wasting crawl budget you'd rather spend on real pages.
Long answer: Redirects are a safety net for external links you can't control. But your own menus, body links, and breadcrumbs you can control — and leaving them pointing at old URLs means Google crawls A→301→B every single time. It works, but it's sloppy, slows discovery of new content, and slightly dilutes signal. Most teams forget this because "the redirects handle it."
The fix:
— Crawl the live site and flag internal links that resolve through a 301
— Update them to point directly at the final URL
— Re-crawl to confirm zero internal redirects remain
Next step: run an internal-link audit and bulk-fix the worst offenders (nav and footer first).
Q: Migration went live last night — what should I check in the first 24 hours?
First night is about catching breakage, not chasing rankings. Here's your triage list.
Short answer: confirm crawlable, redirected, and indexable. In that order.
Long answer, run these in sequence:
— Pull up robots.txt on the live site. Make sure you didn't ship a staging 'Disallow: /'. This is the number one launch-night disaster.
— Spot-check 20 old URLs across different sections — each should 301 to the right new page in one hop.
— Check 10 key pages for a noindex tag that snuck over from staging.
— Confirm the homepage and top templates render, not just return 200.
— Verify your sitemap loads and points to new URLs.
— Submit the new sitemap in GSC.
Next step: set a reminder for day 3 to check crawl stats and coverage — don't refresh rankings hourly tonight.
First night is about catching breakage, not chasing rankings. Here's your triage list.
Short answer: confirm crawlable, redirected, and indexable. In that order.
Long answer, run these in sequence:
— Pull up robots.txt on the live site. Make sure you didn't ship a staging 'Disallow: /'. This is the number one launch-night disaster.
— Spot-check 20 old URLs across different sections — each should 301 to the right new page in one hop.
— Check 10 key pages for a noindex tag that snuck over from staging.
— Confirm the homepage and top templates render, not just return 200.
— Verify your sitemap loads and points to new URLs.
— Submit the new sitemap in GSC.
Next step: set a reminder for day 3 to check crawl stats and coverage — don't refresh rankings hourly tonight.
Q: We 301'd old pages but also left them returning 200 in some cases. Google sees duplicates. Why?
A: Subtle one — nice spot. Short answer: some old URLs are both redirecting and still serving a live 200 page depending on how they're hit, so Google sees two versions of the same content.
Long answer: This happens when a redirect lives at the app level but the old template still responds on certain parameters, or a CDN caches a 200 while the origin sends a 301. The result: Googlebot sometimes gets the redirect, sometimes the old live page. Mixed signals stall the migration and can trigger duplicate-content confusion. It's nasty because it's intermittent and won't show on a single manual test.
The fix:
— Crawl old URLs and look for any returning 200 instead of 301
— Purge CDN cache so it serves the redirect, not the stale page
— Ensure the redirect fires before the app renders old content
Next step: bulk-test your old URL list for status codes; investigate any 200 that should be a 301.
A: Subtle one — nice spot. Short answer: some old URLs are both redirecting and still serving a live 200 page depending on how they're hit, so Google sees two versions of the same content.
Long answer: This happens when a redirect lives at the app level but the old template still responds on certain parameters, or a CDN caches a 200 while the origin sends a 301. The result: Googlebot sometimes gets the redirect, sometimes the old live page. Mixed signals stall the migration and can trigger duplicate-content confusion. It's nasty because it's intermittent and won't show on a single manual test.
The fix:
— Crawl old URLs and look for any returning 200 instead of 301
— Purge CDN cache so it serves the redirect, not the stale page
— Ensure the redirect fires before the app renders old content
Next step: bulk-test your old URL list for status codes; investigate any 200 that should be a 301.