<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Alexander Todosuik</title>
    <description>The latest articles on DEV Community by Alexander Todosuik (@yositeup).</description>
    <link>https://dev.to/yositeup</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4035959%2Fcea84504-2c2b-4309-8b54-3ba5c7e19ebe.jpg</url>
      <title>DEV Community: Alexander Todosuik</title>
      <link>https://dev.to/yositeup</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/yositeup"/>
    <language>en</language>
    <item>
      <title>Google Restated Merchant Center Reporting Back to July 1, 2026</title>
      <dc:creator>Alexander Todosuik</dc:creator>
      <pubDate>Thu, 03 Sep 2026 19:04:28 +0000</pubDate>
      <link>https://dev.to/yositeup/google-restated-merchant-center-reporting-back-to-july-1-2026-2lb5</link>
      <guid>https://dev.to/yositeup/google-restated-merchant-center-reporting-back-to-july-1-2026-2lb5</guid>
      <description>&lt;p&gt;Google restated &lt;strong&gt;Merchant Center&lt;/strong&gt; performance reporting going back to &lt;strong&gt;July 1, 2026&lt;/strong&gt;, with the update landing on August 24. If you manage a Shopping feed and noticed a sudden shift in your historical reports, this is very likely why.&lt;/p&gt;

&lt;h2&gt;
  
  
  What was restated
&lt;/h2&gt;

&lt;p&gt;The core change is that &lt;strong&gt;YouTube affiliate/shopping clicks are now split out from organic traffic&lt;/strong&gt; in Merchant Center reporting, instead of being folded into the same organic bucket as before. Because the restatement is retroactive to July 1, historical charts change shape even though nothing about your actual traffic changed.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why this looks like a traffic drop
&lt;/h2&gt;

&lt;p&gt;If a meaningful share of your organic clicks were actually coming from YouTube shopping surfaces, your organic line in Merchant Center can show what looks like a drop starting in the restated period - purely from reclassification, not from any real change in demand or rankings.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to check
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Compare total (organic + YouTube) clicks pre- and post-restatement rather than organic alone.&lt;/li&gt;
&lt;li&gt;Check whether your YouTube shopping integration is active - the split only matters if you have meaningful YouTube-sourced traffic.&lt;/li&gt;
&lt;li&gt;Do not diagnose a ranking drop from Merchant Center data alone without cross-checking Search Console.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Available in your language
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Russian (Ukraine market): &lt;a href="https://yositeup.com/ru-ua/blog/merchant-center-cross-platform-reporting-2026" rel="noopener noreferrer"&gt;https://yositeup.com/ru-ua/blog/merchant-center-cross-platform-reporting-2026&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Russian (US market): &lt;a href="https://yositeup.com/ru-us/blog/merchant-center-cross-platform-reporting-2026" rel="noopener noreferrer"&gt;https://yositeup.com/ru-us/blog/merchant-center-cross-platform-reporting-2026&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Russian (Poland market): &lt;a href="https://yositeup.com/ru-pl/blog/merchant-center-cross-platform-reporting-2026" rel="noopener noreferrer"&gt;https://yositeup.com/ru-pl/blog/merchant-center-cross-platform-reporting-2026&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Polish: &lt;a href="https://yositeup.com/pl-pl/blog/merchant-center-cross-platform-reporting-2026" rel="noopener noreferrer"&gt;https://yositeup.com/pl-pl/blog/merchant-center-cross-platform-reporting-2026&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>googlemerchantcenter</category>
      <category>ecommerce</category>
      <category>seo</category>
      <category>analytics</category>
    </item>
    <item>
      <title>Google Ads' New Product Titles Report Shows Which Titles Were Rewritten by AI</title>
      <dc:creator>Alexander Todosuik</dc:creator>
      <pubDate>Thu, 03 Sep 2026 19:02:32 +0000</pubDate>
      <link>https://dev.to/yositeup/google-ads-new-product-titles-report-shows-which-titles-were-rewritten-by-ai-4f72</link>
      <guid>https://dev.to/yositeup/google-ads-new-product-titles-report-shows-which-titles-were-rewritten-by-ai-4f72</guid>
      <description>&lt;p&gt;Google Ads has quietly added a &lt;strong&gt;Product Titles report&lt;/strong&gt; inside Shopping campaign diagnostics. It shows which product titles shown to shoppers were rewritten by Google's AI systems, compared to what you actually submitted in your feed.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why titles get rewritten
