JobPosting vs Occupation: the careers markup that quietly expired
Career sites confuse two types and one of them now demands a paid integration. JobPosting marks a specific open role; Occupation describes a profession generically. Critical update: as of 2024, JobPosting rich results require Google's Indexing API and a verified integration — static JobPosting markup alone no longer surfaces in the jobs experience.
— Specific open role you want in Google Jobs: JobPosting plus the required Indexing API workflow, not just markup
— Generic profession/salary-guide page: Occupation, which still works as standard structured data
— Expired roles: you must remove or update via the API, or risk policy issues
What it means for you: if you added JobPosting markup and saw nothing in the jobs widget, it's not broken — Google changed the access model to API-gated. Occupation for guide content still earns normal treatment. Watch this: the API-gating of JobPosting is the template for how Google may restrict other high-value rich results — markup-only access is shrinking.

Microsoft планирует вставлять рекламу в игры

➡️ Читайте на сайте: https://aff.top/blog/microsoft-planiruet-vstavliat-reklamu-v-igry

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

Wikidata anchor vs on-site sameAs pile: where to root your entity
For entity recognition, teams debate which sameAs targets matter. The hierarchy is clearer than the debate suggests: not all identity links carry equal weight. A Wikidata Q-ID is the strongest anchor because Google's Knowledge Graph ingests Wikidata directly.
— Top tier: Wikidata entity URL, Wikipedia article — these feed the Knowledge Graph
— Mid tier: official, verified social profiles that corroborate identity
— Low tier: directory listings, scraped profiles — noise that dilutes precision
What it means for you: getting a Wikidata item created and linking it via sameAs does more for entity recognition than ten social URLs. If you're not in Wikidata, that's the first move — then mirror the Q-ID in your Organization sameAs. AI search and Knowledge Panels both lean on this chain. Watch this: as LLMs decide who's a citable authority, a clean Wikidata-anchored entity graph is becoming the deciding signal — sources in the SERPs increasingly trace citations back to entities with strong Wikidata grounding.

The date-format drift that breaks Article eligibility

Sources in the SERPs keep flagging it: datePublished and dateModified written as 'June 13, 2026' or 06/13/2026 instead of ISO 8601. Google needs 2026-06-13T09:00:00-04:00 — and crucially, a dateModified with no timezone offset gets interpreted as UTC, throwing your 'freshness' signal hours out of sync.

What it means for you: localized date plugins that render human dates into the schema field are a recurring offender. The visible date can be pretty; the JSON-LD value cannot.

Watch this: faking a fresh dateModified on every cron run without changing content is now a known spam pattern — Google compares it against the actual content diff and discounts liars.

The date-format drift that breaks Article eligibility

Sources in the SERPs keep flagging it: datePublished and dateModified written as 'June 13, 2026' or 06/13/2026 instead of ISO 8601. Google needs 2026-06-13T09:00:00-04:00 — and crucially, a dateModified with no timezone offset gets interpreted as UTC, throwing your 'freshness' signal hours out of sync.

What it means for you: localized date plugins that render human dates into the schema field are a recurring offender. The visible date can be pretty; the JSON-LD value cannot.

Watch this: faking a fresh dateModified on every cron run without changing content is now a known spam pattern — Google compares it against the actual content diff and discounts liars.

LocalBusiness schema that fights your Business Profile

Reported across local audits: LocalBusiness JSON-LD whose name, address, or phone disagrees with the Google Business Profile and the visible page. Inconsistent NAP across markup, profile, and footer fragments the entity, and Google trusts the verified Business Profile over your schema — so the mismatch costs you, not it.

What it means for you: your address, telephone, and name must match the Business Profile character-for-character, and the more specific subtype (Dentist, Restaurant) beats generic LocalBusiness. openingHoursSpecification that contradicts the profile is a trust ding.

Watch this: geo coordinates copied wrong from another location are a quiet entity-poisoner — verify lat/long against the actual pin, not a geocoder guess.

The 6-step playbook to salvage value from deprecated FAQ markup

