A short, opinionated kit of no-cost tools for measuring a site, securing it, and sourcing media — with honest notes on what each one is good for and where its limits are.
A practitioner's checklist. This is general guidance, **not legal advice** — get a professional opinion for your jurisdiction before you monetize or scale, especially around images.
A repeatable pattern for AI-written descriptions, summaries, specs and FAQs across a directory or catalog — without an API key, an SDK dependency, or a per-token bill.
A good taxonomy is invisible when it works and infuriating when it doesn't. The trick is to build on an industry standard for completeness and interoperability, then lay a human-friendly navigation over the top — and to keep your filters separate from your tree.
Search is splitting into three audiences: the ranking algorithm, the answer engine, and the generative model. The good news is that one well-structured article can serve all three — if you write for the passage and the source, not just the page.
You're mapping a messy source vocabulary onto a clean target taxonomy. The target has about 5,600 slots, so the job must be roughly 5,600 decisions — right? The backlog is already past 8,900, and still climbing.
You shipped a fix to how one field is computed, re-ran the pipeline across everything, and it reported a clean run. Then the consistency check still flags those records as wrong. The fix is in the code, the rebuild "ran" — and the records never changed. Your own optimisation skipped them.
The report said 80 duplicate groups still to resolve. You'd been resolving them for days. You run it again after a big batch and it *still* says 80-ish. The backlog isn't stubborn — the scan is counting work you already finished.
You hardened a skill in the repo, shipped the PR, and the agent kept loading the old one. Or you fixed the live skill by hand, and the versioned copy quietly stayed behind. Same root cause: the copy you run and the copy you version are two different files.