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

/tech/ - Technical SEO

Site architecture, schema markup & core web vitals
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1791651701428.jpg (220.86 KB, 1024x1024, img_1791651691488_9kxtv0hv.jpg)ImgOps Exif Google Yandex

d5ce5 No.2313

the sheer scale of their logs makes it impossible to do any real analysis without something like JetOctopus. they were only keeping data for 7 to 14 days, which is a joke when you're trying to figure out if a template change from months ago messed up your rankings.
>two weeks of history is enough to notice that something broke on Tuesday. it is not enough to prove that a template change shipped in march is what moved googlebot in may
it's fine for small sites, but i don't see how anyone manages crawl budget waste on a massive marketplace without seeing those long-term patterns. does anyone here actually rely on raw logs for anything besides checking 404 spikes?

more here: https://jetoctopus.com/case-study-large-marketplace/

d5ce5 No.2340

>>2313
Two weeks is basically nothing for anything meaningful. I tried digging into some old server logs to see if a crawler change was hitting our deep pagination, but everything was already wiped gone purged. It's hard to trust any findings when you can't correlate them with historical crawl patterns from the previous quarter. **I hate when devs rotate logs every Sunday



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]