
Local SEO is a Technical Problem Too
Local SEO is a technical problem too, covering crawlable content, structured pages, performance, metadata, internal links, and reliable local signals.
Articles
Search Engine Optimisation (SEO) connects what a site publishes with how people and search systems find it. This category takes the wider view of visibility, content signals, and changing search behaviour. The separate Technical SEO category concentrates on defects in the build itself, whilst Generative Engine Optimisation (GEO) follows those signals into AI‑mediated search.

Local SEO is a technical problem too, covering crawlable content, structured pages, performance, metadata, internal links, and reliable local signals.
Learn how DDoS attacks overwhelm services with distributed botnet traffic, why they are hard to block and which mitigations can reduce the risk.
Time To First Byte (TTFB) is a crucial influence on website performance. The easy answer is increasing server resources, but there are other considerations too.
Time To First Byte (TTFB) is a measurement of the time it takes for a server to respond to a request: how quickly your visitor can start to load your page.
You can let Google know that your website (and the content within) has been updated by submitting an updated sitemap automatically via a simple Node.js script.

Ten practical SEO areas front‑end developers can influence, from site speed and semantics to metadata, mobile UX, internal links, and structured data.

AMP has long split opinion: Google's preferential treatment of sites using AMP has long been a contentious point. Is it worth implementing AMP any longer?

.htaccessBlock bad bots with .htaccess and robots.txt, including why unwanted crawlers waste bandwidth, where rules help, and what to treat with caution too.

Website theft is frustrating, but there are practical ways to spot it and respond. This guide covers copied text, copied code, and escalation options.

Replace Gatsby's inlined production CSS with an external stylesheet by rewriting headComponents, with performance trade‑offs and historical context.

A common issue I come across when auditing sites with Lighthouse is the "Links do not have a discernible name" error where links don't contain text.

When you set up a custom domain in Netlify, the default `netlify.com` subdomain still returns your app, which can lead to duplicate content. It is an easy fix.

urllist.txt from sitemap.xmlUsing PHP it is quick and easy to automatically generate your urllist.txt sitemap from your sitemap.xml file (for example, using gatsby‑plugin‑sitemap).

Compare 301 and 307 redirects clearly, including permanence, browser behaviour, SEO impact, cache handling, temporary moves, and when each status code fits.

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.

SEO risks in WordPress theme and plugin work, including metadata, headings, archives, canonicals, redirects, schema, pagination, and generated markup.