В публичный релиз вышел Fable 5.1

➡️ Читайте на сайте: https://aff.top/blog/v-publichnyi-reliz-vyshel-fable-5-1

🧠 Ещё больше инсайтов → в канале AFF.top

Product vs Offer vs AggregateOffer: stop flattening your merchant markup
Merchant listing rejections in Search Console almost always trace to one mistake — collapsing three types into one. Product is the entity. Offer is a single buyable SKU at one price. AggregateOffer is the price range across variants.
— Single price, single SKU: Product + one Offer, full stop
— Variants at different prices (sizes, colors): AggregateOffer with lowPrice/highPrice, plus child Offers if you can
— Marketplace with multiple sellers: AggregateOffer with offerCount, never a fake single Offer averaging them
What it means for you: if you're shoving a price range into a single Offer's price field, Merchant listings will read one price and your strikethroughs and 'from $X' displays break. Audit your variant pages first — that's where the flattening hides. Watch this as Google tightens variant-level structured data requirements for shopping surfaces.

1xBet перестал спонсировать эмоции

История о том, как казахстанцы зарегистрировали рекламный слоган 1xBet, а сам бренд оказался в юридической ловушке: после сделки с TonyBet права на товарный знак так и не выкупили. На фоне ареста активов Романа Семиохина и уголовного дела по азартным играм вывод простой: с 1xBet сейчас лучше не строить рекламные связки на рынке Казахстана.

➡️ Читайте на сайте: https://aff.top/blog/1xbet-perestal-sponsirovat-emocii

🧠 Ещё больше инсайтов → в канале AFF.top

За продажу аккаунтов в мессенджере теперь грозит статья

С 1 сентября 2026 года продажа аккаунтов соцсетей и мессенджеров в России стала уголовно и административно рискованной: штраф до 700 тысяч рублей, принудительные работы или лишение свободы до 2–3 лет. Если через аккаунт украдут деньги, продавца могут записать в соучастники мошенничества по ст. 159 УК РФ с риском до 10 лет.

➡️ Читайте на сайте: https://aff.top/blog/za-prodazhu-akkauntov-v-messendzhere-teper-grozit-statia

🧠 Ещё больше инсайтов → в канале AFF.top

Google выпустил в релиз Gemini 3.8 flash

Google выпустил Gemini 3.8 Flash спустя две недели после 3.7: модель обещает сильный кодинг и быстрый отклик, а цена остаётся низкой — $0,75 за млн входящих токенов и $3,75 за млн исходящих. Вывод простой: пока Google демпингует, это выгодный вариант для тех, кому нужны дешёвые и быстрые нейросетевые запросы.

➡️ Читайте на сайте: https://aff.top/blog/google-vypustil-v-reliz-gemini-3-8-flash

🧠 Ещё больше инсайтов → в канале AFF.top

FAQPage vs HowTo: both got cut, so why keep either?
As of the 2023 rollbacks, Google restricted FAQ rich results to authoritative government/health sites and killed HowTo rich results entirely. The reflex was to rip out the markup. That's the wrong comparison.
— Keep FAQPage when your content genuinely is Q&A: AI assistants and Search's own systems still parse it for entity context even without the visual snippet
— Keep HowTo schema only as a content-structure signal, not for visuals — the carousel is gone for good
— Drop neither for 'rich result' reasons; drop them only if the markup misrepresents the page
What it means for you: structured data outlived its rich result. The visual payoff vanished but the machine-readability didn't, and LLM search rewards clean Q&A structure. Watch this: the FAQ snippet may never return to Google, but its value migrated to AI answer engines that quote structured Q&A verbatim.

Яндекс запустил сервис ПроБлогер

Яндекс запустил ПроБлогер — платформу для монетизации небольших каналов и групп во ВКонтакте, Дзене, Максе, Telegram, YouTube и Rutube. Для модерации нужны от 1000 подписчиков, свежие публикации, статус самозанятого, ИП или юрлица и соблюдение закона. Доход доступен через автопостинг с оплатой за просмотры и партнёрские ссылки; CPM можно задать самому или отдать аукциону.

➡️ Читайте на сайте: https://aff.top/blog/iandeks-zapustil-servis-probloger

🧠 Ещё больше инсайтов → в канале AFF.top

Google ads упростил перенос креативов из Asset Studio

➡️ Читайте на сайте: https://aff.top/blog/google-ads-uprostil-perenos-kreativov-iz-asset-studio

🧠 Ещё больше инсайтов → в канале AFF.top

sameAs vs knowsAbout: you're using the wrong entity property
Teams stuff every Wikipedia and LinkedIn URL into sameAs and wonder why disambiguation still fails. The two properties answer different questions. sameAs says 'this IS the same entity, here are its other identities' — Wikidata, official social, Wikipedia. knowsAbout says 'this entity has expertise in these topics.'
— sameAs: only canonical identity references, ideally anchored to Wikidata and Google's Knowledge Graph
— knowsAbout: topics, subjects, areas of authority — the E-E-A-T signal
— Never mix: a topic URL in sameAs corrupts the identity claim
What it means for you: a tight sameAs of 3-5 authoritative identity links beats 15 random social profiles for getting an entity recognized. knowsAbout is where you signal expertise. Watch this: as AI search leans on entity graphs to decide who to cite, the precision of sameAs is becoming a ranking input, not decoration.

Enhancement reports vs URL Inspection: which Search Console view to trust
When structured data breaks, webmasters open the wrong panel and chase ghosts. The Enhancement reports (Products, Breadcrumbs, etc.) are aggregate and lag — they batch validation over days and group errors by type. URL Inspection's 'live test' validates the page as Googlebot fetches it right now.
— Triaging a sitewide template bug: Enhancement report, because it shows scale and trend
— Confirming a fix on one page: URL Inspection live test, because aggregate reports won't update for days
— Discrepancy between them: trust the live test for current state, the report for historical impact
What it means for you: a fixed bug still shows red in Enhancement reports for up to a week — don't panic-edit working markup. Validate fixes with live URL Inspection, then let the aggregate catch up. Watch this: re-validation in Search Console still runs on its own clock, and that lag burns people every release.

Article vs NewsArticle vs BlogPosting: the subtype actually matters now
Most sites slap generic Article on everything. The subtypes aren't cosmetic — they route your content into different Google surfaces and signal different freshness expectations.
— NewsArticle: required for Top Stories and Google News eligibility; commits you to journalistic standards and dateline freshness
— BlogPosting: signals opinion/editorial cadence, lighter freshness pressure
— Article: the safe generic when content is reference material, not timely
What it means for you: don't claim NewsArticle on evergreen guides — you invite freshness scrutiny you can't satisfy and risk demotion when the 'news' goes stale. Don't bury genuine news under generic Article and forfeit Top Stories eligibility. Match the subtype to the content's actual lifecycle. Watch this: AI news surfaces increasingly filter by NewsArticle markup, so the subtype is now a distribution gate, not a label.