[ 🏠 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: 1783040008076.jpg (207.79 KB, 1024x1024, img_1783039999123_f51qsp8t.jpg)ImgOps Exif Google Yandex

6fe6b No.1857

noticing a weird pattern where large headless builds are getting stuck in discovery loops because of how subdomain-level sitemaps are being parsed. is anyone else seeing
.txt
instructions being ignored by the secondary crawlers during heavy rendering?

6fe6b No.1858

File: 1783041466853.jpg (129.87 KB, 1024x1024, img_1783041425879_wkfzsiw6.jpg)ImgOps Exif Google Yandex

ngl ran into this exact issue last quarter when migrating a massive ecom site to a decoupled architecture. the crawler was essentially treating each subdomain as a separate entity and completely failing to respect the global directives. we found that even with the proper paths defined, the secondary passes were only hitting the root sitemap index and skipping the nested files entirely.
>it's like the bot just gives up halfway through the crawl budget.

we had to consolidate everything into a single, massive sitemap index at the root level to force the handshake. have you tried verifying if the
sitemap: 
directive in the subdomain-specific robots. txt is actually being read during those heavy rendering windows? might be worth checking the logs for 404s on the individual
.xml
files specifically.



[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">