What is Crawl-Render-Index Pipeline?
The three stages between publishing and ranking: fetch the HTML, render resources including JavaScript, then select and store the page. Failures at different stages need different fixes, so audits must identify which stage broke.
Example
A page crawled but invisible in the index with content only in client-rendered widgets points at the render stage: check blocked scripts and render timeouts before rewriting copy.
Frequently asked questions
Does Google render JavaScript?
Yes, fully for eligible pages, but with a delay tail. Time-sensitive content should not depend solely on client rendering.
Related terms
Crawling
How search-engine bots discover pages by following links, sitemaps, and directives. If a URL is never crawled, it cannot be indexed no matter how good its content is.
Indexing
Storing and organizing crawled pages so they can be retrieved for queries. Indexing is selective: crawled does not mean indexed, and indexed does not mean ranking.
JavaScript SEO
Making client-rendered pages discoverable: crawlable links, server or prerendered critical content, unblocked resources, and unique URLs per state. Rendering usually happens, but slow tails hurt time-sensitive pages.
Technical SEO
The crawling, indexing, rendering, and performance work that lets search engines reach, understand, and serve your pages. It covers directives, architecture, speed, and structured data rather than words on the page.
Crawl Budget
The number of pages a search engine will crawl on a site in a given period, driven by server capacity and demand signals. Large or slow sites must spend it on indexable, valuable URLs.
Robots.txt
A plain-text file at the domain root telling compliant crawlers which paths they may fetch. It controls crawling, not indexing: blocked URLs can still be indexed by URL if linked.