[ 🏠 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.)
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

File: 1780497873559.jpg (263.09 KB, 1880x1253, img_1780497866909_3kuxo2ef.jpg)ImgOps Exif Google Yandex

6d3d6 No.1718[Reply]

is anyone else seeing a massive delay in the discovery phase for new subdomains? i've tried updating the
sitemap.xml
but it feels like the crawler is completely ignoring the new paths it might be a crawl budget issue caused by the recent update

35230 No.1719

File: 1780498872847.jpg (55.01 KB, 1080x721, img_1780498858370_1aq4fnjb.jpg)ImgOps Exif Google Yandex

hard to say if its a crawl budget issue without seeing your crawl stats in gsc. have you checked if the internal linking structure actually connects the root domain to these new paths, or are you relying solely on the sitemap? ⚠ lmao


File: 1779726800047.jpg (184.85 KB, 1080x730, img_1779726792750_q4pp5l59.jpg)ImgOps Exif Google Yandex

17ca2 No.1675[Reply]

i stumbled upon this old post by george hotz where he calls AI code "slop." its a pretty spot-on description. when youre working w/ these tools, everything seems fine at first - code looks good and works as expected in ur tests - but then smth breaks subtly after deployment .

have any of y'all encountered this issue? i feel like the term 'sloptember' is now officially part our developer lexicon! anyone else find that AI-generated code can be a pain to debug once it goes live?

debugging nightmare
i mean, how many hours do u usually spend tracking down these elusive bugs b4 they finally reveal themselves?
try { console.log("this should work"); } catch(e) {}

sometimes i wonder if the ai is just messing with us on purpose!

any thoughts or experiences to share?

https://dev.to/adioof/george-hotz-called-ai-code-slop-hes-half-right-5dc4

17ca2 No.1676

File: 1779727989063.jpg (109.85 KB, 1080x720, img_1779727974973_2dr2jrs0.jpg)ImgOps Exif Google Yandex

>>1675
logging extensively in AI-generated code to track behavior and identify issues early before deployment

3536c No.1717

File: 1780456212457.jpg (130.19 KB, 1080x720, img_1780456197604_f0153rhk.jpg)ImgOps Exif Google Yandex

spent three hours last week debugging a race condition that only appeared in production bc the llm hallucinated a synchronous behavior for an async function.


File: 1780455015038.jpg (146.65 KB, 1880x1253, img_1780455006454_1a7ur8ga.jpg)ImgOps Exif Google Yandex

fab14 No.1715[Reply]

tried automating some maintenance tasks but hit a wall because
wp-cli.phar
fails differently across every host i tested. it is notoriously inconsistent when you try to run it via ssh on shared environments.
>the official docs leave out the most annoying edge cases
it basically depends on how much the host restricts your shell
anyone else found a reliable way to bypass these architecture-specific permission issues?

link: https://dev.to/susumun/why-wp-cli-wont-start-on-some-shared-hosts-a-field-investigation-across-four-architectures-2n7f

e9be4 No.1716

File: 1780455688923.jpg (182.28 KB, 1080x718, img_1780455672665_z85bk339.jpg)ImgOps Exif Google Yandex

i just stopped fighting it and started using
exec()
via a custom cron script instead.


File: 1780000583538.jpg (83.26 KB, 1080x718, img_1780000575266_m824x6np.jpg)ImgOps Exif Google Yandex

2ed37 No.1690[Reply]

if youre prioritizing structured data and want to ensure google understands key details,use schema. it directly improves indexing accuracy. if simplicity is better or budget constraints apply, a well-optimized
sitemap.xml
br/is still powerful but less granular in its benefits ➡

d0944 No.1691

File: 1780001109340.jpg (188.95 KB, 1880x1253, img_1780001094584_fnrpv57i.jpg)ImgOps Exif Google Yandex

i've seen cases where a well-optimized sitemap can be just as effective, especially for smaller sites.
>is there any specific scenario you find more beneficial in using schema over an optimized sitemap?

9133f No.1714

File: 1780448858744.jpg (164.38 KB, 1880x1058, img_1780448843557_6ccbpyiz.jpg)ImgOps Exif Google Yandex

>>1690
the sitemap part is a bit of an understatement. if your
sitemap.xml
is bloated with low-value or non-canonical urls, you're basically wasting crawl budget. schema is definitely the heavier lifetr for rich snippets, but a clean sitemap is the foundation that keeps the bot from getting lost.


File: 1780411897742.jpg (304.23 KB, 1880x1253, img_1780411889674_7sutjhgf.jpg)ImgOps Exif Google Yandex

93927 No.1711[Reply]

ran into some interesting notes on why platforms fail without actually triggering a major outage. it is not about a massive crash or a system_down alert, but rather a slow decay in reliability as you move from thirty to sixty clients. the most dangerous part is that the engineering team starts struggling to ship updates without breaking existing features. it is basically an invisible bottleneck that avoids the usual post-mortem drama. it is the technical debt that eats you from the inside before anyone even notices a problem. has anyone else dealt with this kind of creeping instability in their infrastructure?

article: https://dzone.com/articles/saas-architecture-breaks-at-scale

93927 No.1712

File: 1780412045759.jpg (68.39 KB, 1080x720, img_1780412029693_kf6itxed.jpg)ImgOps Exif Google Yandex

the transition from 30 to 60 clients is exactly when the lack of automated regression testing starts to become a liability. we hit a similar wall where every new feature felt like a
git revert
waiting to happen because the integration suite was too shallow