&lt;/h2&gt;

&lt;p&gt;Google has rewritten Shopping titles for years to better match search intent, but until now there was no dedicated report to see the scale or pattern of these changes. Advertisers relied on spot-checking individual ads.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to check in the new report
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;How many of your active listings have an AI-rewritten title versus the original feed title.&lt;/li&gt;
&lt;li&gt;Whether rewritten titles are dropping key attributes (brand, size, color) that your feed structure relies on for filtering.&lt;/li&gt;
&lt;li&gt;Whether performance differs meaningfully between rewritten and original titles for the same product.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This is especially relevant if your feed pipeline enforces strict formatting for compliance or brand reasons - the report is the first way to audit that at scale rather than product-by-product.&lt;/p&gt;

&lt;h2&gt;
  
  
  Available in your language
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Russian (Ukraine market): &lt;a href="https://yositeup.com/ru-ua/blog/google-ads-product-titles-report-ai-rewritten-2026" rel="noopener noreferrer"&gt;https://yositeup.com/ru-ua/blog/google-ads-product-titles-report-ai-rewritten-2026&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Polish: &lt;a href="https://yositeup.com/pl-pl/blog/google-ads-product-titles-report-ai-rewritten-2026" rel="noopener noreferrer"&gt;https://yositeup.com/pl-pl/blog/google-ads-product-titles-report-ai-rewritten-2026&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>googleads</category>
      <category>ecommerce</category>
      <category>seo</category>
      <category>ppc</category>
    </item>
    <item>
      <title>Google AdSense Switches to Begin-to-Render Impression Counting (Feb 17, 2027)</title>
      <dc:creator>Alexander Todosuik</dc:creator>
      <pubDate>Thu, 03 Sep 2026 19:02:16 +0000</pubDate>
      <link>https://dev.to/yositeup/google-adsense-switches-to-begin-to-render-impression-counting-feb-17-2027-160c</link>
      <guid>https://dev.to/yositeup/google-adsense-switches-to-begin-to-render-impression-counting-feb-17-2027-160c</guid>
      <description>&lt;p&gt;Google AdSense is changing how it counts ad impressions starting &lt;strong&gt;February 17, 2027&lt;/strong&gt;. The platform is moving to a &lt;strong&gt;Begin-to-Render&lt;/strong&gt; model: an impression will only count once the ad slot has actually started rendering in the browser.&lt;/p&gt;

&lt;h2&gt;
  
  
  What actually changes
&lt;/h2&gt;

&lt;p&gt;Under the current method, an impression can be logged even when an ad never really became visible - for example when a page is closed or navigated away from before the ad finished loading. Begin-to-Render tightens that: impressions that started loading but never rendered will no longer be counted.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why this matters for publishers
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Dashboard impression numbers may drop after the switch, with no real change in traffic or ad requests.&lt;/li&gt;
&lt;li&gt;CTR and RPM metrics that are calculated per impression will shift because the denominator (impressions) gets smaller and more accurate.&lt;/li&gt;
&lt;li&gt;It's worth comparing pre- and post-February-2027 data on a like-for-like basis rather than assuming a raw drop means falling traffic.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Available in your language
&lt;/h2&gt;

&lt;p&gt;Full breakdowns with more detail, screenshots and market-specific context:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Russian (Ukraine market): &lt;a href="https://yositeup.com/ru-ua/blog/google-adsense-begin-to-render-impressions-february-2027" rel="noopener noreferrer"&gt;https://yositeup.com/ru-ua/blog/google-adsense-begin-to-render-impressions-february-2027&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Russian (US market): &lt;a href="https://yositeup.com/ru-us/blog/google-adsense-begin-to-render-impressions-february-2027" rel="noopener noreferrer"&gt;https://yositeup.com/ru-us/blog/google-adsense-begin-to-render-impressions-february-2027&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Russian (Poland market): &lt;a href="https://yositeup.com/ru-pl/blog/google-adsense-begin-to-render-impressions-february-2027" rel="noopener noreferrer"&gt;https://yositeup.com/ru-pl/blog/google-adsense-begin-to-render-impressions-february-2027&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Polish: &lt;a href="https://yositeup.com/pl-pl/blog/google-adsense-begin-to-render-impressions-february-2027" rel="noopener noreferrer"&gt;https://yositeup.com/pl-pl/blog/google-adsense-begin-to-render-impressions-february-2027&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you run AdSense on a site with meaningful traffic, it's worth flagging this internally now so nobody panics in February 2027 when the numbers move.&lt;/p&gt;

