Crawl budget: server logs vs. GSC Crawl Stats
This week on the radar — diagnosing why Google isn't recrawling fast enough after you fixed things.

🔗 [Server log analysis] — ground truth: every Googlebot hit, by URL, status, and time; nothing else shows actual crawl distribution.
🔗 [GSC Crawl Stats] — Google's own summary of requests, response times, and fetch purpose; easier, but aggregated and sampled.
🔗 [GSC URL Inspection 'last crawl'] — per-URL recrawl date when you need to confirm one important page got refreshed.

The tradeoff: Crawl Stats is fast and free but won't show you that 60% of crawl is being wasted on parameter URLs — logs will. On a large site recovering from an update, log analysis finds the crawl-budget leak; GSC only hints at it.

One to bookmark: a log-based 'crawl by directory' breakdown — it exposes where Googlebot is spending budget you'd rather it spent on money pages.

Internal linking: crawler graph vs. embedding suggester
Framing: post-update, redistributing internal links is a top lever — but the tool you use changes the recommendation.

🔗 [Crawler-based link graphs (Screaming Frog/Sitebulb)] — show real PageRank-style flow and orphan pages; structural, accurate, manual to act on.
🔗 [Embedding-based suggesters] — propose contextually relevant links by meaning; great for relevance, blind to crawl depth and authority flow.
🔗 [GSC + a custom 'pages with impressions but no internal links' join] — finds undersupported winners worth boosting.

The tradeoff: structural tools fix authority distribution; semantic tools fix topical relevance. The best internal links are both — relevant and from authoritative pages. Pick structural first when traffic concentrates on a few hubs; semantic first when content is broad and flat.

One to bookmark: an orphan-pages export crossed with impression data — it surfaces pages Google found anyway that you've never linked to.

ЕЮ Иванов продолжает кошмарить АффПапу, конторку, которая накинула говна на вентилятор этим летом. Тогда в AffPapa не знали, с каким говном идут бодаться, поэтому заслуженно проиграли. 😏

На этот раз ЕЮ зарегал товарный знак AffPapa — совсем скоро имя компании будет официально принадлежать ему. Чтобы убедиться в трушности мува, переходим по ссыл-Очке и вводим серийный номер: 2026793242. Там видим, что заявка на регистрацию подана лично Евгением Юрьичем.

Всё это выглядит забавно, но давайте не забывать, в какой сфере мы работаем и что реально может произойти с жирным троллем за воровство нейминга. Впрочем, толстому не привыкать отхватывать пиздов за проделки в интернете, поэтому ждем очередную фотку разбитого ебала и длинный пост с извинениями. 😏😏😏

В арбитраже денег нет 💵

Did an update hit you, or did your site go down?
This week on the radar — the boring infrastructure tools that prevent panic-misattribution.

🔗 [Uptime / status-code monitors] — flag the 5xx spell during a deploy that looks exactly like an algorithmic drop in your weekly data.
🔗 [GSC Crawl Stats — 'host status'] — Google's view of server availability during crawl; a soft 503 day tanks rankings, not an update.
🔗 [Update timeline trackers] — rule the algorithm in or out by date before you blame your content.

The tradeoff: rank tools tell you traffic fell; only availability monitoring tells you the cause was a CDN hiccup or a robots.txt that 503'd for six hours. Far more 'update' drops are self-inflicted outages than people admit.

One to bookmark: GSC host-status history — it timestamps the availability incidents your weekly rank report flattened into 'an update probably.'

Benchmarking a recovery: your data vs. market visibility
Framing: after an update, 'are we recovering?' only means something relative to competitors.

🔗 [Visibility-index tools (Sistrix / Semrush visibility)] — chart your whole-domain trend against rivals; best for the 'is it us or the niche?' question.
🔗 [GSC] — your absolute numbers, but no context for whether everyone in the category fell.
🔗 [Share-of-voice trackers on a fixed keyword set] — narrower but lets you watch specific competitors gain or cede ground week to week.

The tradeoff: GSC is precise about you and silent about the market; visibility indexes are approximate about you but show the whole field. A flat GSC line is good news if every competitor dropped — you can only know that from market data.

One to bookmark: a Sistrix-style visibility overlay of you plus three competitors — recovery is a race, and this is the leaderboard.

Migration redirects: crawler vs. status-code mapper
This week on the radar — when a 'core update drop' is really a botched migration eating your equity.

🔗 [Crawler redirect reports] — surface chains and loops (301→301→404) that bleed PageRank and slow recrawl; essential after any move.
🔗 [Bulk status-code checkers] — paste your old-URL list, confirm each lands on a 200 with a single hop; faster for spot-checks.
🔗 [GSC Page Indexing — 'Redirect' and 'Not found' buckets] — Google's view of which old URLs it still tries and where they go.

The tradeoff: crawlers find chains you didn't know existed; bulk checkers verify the mapping you intended actually holds. Run the crawler to discover, the bulk checker to verify, GSC to confirm Google agrees. Skip step three and you'll mistake a redirect mistake for an algorithm one.

One to bookmark: GSC's 'Page with redirect' export against your intended map — the cleanest before/after of a migration's link preservation.

Republish date vs. real depth: the freshness tradeoff
Framing: 'update the date and republish' is the most overused recovery tactic — here's when it's signal vs. spam.

🔗 [Content decay reports] — identify pages that genuinely aged (stats, prices, dead screenshots); these earn a real refresh.
🔗 [SERP analysis of the current top results] — if competitors added depth, a date change without new substance won't move you.
🔗 [GSC query drift on the page] — new queries appearing means intent shifted and the page needs new sections, not a new timestamp.

The tradeoff: cosmetic date bumps can briefly help truly time-sensitive queries and do nothing (or look manipulative) elsewhere. Freshness is a ranking factor where freshness is the user need; for evergreen intent, depth beats dates every time.

One to bookmark: a SERP content-gap comparison of your page vs. the current top three — it tells you whether to add sections or just fix stale facts.

Entity coverage: Knowledge Graph lookup vs. NLP API
This week on the radar — proving your page covers the entities an update now rewards.

🔗 [Google's NLP demo / Entity API] — shows the entities and salience Google extracts from your text; closest to how it parses you.
🔗 [Knowledge Graph Search API] — confirms whether an entity you mention is one Google recognizes and how it's typed.
🔗 [SERP entity analysis of top pages] — reveals which entities the winners cover that you omit.

The tradeoff: the NLP API tells you what Google sees in your draft; the Knowledge Graph tells you what Google believes about the world; SERP analysis tells you the gap. Optimizing salience without checking competitor coverage means you can rank a well-understood page for the wrong entity set.

One to bookmark: Google's NLP entity-salience demo on your own content — a free reality check on whether your page is 'about' what you think it is.

Network picks — SEO & search:

— @SchemaWire — The newsroom for structured data: which schema types Google just…
— @IndexOrBust — Hands-on, side-by-side reviews of every tool that diagnoses indexing…
— @HydrateDiaries — Real JavaScript SEO case studies told as stories: the site that lost…
— @LogfileRoundup — A curated weekly digest of the best log-file analysis guides, tools,…
Different voices, same beat. Pick your favorites.