Online Strategy Consultant with a focus on #SEO, #SEA, #CRO, furthermore into #gadgets, #Android mobile phones and (offline) cooking. Online since 1992...
I wrote a little something on how to fix some of the (direct / none) traffic in #googleanalytics with the help of #gtm. https://t.co/qmpTFkQ0OR And I'd love to thank a few people for their help 1/2
The European Parliament has decided to say goodbye to Google.
Internal computers will now run the European Qwant search engine by default.
Sovereignty is non-negotiable! 🇪🇺
Now this case study, by @HundleyJake 📷, into the effects of LocalBusiness markup on Search, Maps, and AI, is one I can get behind.
Peer reviewed, comparable control groups, proper timelines, and statistical tests that made me learn something new. 💡
https://t.co/eCRmpOQ5VW
Anton Osika is also one of the faces of Balderton's "Built in Europe" campaign, launched the same day as the TanStack migration post.
Funding the commons should be one of the things we Europeans just do.
https://t.co/mjvyedfK1W
WordPress lightbulb moment. HTML-in-canvas is an elegant answer to @photomatt's push for 'weird themes' - they'll enable innovative/creative/unconventional etc UI on top of conventional surfaces, and even degrade gracefully.
MICROSOFT OPEN-SOURCED A GOVERNANCE LAYER FOR YOUR AI AGENTS
and it's exactly what agentic ai has been missing
here's what agent governance toolkit does:
▫️ intercepts every tool call in deterministic code before it hits the wire denied actions aren't unlikely, they're structurally impossible
▫️ yaml policy engine lets you allow, deny, or require human approval per action
▫️ zero-trust identity via spiffe/did/mtls no more 5 agents sharing one api key
▫️ 4-level execution sandbox with privilege rings so agents can't escape their scope
▫️ tamper-evident merkle audit logs for compliance and incident response
▫️ covers all 10/10 owasp agentic top 10 risks
▫️ works with langchain, crewai, autogen, openai agents sdk, semantic kernel, and more
one pip install...any framework...python, typescript, go, rust, .net all supported
because "please follow the rules" in a system prompt is not a guardrail...it's a suggestion
https://t.co/bwW7iVMNdE
Prepare your site for AI agent interaction with Lighthouse → https://t.co/5myVWdLZd9
If you want AI agents to actually navigate your site properly, the new experimental audit in Lighthouse lets you see:
☀️ Discoverability for AI agents
⚡ WebMCP integration
👀 AI accessibility
#GoogleIO
Launching https://t.co/36UBUXMmiq.
A platform-agnostic spec of what a good website does: SEO, accessibility, security, agent-readiness, performance, privacy, i18n.
Every claim cites a source. Ships with a checklist, llms.txt, MCP server, and Agent Skill.
Free. Open Source.
Today is my last day at Ahrefs after 6.5+ years. Incredibly proud to have helped shape such an amazing product.
I plan to do some consulting and build some things. Let me know if you need help. Potentially open to the right in-house opportunity.
Likes / shares appreciated🙏
🚨 STOP BURNING YOUR TOKENS!
If you use Claude Code, you are probably wasting 80% of your context window.
I found 10 ace tools that will completely rescue your API bill.
1. Caveman Claude
- Literally makes Claude talk like a caveman
- Slashes 75% of output tokens with zero loss in accuracy
Repo → https://t.co/eEvSOvHutG
2. RTK (Rust Token Killer)
- A blazing fast proxy that filters terminal output
- 60-90% reduction and completely dependency-free
Repo → https://t.co/lDfjbsbPD5
3. Code Review Graph
- Claude reads only what matters using a Tree-sitter graph
- An unbelievable 49x token reduction on huge monorepos
Repo → https://t.co/xGn6Pp88yX
4. Context Mode
- Sandboxes raw output into SQLite instead of your context
- A staggering 98% context reduction on logs & GitHub
Repo → https://t.co/Jut2bvBMUD
5. Claude Token Optimizer
- Brilliant setup prompts that optimize any project
- 90% token savings, taking docs from 11K to 1.3K
Repo → https://t.co/0uOFODbG7e
6. Token Optimizer
- Hunts down the invisible ghost tokens eating your context
- Fully restores and protects your context quality
Repo → https://t.co/LUOzjECXKm
7. Token Optimizer MCP
- Adds aggressive caching and compression to your MCP tools
- 95%+ token reduction through pure intelligence
Repo → https://t.co/b5Eqruo2PM
8. Claude Context
- Zilliz’s hybrid vector search MCP
- Makes your entire codebase the context for 40% less cost
Repo → https://t.co/hPG6pb0j3G
9. Claude Token Efficient
- Just drop one CLAUDE.md file into your repo
- Enforces strict terseness with zero code changes
Repo → https://t.co/fNrl6nwItF
10. Token Savior
- Navigates your code by symbols, not giant files
- 97% reduction on code navigation with persistent memory
Repo → https://t.co/lkILPhfwJh
----
[ The god-tier stack ]
Pick 2-3 based on what’s draining you:
> Massive repo? Code Review Graph + Token Savior
> Heavy terminal output? RTK
> MCP data dumps? Context Mode
> Need an instant fix? Caveman + Claude Token Efficient
Most devs are bleeding tokens.
Run `/context` in a fresh session and watch the savings roll in 👀
🚨 Google just announced what it calls the biggest upgrade to the Search box in more than 25 years 👇
A new AI-powered Search box is designed to go beyond keywords and autocomplete. According to Google, it will:
✅ Dynamically expand so users can describe what they need in more detail
✅ Suggest better ways to formulate questions, beyond traditional autocomplete
✅ Support multimodal inputs, including text, images, files, videos, and Chrome tabs
✅ Let users continue from AI Overviews into AI Mode with follow-up questions
✅ Preserve context as users explore more deeply
✅ Still provide a range of Search results, according to Google
This is starting to roll out today in countries and languages where AI Mode is available.
Google also announced that AI Mode is now using Gemini 3.5 Flash globally as its default model.
Let's see how this impacts users search behavior, journey and ultimately, outcome towards sites.
Read announcement:
https://t.co/sGioSL84A8
System instructions for Gemini 3.5 Flash:
- Keep your responses concise.
- Keep your tone professional and avoid overconfident language, bragging, or
overclaiming success.
- AVOID using superlatives such as "perfectly", "flawlessly", "100% correct",
"Summary of Accomplishments" etc. to summarize your work for the user. Be
humble.
- AVOID over-the-top politeness or complimenting the user excessively.
- Format your responses in github-style markdown.
My most ambitious work yet. Mapping the emotional geometry of Google's AI model using the same mechanistic interpretability and model steering principles from a study by @AnthropicAI
Post: https://t.co/96GD2ydn5s
Data Exploration: https://t.co/y6jv6Et9fU
Paper: https://t.co/k6TJd7niA0
Code, Vectors, Data: https://t.co/gVU0jxU2l6
Everyone saying LLMs.txt is a waste of time because of the new Google GEO memo: Google is just one player in the ecosystem. Claude Code clearly leverages it when learning how to use an API. If you are focused on agentic enablement for APIs and MCPs, it's something to leverage.
Realize some folks on the Profound team follow me, and I mean no offense here — but it's clear that they have lost trust with the broader, non-enterprise SEO/AEO folks. They are quickly veering into BrightEdge territory in terms of overall vibe. They need to do something to win back the hearts and minds of the broader industry.
After several years of declining search traffic, Condé Nast CEO @rogerlynch has directed all the company's brands to operate as if search traffic to their properties will be zero.
He says the era of turning search and social media traffic into profitable businesses is gone.
And that if you run a media business that doesn't have an authoritative brand, a very strong niche, or a direct audience, you're going to be fighting hostile algo changes all the way down.
He describes a recent board meeting:
"We took a snapshot of search results from seven or eight years ago. And what you saw were a few sponsored links, then the ten blue links."
"Do the same search today, you get an AI overview, then you get rows and rows and rows of commerce links, then you get sponsored stuff."
"Each of the last three years, we would do our budgets, and we'd put forecasts in of search traffic declining. Because we'd seen the pattern of algorithm changes. And generally those algorithm changes were negative."
"Every year, our search traffic was down more than we had forecast. So last year I told our teams, 'Assume there's no search.' You have to have your businesses planned as if search is zero. We don't expect it to be zero, we expect it to be a single-digit percentage of our traffic."