</description>
      <category>adsense</category>
      <category>googleads</category>
      <category>seo</category>
      <category>monetization</category>
    </item>
    <item>
      <title>What Article Marketing Actually Means in SEO (Not What Most Guides Say)</title>
      <dc:creator>Alexander Todosuik</dc:creator>
      <pubDate>Fri, 28 Aug 2026 00:40:21 +0000</pubDate>
      <link>https://dev.to/yositeup/what-article-marketing-actually-means-in-seo-not-what-most-guides-say-3pgd</link>
      <guid>https://dev.to/yositeup/what-article-marketing-actually-means-in-seo-not-what-most-guides-say-3pgd</guid>
      <description>&lt;p&gt;Most explanations of "article marketing" in SEO stop at "write content and rank." That is not&lt;br&gt;
wrong, but it skips the part that actually matters: which articles compound and which ones just add&lt;br&gt;
word count.&lt;/p&gt;

&lt;h2&gt;
  
  
  What article marketing actually is
&lt;/h2&gt;

&lt;p&gt;It is the practice of publishing topic-specific, high-quality articles whose purpose is to build&lt;br&gt;
topical authority around a cluster of related search intents, not just to target one keyword each.&lt;br&gt;
A single article rarely ranks in isolation for long -- what ranks and holds is a cluster where each&lt;br&gt;
piece links to the others and covers a distinct angle of the same underlying question.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why most article marketing efforts underperform
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Articles are commissioned by keyword volume alone, with no check on whether the search intent is
informational, commercial, or navigational&lt;/li&gt;
&lt;li&gt;No internal linking plan between articles in the same cluster&lt;/li&gt;
&lt;li&gt;Publishing stops as soon as rankings appear, before the authority signal compounds&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What to check before commissioning content
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Does this topic already have an AI Overview or featured snippet answering it in one paragraph?
If yes, a generic article will not get clicks even at position 1-3.&lt;/li&gt;
&lt;li&gt;Is there an existing cluster this article should link into, or is it a true standalone topic?&lt;/li&gt;
&lt;li&gt;What does the top 10 for this query actually cover that a generic 800-word article does not?&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Full guide with the complete framework: &lt;a href="https://yositeup.com/blog/seo-article-marketing" rel="noopener noreferrer"&gt;https://yositeup.com/blog/seo-article-marketing&lt;/a&gt;&lt;/p&gt;

</description>
      <category>seo</category>
      <category>contentstrategy</category>
      <category>marketing</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Your SEO Competitors Are Not Who You Think They Are</title>
      <dc:creator>Alexander Todosuik</dc:creator>
      <pubDate>Thu, 27 Aug 2026 22:51:30 +0000</pubDate>
      <link>https://dev.to/yositeup/your-seo-competitors-are-not-who-you-think-they-are-cm0</link>
      <guid>https://dev.to/yositeup/your-seo-competitors-are-not-who-you-think-they-are-cm0</guid>
      <description>&lt;p&gt;A common mistake in competitor analysis: teams list their direct business rivals and&lt;br&gt;
call it done. But a search competitor is not the same thing as a business competitor -- it is&lt;br&gt;
simply whoever else ranks for the same queries, and that list is often unrelated to who you&lt;br&gt;
compete with for customers.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why this matters
&lt;/h2&gt;

&lt;p&gt;If you only track companies you already know, you miss:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Aggregator and comparison sites that outrank every individual business in the category&lt;/li&gt;
&lt;li&gt;Content publishers with no product at all, just better-optimized pages&lt;/li&gt;
&lt;li&gt;Adjacent businesses that happen to rank for a shared keyword cluster&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  A quick way to find your real list
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Take your 10-15 most important queries&lt;/li&gt;
&lt;li&gt;Search each one and record every domain in the top 10, not just ones you recognize&lt;/li&gt;
&lt;li&gt;Any domain that appears for 3+ of your queries is a real SEO competitor, regardless of
what it sells&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What to do with the list
&lt;/h2&gt;

