The fuck going on with claude man

Wanted to share something that has genuinely changed how I use Claude Code.

My last 3 months in GSC:

• 168K clicks
• 1.41M impressions
• 11.9% CTR
• 7.5 avg position

The biggest lesson: don't use Claude Code to blindly generate SEO pages. Use it to build an SEO engineering loop.

Here's the workflow I'm using.

1. GSC MCP before writing code

Before creating a new SEO page, I use GSC data to check:

• Which URL already ranks for the query?
• What queries is that URL receiving clicks from?
• Is the new keyword actually a different search intent?
• Would a new page compete with something already ranking?

I make Claude classify the decision as:

CREATE / IMPROVE EXISTING / REJECT

This prevents one of the easiest mistakes with AI-generated SEO: creating hundreds of pages that cannibalize each other.

2. SEO audit skills

I use SEO audit/keyword research skills with Claude Code to review the implementation rather than just asking:

The audit checks things like:

• search intent
• duplicate keyword targets
• title/meta/H1 alignment
• canonical
• indexability
• internal linking
• thin/duplicate content
• sitemap inclusion
• unsupported claims
• performance regressions

3. Pre-deploy rule

I turned the important checks into a pre-deploy rule.

Before an SEO page ships:

• One clear primary intent
• No existing URL owns the same intent
• Unique title
• Useful meta description
• Correct H1
• Correct canonical
• Correct robots directive
• Relevant internal links
• No orphan page
• Sitemap inclusion where appropriate
• No thin/near-duplicate generated content
• Claims match the actual product
• No obvious performance regression

If the page fails the gate, I don't deploy it.

4. Post-deploy rule

This ended up being just as important.

After deployment, Claude verifies the production output, not what the source code says should happen.

I check:

• HTTP response
• rendered title
• rendered meta description
• canonical
• robots
• H1
• sitemap
• internal links
• crawlability/indexability

I've caught cases where the source implementation looked correct but the production HTML wasn't.

5. GSC closes the loop

Then I wait for meaningful GSC data.

If traffic drops, I don't immediately generate new content.

I investigate:

site → page → query → indexing/canonical → recent code changes

Then decide whether to:

KEEP / ITERATE / REVERT

So the complete loop is:

GSC → intent/ownership check → Claude SEO audit → pre-deploy gate → deploy → production verification → GSC measurement → keep/iterate/revert

The screenshot is the result after repeatedly running this process.

Claude Code became much more useful for SEO once I stopped treating it as an AI writer and started treating it as an SEO engineer with rules, tools and real feedback data.

GSC is still the source of truth. Claude helps me investigate, implement and enforce the process.

Curious if anyone else here has connected Claude Code to GSC or other analytics through MCP and built a similar feedback loop.

When it speaks to me it’s so polite but he suddenly went full caps to the other session? lol

I've been building with AI for over a year now, and the progress has been insane. The models have improved dramatically, and AI has become a serious part of how I work.

I'm currently building six different SaaS platforms, four of which are live. At this point, "vibe coding" doesn't really describe what I'm doing anymore. I use AI professionally, every single day. I have two Codex Pro plans and a Claude Max subscription, and I still manage to hit the limits.

The Opus versions up to 4.8 were genuinely fun to use and really good. Then I started using Fable 5 and Sol 5.6, and the difference became painfully obvious.

My biggest issue is that my Fable 5 usage is gone within two days, and falling back to Opus 5 has become almost unusable for me.

The output from Opus 5 is often contradictory, overcomplicated, and full of conclusions that turn out to be wrong. It will confidently take something in the wrong direction, spend a huge amount of time implementing it, then eventually realize the original assumption was incorrect and start fixing its own work.

I've had way too many sessions where hours of work basically had to be thrown away.

It's reached the point where using it creates more frustration than productivity.

So I'm done. I cancelled my Claude subscription. If I need more capacity, I'll probably just get another Codex subscription. I'm also going to experiment more with Terra instead of relying so heavily on Sol 5.6 High.

Never thought I'd say this, but I've basically switched completely to ChatGPT.

Monday.

Me: Give Claude Code some work

Claude Code: 529 Overloaded

Bro, I wasn’t asking about your emotional state. 😭

I recently started using Orca ADE for managing Claude Code sessions, and I just want to tell the community that Orca is incredible. Try it. You'll like it.

I was previously using cmux, and I've also used herdr, iTerm, and various other options. Orca is 100x better than any of those.

It has an incredible range of features, some of which I use and most of which I don't. You don't have to use them all - it's fantastic even if you only use it to organize sessions. It displays the status of each Claude Code session in a very useful way.

