Most SEO advice on indexing is cargo cult behaviour. Someone observed that requesting indexing seemed to speed things up, published it as a tip, and it became received wisdom. The problem is nobody isolated the variable. Nobody compared requested vs non-requested pages on the same domain, at the same time, with equivalent content. We did. This article documents what Google's indexing request tool actually does, what the public data shows, how we designed the experiment, and what we are measuring. The first results will be published when the 30-day observation window closes — the slot is clearly marked below.
What does "Request Indexing" in Google Search Console actually do?
Requesting indexing submits a specific URL to Google's crawl queue, signalling that the page exists and is ready to be crawled. It does not guarantee crawling, and it does not guarantee indexing. Google treats it as a priority signal, not an instruction. The official documentation states that the tool "asks Google to crawl your URL" — the word asks is doing significant work in that sentence. The mechanism sits inside Google Search Console under the URL Inspection tool. You paste a URL, wait for the inspection to complete, and click "Request Indexing." Google's systems then add the URL to a crawl queue with elevated priority relative to URLs discovered through natural link-following. What happens after that is less documented. Google has not published data on how much priority elevation the request produces, how long the elevated status lasts, or whether it affects ranking speed once the page is indexed — only whether and when the page gets crawled. Those downstream questions are what this experiment tests.
What does the public data say about manual indexing requests?
The SEO community's position on indexing requests splits into two camps and neither has controlled data behind it. The first camp treats requesting indexing as mandatory — something to do within minutes of publishing every new article. The reasoning is reasonable: why wait for Googlebot to discover a page by following links when you can tell it the page exists immediately? On a new domain with few inbound links, natural discovery can take weeks. The second camp argues the effect is overstated, particularly for sites that already have a sitemap submitted to GSC. Google crawls submitted sitemaps regularly, which means new URLs appearing in the sitemap get discovered within days regardless of whether indexing was manually requested. The request, in this view, is redundant for any site with a functioning sitemap. Google itself has been measured about what the tool does. John Mueller confirmed in multiple public discussions that the tool sends a crawl request but provides no guarantees on timing or indexing outcome. He has also noted that for sites publishing content regularly, Googlebot tends to increase its crawl frequency organically — reducing the marginal value of manual requests over time. Neither camp has run a controlled test on new, low-authority domains — which is the context most relevant to content site builders starting from zero. That is the gap this experiment addresses.
How did we set up the experiment?
We published 20 articles on a photography niche site with a domain age of under 12 months, a domain rating below 10, and a Yoast-generated XML sitemap already submitted to Google Search Console. These conditions represent a typical new content site — low authority, no significant backlink profile, sitemap in place. We split the 20 articles into two matched groups of 10 at the point of publication: Group A — Requested indexing: Immediately after publishing each article, we pasted the URL into GSC URL Inspection and clicked Request Indexing. We did this within 5 minutes of the article going live. Group B — Natural discovery: We published the articles with no indexing request. No GSC action was taken. The articles were accessible via the sitemap, internally linked from the blog index page, and linked from one relevant existing article each. No other promotion. Matching criteria between the two groups: similar word counts (1,200 to 1,500 words each), same author, same schema markup (Article + FAQPage on all 20), same internal linking depth (2 clicks from homepage), published across the same two-week window. The single variable: whether a manual indexing request was submitted within 5 minutes of publication.
What metrics are we measuring?
We defined the measurement criteria before starting the experiment to avoid cherry-picking after the results arrived. Four metrics are being tracked for every article in both groups: Days to first crawl. The date Google first crawled each article, identified via GSC URL Inspection — the "Last crawl" date shown when you inspect a URL. Measured every 3 days for the first 30 days. Days to first impression. The date each article first appears in GSC Performance data with at least one impression. A page generating impressions has been indexed and is being served in some search results, even if not yet clicking. Measured daily via GSC Performance filtered by URL. Average position at Day 30. The average ranking position across all queries for each article at the 30-day mark. Pulled from GSC Performance with date range set to the full 30-day window. Total impressions at Day 30. The cumulative impressions for each article over the first 30 days. A secondary metric to average position — a page can rank at position 40 for a high-volume query and generate more impressions than a page ranking at position 12 for a low-volume one.
How to run this experiment on your own site
This experiment requires no additional tools beyond Google Search Console. Here is the exact process step by step. Step 1 — Prepare your articles. Write 10 articles minimum. They need to be matched on word count, topic specificity, internal linking depth, and schema markup. The closer the match, the cleaner the result. Do not use articles that already exist — publish all 20 fresh on the same day or within the same week. Step 2 — Split into two groups before publishing. Decide which 10 will be Group A (requested) and which 10 will be Group B (natural) before you publish anything. Write the URLs in a spreadsheet now. Do not decide after publishing based on which ones you want to favour. Step 3 — Publish Group A and immediately request indexing. Publish a Group A article. Open a second tab: go to Google Search Console → URL Inspection → paste the exact URL of the article you just published → wait for inspection to complete (20 to 40 seconds) → click "Request Indexing" → wait for confirmation → record the time in your spreadsheet. Repeat for all 10 Group A articles. Do this within 5 minutes of each publication. Step 4 — Publish Group B with no action. Publish all Group B articles. Do nothing in GSC. Do not inspect the URLs. Do not request indexing. Record the publication date and time only. Step 5 — Set up tracking in your spreadsheet. Create one row per article. Columns: URL, group (A or B), publish date, first crawl date, first impression date, Day 30 average position, Day 30 total impressions. Leave the last four columns blank until data arrives. Step 6 — Check GSC every 3 days for the first 2 weeks. Go to URL Inspection for each article. Note the "Last crawl" date when it appears. The moment it shows a crawl date, record it in your spreadsheet. After Day 14, switch to weekly checks — crawl frequency stabilises by then for most new content. Step 7 — Pull Day 30 data. At exactly 30 days after the publication date, go to GSC → Performance → set date range to the 30-day window → filter by each URL → record average position and total impressions for every article in both groups. Export to CSV for your records. Step 8 — Calculate the difference. For each metric, calculate the Group A average and the Group B average. The percentage difference tells you whether requesting indexing produced a measurable effect. If the difference is under 10 percent in either direction, the result is inconclusive at this sample size.
What results are we seeing so far?
This article will be updated on a regular basis. Make sure to follow to find the end results We are currently at Day 0 of the 30-day measurement window. Preliminary observations from the first two GSC checks: We are currently tracking both groups through GSC URL Inspection every 3 days. We will publish the first data point here when we reach Day 14 — the earliest point at which a meaningful pattern typically becomes visible on a new domain. Check back on July 19th or subscribe for the update. One early observation worth noting: the rate at which Group B articles are appearing in the sitemap crawl vs requiring Googlebot to follow internal links is relevant to interpreting whatever results emerge. We are documenting this alongside the primary metrics.
What we expect to find — and why we might be wrong
Our hypothesis going into this experiment: requesting indexing will produce faster first-crawl dates for Group A articles but will show no statistically meaningful difference in average position or total impressions at Day 30. The reasoning is that indexing speed and ranking speed are separate variables. Getting crawled faster does not change how Google evaluates the content once it has been crawled. A page that gets crawled on Day 2 and ranks at position 35 is not meaningfully different from a page that gets crawled on Day 12 and ranks at position 35. Where we might be wrong: if requesting indexing produces significantly faster first-impression dates, that gives Group A articles a longer window to accumulate ranking signals within the 30-day measurement period. A page generating impressions from Day 3 has 27 days of signal accumulation. A page generating impressions from Day 15 has only 15. On a competitive query, that head start may matter. We will know which scenario played out at Day 30.
What are the limitations of this experiment?
Three limitations to state clearly before the results arrive. Sample size. Twenty articles is sufficient for directional findings. It is not sufficient for statistical significance. We are identifying a pattern, not proving a law. Single domain. This experiment runs on one photography niche site. Results on a higher-authority domain, a different niche, or a site with a different crawl frequency baseline may differ. Sitemap dependency. All 20 articles appear in the Yoast-generated sitemap submitted to GSC. The experiment is therefore testing the marginal value of a manual request on top of sitemap discovery — not whether requesting indexing works in the absence of a sitemap. Sites without a sitemap may see a larger effect.
Full Results — Day 30
This section will be updated with complete data on August 9th 2026. The update will include the average days-to-first-crawl for both groups, average days-to-first-impression, average position at Day 30, and total impressions comparison. Screenshots from GSC will be included. If you want to be notified when the results are published, use the contact page to send us your email with the subject line "Experiment 009 results."
FAQs
What does requesting indexing in Google Search Console do?
Requesting indexing submits a specific URL to Google's crawl queue with elevated priority. It signals that the page is ready to be crawled. It does not guarantee crawling or indexing, and it does not affect how Google evaluates the content once it has been crawled. Google describes it as asking for a crawl, not instructing one.
Does requesting indexing speed up Google rankings?
Requesting indexing may speed up the crawl date, which in turn produces faster first impressions in search results. Whether faster crawling translates to higher rankings at 30 days is what this experiment tests. Our hypothesis is that crawl speed and ranking speed are separate variables, and that the content quality and on-page signals matter more than whether indexing was manually requested.
Does a submitted XML sitemap make indexing requests unnecessary?
Google crawls submitted sitemaps regularly, which means new URLs in the sitemap are discovered without manual requests. The question is whether requesting indexing provides a meaningful additional speed advantage on top of sitemap discovery. This is one of the specific conditions our experiment controls for — all test articles appear in the sitemap regardless of group assignment.
How do you check if Google has indexed a page?
Go to Google Search Console, click URL Inspection, and paste the page URL. If the page shows "URL is on Google" with a last crawl date, it has been indexed. If it shows "URL is not on Google," it has not been indexed yet. You can also search Google directly using the operator site:yourdomain.com/exact-url — if the page appears in results, it is indexed.
How long does it take Google to index a new article on a new domain?
On a new domain with a submitted XML sitemap and at least one internal link pointing to the article, first crawl typically occurs between 3 and 14 days after publication. First impressions in Google Search Console typically follow 2 to 5 days after the first crawl. Domains with higher crawl frequency established through regular publishing may see faster indexing on subsequent articles.
