archive
356 · Page 1
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 salon conversation about editing a website with ChatGPT leads to external booking systems, free static hosting, maintenance debt, and the changing value of web developers.
A working wallet connection does not prove people can finish authentication. A practical review of consent, recovery and alternatives without weaker checks.
A governance audit pipeline reported success on all 15 runs, yet produced no actual measurements. The exit code alone cannot distinguish a clean result from a failed one, so teams must verify that result files exist before trusting a green light.
A security check that finishes successfully can still leave no results. When the result files are missing, a zero score means "not measured," not "no risk," so teams need a storage rule before they adopt any scoring tool.
A robots.txt file decides whether AI crawlers may use your content, and providers differ in how finely you can control them. OpenAI documents independent tokens so you can allow search and block training, while Google-Extended bundles training and citation into a single lever.
Roadmap promises and the published specification are two different things. This article measures how much data a program loads the moment it connects, and checks which roadmap features exist in the published specification.
A popular way to share one rules file between two AI coding tools is a shortcut link, but no official document backs the trick, and file-system measurement shows absolute links break when a folder moves. This piece explains the evidence, its limits, and what to do about it.
A test with 60 runs shows that the same rules file can reach the AI helper from one folder but not from another, and a rules file handed over mid-conversation was followed only half the time. The launch folder decides the first part; the arrival time decides the second.
Three official ways to connect AGENTS.md to CLAUDE.md all loaded the document in testing, with at most 122 tokens of difference. The actual risk is not the wiring but a single example line wrapped in a code block that quietly erases the whole document.
A committed rules file like CLAUDE.md or AGENTS.md is a suggestion the assistant reads, not a rule anyone enforces. When one user request conflicts with a single rule, the model judged the whole file a prompt attack and discarded all of it, 6 times out of 6.
Google shipped a dedicated page and button code for the Preferred Source feature on August 20, 2026, while the way to keep a site out of AI answers sits in a single sentence of the developer docs. A count of our own 12 pages found that sentence's controls on zero of them.