How to Compare Rendered HTML Before and After a Migration
Compare rendered HTML before and after a migration, checking headings, metadata, links, schema, body copy, media, crawl signals, and launch risk.
Articles
Technical SEO, page 2 of 2
Technical SEO is where Search Engine Optimisation meets the build. General SEO can deal with demand, content, and reputation; this category is for the problems caused by the website itself. The articles follow those failures through rendered HTML, crawl paths, and production behaviour until the implementation decision becomes visible.
How to Compare Rendered HTML Before and After a Migration. 
Traffic Dropped After a WordPress to Next.js Migration: What to Check First. Traffic Dropped After a WordPress to Next.js Migration: What to Check First
How to diagnose traffic loss after a WordPress to Next.js migration by checking redirects, rendered HTML, metadata, canonicals, and tracking noise.
WordPress to Next.js Migration Checklist for Content, Preview and SEO. WordPress to Next.js Migration Checklist for Content, Preview and SEO
A WordPress to Next.js migration checklist for URLs, content models, media, preview, redirects, metadata, schema, sitemaps, SEO, and launch checks.
Next.js Sitemap, Robots, and Crawlability Debugging Checklist. Next.js Sitemap, Robots, and Crawlability Debugging Checklist
A Next.js crawlability checklist for debugging sitemaps, robots.txt, canonicals, route generation, redirects, staging leaks, missing pages, and indexation.
Why JavaScript Pages are Crawled but Not Indexed. Why JavaScript Pages are Crawled but Not Indexed
Why JavaScript pages get crawled but not indexed, covering rendered content, metadata, canonicals, links, noindex rules, quality, and crawl signals.
React SPA to Next.js Migration Checklist for SEO and Indexing. React SPA to Next.js Migration Checklist for SEO and Indexing
A React SPA to Next.js SEO migration checklist for preserving indexing, redirects, metadata, rendered HTML, internal links, crawl paths, and launch confidence.
How View Source Stopped Being Enough. How View Source Stopped Being Enough
Why view source stopped being enough for modern web checks, and how rendered HTML, hydration, metadata, schema, crawl paths, and client output changed audits.
Build‑Time SEO Checks in Gatsby. 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.
Local SEO is a Technical Problem Too. 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.
Checking Rendered HTML for JavaScript Pages. Checking Rendered HTML for JavaScript Pages
Check rendered HTML for JavaScript pages by comparing source and DOM output across metadata, headings, links, schema, content, hydration, and crawlability.
Client‑Side Rendering and Search Visibility. Client‑Side Rendering and Search Visibility
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. JavaScript Rendering and SEO Checks
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. Technical SEO Checks for CMS Templates
Technical SEO checks for CMS templates, including headings, metadata, canonicals, links, pagination, structured data, crawlable content, and editor output.
Optimising HTML Markup for SEO. Optimising HTML Markup for SEO
Optimise HTML markup for SEO and accessibility with semantic elements, heading structure, alt text, clean code, anchor text, and crawler‑friendly structure.