[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/ana/ - Analytics

Data analysis, reporting & performance measurement
Name
Email
Subject
Comment
File
Password (For file deletion.)
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

File: 1791507587761.jpg (193.58 KB, 1024x1024, img_1791507580036_gw51qd2n.jpg)ImgOps Exif Google Yandex

7a99f No.2298[Reply]

another way for google to tell us what we already know. they're adding these ai-powered insights directly into the experiment reporting now.
>highlight key insights and recommend next steps
it's basically just an automated summary of the results. i can't wait to see it hallucinate some 'optimization' that actually ruins my campaign performance. trusting the machine is a bad idea when it comes to budget. it'll probably just suggest more spend whenever there's a tiny spike in data. anyone else planning to ignore these recommendations entirely?

article: https://searchengineland.com/google-ads-adds-ai-powered-insights-to-experiment-reporting-494562

7a99f No.2304

>>2298
The part about those tiny data spikes is spot on because I've seen the auto-recommendations push budget into a dead segment just because of one lucky afternoon. It's basically just low-effort text generation that lacks any sense of actual hierarchy or nuance in the data.

7a99f No.2326

>>2304
I don't think it's really a lack of nuance, just that LLMs are terrible at seeing statistical significance. It'll probably just parrot back the p-values and confidence intervals that are already in the report. The text generation might be low effort, but it's not inventing new logic. It's just going to give us a fancy way to read the same boring summary we're already looking at. I expect it to be mostly redundant. Basically just a different font for the same bad news.



File: 1791954348086.jpg (244.94 KB, 1024x1024, img_1791954340946_lk8ugu5a.jpg)ImgOps Exif Google Yandex

2e83d No.2325[Reply]

the 10% sov to 0.5% market share math seems way too clean. hard to believe sentiment balance is enough for a cmo without seeing more of the source mix or velocity stuff.

https://planable.io/blog/social-media-listening-metrics/


File: 1791911577312.jpg (153.49 KB, 1024x1024, img_1791911569135_dii2spp2.jpg)ImgOps Exif Google Yandex

7401b No.2323[Reply]

google's been nuking pdfs lately and just dumping them into "crawled, not indexed" in gsc. i've got a few clients with old manuals and menus that are probably tanking right now. supposed you can use the search analytics and url inspection apis to hunt them down, but manually checking every site is impossible way too much work.

more here: https://www.gsqi.com/marketing-blog/how-to-find-all-pdfs-deindexed-url-inspection-api/


File: 1791587307614.jpg (109.83 KB, 1024x1024, img_1791587299301_cafro1af.jpg)ImgOps Exif Google Yandex

87f2f No.2303[Reply]

google actually having to show clicks and impressions for ai search is kinda wild. imagine if they actually let us opt out of training without some weird penalty lmao.

found this here: https://www.sistrix.com/blog/google-must-report-ai-search-data-in-uk-new-regulations-published-by-cma/

87f2f No.2312

>>2303
>imagine if they actually let us opt out of training without some weird penalty lmao

The penalty is basically just losing all your organic traffic anyway. I've been trying to use the robots.txt block for Google-Extended, but it doesn't seem to stop them from scraping the actual content for search results. It only works if you don't care about appearing in the standard snippets.

87f2f No.2319

>>2312
That's exactly why I stopped recommending the block to clients. You end up with a total visibility blackout on standard search too. It's basically just choosing between being scraped or being invisible. I miss when we could actually track attribution without all this guesswork

87f2f No.2321

>>2319
tried this with a dev's site last month and watched their traffic crater overnight. tried to use google-extended but ended up just nuking their entire index for good.



File: 1791874762138.jpg (94.9 KB, 1024x1024, img_1791874755420_wo6cbubd.jpg)ImgOps Exif Google Yandex

83932 No.2320[Reply]

been thinking about this all morning. looking at candidate page selection is fine but it's basically useless without tracking how authority actually moves the needle. we're already doing way too much with standard ranking metrics and not enough of the actual stack layers. i don't see how anyone tracks authority depth without making their dashboard a total mess. plus, the whole idea of monitoring page selection feels like just more work for no real reward. it's all just guesswork until we actually get some decent tools for this. what are you guys using to track candidate pages right now?

link: https://www.lumar.io/blog/best-practice/geo-analytics-stack-ai-search/


File: 1791831953748.jpg (177.89 KB, 1024x1024, img_1791831944712_8vaowfgq.jpg)ImgOps Exif Google Yandex

657af No.2318[Reply]

saw some data on what gemini actually searches for when it's trying to be "grounded." it's basically just machines running long-tail junk that no human would ever type. most of these queries are only about 6 or 7 words long, but they're all weirdly specific like
>lithography deposition etching doping
it's not even real search behavior, just strings of keywords dumped into a prompt to find facts. seeing stuff like "best indie games of 2025" being used as a primary query makes me wonder if we're even tracking the right thing anymore. the search volume for these is probably zero it's all just nonsense strings of terms. does anyone actually know how to track these specific machine-driven fragments?

full read: https://moz.com/blog/demystifying-grounding-queries-with-real-data


File: 1791422157617.jpg (263.81 KB, 1024x1024, img_1791422149135_xk2f82ov.jpg)ImgOps Exif Google Yandex

b2200 No.2292[Reply]

google finally added actual metrics for ad density and cpu weight to CrUX. it's pretty wild seeing how much processing time those frames actually hog from the user.
>Ad CPU Weight: How much CPU processing time is caused by ad frames?
honestly feels like a way for them to shame publishers into less inventory, but i guess we'll see if the data even holds up when we check our own devtools. do you think this is going to tank anyone's rankings?

full read: https://www.debugbear.com/blog/chrome-ad-performance-insights

b2200 No.2295

>>2292
>how much processing time those frames actually hog from the user
I'm not convinced yet because we need to see this run for at least a full month to account for seasonal traffic spikes, but you might try lazy loading all non-visible slots if your layout allows it.

b2200 No.2310

File: 1791652635057.jpg (185.59 KB, 1024x1024, img_1791652619691_i4vohtk7.jpg)ImgOps Exif Google Yandex

>>2292
>>2295 lazy loading won't help much if the heavy scripts still trigger during scroll. i've seen plenty of sites tank because they tried to be too clever with visibility observers instead of just cutting the bloat. op, did you actually run a comparison on your own site using the new metric? need to know if we're looking at a massive jump or just some minor noise in the devtools. i'm seeing some crazy spikes on my end that dont even seem to correlate with actual ad impressions.

df329 No.2317

File: 1791811802259.jpg (289.14 KB, 1024x1024, img_1791811788023_y4bnbhhe.jpg)ImgOps Exif Google Yandex

>>2295 lazy loading is just a band-aid if you're still firing all those heavy tag manager containers on page load. try using requestidlecallback for your non-critical tracking pixels instead, but don't bother with it for anything above the fold or you'll wreck your lcp.



File: 1791752366247.jpg (188.79 KB, 1024x1024, img_1791752357322_moxj1d4z.jpg)ImgOps Exif Google Yandex

b507a No.2315[Reply]

everyone's obsessed with getting on reddit or listicles like that's the only way to win. even if 85% of citations come from third party stuff, it apparently doesn't actually drive brand mentions. i don't see how we're supposed to optimize anything if the attribution isn't even linked to the content source.

article: https://www.growandconvert.com/research/third-party-citation-research/


File: 1791299684593.jpg (148.96 KB, 1024x1024, img_1791299677231_4ulibgeq.jpg)ImgOps Exif Google Yandex

85063 No.2285[Reply]

I'm tired of people clicking a bar chart and getting nothing but a generic summary. I started putting the raw underlying values in the tooltip so you can actually see what's driving the spike without opening a new sheet. It makes the dashboard feel actually useful instead of just being a pretty picture that hides all the detail. It saves me about twenty minutes of explaining things every Monday.

85063 No.2313

>>2285
>It saves me about twenty minutes of explaining things every Monday.
did this for a retail client last month and it stopped them from pestering me about why sales dropped every single morning. saved my sanity.



File: 1791629987198.jpg (289.64 KB, 1024x1024, img_1791629979990_ye4p3jyw.jpg)ImgOps Exif Google Yandex

cf48f No.2309[Reply]

just saw some claims that 94% of business buyers are using ai search now. it's such a mess trying to attribute anything when chatgpt just strips the referrer data and leaves you with direct traffic. even if we try to use an ad-equivalent value, there's no way to prove someone actually bought something because they saw a snippet in a response. how are you guys even attempting to report this to your managers without looking like you're making up numbers?

full read: https://ahrefs.com/blog/ai-search-roi/


Delete Post [ ]
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]
| Catalog
[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]