rank.fast

Four ways into Google's index, raced on a day-old domain

● this URL is being tracked on the live log from the moment of publication

Thirty-two hours ago this website did not exist as far as Google was concerned: a domain registered a year ago but never used, zero inbound links, zero crawl history. Since then, every page we published has been pushed into Google's index through a different route, timed to the second. All four landed. Here is the complete dataset.

The setup

Four URLs, four acceleration methods. Three pages were published at the same moment (2026-08-21 18:04 UTC), one joined later. Each got exactly one treatment:

Crawl timestamps come from our own server logs with the crawler's IP verified against Google's reverse DNS, not from anyone's dashboard. Indexing was confirmed by observing the URL live in Google search results, the probabilistic tier of our verification methodology.

The results

Priority route Submitted 18:53:52. Googlebot arrived 2m 10s later. Live in search results within 4 minutes of submission.
Free GSC request Requested 18:50. Googlebot arrived in 77 seconds, the fastest crawl response of the day. Indexed roughly 2.5 to 3.5 hours later.
Standard route Submitted 18:54. First crawl 2.5 hours later; still unindexed at the 7-hour mark, at which point we escalated it (below), so its natural time-to-index went unmeasured. This post is its clean rerun.
Expedited escalation Two URLs, submitted 01:47. Googlebot arrived in 9 seconds. Both. Live in search results within 2 minutes.

What we learned

What this proves, and what it doesn't

It proves the routes work, repeatably, on a domain with nothing going for it. It doesn't prove a success rate (one domain, single URLs per route: we'll quote rates when we've measured them on volume), and indexed is not ranked: getting into the index is admission, not placement. This post itself went through both the standard and expedited lanes, so the standard route's solo time-to-index is still an open measurement for a future post. Every timestamp behind this article is on the live log, raw data at /data/crawl-log.json.