<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>戯言手帳</title>
    <link>https://learyliang.com/</link>
    <description>Recent content on 戯言手帳</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 08 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://learyliang.com/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Let AI Directly Operate Your Google Ads and GSC</title>
      <link>https://learyliang.com/post/openclaw-your-gsc-and-ads/</link>
      <pubDate>Fri, 08 May 2026 00:00:00 +0000</pubDate>
      <guid>https://learyliang.com/post/openclaw-your-gsc-and-ads/</guid>
      <description>&lt;p&gt;The idea is simple: connect your AI agent directly to Google Ads and Search Console via API, enabling fully automated data queries, analysis, and bulk operations.&lt;/p&gt;&#xA;&lt;p&gt;Not the &amp;ldquo;screenshot it and ask GPT to guess&amp;rdquo; approach. The AI holds your credentials and calls the API directly — query anything, modify anything.&lt;/p&gt;&#xA;&lt;p&gt;Total setup time: about 30 minutes. Here&amp;rsquo;s the full walkthrough.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-you-can-do-after-setup&#34;&gt;What You Can Do After Setup&lt;/h2&gt;&#xA;&lt;h3 id=&#34;google-ads-api&#34;&gt;Google Ads API&lt;/h3&gt;&#xA;&lt;h4 id=&#34;data-queries&#34;&gt;Data Queries&lt;/h4&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Pull ad data across any time range and dimension (campaigns/ad groups/keywords/search terms/geo/device)&lt;/li&gt;&#xA;&lt;li&gt;Never manually export CSVs from the dashboard again&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h4 id=&#34;bulk-operations&#34;&gt;Bulk Operations&lt;/h4&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Add 50 negative keywords, change bidding strategies, adjust budgets, create campaigns — all in one go&lt;/li&gt;&#xA;&lt;li&gt;What takes 30 minutes of clicking in the UI, the API does in one second&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h4 id=&#34;diagnostics--optimization&#34;&gt;Diagnostics &amp;amp; Optimization&lt;/h4&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;AI analyzes complete data: detects self-competition, pinpoints budget waste, surfaces high-performing keywords&lt;/li&gt;&#xA;&lt;li&gt;Generates data-backed weekly reports and optimization recommendations&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;gsc-api&#34;&gt;GSC API&lt;/h3&gt;&#xA;&lt;h4 id=&#34;search-performance&#34;&gt;Search Performance&lt;/h4&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Analyze organic traffic by keyword/page/country/device&lt;/li&gt;&#xA;&lt;li&gt;Find keywords ranking 5-15 to push to page one&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h4 id=&#34;index-management&#34;&gt;Index Management&lt;/h4&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Bulk submit URLs, manage Sitemaps, check indexing status&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h4 id=&#34;seo--sem-synergy&#34;&gt;SEO + SEM Synergy&lt;/h4&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Cross-analyze organic and paid search data to find overlaps and complementary opportunities&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;api-access-levels-important&#34;&gt;API Access Levels (Important)&lt;/h2&gt;&#xA;&lt;p&gt;Google Ads API has three tiers that determine what you can do:&lt;/p&gt;</description>
    </item>
    <item>
      <title>When the Crawlers Stop Playing Nice: Surviving Aggressive Bot Traffic in 2025</title>
      <link>https://learyliang.com/post/there-are-no-good-robots-anymore/</link>
      <pubDate>Sat, 11 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://learyliang.com/post/there-are-no-good-robots-anymore/</guid>
      <description>&lt;h3 id=&#34;background&#34;&gt;Background&lt;/h3&gt;&#xA;&lt;p&gt;I work on SEO and SEM for a large-scale content platform. In August 2025, a newly launched section of our site began experiencing something unusual—massive, abnormal crawling traffic.&lt;/p&gt;&#xA;&lt;p&gt;This wasn’t a small system. The section exposed &lt;strong&gt;over 6 billion accessible URLs&lt;/strong&gt;, designed to scale far beyond typical workloads. But within two months, traffic surged past expected limits. By November, the system began to &lt;strong&gt;crash frequently under extreme load&lt;/strong&gt;, and it became clear: something was very wrong.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
