seo. 37 essays.

Google's site reputation manual actions now behave differently inside the EEA, Next.js ends a six-day AVIF optimization outage, and a major crawler starts honoring Content Signals.

Two Google changes landed on August 28 and took effect August 30. Plus the redirect rollout that quietly repriced every rank-tracking query you pay for.

Saturday brought no new announcements. What lands today is the enforcement change Google scheduled two days ago: one URL can now hold two ranking positions depending on where the query starts.

Google says AI Overviews now open fully on some queries with no Show more click. Plus a ReDoS in the Protego robots.txt parser and Cloudflare's new bot operator registry.

Google will stop applying site reputation manual actions to EEA searchers on August 30, and two unauthenticated Next.js RCEs need a same-day deploy.

The critical AVIF flaw that forced Next.js to switch off image optimization now has an upstream patch, and it has already reached sharp. Google's ranking surfaces stayed quiet.

Next.js closed two critical remote code execution flaws, one of them in the image pipeline behind your largest paint. Google repeated that AI answers need no separate playbook.

A quiet day on the ranking side. The moves that matter sit in infrastructure and distribution: your CDN can now edit robots.txt for you, and Top Stories has a reader-facing opt-in button.

The August 2026 Google spam update wrapped early Friday. On the same day, Vercel and Cloudflare rolled soft-navigation SPA measurement into their real-user monitoring.

Two changes worth acting on: a reader-facing button that boosts Top Stories and AI Mode placement, and a CDN toggle that can rewrite your robots.txt without a deploy.

OpenAI switches ChatGPT Ads on across Europe next week, a 41-day study shows AI bots skipping JavaScript links, and Astro patches a silent canonical URL bug.

Google confirmed its third spam update of the year at 16:27 UTC yesterday. It is global, all languages, and lands while Search Console's AI and Discover reporting is already miscounting.

Google's product feed API goes dark today. Alongside it: an open logging bug hiding AI impressions in Search Console, and a WordPress RCE record that went public overnight.

A quiet 72-hour window at Google. What actually moved: a canary-only image cache guard, a metadata pipeline mid-rebuild, and an advisory worth checking your Nuxt version against.

A quiet weekend window with one real bug: several onINP() calls on a page were erasing each other's counters. Plus the AI fetcher your robots.txt does not govern.

Google's ranking surfaces logged nothing again. The movement was at the edge: a Cloudflare toggle that can put a login screen in front of Googlebot, and a quiet OpenAI crawler IP refresh.

Google's ranking surfaces logged nothing. The movement was Next.js 16.3.1 walking back yesterday's metadata regression, plus a Clarity report scoring AI crawlers on the visits they return.

Both tracks moved. Stable Next.js hands metadata a detached view of request headers, SvelteKit 3 relocates remote-function imports, and Merchant Center is about to restate organic traffic.

Both tracks moved. A live Next.js routing defect loops prefetches against your own origin, Astro ships a stable CSP fix for prerendering, and Google's AI report is less rolled out than reported.

Anthropic will mark supported Claude output with invisible text watermarks and signed C2PA provenance metadata. Here is how the two systems work, what detection actually proves, and what developers and publishers must prepare for.

One track empty, one active: Google logged no ranking or documentation change today, while SvelteKit 3 and a Next.js canary shipped verified routing and build-level updates.

A quiet 72-hour weekend window. Google's ranking surfaces logged nothing, but its generative-AI guidance and an approaching Cloudflare bot deadline both need attention this week.

Four quiet days at Google. The verified movement is a Next.js documentation fix that decides whether your exported feed builds at all, plus a relocated OpenAI crawler policy page.

Google's ranking and policy surfaces stayed silent a second day. The movement was all in the stack: a SvelteKit 3 prerelease wave, two Next.js fixes, and a Cloudflare bot reclassification.

Google's ranking systems stayed still for another day. The real work today is patching: WordPress 7.0.3, a nine-advisory Craft CMS batch, and a Markdown parser DoS.

A quiet day at Google, a busy one everywhere else: topic-level AI visibility data for editors, plus three engineering deadlines that land before the end of August.

A managed WAF rule can now block your own image proxy without a deploy, while Google's ranking systems stayed silent for a second straight day.

Google's ranking surfaces stayed quiet for a second day. The movement came from tooling: a stable Next.js minor and a new brand-level cut of AI citation data.

Three days without a Google announcement. The verified movement is all in the toolchain: two Next.js canaries touching not-found routes, and a WPGraphQL enumeration flaw that still has no patch.

Quiet day on Google's ranking surfaces, loud one everywhere else: an undocumented boundary in the AI opt-out control, and a stored XSS in an SEO package.

A rare empty day on the editorial side: no Google announcement, no dashboard entry, no docs revision. The only verified shipping happened in the toolchain.

Google's ranking systems stayed quiet all month. Today's movement is elsewhere: new research on how AI models pick which brands to search, and a Vercel header change that exposes backend timings.

Google opened platform properties to everyone and shipped a guide for reading social and video performance. On the build side, bot rendering and header parsing both needed fixes.

Google logged nothing in the last 24 hours. The real movement was in the build layer: Next.js and Astro both shipped changes that decide what Googlebot actually receives.

Google Search Console misreported impression data since May 13, 2025 due to a logging error. The fix will roll out over the coming weeks, causing reported impressions to decrease.

Introducing Cloudflare's new /crawl endpoint that automatically discovers, renders, and returns entire website content in multiple formats with respect for robots.txt directives.