1. GA through 6 Sep
Closed. Do not pull 6 Sep. That day will look thin. I already have GA through 5 Sep 2026.
Scalekit traffic · 29 Jun 2026 to 5 Sep 2026
PostHog says traffic dropped. I am checking if that is real demand, or bots and measurement.
No. We did not lose real people.
Real users held or grew the whole time. What left was automated traffic from Singapore, China and Hong Kong. Search clicks barely moved. Three numbers carry the answer, all measured per day so the short 6-day window compares fairly.
It was not one drop. It was 6 separate events stacked. Five are anomalies I ignore for demand. One is a possible trend worth watching, and it is small. Two still need a "did we cause this?" check. The action list sits at the bottom of this page.
scalekit.com is the marketing site. I used to write www. That meant the same host.
docs.scalekit.com is the docs site.
SG is Singapore. CN is China. HK is Hong Kong. LLM agent bots hit us from those countries through proxies.
uniqExact counts each person once, with no estimating. session_start is GA's real session count. I avoided the per-page session column because it counts one visit once per page.| Slice | 29 Jun–5 Jul | 6–12 Jul | 24–30 Aug | 31 Aug–5 Sep | Change |
|---|---|---|---|---|---|
| scalekit.com · real | 208.6 | 229.6 | 235.4 | 270.2 | +30% |
| scalekit.com · bots | 78.9 | 14.9 | 13.1 | 14.8 | −81% |
| docs.scalekit.com · real | 58.9 | 44.7 | 53.7 | 53.7 | −9% |
| docs.scalekit.com · bots | 234.1 | 174.0 | 25.1 | 38.8 | −83% |
Bots fell 81% on scalekit.com and 83% on docs. Real users per day on scalekit.com went up 30% over the same 10 weeks. Docs real users dipped in the 6 Jul week, then came back. Search clicks per day fell 3%. That is the whole story in one table.
| Host | PH users | PH sessions | GA sessions | Same direction? |
|---|---|---|---|---|
| scalekit.com | 3,097 → 2,744 (−11%) | 3,454 → 3,165 (−8%) | 3,697 → 3,379 (−9%) | Yes, but see mix below |
| docs.scalekit.com | 2,264 → 1,700 (−25%) | 2,421 → 1,848 (−24%) | 1,059 → 1,124 (+6%) | No |
docs.scalekit.com: PostHog users −25%. GA sessions +6%. That is not real demand dying. I think this is bots in PostHog, or mix.
| docs.scalekit.com | 29 Jun–5 Jul | 6–12 Jul | Change |
|---|---|---|---|
| PostHog users | 2,264 | 1,700 | −25% |
| PostHog sessions | 2,421 | 1,848 | −24% |
| Sessions per user | 1.07 | 1.09 | flat |
Both fell by the same amount, so sessions per user did not change. Whatever left was visiting once and leaving, at the same rate before and after. That is the shape of a bot, not of a reader who lingers.
| Slice | 29 Jun–5 Jul | 6–12 Jul | Change |
|---|---|---|---|
| Singapore | 531 | 84 | −447 |
| United States | 1,026 | 1,101 | +75 |
| India | 435 | 507 | +72 |
Singapore / China / Hong Kong · 505 users on 29 Jun, then ~5–30/dayUS + India held
Daily cut agrees. 505 of those users sit on 29 Jun. Singapore / China / Hong Kong is where LLM agent bots run (proxies). I ignore this for demand.
| Slice | 29 Jun week | 6 Jul week |
|---|---|---|
| Hong Kong | 836 | 516 |
| China | 641 | 452 |
| Singapore | 162 | 250 |
| United States | 260 | 186 |
| India | 154 | 128 |
| GA sessions | 1,059 | 1,124 |
Singapore / China / Hong Kong · 404 → 72 on 8–9 JulUS + India · 69 → 79 that same day
One segment fell (404 to 72). US + India that day went 69 to 79. GA sessions went up that week. Singapore / China / Hong Kong is LLM agent bots on proxies. I ignore this for demand.
| Page | 29 Jun–5 Jul | 6–12 Jul | Change | Share of week 1 |
|---|---|---|---|---|
| /agentkit/quickstart/ | 158 | 77 | −81 | 15% |
| / (home) | 118 | 112 | −6 | 11% |
| /authenticate/fsa/quickstart/ | 62 | 51 | −11 | 6% |
| /authenticate/mcp/intro-to-mcp-auth/ | 25 | 13 | −12 | 2% |
| /cookbooks/java-spring-boot-jwt-timeout/ | 21 | 33 | +12 | 2% |
| /authenticate/mcp/quickstart/ | 17 | 26 | +9 | 2% |
322 docs pages had a session that first week. The top 10% is 32 pages. /agentkit/quickstart/ is the one that dropped. Home held. Site total still went up.
| Week | scalekit.com clicks | scalekit.com impressions | docs clicks | docs impressions |
|---|---|---|---|---|
| 29 Jun–5 Jul | 1,576 | 601,664 | 75 | 18,655 |
| 6–12 Jul | 1,585 | 580,760 | 69 | 15,947 |
| 24–30 Aug | 1,535 | 431,772 | 62 | 12,723 |
| 31 Aug–5 Sep | 1,272 | 390,019 | 62 | 17,074 |
| Ahrefs day | Keywords 1–3 | Top 10 | All keywords |
|---|---|---|---|
| 5 Jul 2026 | 214 | 423 | 466 |
| 30 Aug 2026 | 181 | 411 | 448 |
I already have the GSC queries file. It ends 5 Sep. That is the minus-2 cut. Ahrefs is not a mass deindex. Keywords in 1-3 went 214 to 181. Top 10 only went 423 to 411. I still will not name a reverse.
| Measure | 29 Jun–5 Jul | 24–30 Aug | Change |
|---|---|---|---|
| Impressions on named queries | 192,619 | 227,835 | +18% |
| Distinct named queries | 12,561 | 13,815 | +10% |
| Total property impressions | 601,664 | 431,772 | −28% |
| Clicks per day | 225.1 | 219.3 | −3% |
Read those four rows together. Named queries grew and carried more impressions. The property total still fell. So the loss sits in queries Google will not name, which is the anonymous long tail. I did not lose ranked search demand.
Two queries carried 61,310 impressions in the 29 Jun week at position 2.5 and 2.9. Between them they produced 1 click. At that position a real audience gives 10% or more.
| Query | Impr 29 Jun | Impr 24 Aug | Position | Clicks |
|---|---|---|---|---|
| sso idp | 32,270 | 24,595 | 2.5 → 4.9 | 1 → 0 |
| sso idp vs sp | 29,040 | 25,192 | 2.9 → 2.8 | 0 → 0 |
Of the top 200 losing queries, 121 vanished to zero, 50 kept a worse position, and 29 lost impressions without losing rank. Mostly long-tail churn.
The query scalekit went 265 clicks to 186, down 30%, while my position improved from 3.5 to 1.9. Better rank, fewer clicks. That is not SEO. Fewer people search my name. Different problem, different owner.
That window has 6 days, not 7. Per day it goes the other way. This supports not calling it a trend.
| Per day | 24–30 Aug | 31 Aug–5 Sep | Change |
|---|---|---|---|
| scalekit.com impressions | 61,682 | 65,003 | +5% |
| scalekit.com clicks | 219.3 | 212.0 | −3% |
| docs impressions | 1,818 | 2,846 | +57% |
Still worth doing: positions 1-3 went 214 to 181 while 4-10 went 209 to 230. About 33 keywords slipped one tier. Total keywords held, 466 to 448, so nothing was deindexed. That is reversible with normal content and link work. It cost almost no clicks, so it is not urgent. I still will not name AI Overviews as the cause. Search Console gives web, image and news only. There is no generative column.
| GA docs week | Sessions | Change |
|---|---|---|
| 27 Jul | 1,478 | — |
| 3 Aug | 1,760 | +19% |
| 10 Aug | 841 | −52% |
| 17 Aug | 947 | +13% |
| 24 Aug | 862 | −9% |
| Test, 3 Aug → 10 Aug | Result |
|---|---|
| Pages that dropped | 546 of 699 |
| Median drop per page | −1 session |
| Pages losing 20 or more | 2 |
| Top 10 pages, share of the drop | 11.3% |
| Top 50 pages, share of the drop | 28.6% |
| Biggest single loss | /authenticate/mcp/quickstart/ −24 |
A bad deploy or a lost ranking concentrates in a few URLs. This is 78% of all pages each losing 1 or 2 sessions. That shape is a crawler leaving, not readers leaving. Compare 6 Jul, where /agentkit/quickstart/ alone was 15% of the week and took the whole hit. These two dips have opposite shapes.
| Host | PH users | PH sessions | GA sessions |
|---|---|---|---|
| scalekit.com | 2,783 → 2,566 (−8%) | 3,129 → 2,919 (−7%) | 3,810 → 3,589 (−6%) |
| docs.scalekit.com | 706 → 678 (−4%) | 812 → 759 (−7%) | 862 → 704 (−18%) |
| Host | Today | When added |
|---|---|---|
| scalekit.com | No Content-Signal. Only Disallow /authors/. | Not present. |
| docs.scalekit.com | Content-Signal: search=yes, ai-train=no, ai-input=yes |
20 Apr 2026. developer-docs #576. Bundled in an AgentKit docs PR. |
What it means: ask crawlers not to use docs to train models. Search indexing is still yes. Feeding docs into an answer at request time is still yes.
Should it be there? Common on docs sites. It is a preference, not a block. It does not stop Google Search. It was already there in April, so it did not cause the July drop.
| Date | What shipped |
|---|---|
| 13 Aug 2026 | Gemini 3.7 Flash |
| 19–28 Aug 2026 | Google AI Overviews: generative UI, then longer auto-expand |
| 1 Sep 2026 | Claude Fable 5.1 |
| 2 Sep 2026 | Gemini 3.8 Flash |
| 3 Sep 2026 | OpenAI GPT-6 Astra |
| Week | Sessions | Week | Sessions |
|---|---|---|---|
| 15 Jun | 35 | 27 Jul | 41 |
| 22 Jun | 41 | 3 Aug | 39 |
| 29 Jun | 41 | 10 Aug | 38 |
| 6 Jul | 45 | 17 Aug | 41 |
| 13 Jul | 22 | 24 Aug | 35 |
| 20 Jul | 28 | 31 Aug | 46 |
| Test | If models caused it | Actual |
|---|---|---|
| LLM referrals | Rise | Flat. Best week is 31 Aug. |
| Organic search sessions | Fall | Flat. 322 to 318 per day. |
| Named-query impressions | Fall | Up 18%. |
| Google clicks per day | Fall | −3%. |
| Timing of the 8–9 Jul cliff | On or after 13 Aug | 5 weeks earlier. |
The broad version of this angle is dead. New models did not take our readers. Five independent tests say so, and the July cliff predates every launch by 5 weeks.
A narrow version survives. The traffic that left executed JavaScript, because GA counted it, and it arrived as Direct from proxy countries. That is agent browsing, not Googlebot, because Googlebot does not create GA sessions. New models do change which agents run. I cannot tie that to any single launch date, so I am not calling it.
CDN or server logs. Netlify and Cloudflare logs carry the user agent string. GA and Search Console do not. Those logs would name agent traffic directly, and would settle this angle and the 8–9 Jul question in one pass. This is a better next input than anything else on my list.
| Item | Was | Should be |
|---|---|---|
| docs 24–30 Aug PostHog users | 707 | 706 |
| docs Google referrer, first week | 87 | 89 |
| app.eu week of 26 Jul | 607 → 8 | 607 → 169 → 10 |
The 706 matters only for method. uniqExact gives 706. count(DISTINCT) gives 707 because HogQL maps it to the approximate uniq(). The percentage does not change. The app.eu number was a 3-week slide, not one drop. Nothing here changes a single call on this board.
| Do this | Why | Owner |
|---|---|---|
| 1. Get Netlify or Cloudflare logs for 8 Jul to 16 Aug | These logs carry the user agent string. GA and Search Console do not. They would name the agent traffic directly, and they settle two open questions in one pass: what left on 8–9 Jul, and whether agent browsing changed in August. This is the highest-leverage input I have left. | Infra |
| 2. Pull the change log for 8–9 Jul | Bot traffic vanished overnight. If we shipped a WAF rule, a bot-fight setting, a geo block, or a PostHog snippet change that day, then we caused it and it is explained. If we shipped nothing, I close it as outside noise. | Infra |
| 3. Check index status on 3 blog URLs | zoominfo-mcp-vs-api, clickup-mcp-vs-api and asana-mcp-vs-api lost nearly all impressions in July. They return 200 today, so this is not an unpublish. I need Search Console index coverage to tell me if Google dropped them. |
Marketing |
| 4. Watch the rank tier for 2 more full weeks | Keywords in positions 1-3 went 214 to 181 while 4-10 went 209 to 230. About 33 keywords slipped one tier. It cost almost no clicks, so it is not urgent. Normal content and link work reverses it. | Marketing |
Not on this list: brand search. The query scalekit lost 30% of its clicks while my ranking improved. That is a demand and awareness question, not a traffic bug. It needs a different owner and a different conversation.
Closed. Do not pull 6 Sep. That day will look thin. I already have GA through 5 Sep 2026.
Closed. I already have gsc_site_queries.csv. It ends 5 Sep 2026. I used it for phrase moves. Page-level totals stay the impression number (602k to 390k).
Closed. Used scalekit.com-organic-keywords-history-subdoma_2026-09-07_17-53-10.csv. Keywords 1-3 went 214 to 181 (5 Jul to 30 Aug). Top 10 held 423 to 411. Not a mass deindex.
Closed. Those are the top locations where LLM agent bots run, on proxies. That locks ignore for demand.
Closed. I have the merges from scalekit-inc/developer-docs. I do not need anything else from that repo. I am not calling those merges the cliff.
Closed. Nope. They were not unpublished, redirected, or noindex in 29 Jun 2026 to 12 Jul 2026. They return 200 today.