Shwetank Ojha
Technical SEOIntermediate

Crawling

Crawling is the process by which search engine bots like Googlebot visit web pages, read their content, and follow links to discover more pages — the first step before a page can be indexed and ranked.

5 June 20267 min read

The Ranking Room · Max & Alex

Crawling — Max & Alex break it down

A ~-minute deep-dive on everything you need to understand about Crawling — context, strategy, and what it means for your SEO in 2026.

0:00
--:--

Like this episode? · Subscribe on Spotify and Apple Podcasts

Episode transcript

Auto-generated transcript · The Ranking Room with Max & Alex

MAXBefore Google can rank your page, it has to find it. Before it finds it, it has to crawl it. And this is where a surprising number of websites quietly fail before anyone even knows there's a problem.

ALEXCrawling is the process where Google's automated programs — primarily Googlebot — discover and read pages on the web. Googlebot works continuously, following links from page to page, reading content, and storing it for indexing.

MAXIt starts from a list of known URLs, either previously crawled pages or URLs submitted via Google Search Console. It visits each page, reads the HTML, follows the links it finds, and comes back periodically.

ALEXHow often it comes back depends on two things: how frequently your site changes, and how much crawl authority Google assigns to your domain. High-authority sites with fresh content get crawled more often. New or low-authority sites wait longer between visits.

MAXThere's also something called crawl budget that matters at scale. For large sites, Google allocates a finite number of crawl requests. If you have thousands of pages with thin or duplicate content, Google burns that budget on pages that will never rank.

ALEXAnd that means important content gets left undiscovered. Low-value pages don't just fail to rank — they slow down the crawling of pages that actually matter. Content quality and crawl efficiency are directly connected.

MAXThe mistakes that actually block crawling are fairly consistent. Robots dot txt rules that accidentally block Googlebot from key pages is the most catastrophic. I've seen live production sites blocking Googlebot from their entire content directory because a dev-mode rule was never removed.

ALEXFive-second fix. Months of invisible damage. The frustrating part is there's no visible error — everything looks fine to users. It only shows up when you look at Google Search Console and see zero impressions.

MAXNoindex tags on pages that should be indexed — same issue, different mechanism. Often left over from staging environments. The page exists, users can reach it, but Google has been explicitly told not to include it.

ALEXJavaScript-heavy pages are another common crawl problem. If critical content only loads after JavaScript executes, Googlebot may miss it on the first pass. It does process JavaScript, but not immediately — there's a rendering delay.

MAXServer-side rendering is significantly more crawler-friendly. If your framework renders content client-side only, it's worth understanding what Googlebot actually sees versus what a browser shows. Those can be very different things.

ALEXFaceted navigation and URL parameters are the fourth issue. E-commerce sites especially — filter combinations generate thousands of near-duplicate URLs that create effectively infinite crawl loops. Canonicalization and parameter handling in Search Console are how you address that.

MAXHow do you check? Google Search Console. The Coverage report tells you which pages are indexed, which are found but not indexed, and which Google can't reach at all.

ALEXThat report should be a regular check, not something you look at when rankings drop. Catching crawl issues early prevents compounding problems.

MAXTakeaway: crawl health is the foundation that makes everything else matter. If Google can't crawl it, Google can't rank it. Fix crawl issues before anything else.

ALEXThat's The Ranking Room. I'm Alex.

MAXAnd I'm Max. See you next time.

Crawling — featured image
Crawling is how search engines find your pages. Bots like Googlebot visit a page, read it, and follow its links to discover more pages. No crawl → no index → no rankings.

Before Google can rank your page, it has to find it. Before it can find it, something has to go looking.

That something is a crawler. Here's how it works — and the silent mistakes that keep your best pages invisible.

What is crawling in SEO?

Crawling is the first step in a three-stage pipeline: crawl → index → rank.

The three-stage search pipeline: crawling, then indexing, then ranking
Crawl → Index → Rank

A crawler (or "bot") visits a URL, reads the HTML, and follows the links it finds to discover more pages. Google's crawler is Googlebot. Bing uses Bingbot. Apple uses Applebot. And now there's a new layer — AI crawlers like OpenAI's GPTBot, Anthropic's ClaudeBot, and Perplexity's PerplexityBot, each reading the web to feed its own product.

The rule never changes. A page Googlebot has never visited cannot be indexed. A page that is not indexed cannot rank. Crawlability comes before everything else.

Crawling vs indexing: what's the difference?

This is the most common mix-up in technical SEO, so let's settle it.

  • Crawling is Googlebot finding and reading your page.
  • Indexing is Google deciding the page is worth storing in its database.

They are not the same step. A page can be crawled and still never indexed — if Google judges the content too thin or duplicate to keep.

Short version: crawling is discovery, indexing is the decision, ranking is the reward.

How crawling works (step by step)

Googlebot doesn't wander randomly. It runs a simple loop:

  1. Start with known URLs — pages it has crawled before, plus URLs from your XML sitemap.
  2. Fetch the page — it requests the URL and reads the HTML.
  3. Render the page — it runs CSS and JavaScript in a headless browser to see what a real user would see.
  4. Extract every link on the page.
  5. Queue those links for future crawling — then repeat.

That loop is how a single homepage link can eventually lead Google to every page on your site. It's also why orphan pages — pages with no links pointing to them — get missed entirely.

Googlebot, in one line

Google doesn't crawl with a single bot. Googlebot is a family of crawlers — a primary Smartphone crawler that does most of the work under mobile-first indexing, a Desktop crawler, and specialist bots for images, news, and video. The practical takeaway: the version Google usually crawls and indexes is your mobile version. Full breakdown on the Googlebot page.

What controls how often Google crawls you

