
The Web Just Invented a Toll Booth for AI
Cloudflare Pay Per Crawl, AWS WAF AI Traffic Monetization and AI crawlers show crawler access becoming commercial infrastructure, not just bot control.
Articles
Technical SEO is where Search Engine Optimisation meets the build. It is the work of making sure a site can be crawled, rendered, understood and trusted when the CMS, templates, JavaScript, redirects and platform architecture get in the way. General SEO can deal with demand, content and reputation. This category is for the problems caused by the website itself.
Below you will find a subset of articles from my blog specifically about technical SEO implementation and related technical SEO for JavaScript applications. This is an area I have worked with for many years, and it has been a regular subject in my writing. There are twenty‑three articles collected together for you below.

Cloudflare Pay Per Crawl, AWS WAF AI Traffic Monetization and AI crawlers show crawler access becoming commercial infrastructure, not just bot control.

Technical GEO for websites, covering indexing, renderability, entity clarity, structured data, and crawl paths without inventing an AI‑only markup layer.

Model service page schema without overclaiming by matching visible content, Service data, OfferCatalog, breadcrumbs, FAQs, entities, and proof clearly.

How service pages become easier for AI search to retrieve and summarise through clear problems, visible proof, internal links, schema, and answers.

Diagnose traffic drops after a redesign, migration, or replatform by checking route parity, rendered HTML, redirects, canonicals, sitemaps, and schema.

How to migrate e‑commerce product and category pages to Next.js without losing SEO value, including URLs, filters, schema, canonicals, and redirects.

How to isolate Core Web Vitals regressions after a redesign, covering LCP, INP, CLS, templates, scripts, images, fonts, data, and release evidence.

A headless CMS SEO checklist covering metadata, canonicals, schema, redirects, sitemaps, preview, internal links, image fields, and publishing controls.

Technical SEO launch criteria for Next.js migrations, covering URLs, redirects, canonicals, metadata, rendered HTML, schema, sitemaps, and recovery.

Compare rendered HTML before and after a migration, checking headings, metadata, links, schema, body copy, media, crawl signals, and launch risk.

How to diagnose traffic loss after a WordPress to Next.js migration by checking redirects, rendered HTML, metadata, canonicals and tracking noise.

A WordPress to Next.js migration checklist for URLs, content models, media, preview, redirects, metadata, schema, sitemaps, SEO, and launch checks.

A Next.js crawlability checklist for debugging sitemaps, robots.txt, canonicals, route generation, redirects, staging leaks, missing pages, and indexation.

Why JavaScript pages get crawled but not indexed, covering rendered content, metadata, canonicals, links, noindex rules, quality, and crawl signals.

A React SPA to Next.js SEO migration checklist for preserving indexing, redirects, metadata, rendered HTML, internal links, crawl paths, and launch confidence.

Why view source stopped being enough for modern web checks, and how rendered HTML, hydration, metadata, schema, crawl paths, and client output changed audits.

Run build‑time SEO checks in Gatsby across routes, metadata, canonicals, headings, sitemaps, schema, redirects, CMS content gaps, and release confidence.

Local SEO is a technical problem too, covering crawlable content, structured pages, performance, metadata, internal links, and reliable local signals.