Chrome Now Measures Ad Count, Density and Weight in CrUX
Chrome added four experimental ad metrics to CrUX. We measured a fixed publisher panel and found why count, density, CPU and network weight need separate diagnoses.
From this desk
Start with the most useful page
The featured page offers a strong introduction. The remaining cards help readers move through this editorial section without turning the archive into a service menu.
Start with the editorial guide
Choose the desk that matches your question
Use the subject desks for focused browsing, or continue to the complete chronological archive below.
SEO
Crawling, content, and measurement
Reporting and practical analysis for technical, on-page, content, and publishing decisions.
AEO & AI Search
Answers, citations, and visibility
Platform changes, retrieval behavior, source attribution, and measurement without unsupported promises.
Research
Tests, methods, and evidence
Original protocols, observations, evidence reviews, and the limits on what each result establishes.
Workflows
APIs, automation, and verification
Implementation stories with reproducible inputs, failure states, evidence, and stopping conditions.
Complete archive
Every story, newest first
Open a story for its complete evidence, examples, limitations, author information, and reader discussion.
-
-
What 30,000 Reddit Answers Reveal About Which Voices Survive AI Search
A 30,000-output study finds retrieval drives most variation while Reddit Answers favors early, top-level and more formal comments in its selected evidence.
-
Google Tests Publisher Payments for Contributions to AI Answers
Google is testing payments when publisher content significantly contributes to AI answers. Here is what is confirmed, undisclosed and worth measuring.
-
Google Research Cut Retrieval Fan-Out Time 12× to 20×
Google researchers report that Retrieve-for-Train generated ten retrieval directions 12× to 20× faster in fashion and music benchmarks, while the diffusion model traded some recall for greater diversity.
-
What Perplexity’s CobbleDB Reveals About AI Search Retrieval
Perplexity reports roughly 80% lower read latency after separating passage processing, publishing and hot retrieval. Here is what publishers can and cannot infer.
-
OpenAI Plans to Retire Custom GPTs: Build the Migration Inventory
Prepare for OpenAI’s planned Enterprise custom GPT transition with the September 17 and 25 milestones, December 11 retirement date and a migration inventory.
-
Claude On-Demand Compaction Needs a Citation-Retention Test
Use a six-case release gate to test whether Claude on-demand compaction preserves source IDs, claim links, contradictions and recent turns.
-
Q2D-Web Shows Why AI Citations Depend on First-Stage Retrieval
A 190-million-document benchmark shows why retrieval recall, unique evidence coverage and downstream citations must be measured separately.
-
Cloudflare Browser Run Guardrails: Build a Safe Hostname Allowlist
Configure Browser Run hostname guardrails and use Session Recording logs, network HAR and final DOM to explain blocked dependencies.
A useful standard
What every story should make clear
SearchEngineAnswer is an independent publication. Stories should help a reader understand what changed, what the evidence supports, and what to do next.
The reader job is explicit
A story should answer a focused question or support a concrete decision rather than merely announce a topic.
Sources remain inspectable
Material facts stay close to current primary documentation, reproducible evidence, or clearly attributed reporting.
Updates retain context
Meaningful changes, uncertainty, corrections, and publication dates remain visible so readers can judge freshness.
References and next steps