Join my community / free newsletter — sign up here

third-party scripts

By Greg Nowak, 20 April, 2026

Why Your Website’s Third-Party Stack Needs a Real Owner

Third-party scripts affect speed, data, resilience, and conversion. Learn how to assign ownership, audit the stack, and govern every vendor dependency.

Tags

Review Greg on Google

AI crawler policy now has verbs: separate search, RAG, and training

2026-08-02

AI crawler rules now need separate decisions for search, RAG, and training, backed by practical testing across robots.txt, CDNs, WAFs, and CMS controls.

WordPress Supports Old PHP; Your Production Server Shouldn’t

2026-08-01

WordPress still runs on legacy PHP, but compatibility is not a security policy. Build and test your upgrade path before PHP 8.2 support ends.

The AI-built tool your team relies on needs an owner

2026-07-31

AI-built internal tools can become business-critical before anyone owns them. Here is how to secure, review, monitor, and retire them without blocking useful work.

Your AI model has an expiry date: build the migration lane now

2026-07-30

AI models retire on a schedule. Learn how to map dependencies, test replacements, release safely and preserve a working rollback route.

Copilot Has Repo-Level Metrics Now. What Should Teams Measure?

2026-07-29

GitHub’s repo-level Copilot metrics show where AI is active, but not whether it adds value. This scorecard connects usage with delivery, quality, and cost.

Not Every AI Job Needs an Instant Answer: Batch the Backlog

2026-07-28

Move delay-tolerant AI work into dependable batch queues to cut processing costs without compromising quality, data controls, or urgent workflows.

A stray Set-Cookie can waste your CDN: audit the cache at the edge

2026-07-27

Cloudflare Cache Response Rules can recover wasted CDN capacity, but first you need a route-level audit of public, personal and authenticated responses.

Shorter TLS certificates expose every renewal you never automated

2026-07-26

Shorter TLS lifetimes leave less room for manual handoffs and faulty deploy hooks. Build a renewal path that protects service availability.

One Timeout, Two Orders: Make AI Actions Safe to Retry

2026-07-25

A timed-out AI action may already have succeeded. Stable keys, durable ledgers, queues and stored results prevent a routine retry from duplicating real work.

Your AI Visibility Dashboard Needs a Methodology, Not More Charts

2026-07-24

A practical framework for measuring AI-search visibility with fixed prompts, repeated tests, separate metrics, retained evidence, and honest reporting.