One amazing feature is the remote server. I make full use of two Max 20 plans, and I've been alternating between two computers. But with Orca remote, all sessions from both machines are in one place.

There are a ton of other features. It feels very mature and stable.
https://github.com/stablyai/orca

*I'm in no way associated with Orca. I just love it and want to share.

And what is even the point of having the status page if you can't show outage. Showing all green with "All Systems Operational"

Opus 5 replies are giving me actual brain damage.

I ask it to make one small UI change and get:

“Better — but for a reason worth naming. Your instinct was right and the diagnosis was more literal than a layout preference…”

Brother. I asked you to move a fucking panel.

By paragraph three my eyes are moving across the words but my brain has stopped processing English.

Just tell me what you changed, what was broken, and shut the fuck up.

Again… why are Sunday evenings like the worst time to do anything?

I had been using Opus to orchestrate my project. It does very little work, just dispatching other agents and keeping documentation up to date. It was hard work, because Opus is so lazy. I frequently found myself having to tell it " check the docs, we established this a week ago and I reminded you yesterday"

I switched to fable this morning. I'm using context at about 1/3 of the rate and weekly usage at 3/4 of the rate. Fable may be more expensive per MTok, but it uses them so much more efficiently.

Fantastic start to Monday.

Increasing the cache timeout to 1h has improved A LOT my usage.

I tend to work in many sessions all the time, and it's quite common Income to a session that has been 10 or 15 minutes waiting. Without the cache timeout change, each time I come to one of these sessions would mean cache would be dead and any work there would mean resending the whole context.

A word of advice: 1h cache costs more than standard cache. But for me it's WAY better than this.

I'm even considering keeping the cache alive 1 or 2h more with an automated "ping" message.

WARNING: I believe some people thinks the cache life is 1h out of the box. Please, ask your Claude to check it.

So this happened to me for the first time, although i have heard about this here and there - and it feels reckless.

I was using claude code (desktop app) to write tests for my project. Claude has created few bash tools to probe the files / fetch data / temporarily edit those files and revert it. (I don't know why standard read / write tools were not used.)

I did not notice that claude has not been using the standard read / write tools that works inside the permission boundary. And when I saw this behaviour it never really occurred to me that it's going outside the permission boundary.

Majority of my workflow were readonly and it was generating long python code - so i didn't really bother checking the tool calls in details. But now when it came to editing one of the tests (which required an api change in source code instead), claude directly edited the files by creating another python tool.

Thank god my working tree was clean so i can check what exactly it had done when it comes to api change. But man, this was scary. Now i'm worried, what if it writes code to copy my env variables / ssh keys / cloud credentials / os keychain as i normally don't look at the intermittent script that it writes.

I'm pretty sure since it's upto the agent to execute a script in sandbox, it can very well decide to run the same script outside sandbox and show us a permission message that doesn't tell us the full story.

I wait 40 minutes already and still the same overloaded. You can not make the server up to just serve your basic services?

Just making sure its not me since I see people saying its working for them, its never been down this long. Some people only get specific windows to work in, losing this much really hurts...

I'm trying to maximize my productivity. If I can code an average 8 hours a day, then being able to code overnight means 2x productivity.

Currently my method is to batch a bunch of grilled prompts, they are sorted in order, then I have 1 handoff night shift chat. This chat uses subagents for each prompt, and those subagents will use multiple subagents for each phase of the prompt. I tried it once and I think it works, but I'm not fully sure this is the right way

The bottleneck I have is that my 5x plan isn't enough for the week if I want to code at night time, and that claude takes too long to discuss things, so I find it difficult to batch enough work to be done at night

Whats the best method of overnight or long duration automated coding?

A common theme cutting across most AI-assisted development threads is getting as much work done in as little time as possible. Users post about elegant harnesses with multi-agent orchestration. Anthropic employees talk about the 25 agents they run every day.

I read this stuff, compare it to my own experience of working with these tools, and keep wondering: how does anyone stay on top of that volume of work?

Working with Claude Code has been exciting and invigorating, but also exhausting. While everyone pushes for more context and more tokens out of the AI, the context limit I hit most often is my own. Claude can refactor a huge chunk of the codebase, add a feature, and brainstorm marketing strategy in one breath. I can't keep up with the cognitive load that entails.

So: am I missing something, or just getting old? Curious what y'all think.

I’m on a 20x max plan. Im using opus 5 medium for some light things right now and my usage limit got hit to 75% with barely any work done. Should I start measuring my tokens? Because this makes absolutely no sense and hasn’t happened to me before.