
Build‑Time SEO Checks in Gatsby
Run build‑time SEO checks in Gatsby across routes, metadata, canonicals, headings, sitemaps, schema, redirects, CMS content gaps, and release confidence.
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‑five articles collected together for you below.

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.

Check rendered HTML for JavaScript pages by comparing source and DOM output across metadata, headings, links, schema, content, hydration, and crawlability.

How client‑side rendering can affect search visibility, and what to check around content, links, metadata, routing, loading states, and fallbacks.

JavaScript rendering and SEO checks for pages that rely on client‑side behaviour, including content, links, metadata, fallbacks, and rendered output.

Technical SEO checks for CMS templates, including headings, metadata, canonicals, links, pagination, structured data, crawlable content, and editor output.

Optimise HTML markup for SEO and accessibility with semantic elements, heading structure, alt text, clean code, anchor text, and crawler‑friendly structure.