&lt;p&gt;Once you know who actually occupies page 1, the useful comparison is technical and content&lt;br&gt;
depth, not brand size: page speed, internal linking, content freshness, and how much of the&lt;br&gt;
query's search intent each page actually answers.&lt;/p&gt;

&lt;p&gt;Full walkthrough with the complete methodology: &lt;a href="https://yositeup.com/en-ua/blog/competitors-website-analysis-for-seo-marketing" rel="noopener noreferrer"&gt;https://yositeup.com/en-ua/blog/competitors-website-analysis-for-seo-marketing&lt;/a&gt;&lt;/p&gt;

</description>
      <category>seo</category>
      <category>marketing</category>
      <category>webdev</category>
      <category>growth</category>
    </item>
    <item>
      <title>Reading Google Search Console Data Without Fooling Yourself</title>
      <dc:creator>Alexander Todosuik</dc:creator>
      <pubDate>Sat, 22 Aug 2026 12:58:32 +0000</pubDate>
      <link>https://dev.to/yositeup/reading-google-search-console-data-without-fooling-yourself-2e1o</link>
      <guid>https://dev.to/yositeup/reading-google-search-console-data-without-fooling-yourself-2e1o</guid>
      <description>&lt;p&gt;Three ways Search Console performance data gets misread, and what to check instead.&lt;/p&gt;

&lt;h2&gt;
  
  
  Average position is a blend, not a single truth
&lt;/h2&gt;

&lt;p&gt;A page at "position 8" can be #1 for its main keyword and #40 for ten low-volume variants&lt;br&gt;
dragging the average down. Before reacting to a position number, filter the Queries tab to&lt;br&gt;
that specific page and look at the actual query breakdown.&lt;/p&gt;

&lt;h2&gt;
  
  
  Low CTR at a bad position is expected
&lt;/h2&gt;

&lt;p&gt;CTR naturally drops under 1% past position 20-30. That is not a red flag by itself - the&lt;br&gt;
position is the actual problem. Low CTR at position 5-8 is the pattern worth investigating,&lt;br&gt;
because it usually means a title/meta mismatch with what users actually want to click.&lt;/p&gt;

&lt;h2&gt;
  
  
  High impressions with zero clicks
&lt;/h2&gt;

&lt;p&gt;This usually means Google is showing the page for real queries, but the listing isn't winning&lt;br&gt;
the click. Cross-reference the specific queries driving those impressions against your title&lt;br&gt;
and meta description - the mismatch is often obvious once you see the actual query list.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is actually worth acting on
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Pages with high impressions AND position 11-20 - real demand, one push from page one&lt;/li&gt;
&lt;li&gt;A position swing across many pages at once on the same day - algorithm update, not a
page-level problem&lt;/li&gt;
&lt;li&gt;Good position (top 5) but unusually low CTR - a title/meta fix, not a ranking fix&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Full report-by-report guide:&lt;br&gt;
&lt;a href="https://yositeup.com/blog/google-search-console-data-guide-2026" rel="noopener noreferrer"&gt;Search Console data guide 2026&lt;/a&gt;&lt;/p&gt;

</description>
      <category>seo</category>
      <category>analytics</category>
      <category>webdev</category>
      <category>growth</category>
    </item>
    <item>
      <title>Multi-Regional Website Structure: The Mistakes That Actually Tank Rankings</title>
      <dc:creator>Alexander Todosuik</dc:creator>
      <pubDate>Sat, 22 Aug 2026 12:57:37 +0000</pubDate>
      <link>https://dev.to/yositeup/multi-regional-website-structure-the-mistakes-that-actually-tank-rankings-2aie</link>
      <guid>https://dev.to/yositeup/multi-regional-website-structure-the-mistakes-that-actually-tank-rankings-2aie</guid>
      <description>&lt;p&gt;Expanding one site into multiple languages/markets fails in a small number of predictable&lt;br&gt;
ways. Checklist form, because it's faster to audit against than prose.&lt;/p&gt;

