The crawlability, rendering and indexation work that makes content rankable
Content does nothing if Google cannot crawl, render and index it cleanly. Technical SEO is where most ranking problems actually start, and where the highest-ROI fixes usually live. These articles are written for engineers, technical SEOs and product managers who own the underlying site.
Topics span JavaScript SEO, edge rendering, structured data, internal linking architecture, sitemap hygiene and Core Web Vitals. Heavy on examples, light on theory.
If you want us to apply these insights on your account, see our Technical SEO service.
Interaction to Next Paint is usually one slow filter, menu or consent banner, not a slow site. The order that works: confirm the problem in field data, identify the single interaction, read which of the three phases is eating the time, and apply the fix that matches that phase. Plus why none of this is worth doing for ranking points.
Robots.txt controls crawling, noindex controls indexing, canonical controls which duplicate gets the credit. Most sites treat them as three strengths of the same tool, which is how a page ends up stuck in Google with a noindex tag Google can never read. Here is what each one does, the pairings to avoid, and the order that actually removes a page.
A tool says you have a cannibalisation problem. Google's own people are openly unconvinced the problem exists most of the time. Here is how to tell a real case from a rank-tracker artefact, why a Search Console-only audit structurally misses the worst version, and why the fix is usually to separate intent rather than merge anything.
Most sites are carrying a pile of structured data that stopped producing anything visible a year or more ago. Google's gallery lists 25 features, fewer than ten apply to a normal business site, and about four do real work. Here is which ones, the review snippet rules that disqualify most sites, and why 'schema for AI search' is a purchase you can skip.
Open the image audit on almost any site and the findings repeat: the hero is lazy-loaded, the gallery is a CSS background, every photo is stock, and the alt text is fine. Here is the order we would put the checks in, and why the camera makes original photos worth more than they were.
A category with six pages where everything past page 1 is invisible quietly orphans every product on pages 2 to 6. Most pagination advice was written for million-page retailers and makes this worse on a 400-page site. Here is what Google actually asks for, the mistake that causes most of it, and an afternoon audit to find out whether you have it.
The ticket usually says the canonical is correct and Google is still indexing the wrong URL. Most of the time the tag is fine and the rest of the site is arguing with it. Here is how to find out which URL Google actually picked, what each Search Console status really means, and which contradictions to go and remove.
Most internal linking advice is written for six-figure e-commerce sites and does nothing for a 200-page business site. The problems there are smaller and more specific: orphan pages, money pages buried five clicks deep, navigation anchors that all say the same thing, and links still pointing at old URLs. Here is how we find each one and what we fix first.
A filter sidebar can generate more URLs than your store has products, and the two standard answers (index everything, block everything) are both wrong. Here is how to decide facet by facet, why rel=canonical does not fix the crawl problem, and what to check in Search Console after you ship the change.
Most redesigns that lose traffic fail for one of a handful of reasons, and every one of them is checkable before launch. Here is the order we work through, why mass-redirecting to the homepage is worse than a 404, and what changes now that ChatGPT and Perplexity crawl on their own schedule.
A crawl tool tells you what a bot could do. A server log tells you what it did. Most log file guides are written for sites with millions of URLs, then handed to people with four hundred pages and no SSH access. Here is the honest version: why crawl budget is probably not your problem, why the bot population is, and where the logs actually live on Cloudflare, Vercel, cPanel and Shopify.
Google has looked at the page and decided not to keep it. Most advice treats that as a technical fault and sends you off to hammer Request Indexing. Here is the order that actually finds the cause: an afternoon of cheap plumbing checks, a look at what Google chose as the canonical, and then the harder question of whether the page deserves to exist.
Apple's published Applebot address pool went from 2,400 IPs to 7,056 with no blog post and no explanation, weeks before the rebuilt Siri ships in iOS 27. Most sites have never looked at how they treat Applebot, and a lot of them are blocking the wrong user agent. Here is what changed and what to check this week.
New research pulled apart how ChatGPT actually fetches web pages, and the answer is uncomfortable. It runs its own index that barely overlaps with Bing, serves most answers from a cached copy of your page, and only truly opens about one page in eighty. Here is what that means for how you write and structure a page.
Businesses are buying GEO tools to fix problems a 2019 site migration created. AI search did not add new technical requirements, it just stopped compensating for the old ones. Here is our practitioner take on why the technical SEO backlog is now the AI visibility roadmap, and why that favours smaller sites.
Everyone is optimising for Google AI Overviews and ChatGPT. Meanwhile a second network of answer engines runs on Microsoft's index, and most businesses have never once checked whether they are properly crawled and indexed there. It is the cheapest visibility audit in SEO and hardly anyone does it.
On May 7, 2026 Google stopped showing FAQ rich results, then told everyone in its new AI search guide that special schema is not needed for AI features either. Both moves point the same way. Here is our practitioner read on what structured data is actually for now, and what to stop wasting time on.
Most sites that block AI crawlers block the wrong ones. Here is every major AI bot user agent, checked against OpenAI, Anthropic, Google, Perplexity, Apple, Meta and Amazon's own documentation, sorted into training crawlers, search crawlers and user fetchers, with three robots.txt policies you can paste in.
Screaming Frog has let you run your own JavaScript on every rendered page since version 20. Most people still use it as a link checker. Here is how the seoSpider API actually works, the snippets we run on real crawls, and when the built-in AI tab is the better tool.
Google renders your JavaScript. ChatGPT, Claude and Perplexity do not. That one fact changes what a JavaScript SEO audit has to check in 2026. Here is how Google's pipeline works, how to see exactly what it rendered, and the fixes we keep making on React, Next.js, Vue and Angular sites.
The most common hreflang failure we see on casino sites has nothing to do with the tags. It is a geo-block that hands Googlebot a 403 because it crawls from the US. This guide covers codes, x-default, cross-domain licence setups, mirrored markets, the three implementation methods with working examples, and what to test with now that Search Console's report is gone.
Get new articles in this hub the day they ship. No spam, unsubscribe anytime.
Start with a free SEO review. We will pull the data and tell you the highest-impact move in your specific situation.
Get a free SEO review