---
title: "Jonas (@jonasb) | Hashnode"
description: "Sharing various dev's thoughts. Read the latest articles by Jonas on Hashnode."
url: "https://hashnode.com/@jonasb"
---

@jonasb

# Jonas

@jonasb · Joined August 2026

Sharing various dev's thoughts.

## Comments

[I’d add a normal GET request alongside curl -I in the test. -I sends HEAD, so it checks the headers but doesn’t give you the page body. Keep the GET status, redirect chain and returned HTML together for a valid page and a missing one. That catches cases where HEAD and GET are handled differently, and makes it easier to tell whether the 200 is actual page content or the fallback shell. The existing route-state table is a good basis for that regression check.](https://hashnode.com/posts/when-every-url-returns-200-how-single-page-applications-create-soft-404s/6ac4e9442272a07ff9adf921/comment/6ac74a751f0b440f5fba9943)

Comment · Article · Oct 8 · [When Every URL Returns 200: How Single-Page Applications Create Soft 404s](https://hashnode.com/posts/when-every-url-returns-200-how-single-page-applications-create-soft-404s/6ac4e9442272a07ff9adf921)

[I’d extend check-meta to check the body too: the expected H1, a route-specific paragraph and the main links. The JSON-LD element can appear before async content has finished loading, so it’s possible to save a snapshot with a complete head and a loading state in the body. If the page has async content, I’d wait for a signal from that content before saving it, then check the deployed URL as well as the file in dist. I’m building Prerender Buddy, so this is close to what I work on. The check that matters here is what the URL actually returns.](https://hashnode.com/posts/prerendering-a-vite-react-spa-with-playwright-so-crawlers-and-ai-agents-see-real-html/6abdf8449c9c4d86651e41cf/comment/6ac7446c3aa386bcb6090555)

Comment · Article · Oct 8 · [Prerendering a Vite + React SPA with Playwright so crawlers and AI agents see real HTML](https://hashnode.com/posts/prerendering-a-vite-react-spa-with-playwright-so-crawlers-and-ai-agents-see-real-html/6abdf8449c9c4d86651e41cf)

[I’d add an unchanged article as a control and run the same questions for both over a few days. Save the full answers and cited URLs each time. Also keep failed searches separate from answers that completed but didn’t cite the page. Otherwise those can both look like zero visibility. That should make the before/after easier to read. One citation after an edit is interesting, but I wouldn’t take it as proof that the edit caused it.](https://hashnode.com/posts/aeo-and-ai-search-demo-can-a-small-tool-help-my-article-get-cited/6abb54498b4f708280fd24e0/comment/6ac73a453a0a9add3fbe2219)

Comment · Article · Oct 8 · 1 · [AEO and AI Search Demo: Can a Small Tool Help My Article Get Cited?](https://hashnode.com/posts/aeo-and-ai-search-demo-can-a-small-tool-help-my-article-get-cited/6abb54498b4f708280fd24e0)

[This is pretty close to how I look at it too. First: can the crawler access the page? Second: what does it actually get back? Then I start looking at mentions, citations, competitors and the content itself. A lot of “AI visibility” problems I’ve checked still turn out to be much simpler things like blocked access or thin HTML on the first response.](https://hashnode.com/posts/what-actually-makes-a-site-ai-readable-in-2026-not-the-folklore-version/6aac162d60526f6c47142adc/comment/6ab120217858657afca8ccca)

Comment · Article · Sep 21 · [What Actually Makes a Site AI-Readable in 2026 (Not the Folklore Version)](https://hashnode.com/posts/what-actually-makes-a-site-ai-readable-in-2026-not-the-folklore-version/6aac162d60526f6c47142adc)

[This is a good example of why “it works in the browser” is not enough. If the important navigation only appears after JS runs, some crawlers never really see the site structure at all. For category, docs and product trees I’d still want the important links in the first HTML response. We check this kind of crawler-facing HTML in Prerender Buddy as well, because it is very easy to miss from the normal rendered page.](https://hashnode.com/posts/javascript-links-ai-crawlers-41-day-test/6a87a6b43dca225165d44806/comment/6ab11fe656811492e977bcd7)

Comment · Article · Sep 21 · [JavaScript Links Can Hide Content From AI Crawlers, a 41-Day Test Shows](https://hashnode.com/posts/javascript-links-ai-crawlers-41-day-test/6a87a6b43dca225165d44806)

[I like the order here. Get the important content into the initial HTML first, then worry about schema, llms.txt and the rest. I’d also test more than the homepage. Product and category pages are usually where I find the bigger difference between what the browser shows and what a crawler actually receives.](https://hashnode.com/posts/best-peptide-supplier/6a38987bb45fa413fa08caa2/comment/6ab11f98490faaefba21c37a)

Comment · Article · Sep 21 · [Best Peptide Supplier in 2026: How to Choose a Research Peptide Supplier](https://hashnode.com/posts/best-peptide-supplier/6a38987bb45fa413fa08caa2)

[This is something I keep seeing as well. The browser can look completely fine while the crawler gets almost nothing useful back. I normally check a few important pages with JS out of the picture first. If the content, headings or links are missing there, I’d fix that before going deeper into AI visibility. This is also one of the checks I use Prerender Buddy for pretty much every day now.](https://hashnode.com/posts/your-site-might-be-invisible-to-ai-crawlers-here-s-how-to-actually-check/6a747af57ddde48ce1cbbeee/comment/6ab11f5069a5234e62772fe3)

Comment · Article · Sep 21 · [Your Site Might Be Invisible to AI Crawlers — Here's How to Actually Check](https://hashnode.com/posts/your-site-might-be-invisible-to-ai-crawlers-here-s-how-to-actually-check/6a747af57ddde48ce1cbbeee)

[Agree on putting critical copy, links, and metadata in the initial response. AI crawlers make that less optional than it used to feel when teams could lean on Google’s rendering. One practical habit: check the raw HTML with curl (or view source), not the browser DOM after JS runs. That’s the same check we care about with Prerender Buddy when looking at what bots actually receive.](https://hashnode.com/posts/ssr-ssg-critical-content-discovery/6a86358f15c1b208cee9a317/comment/6aaadaabb4e241087c30ed32)

Comment · Article · Sep 16 · [Why Critical Content Should Not Depend on Client-Side Rendering](https://hashnode.com/posts/ssr-ssg-critical-content-discovery/6a86358f15c1b208cee9a317)

[The useful split here is fetch readiness vs citation myths. Watching homepage PSI while bots hit long-tail URLs that time out or return a JS shell is a common mismatch. Checking that the primary content is in the first HTML response, and monitoring the paths logs actually show, is the access layer before anyone argues about schema or “AI rankings.” That’s the same readable-HTML check we care about with Prerender Buddy: can the crawler get real text without executing the app.](https://hashnode.com/posts/bots-read-fast-pages-too-what-we-reprioritised-after-an-ai-crawler-audit/6a1b4cab860ed170819d62f0/comment/6aaada2757c6992e4106900d)

Comment · Article · Sep 16 · 1 · [Bots read fast pages too: what we reprioritised after an AI-crawler audit](https://hashnode.com/posts/bots-read-fast-pages-too-what-we-reprioritised-after-an-ai-crawler-audit/6a1b4cab860ed170819d62f0)

[The training vs retrieval split is useful, and the CDN layer is the one people skip. I’ve seen the same pattern: robots.txt looks open, but the edge is quietly blocking OAI-SearchBot or PerplexityBot, so the allow never matters. Auditing both layers, then checking Security Events for actual fetch attempts, is the right order before anyone worries about schema or “AI-ready” content.](https://hashnode.com/posts/ai-crawler-access-audit-robots-txt-cdn-2026/6a623cd1112ec6b26ef76492/comment/6aa989b335308b55b6b7c3ec)

Comment · Article · Sep 15 · [The Two-Layer AI Crawler Access Stack Every Developer Should Audit](https://hashnode.com/posts/ai-crawler-access-audit-robots-txt-cdn-2026/6a623cd1112ec6b26ef76492)
