Tags
23 posts
An explanation of the roles of SEO and web accessibility in how AI search finds documents and generates answers. Using a hypothetical pricing page, this article examines how to verify retrieval paths and information accuracy, and how to apply checklists and LLM review to CMS operations.
A working wallet connection does not prove people can finish authentication. A practical review of consent, recovery and alternatives without weaker checks.
I built 69 text-fragment links from my own production build and clicked each one in Chromium. All 48 prose quotes landed; 14 of 15 code-block quotes did not.
A breadth-first crawl of 1,330 built pages put 1,276 posts at depth 2. Dropping the four flat archives left 296 of them unreachable from the homepage.
Speculation Rules prerendering folds the whole pre-click wait into raw LCP. I measured a 6244ms vs 103.5ms gap on Chrome 150 and mapped where RUM needs fixing.
I ran a prompt-injection regression suite on my LLM pipeline. A naive guard caught 2 of 11, a structural guard caught all 11, and it flagged my own regression.
WebMCP shipped as a Chrome 149 origin trial, but its API already moved: navigator.modelContext is now document.modelContext and provideContext is gone.
Chrome 149 said active WebSockets no longer block bfcache. I re-measured on three Chrome 150 builds and notRestoredReasons still returned 'websocket'. Why?
Keyboard focus escaped an aria-modal dialog on the third Tab press while axe reported zero violations. I measured the same markup under aria-hidden and inert.
Six pages, one bfcache blocker each, measured on real back navigations with pageshow.persisted and notRestoredReasons. Only unload blocked the restore.
W3C published a first draft on language and direction metadata for strings. I audited my four-language blog against it, measured where dir=auto guesses wrong, and shipped a build gate.
22×22 pagination links your thumb keeps missing still scored 92 on Lighthouse. I measured WCAG 2.2 SC 2.5.8 (24×24) two ways and coded the spacing exception.
I seeded eight WCAG barriers into a checkout page and ran axe-core. It caught the four rule-based ones and missed the four needing human judgment entirely.
The same Product entity in three syntaxes, bytes and fragility measured. Google treats them equally, so the reason to choose JSON-LD is coupling, not ranking.
aria-label can make the accessibility tree announce a word no one sees. A reproduced WCAG 2.5.3 Label in Name failure, with Agentic Browsing going 0 to 100.
GPTBot and ClaudeBot don't render JS. Here's a curl experiment proving client-side pages are invisible to AI search, plus how to fix it server-side.
axe-core in jsdom catches structural a11y violations without a browser, but color-contrast comes back incomplete, not pass. Why it happens, and how to split CI into two tiers.
A 5-day audit of my 4-language blog: 12 broken links, 4 hreflang pairs, 405KB blocking CSS, 21 drifted translations, all fixed and locked in with build gates.
I aimed a 30-line checker at my build output: 248 posts passed their hreflang clusters, the homepage failed. Google's reciprocity rules, run logs, and the fix.
A demo bakery page scored 55 on a Lighthouse accessibility audit. Here's the log of fixing six WCAG failures to reach 100, plus a keyboard trap the tool missed.
Inject LocalBusiness JSON-LD with JavaScript and the raw HTML has zero ld+json blocks. I compare it with server-side output, Google's stance and ranking limits.
Chrome 146 embeds MCP server capabilities directly into the browser. Learn how WebMCP works, how AI agents interact with it, and what it means for web development.
A practical case study of auto-generating 31 HTML pages using a parts library-based approach. Complete guide covering CSV metadata management, SubAgent parallel processing, and two-phase quality validation.