Googlebot doesn't give every site the same attention. Four things decide how much and how often it crawls:

  • Crawl budget — the number of pages Googlebot will fetch in a given window. Under a few thousand pages? You can ignore this. Large e-commerce site? It matters.
  • Update frequency — pages that change often get re-crawled more often. Stale pages get visited less.
  • Server speed — a slow server makes Googlebot throttle back. A fast one invites deeper, more frequent crawling.
  • Page authority — well-linked pages get re-crawled fast. A brand-new page with no internal links can wait weeks for its first visit.

Here's a stance worth planting a flag on: crawl-budget anxiety is misplaced on most sites. Teams obsess over budget on a 400-page brochure site when their real problem is orphan pages and a slow server. If you're under ~10,000 URLs, stop tuning crawl budget and go fix discovery instead.

From the field: A mid-size e-commerce site had healthy Crawl Stats — thousands of requests a day — yet a whole category of roughly 600 product pages sat unindexed. The budget was fine. The problem was discovery: those products were only reachable through a JavaScript filter Googlebot wasn't expanding, so not a single crawlable link pointed to them. Adding plain <a href> links from the category page got them indexing within a week.

What blocks Googlebot — the silent killers

Crawl problems rarely announce themselves. Your site can look perfect to visitors while being invisible to Googlebot. The usual culprits:

  • robots.txt mistakes — The file at yourdomain.com/robots.txt tells crawlers where they can and can't go. One wrong line can block your entire site. It happens more often than you'd think.
  • The noindex + robots.txt trap — A noindex tag tells Google not to index a page. But Googlebot has to crawl the page to read that instruction. If robots.txt also blocks crawling, Google never sees the noindex — and the page can stay indexed anyway. Two well-meaning rules cancel each other out.
  • JavaScript delays — Googlebot can run JavaScript, but it's slower than reading plain HTML. Heavily JS-dependent pages get crawled later, sometimes much later.
  • Crawl traps — Faceted navigation, session IDs in URLs, or calendar links with endless dates create near-infinite URLs. Googlebot burns its budget on junk instead of your real pages.

First, diagnose: crawl problem or index problem?

When a page isn't showing up, don't guess. Ask one question first: was the page never visited (a crawl problem), or visited and then excluded (an index problem)? The two have completely different fixes — and most wasted audit time comes from solving the wrong one.

  • Page never crawled → look at discovery: internal links, sitemap, robots.txt, server errors.
  • Page crawled but not indexed → look at quality: thin content, duplication, canonical conflicts, noindex.

Search Console's URL Inspection Tool answers this in about ten seconds.

Going deeper: log-file analysis

Crawl Stats in Search Console is a summary. Your server logs are the source of truth — every real request Googlebot made, in order.

Pull a sample and you can answer questions no dashboard will: Which sections does Googlebot actually visit, and which does it ignore? How much budget is being spent on parameter junk versus money pages? Is the smartphone or desktop crawler hitting you, and what status codes (200 / 3xx / 4xx / 5xx) is it getting back?

From the field: On one large catalog site, server logs showed roughly 40% of Googlebot's daily requests landing on faceted-filter URLs that returned near-duplicate pages. Money pages were getting crawled about once a week. Blocking those parameter patterns in robots.txt redirected the budget — within a month, key product pages were being recrawled every day or two.

For most small sites this is overkill. For a large site with a real crawl-efficiency problem, it's the only honest way to see what's happening.

AI answer engines run their own crawlers — and you can control them separately from Google.

You can allow or block GPTBot, ClaudeBot, and PerplexityBot in robots.txt, independent of Googlebot. Here's the tradeoff: blocking them protects your content from training, but it also removes you from AI-generated answers. For most publishers the smart move is to allow the search-oriented AI crawlers that cite you, and be more selective about pure training crawlers.

Worth noting for Google specifically — AI Overviews and AI Mode don't use a separate index. They draw from the same content Googlebot already crawled and indexed. So if Googlebot can't reach a page, no amount of GEO optimization will get it cited. Crawlability is the floor for AI visibility, not a side quest.

How to check if your site is being crawled

Two fast diagnostics:

  • Google Search Console → Crawl Stats report — shows how often Googlebot visits, what it fetched, the host status, and any server errors it hit. Watch the response-code breakdown and the "by Googlebot type" split.
  • URL Inspection Tool — for any single URL, shows the last crawl date and whether Google could access the page. Click "Request Indexing" to nudge a new one.

Frequently asked questions

How do I get Google to crawl a new page?

Two ways. Fast: open the URL Inspection Tool in Search Console and click "Request Indexing." Reliable: add internal links to the new page from pages that already get crawled often. Googlebot follows links — so give it links to follow.

What is crawl budget, and should I worry about it?

If your site is under ~1,000 pages and loads quickly: no. If you run a large e-commerce site where filters generate thousands of URL combinations: yes. Block the low-value URL patterns and point strong internal links at the pages that matter.

Can I block AI crawlers from my site?

Yes — disallow GPTBot, ClaudeBot, or PerplexityBot in robots.txt. Just know the cost: block them and you drop out of their AI answers. For most sites, allow the crawlers that cite you and be choosier about the ones that only train.

What's the difference between a crawler and a spider?

Nothing — they're the same thing. "Crawler," "spider," and "bot" all describe the same automated program that reads web pages and follows links.

Real-world example

A new SaaS product page gets zero organic traffic despite excellent content. An audit finds the cause: a staging site's robots.txt was accidentally pushed to production, blocking Googlebot from the entire domain. The fix — correct the robots.txt and resubmit the sitemap in Search Console — restores crawl access, and the pages start appearing in search within days.

SO

Shwetank Ojha

SEO & AIO Strategist

Helping businesses dominate search results through data-driven SEO strategies, AI-powered optimization, and content systems that compound growth.