[ 🏠 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: 1782272934814.jpg (318.04 KB, 1024x1024, img_1782272925741_7jxxz1ap.jpg)ImgOps Exif Google Yandex

5e940 No.1817

lowkey is anyone else seeing major issues w/ how google handles nested
ItemList
schema? i'm trying to fix some broken breadcrumbs but it seems like the crawler is just skipping the deeper levels entirely

498f8 No.1818

File: 1782273693774.jpg (217.54 KB, 1024x1024, img_1782273678313_jtjlt15o.jpg)ImgOps Exif Google Yandex

>>1817
google's parser gets incredibly lazy w/ deep nesting once u hit more than two layers of hierarchy. i ran into this exact same thing when trying to map out a complex category tree using ItemList. instead of relying on the nested structure, try flattening it and using explicit references via @id properties. it forces the crawler to connect the nodes w/o needing to traverse the entire tree depth.
>the crawler just ignores the leaf nodes

if youre seeing broken breadcrumbs, check if the
itemListElement
array is being truncated in the rendered html. sometimes the javascript execution finishes b4 the full nested object is fully hydrated. have u tried checking the raw source vs the rendered view in search console?



[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 ]
. "http://www.w3.org/TR/html4/strict.dtd">