&lt;h2&gt;
  
  
  URL structure — pick one, do not mix
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Subdirectory: &lt;code&gt;example.com/en-us/&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Subdomain: &lt;code&gt;us.example.com&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;ccTLD: &lt;code&gt;example.de&lt;/code&gt; (strongest local signal, highest cost/maintenance)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Mixing patterns across different sections of the same site is the single most common&lt;br&gt;
structural mistake found in multi-regional audits.&lt;/p&gt;

&lt;h2&gt;
  
  
  hreflang, done correctly
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Every variant must reference itself AND every sibling variant — self-referencing is
required, not optional&lt;/li&gt;
&lt;li&gt;Include an &lt;code&gt;x-default&lt;/code&gt; for the fallback/international version&lt;/li&gt;
&lt;li&gt;Use exact ISO codes (&lt;code&gt;en-us&lt;/code&gt;, not &lt;code&gt;en_US&lt;/code&gt; or &lt;code&gt;en-US-x&lt;/code&gt;)&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What actually breaks rankings
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Machine-translating without local market adaptation (currency, examples, local
regulations) — Google and users both notice&lt;/li&gt;
&lt;li&gt;Internal links defaulting back to the English version instead of the current
language/region&lt;/li&gt;
&lt;li&gt;Duplicate hreflang errors — Search Console's International Targeting report surfaces
most of these directly&lt;/li&gt;
&lt;li&gt;Treating "same language, different country" as identical — UK English and US English
have different commercial intent and different competitors&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Full guide on planning multi-regional structure from scratch:&lt;br&gt;
&lt;a href="https://yositeup.com/blog/multi-regional-website-is-your-tool-for-expanding-your-business" rel="noopener noreferrer"&gt;Multi-regional website expansion guide&lt;/a&gt;&lt;/p&gt;

</description>
      <category>seo</category>
      <category>webdev</category>
      <category>i18n</category>
      <category>growth</category>
    </item>
    <item>
      <title>The "AI Overviews Killed CTR by 61%" Number Everyone Misquotes</title>
      <dc:creator>Alexander Todosuik</dc:creator>
      <pubDate>Sat, 22 Aug 2026 12:57:25 +0000</pubDate>
      <link>https://dev.to/yositeup/the-ai-overviews-killed-ctr-by-61-number-everyone-misquotes-lne</link>
      <guid>https://dev.to/yositeup/the-ai-overviews-killed-ctr-by-61-number-everyone-misquotes-lne</guid>
      <description>&lt;p&gt;A widely cited study found a 61% CTR drop tied to AI Overviews. The number is real, but it&lt;br&gt;
gets misquoted as "AI Overviews cut organic CTR by 61%" across the board, which is not what&lt;br&gt;
was measured.&lt;/p&gt;

&lt;h2&gt;
  
  
  What was actually measured
&lt;/h2&gt;

&lt;p&gt;The 61% figure is the CTR drop for queries where an AI Overview appears ABOVE the organic&lt;br&gt;
results, compared to the same query type without an AI Overview present. It is not a blanket&lt;br&gt;
number across all search traffic.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where the impact concentrates
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Informational "what is / how to" queries: largest measured impact&lt;/li&gt;
&lt;li&gt;Transactional / commercial-intent queries: comparatively smaller impact&lt;/li&gt;
&lt;li&gt;Branded queries: minimal impact, people searching your brand name still click through&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The practical read
&lt;/h2&gt;

&lt;p&gt;If most of your organic traffic is informational content, expect CTR compression specifically&lt;br&gt;
on the queries that trigger an AI Overview — not site-wide. Search Console's query-level data&lt;br&gt;
will show you exactly which queries have impressions growing while clicks stay flat; that&lt;br&gt;
pattern is the AI Overview signature.&lt;/p&gt;

&lt;p&gt;The response is not to abandon informational content — being the cited source inside an&lt;br&gt;
Overview still drives some referral clicks — but to weight commercial/transactional query&lt;br&gt;
tracking more heavily as the currently more reliable traffic base.&lt;/p&gt;

&lt;p&gt;Full study breakdown:&lt;br&gt;
&lt;a href="https://yositeup.com/blog/ai-overviews-ctr-drop-61-study-2026" rel="noopener noreferrer"&gt;AI Overviews CTR drop study, explained&lt;/a&gt;&lt;/p&gt;

