Content cannot rank on a page Google never finished reading.

Everything that determines whether a search engine can reach, render, understand and trust your pages — crawling, indexing, canonicals, redirects, speed, mobile rendering and structured data. It is separate from content and links, and it comes first because neither of those works without it.

The usual causes, in order: blocked by robots.txt or a noindex tag, a canonical pointing elsewhere, judged duplicate of another page, content that only exists after JavaScript runs, or simply not discovered because nothing links to it. Search Console’s coverage report names which one it is.

Yes, though less than people assume as a direct factor. Its larger effect is indirect: slow pages lose visitors before they read anything, which shows in every behavioural signal. On mobile, where Google measures, the difference between a two-second and a six-second load is commercially significant regardless of ranking.

It rarely changes rankings by itself. What it does is make you eligible for richer results — FAQs, breadcrumbs, products, reviews — and it tells engines unambiguously what a page is, which increasingly matters for AI-generated answers. It is cheap to add and worth having.

It can be. If content is rendered only in the browser, crawlers may see an empty shell. Server-side rendering or pre-rendering solves it. The way to know is to fetch the page as Google does and look at what actually comes back, rather than assuming either way.

A full one annually, and always before and after a redesign, migration or platform change. Beyond that, watching Search Console coverage monthly catches most regressions early — they usually arrive through ordinary content edits rather than dramatic events.