# Pulse · August 13, 2026

> A judge lets an SEO-sabotage suit proceed, Google amends its SerpApi case with licensing claims, and OpenAI opens ChatGPT ads to health and finance advertisers.

Canonical: https://brandonlazovic.dev/pulse/2026-08-13/  
Author: Brandon Lazovic  
Published: 2026-08-13

## Federal judge allows SEO sabotage lawsuit against toxic-backlink campaign to proceed

Status: Confirmed  |  Topics: organic-search-core

A federal judge in the Northern District of Illinois ruled that Montway Auto Transport's lawsuit against Nexus AT LLC can proceed on Lanham Act false-advertising, trademark, and Illinois consumer-protection claims. Montway alleges Nexus built more than 2,350 toxic backlinks pointing to Montway's site between April and October 2025, using anchor text tied to illegal-drug and steroid sales to suppress its Google rankings. California unfair-competition claims were dismissed.

In plain terms: Negative SEO here means someone deliberately built spammy links pointing at a competitor's site to try to get Google to rank it lower, and a judge just ruled that can count as illegal false advertising, not just an SEO headache.

Why it matters: A ruling that lets false-advertising law reach a negative-SEO campaign gives sites hit by toxic backlinks a legal remedy beyond a disavow file.

Our take: Watch whether the Lanham Act claim survives summary judgment. A false-advertising theory succeeding here would give sabotage targets a court remedy that a Google disavow tool never provided.