Google killed FAQ rich results for nearly all sites back in 2023, but the markup itself never stopped being readable. As of this week, the smart move isn't deleting it — it's repurposing it. Here's the recovery sequence we've watched work:

— Audit which URLs still ship FAQPage in the DOM (Rich Results Test, not the deprecated report)
— Keep the markup if the visible Q&A still serves users; strip it if it was injected only for stars
— Re-point those Q&A blocks into a Question/Answer pair under your main entity
— Verify no orphaned mainEntity arrays remain after the swap
— Resubmit the URL for crawl, don't wait for organic recrawl
— Log a before/after in a sheet so you can prove causation later

What it means for you: AI engines still parse FAQPage even though Google won't draw a widget. Watch this — citation surfaces reward the structure Search abandoned.

The pre-submit checklist before you push Product markup to Merchant listings

Sources in the SERPs keep flagging the same rejection: a Product that validates in the Rich Results Test but still gets bounced from free Merchant listings. The two systems have different bars. Run this gate before you ship:

— Confirm offers carries price, priceCurrency, and a real availability enum (not a guess)
— Add shippingDetails and hasMerchantReturnPolicy — Merchant Center treats these as near-required now
— Match the gtin/mpn to the value in your product feed exactly, character for character
— Keep the markup price and the on-page price identical at crawl time
— Validate against the Merchant listings report, not just the generic rich result

What it means for you: feed mismatch is the silent killer here, not syntax. Watch this — Google has been tightening returns and shipping fields quarter over quarter, and the loose era is closing.

BreadcrumbList markup vs URL path: don't assume Google reads your slashes
There's a myth that a clean /category/subcategory/ URL gives you breadcrumb display for free. It doesn't. Google generates breadcrumb display from BreadcrumbList structured data first; URL structure is a weak fallback it may or may not infer.
— Want guaranteed breadcrumb display in SERPs: explicit BreadcrumbList JSON-LD, every position with item and name
— Deep nesting: markup lets you collapse a 5-level path into the 2-3 breadcrumbs you actually want shown
— Faceted/filtered URLs: markup lets you point breadcrumbs at the canonical category, not the messy filtered URL
What it means for you: relying on URL inference means Google chooses your breadcrumb labels, often wrong or truncated. Explicit BreadcrumbList puts you in control of the displayed path. Watch this: breadcrumb display is one of the most stable rich results left standing — worth the markup that FAQ and HowTo no longer are.

На Anthropic, OpenAI, Google и SpaceXAI подали в суд из-за ИИ

В Калифорнии против ИИ-компаний подали антимонопольный иск: регулятору показалось подозрительным, что игроки синхронно призывают ограничить развитие нейросетей ради безопасности. Смысл спора в том, что инвестиции в ИИ уже обгоняют реальный прогресс, а бизнесу выгодны правила, которые защитят капитал. Вывод: быстрых прорывов ждать не стоит, лучше выжимать максимум из текущих инструментов.

➡️ Читайте на сайте: https://aff.top/blog/na-anthropic-openai-google-i-spacexai-podali-v-sud-iz-za-ii

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

Google ads начал показывать расходы конкурентов

Google Ads запустил Peer Spending — инструмент, который сравнивает расходы аккаунта с рекламодателями из той же ниши без раскрытия чужих данных. Он показывает, тратите вы больше, меньше или примерно на уровне конкурентов на уровне кампаний и групп объявлений. Для арбитража это скорее ориентир по бенчмаркам, чем инструмент прямого усиления залива.

➡️ Читайте на сайте: https://aff.top/blog/google-ads-nachal-pokazyvat-raskhody-konkurentov

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

Минфин РФ планирует выпустить собственный стейблкоин

Власти РФ обсуждают запуск рублёвого стейблкоина: сейчас решают, как его обеспечить, какие операции разрешить и будет ли на него спрос. Основной кейс — международные переводы, а не использование физлицами. Если проект доведут до запуска, он может стать частью новой криптоинфраструктуры и альтернативой токенам, привязанным к дружественным валютам.

➡️ Читайте на сайте: https://aff.top/blog/minfin-rf-planiruet-vypustit-sobstvennyi-steiblkoin

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