</description>
      <category>seo</category>
      <category>ai</category>
      <category>marketing</category>
      <category>growth</category>
    </item>
    <item>
      <title>AI Max for Shopping Is Not Performance Max With a New Name</title>
      <dc:creator>Alexander Todosuik</dc:creator>
      <pubDate>Sat, 22 Aug 2026 12:57:02 +0000</pubDate>
      <link>https://dev.to/yositeup/ai-max-for-shopping-is-not-performance-max-with-a-new-name-403d</link>
      <guid>https://dev.to/yositeup/ai-max-for-shopping-is-not-performance-max-with-a-new-name-403d</guid>
      <description>&lt;p&gt;Merchants keep asking why their Performance Max playbook stopped working after switching&lt;br&gt;
to AI Max for Shopping. Three concrete mechanical differences explain most of it.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Product feed weight went up
&lt;/h2&gt;

&lt;p&gt;Title quality, product type hierarchy, and custom labels now carry more direct weight in who&lt;br&gt;
sees which product. A generic or SKU-only title has a bigger downside than it did before.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Negative keywords are actually enforced
&lt;/h2&gt;

&lt;p&gt;Performance Max had well-documented cases where negatives were inconsistently applied across&lt;br&gt;
an account. Early AI Max data shows more consistent enforcement — which also means old negative&lt;br&gt;
lists that "didn't seem to matter" suddenly do.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Creative generation is now explicit policy
&lt;/h2&gt;

&lt;p&gt;The July 2026 Terms of Service update formally states the system can generate and test ad&lt;br&gt;
creative combinations from your feed and assets. This behavior existed under Performance Max&lt;br&gt;
too, it just wasn't documented as clearly.&lt;/p&gt;

&lt;h2&gt;
  
  
  Before migrating, check
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Are product titles descriptive, or just codes?&lt;/li&gt;
&lt;li&gt;Are custom labels actually used for margin/season/bestseller segmentation?&lt;/li&gt;
&lt;li&gt;Are negative keywords account-level (more reliable) or campaign-level only?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Full migration breakdown with more detail on each mechanism:&lt;br&gt;
&lt;a href="https://yositeup.com/blog/google-ai-max-shopping-replacing-performance-max-2026" rel="noopener noreferrer"&gt;AI Max for Shopping vs Performance Max&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ecommerce</category>
      <category>googleads</category>
      <category>marketing</category>
      <category>seo</category>
    </item>
    <item>
      <title>Your Google Ads Historical Data Is Gone. Here Is What Actually Survives</title>
      <dc:creator>Alexander Todosuik</dc:creator>
      <pubDate>Sat, 22 Aug 2026 12:56:49 +0000</pubDate>
      <link>https://dev.to/yositeup/your-google-ads-historical-data-is-gone-here-is-what-actually-survives-22ak</link>
      <guid>https://dev.to/yositeup/your-google-ads-historical-data-is-gone-here-is-what-actually-survives-22ak</guid>
      <description>&lt;p&gt;Google deleted historical performance data older than a June 2026 cutoff from the Ads&lt;br&gt;
interface and API — campaign history, keyword performance, search terms, auction insights.&lt;br&gt;
Support tickets about "missing data" all trace back to the same policy change, not an account bug.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is gone for good
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Search term reports not exported before the cutoff&lt;/li&gt;
&lt;li&gt;Auction insights history&lt;/li&gt;
&lt;li&gt;Keyword-level Quality Score history&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What you can still pull back
&lt;/h2&gt;

&lt;p&gt;If GA4 was linked with auto-tagging on, click and session data survived independently:&lt;br&gt;
Reports &amp;gt; Acquisition &amp;gt; Traffic Acquisition, filtered to &lt;code&gt;google / cpc&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;If BigQuery export was enabled on the GA4 property, the raw &lt;code&gt;events_*&lt;/code&gt; tables still have it —&lt;br&gt;
query for &lt;code&gt;traffic_source.medium = 'cpc'&lt;/code&gt; over the deleted date range.&lt;/p&gt;

&lt;p&gt;Any scheduled CSV/Sheets export from before the cutoff also still has the numbers, just not&lt;br&gt;
inside the Ads UI anymore.&lt;/p&gt;

&lt;h2&gt;
  
  
  The actual fix