- [CourtListener: Docket, Montway LLC v. Nexus AT LLC, 1:25-cv-13100 (N.D. Ill.)](https://www.courtlistener.com/docket/71776095/montway-llc-v-nexus-at-llc/)

## Google Merchant Center separates YouTube affiliate traffic from organic reporting

Status: Confirmed  |  Topics: product-feeds-shopping, measurement-analytics

Google's Merchant Center performance reports change on August 24, 2026, with historical data retroactively updated from July 1. YouTube affiliate-commission traffic will report separately from organic traffic instead of blending into it, which can produce a one-time drop in organic numbers. Product-level reporting expands to include Performance Max, Video, App, and Demand Gen campaigns, which can raise reported impressions and clicks. A future network-dimension breakout is also planned.

In plain terms: Merchant Center is the dashboard that shows how a product feed performs in Google Shopping, and this update means traffic a shopper found through a YouTube creator's affiliate link stops being lumped in with organic traffic, so the two numbers won't match last month's report even if nothing about the product changed.

Why it matters: Merchants who don't know the reclassification is coming will misread a real organic-traffic drop as a ranking problem instead of a reporting change.

Our take: I've written about the gap between Merchant Center's eligible status and whether a product is actually distributed to shoppers. This reporting split narrows a related blind spot with cleaner attribution between organic and YouTube-affiliate traffic, but it still won't tell a merchant why an eligible product draws zero impressions in a market.

- [Google Merchant Center Help: Merchant Center reporting updates](https://support.google.com/merchants/answer/17103877)

## Google amends SerpApi lawsuit with content-licensing claims after DMCA dismissal

Status: Confirmed  |  Topics: crawling-indexing-rendering, organic-search-core

Google filed an amended complaint against SerpApi on August 10, 2026, the 21-day deadline a judge set after dismissing the original DMCA claims in July for failing to show copyright holders authorized Google's anti-scraping measures. The amended filing adds terms from Google's licensing agreements with content providers, including Reddit, arguing those deals require Google to block unauthorized third-party access to licensed content. Discovery remains frozen pending the court's ruling.

In plain terms: DMCA anti-circumvention is the part of copyright law that bans breaking a technical lock protecting copyrighted material. The judge already ruled plain search results aren't that kind of protected material, so Google's new argument tries a different angle: its licensing contracts with sites like Reddit require it to keep scrapers out of that licensed content specifically.

Why it matters: If a licensing-deal theory succeeds where the original DMCA claim failed, it gives platforms with content-licensing contracts a new legal lever against SERP-scraping tools.

Our take: The theory shift is the story. Google is no longer arguing scraping itself is illegal, it's arguing a licensing contract obligates it to block access to specific licensed content, a narrower and more defensible claim than the one that just failed.

- [CourtListener: Docket, Google LLC v. SerpApi, LLC, 4:25-cv-10826 (N.D. Cal.)](https://www.courtlistener.com/docket/72059948/google-llc-v-serpapi-llc/)

## OpenAI opens ChatGPT ads to health and finance advertisers on a case-by-case basis

Status: Confirmed  |  Topics: chatgpt-assistants, ads-paid

OpenAI's ad policy, updated August 10, 2026, now allows approved advertisers in financial services and healthcare to run ads in ChatGPT, reviewed manually case by case, rather than blocking those categories outright. Legal services ads remain prohibited entirely, with only general legal education or media allowed. Ads still can't appear in emotionally reliant, mental-health, or other sensitive-context conversations. These categories had been broadly excluded since ChatGPT's ad test began, and OpenAI has revised the ad rules multiple times since.

In plain terms: OpenAI is starting to show real ads inside ChatGPT conversations, and this update means a health insurer or financial advisor can now apply to be one of them instead of being blocked outright, as long as OpenAI approves them individually and keeps the ad away from sensitive personal conversations.

Why it matters: Advertisers in health and finance now have a case-by-case path into ChatGPT's ad surface, a new visibility channel next to organic citations for exactly the verticals AI Overviews and Perplexity treat most cautiously.

Our take: Watch the approval bar, not the announcement. Manual review, case by case, for two categories regulators watch closely means the practical rollout will likely stay narrow for months, whatever the policy page technically allows starting today.

- [OpenAI: Ad policies](https://openai.com/policies/ad-policies/)

## Cloudflare gives AI agents wallets to pay for API and content access directly

Status: Confirmed  |  Topics: agentic-commerce, crawling-indexing-rendering

Cloudflare announced on August 4, 2026 a payment system letting AI agents hold and spend stablecoins autonomously. Human-controlled Account Wallets delegate capped spending, an allowance, an allow list, a maximum transaction size, to agent-operated Virtual Wallets tied to API keys. Agents can optionally claim a readable cloudflare.pay identity handle. Payments settle peer-to-peer over the x402 protocol, built on HTTP's little-used 402 Payment Required status code, covering web pages, datasets, APIs, and MCP tools.

In plain terms: Right now a website can only let an AI crawler in for free or block it outright. This gives sites a middle option, a way to charge an AI agent per page or per API call automatically, the same way a vending machine charges a person, without a subscription or a negotiated deal.

Why it matters: A native payment rail for agents turns block-or-let-in-free into a third option, charge it, which changes the economics of content access for anyone currently relying on paywalls or robots.txt alone.

Our take: Most of this is still future tense, full access ships in coming months, so the thing worth tracking now is adoption on the merchant side. A payment rail only matters once publishers actually price content behind it instead of choosing between free and blocked.

- [Cloudflare Blog: Wallets for agents](https://blog.cloudflare.com/wallets/)

## Google lowers Search Profile follower thresholds across all four platforms

Status: Confirmed  |  Topics: organic-search-core

Google lowered the minimum follower count required to create a Search Profile on every supported platform: from 100,000 to 35,000 on YouTube, Instagram, and X, and from 300,000 to 100,000 on TikTok. Google updated its help documentation with the new figures, and Search product lead Robby Stein confirmed the change on X, adding that profiles will expand to more countries soon. Search Profiles are currently available only in the United States.

In plain terms: A Search Profile is a shareable page Google can attach to your name in search results, pulling together your content from YouTube, Instagram, X, and TikTok in one place. The bar to qualify just dropped everywhere: YouTube, Instagram, and X went from 100,000 followers down to 35,000, and TikTok went from 300,000 down to 100,000.

Why it matters: A lower bar means mid-tier creators and smaller publishers can now claim a Search Profile, the dedicated space Google surfaces alongside knowledge panels and Discover results for verified sources.

Our take: The threshold cut plus Stein's note about expanding to more countries points at Google building out Search Profiles as a broader identity layer for search, worth setting up now for any creator or brand account that just crossed 35,000 followers on YouTube, Instagram, or X, or 100,000 on TikTok.

- [Google Search Help: Create a new Search profile](https://support.google.com/websearch/answer/16904498?hl=en)
- [Android Authority: You may now qualify for Google's new Search profile, here's how to check](https://www.androidauthority.com/google-search-profile-lower-requirements-3698116/)

## ChatGPT moves its source-visibility button behind an extra click

Status: Observed  |  Topics: chatgpt-assistants

SEO practitioner Glenn Gabe reported that ChatGPT is testing a change that moves the Sources button out of a response's visible footer and into the three-dot More actions overflow menu, requiring an extra click to reach the citation panel. OpenAI hasn't announced or confirmed the change, and Gabe's own screenshots show both the old and the new placement, suggesting a partial rollout rather than a platform-wide flip.

In plain terms: The Sources button is what lets someone reading a ChatGPT answer see and click through to the web pages it cited. Moving it inside a hidden menu means fewer people will bother clicking, even though the citations are technically still there.

Why it matters: Burying the sources button behind an extra click will suppress click-through to cited pages precisely when publishers are already fighting to prove AI referral traffic exists at all.

Our take: I've written about ChatGPT's source-selection mechanics living in an editable, server-side policy OpenAI can change without announcing anything. This is that same instability showing up in the UI layer instead of the retrieval layer, a citation surface a publisher's traffic depends on, moved without a changelog entry.

- [Search Engine Roundtable: OpenAI Makes The ChatGPT Sources Less Visible (spotted by Glenn Gabe)](https://www.seroundtable.com/openai-chatgpt-sources-less-visible-41864.html)