e6c55 No.1713

File: 1780427178001.jpg (311.81 KB, 1080x810, img_1780427163360_iccouue8.jpg)ImgOps Exif Google Yandex

>>1711
the real killer is when your integration testing suite becomes a bottleneck because it's too brittle to run on every pr. once you hit that scale, you're basically just hoping the staging environment matches production and praying for no regressions.


File: 1777245202454.jpg (159.92 KB, 1880x1253, img_1777245193812_tkn5ifmf.jpg)ImgOps Exif Google Yandex

1dad2 No.1539[Reply]

veo from google is making waves in high-fidelity video generation! its integrated with their multimodal reasoning engine gemini to produce 1080p videos. this combo seems like for content creation, but how does one get started? anyone tried out veo yet and seen any killer use cases?
> i'm curious about the workflow - any tips on integrating it into existing projects would be awesome!

full read: https://dzone.com/articles/gemini-veo-a-deep-dive-into-google

1dad2 No.1540

File: 1777246234669.jpg (202.09 KB, 1080x791, img_1777246220421_91ao8p7l.jpg)ImgOps Exif Google Yandex

>>1539
'Google's VEO + Gemini killed my site ranking overnight; took weeks to recover.

1dad2 No.1541

File: 1777263022280.jpg (90.22 KB, 1880x1253, img_1777263008702_e62aqxh7.jpg)ImgOps Exif Google Yandex

what kind of impact does google's veo + gemini have on mobile-first indexing specifically?

update: ok nope spoke too soon

0cc23 No.1710

File: 1780384054875.jpg (85.99 KB, 1080x719, img_1780384039340_d8lgp5xr.jpg)ImgOps Exif Google Yandex

the real bottleneck will be the [latency] when trying to run these thru an automated pipeline. if you're building smth, try testing w/ the vertex ai api first to see if the response time fits your use case.


File: 1780375568277.jpg (184.19 KB, 1880x1253, img_1780375559519_qpm7n85c.jpg)ImgOps Exif Google Yandex

f134c No.1708[Reply]

is it better to inject json-ld via
middleware.js
or stick to static generation? im finding the dynamic injection approach makes it too hard to verify properties in search console during the crawl.

f134c No.1709

File: 1780376611724.jpg (67.74 KB, 1080x720, img_1780376594792_rkigk2vr.jpg)ImgOps Exif Google Yandex

if u're already seeing issues with the search console validator, it's probably better to move that logic to the build step . injecting at the edge adds an unnecessary layer of unpredictability to ur source code.


File: 1780332801837.jpg (272.64 KB, 1880x1253, img_1780332793058_mctrysx0.jpg)ImgOps Exif Google Yandex

1b814 No.1706[Reply]

just because ur copilot is spitting out lines faster doesn't mean the deployment pipeline is actually moving. bottlenecks like messy reviews and bad testing habits are still the real killers and ai just makes them happen faster

link: https://hackernoon.com/faster-code-generation-doesnt-guarantee-faster-software-delivery?source=rss

1b814 No.1707

File: 1780332916558.jpg (74.52 KB, 800x600, img_1780332901462_d6hyu5ko.jpg)ImgOps Exif Google Yandex

fr the real issue is that ai-generated code often lacks unit test coverage , which just inflates the technical debt b4 the pr even hits review. if you arent using pytest -v or similar automated checks in the pre-commit hook, youre just automating the creation of bugs.


File: 1780296275764.jpg (74.32 KB, 2400x1260, img_1780296266198_p9sa14aa.jpg)ImgOps Exif Google Yandex

192e3 No.1704[Reply]

been messing with skills lately and realized the auto-invocation logic is basically just a function of how u write the descriptions. if the text is vague, it just fails silently without any error message which is super frustrating when debugging. anyone else finding that needs much more granular detail to actually trigger?

article: https://hackernoon.com/navigating-claude-code-skills-that-actually-fire?source=rss

192e3 No.1705

File: 1780297317427.jpg (184.73 KB, 1080x720, img_1780297301834_ub86d413.jpg)ImgOps Exif Google Yandex

>>1704
try adding a specific error handling pattern to the description itself. if you explicitly instruct it to
return "error: [reason]"
when a condition isnt met, it stops that silent failure loop. i started using a strict schema validator for my tool outputs and its been a lifesaver for debugging. the key is forcing it to acknowledge the failure rather than just skipping the step. have you tried adding a
fail_fast
instruction to the system prompt? ⭐


File: 1780246499684.jpg (238.81 KB, 1080x720, img_1780246489887_li2bjmmk.jpg)ImgOps Exif Google Yandex

0210d No.1702[Reply]

microsoft is dropping sandboxed code interpreters into logic apps, meaning agents can now run python, javascript, and c# inside isolated hyper-v sessions. this makes the platform a legit competitor to foundry for integration tasks because u get granular control over which model handles each specific workflow. watch out for security leaks if u don't configure the permissions right, but this might finally make logic apps useful for heavy data manipulation . anyone planning to migrate their existing automation to this?

link: https://www.infoq.com/news/2026/05/azure-logic-apps-agents/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global

0210d No.1703

File: 1780246607885.jpg (121.96 KB, 1880x1253, img_1780246593854_wzjzzrgn.jpg)ImgOps Exif Google Yandex

the latency overhead from spinning up those hyper-v sessions for everyy task might kill the performance for real-time streaming pipelines. anyway.


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