Posts

Search Console: When sitemap index shows 0

Image
I spend a lot of time digging into technical glitches, often running automation scripts on my Mac mini to isolate points of failure. Recently, I encountered a confusing issue in Google Search Console where my sitemap status seemed inaccurate, leading me down a rabbit hole of checking HTML sources and API responses. Why does the sitemap screen show 0 indexed pages? For several weeks, my sitemaps screen displayed "Submitted: 52" and "Indexed: 0". I had submitted both sitemap.xml and the Tistory-generated rss feed, and both were marked as "Success". It felt like something was broken; I started questioning if my google-site-verification code was missing or if the URLs were incorrect. To verify, I used the Search Console API to run sitemaps().list() . The results showed 55 items for sitemap.xml and 11 for rss , both returning HTTP 200 status codes. In my automation scripts, a 200 OK signal indicates the process should move to the next step, so technica...
Post a Comment
Read more

Claude Code: Analyzing 159 Feedback Memory Files

Image
Symptom / Cause / Fix Repeated mistakes despite automatic memory / Claude reads only the one-line index summary at session start, not the full body / Include the "Why" directly in the one-line summary. I've been using Claude Code across my work laptop and home Mac mini for about 15 months. Claude Code includes an automatic memory feature: whenever I correct the AI, it creates a feedback file. Each file contains a one-line explanation of "why" the correction happened and "how" to apply it next time. While migrating these files from my work laptop, I realized I had accumulated 159 of them—meaning I've had to correct Claude 159 times. Reviewing the files labeled as "reoccurred twice," "strongly repeated correction," or "repeated thinking error," I found that the issues fall into five distinct patterns. Interestingly, none of these concern specific code syntax; they are all about the workflow. 1. Solving in fragments...
Post a Comment
Read more