&lt;/h2&gt;

&lt;p&gt;Set up a recurring quarterly export (a simple Ads Script writing to Sheets, or a BigQuery&lt;br&gt;
export) so a future retention policy change can't erase your own history again. Waiting for&lt;br&gt;
Google to reverse a data policy is not a strategy.&lt;/p&gt;

&lt;p&gt;Full breakdown of exactly what changed and a step-by-step recovery checklist:&lt;br&gt;
&lt;a href="https://yositeup.com/blog/google-ads-reporting-data-deleted-june-2026" rel="noopener noreferrer"&gt;Google Ads reporting data deleted - what to do&lt;/a&gt;&lt;/p&gt;

</description>
      <category>googleads</category>
      <category>marketing</category>
      <category>analytics</category>
      <category>growth</category>
    </item>
    <item>
      <title>Google Search Console Now Tracks YouTube and Social Media in Search</title>
      <dc:creator>Alexander Todosuik</dc:creator>
      <pubDate>Sun, 16 Aug 2026 14:53:19 +0000</pubDate>
      <link>https://dev.to/yositeup/google-search-console-now-tracks-youtube-and-social-media-in-search-10pp</link>
      <guid>https://dev.to/yositeup/google-search-console-now-tracks-youtube-and-social-media-in-search-10pp</guid>
      <description>&lt;p&gt;Google Search Console expanded its coverage in 2026 to track how pages perform when they surface alongside YouTube and social media results inside Google Search - not just classic blue-link organic results.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why this changed the reporting picture
&lt;/h2&gt;

&lt;p&gt;Previously, a page could be driving real visibility through video or social integration in the SERP without that showing up anywhere in Search Console's standard performance report. That blind spot is now closed.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to check
&lt;/h2&gt;

&lt;p&gt;Filter the Performance report by the new search appearance types. Compare position and CTR for pages with video/social integration against pages without - the difference is often larger than expected.&lt;/p&gt;

&lt;p&gt;Full breakdown: &lt;a href="https://yositeup.com/blog/google-search-console-social-video-platforms-2026" rel="noopener noreferrer"&gt;yositeup.com&lt;/a&gt;&lt;/p&gt;

</description>
      <category>seo</category>
      <category>googlesearchconsole</category>
      <category>marketing</category>
    </item>
    <item>
      <title>Unconfirmed Google Ranking Volatility, August 12-13 2026</title>
      <dc:creator>Alexander Todosuik</dc:creator>
      <pubDate>Sat, 15 Aug 2026 21:55:41 +0000</pubDate>
      <link>https://dev.to/yositeup/unconfirmed-google-ranking-volatility-august-12-13-2026-lpf</link>
      <guid>https://dev.to/yositeup/unconfirmed-google-ranking-volatility-august-12-13-2026-lpf</guid>
      <description>&lt;p&gt;Multiple independent SERP trackers - AccuRanker, Algoroo, AWR, SEMrush Sensor, Sistrix, Mozcast - registered a synchronized volatility spike on August 12-13, 2026. Google has made no official statement; the Search Status Dashboard still shows the June 2026 spam update as the most recent confirmed event.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why the silence doesn't mean nothing happened
&lt;/h2&gt;

&lt;p&gt;Each tracker runs its own keyword panel and its own methodology. When several independently-built tools spike on the same dates, that agreement is a stronger signal than any single tool moving alone.&lt;/p&gt;

&lt;h2&gt;
  
  
  Scale
&lt;/h2&gt;

&lt;p&gt;Reported at roughly 56% of a typical confirmed core update's magnitude, and it faded within about a day.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to actually check
&lt;/h2&gt;

&lt;p&gt;Treat average position, impressions and clicks in Search Console as three separate signals, not one blended number. Separate Discover/Google News traffic from regular Search. Cross-check GA4 against Search Console before concluding anything.&lt;/p&gt;

&lt;p&gt;Full data breakdown and market context: &lt;a href="https://yositeup.com/ru-us/blog/google-ranking-volatility-august-12-2026" rel="noopener noreferrer"&gt;yositeup.com&lt;/a&gt;&lt;/p&gt;

</description>
      <category>seo</category>
      <category>googlesearch</category>
      <category>marketing</category>
    </item>
  </channel>
</rss>
