
GTM, Consent Tools, and Core Web Vitals: How to Audit Third‑Party Script Cost
Audit third‑party script cost across GTM, consent tools, analytics, experimentation, and personalisation, without breaking measurement or business workflows.
Articles
Search Engine Optimisation (SEO) is the practice of improving how a website is crawled, understood, indexed, and ranked by search engines. It now sits alongside Generative Engine Optimisation (GEO), where the same underlying signals also help AI‑mediated search experiences understand, trust, and surface content.
Below you will find a subset of articles from my blog specifically about Search Engine Optimisation 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 fifty‑two articles collected together for you below.

Audit third‑party script cost across GTM, consent tools, analytics, experimentation, and personalisation, without breaking measurement or business workflows.

A practical Gatsby to Next.js migration checklist covering routes, data, rendering, plugins, images, redirects, preview, sitemaps, and SEO validation.

A practical Contentful to Sanity migration checklist for Next.js sites, covering schemas, references, preview, redirects, metadata, and SEO checks.

SEO best practices in Next.js, with a sharper focus on Core Web Vitals, stable layouts, lighter bundles, metadata, and real user measurement for search.

Google's old exchange was simple: crawl the web and send traffic back. AI search weakens that bargain by answering more journeys before the click.

Contentful to Sanity migration risks for Next.js sites, including models, references, rich text, preview, metadata, redirects, and launch checks.

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

The AI content collapse makes cheap publishing less valuable, shifting durable content strategy towards proof, authorship, structure, trust, and expertise.

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.

Decide whether Shopify to Next.js is worth it by weighing storefront control, SEO, performance, checkout, apps, content workflow, cost, and risk.

AEO explained alongside SEO and GEO, covering answer engines, featured snippets, AI answers, content structure, measurement, and practical workflow.

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

GEO and SEO overlap, but they are not interchangeable. This article breaks down where they meet, where they differ, and how websites need to adapt.

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