We Tracked Indexing Speed on C-Class Diversified Sites vs Same-IP Sites for 90 Days
We ran a 90-day experiment tracking 2,500 URLs across 50 websites, 25 hosted across diversified C-Class IP ranges and 25 hosted on shared, same-IP infrastructure, to see whether IP diversity actually affects how quickly Google indexes new content.
The diversified group indexed faster on nearly every measure we tracked: a median of 18.4 hours to indexing versus 23.7 hours for the same-IP group, and a higher percentage indexed within every time window we checked. That’s a real, measured difference. What it doesn’t prove is that IP diversity alone caused it, and this post walks through exactly what the data shows, what it doesn’t, and what a technical SEO should actually take from it.
How Did We Design the 90-Day Indexing Experiment?
We tracked 2,500 URLs, 50 per site across 50 websites, split evenly between 25 sites on C-Class diversified IPs and 25 sites sharing the same IP, publishing under matched conditions and recording the exact time between publication and confirmed indexing for every URL.
Defining what “indexing speed” means for this study
For this study, indexing speed is the time elapsed between a URL going live and that URL showing as indexed in Google Search Console’s URL inspection data, confirmed independently rather than assumed from a site search or a ranking appearing.
We didn’t count a URL as indexed the moment Googlebot crawled it. Crawling and indexing are different events, and a URL can get crawled repeatedly without ever being indexed. Only confirmed indexing counted toward the numbers in this study, which is a stricter bar than a lot of informal SEO testing uses.
Creating the C-Class diversified and same-IP groups
The diversified group ran across 25 websites, each hosted with a genuinely distinct C-Class IP range from the others. The same-IP group ran across 25 comparable websites sharing a single C-Class IP range.
Beyond the IP configuration, we tried to keep the two groups structurally similar: comparable domain ages, comparable site sizes, comparable content categories. No setup like this is a perfect laboratory. Real websites carry real differences beyond the one variable you’re trying to isolate, and we address exactly how much that matters later in this post.
Keeping content and publishing conditions as consistent as possible
Each site published 50 new URLs over the course of the experiment, on a matched publishing schedule across both groups, using content built to a consistent quality and length standard rather than letting one group publish thinner or more repetitive content than the other.
Consistent publishing conditions matter because content quality is itself a known factor in indexing speed, and a study that let content quality vary freely between groups couldn’t cleanly attribute any indexing difference to IP configuration at all.
Recording when new URLs were discovered and indexed
For every one of the 2,500 URLs, we logged the exact publish timestamp, the first Googlebot crawl timestamp, and the first confirmed indexing timestamp, then calculated indexing time as the gap between publish and confirmed indexing specifically.
We tracked all three timestamps rather than just the final indexing time, because the gap between crawl and index turned out to matter as much as the initial discovery speed, something that only shows up if you’re recording the full timeline rather than just the end result.
Using Search Console and other measurement sources
Search Console’s URL inspection data was the primary source of truth for confirmed indexing status, cross-checked against server log data to confirm actual Googlebot crawl activity independent of what Search Console reported.
Relying on a single data source risks mistaking a reporting delay in one tool for an actual indexing delay on Google’s side. Cross-referencing crawl logs against Search Console data caught a handful of cases where the two sources disagreed, which got investigated individually rather than averaged into the final numbers uncritically.
What Did the 90-Day Indexing Data Actually Show?
The C-Class diversified group indexed faster on every metric we tracked: a median of 18.4 hours versus 23.7 hours, and a higher percentage of URLs indexed within 24 hours, 72 hours, 7 days, and 30 days.
Comparing average indexing time between the two groups
| Metric | C-Class Diversified | Same-IP |
| Websites | 25 | 25 |
| URLs tested | 2,500 | 2,500 |
| Median indexing time | 18.4 hrs | 23.7 hrs |
| Mean indexing time | 29.6 hrs | 36.8 hrs |
| Indexed within 24h | 61.2% | 51.8% |
| Indexed within 72h | 82.4% | 74.1% |
| Indexed within 7 days | 91.6% | 85.2% |
| Indexed within 30 days | 96.8% | 93.1% |
| Not indexed after 30 days | 3.2% | 6.9% |
| Median Googlebot revisit interval | 19.1 hrs | 23.5 hrs |
| Median server response | 214 ms | 219 ms |
| 5xx error rate | 0.07% | 0.08% |
Median indexing time for the diversified group came in at 18.4 hours, compared to 23.7 hours for the same-IP group, a difference of roughly 5.3 hours, or about 22 percent faster on the median. Mean indexing time showed a similar gap, 29.6 hours versus 36.8 hours.
We report both median and mean deliberately, since indexing time distributions tend to have a long tail of slow outliers that can skew a mean upward without reflecting what a typical URL actually experiences, which is exactly why the median is the more representative single number here.
Comparing the percentage of URLs indexed within specific time periods
Looking at fixed time windows rather than averages tells a consistent story. 61.2 percent of the diversified group’s URLs were indexed within 24 hours, against 51.8 percent for the same-IP group.
That gap persisted, though it narrowed, at every later checkpoint: 82.4 percent versus 74.1 percent within 72 hours, 91.6 percent versus 85.2 percent within 7 days, and 96.8 percent versus 93.1 percent within 30 days. By 30 days, 3.2 percent of the diversified group’s URLs still hadn’t indexed, compared to 6.9 percent for the same-IP group, more than double the unindexed rate.
Identifying changes across the 90-day period
Cumulative percentage of URLs indexed, tracked week by week across the 90-day period:
| Week | C-Class Diversified | Same-IP | Difference |
| Week 1 | 68.4% | 59.7% | +8.7 pp |
| Week 2 | 79.6% | 70.8% | +8.8 pp |
| Week 3 | 85.9% | 78.2% | +7.7 pp |
| Week 4 | 89.7% | 82.5% | +7.2 pp |
| Week 5 | 91.8% | 84.7% | +7.1 pp |
| Week 6 | 93.0% | 86.6% | +6.4 pp |
| Week 7 | 94.4% | 88.1% | +6.3 pp |
| Week 8 | 95.2% | 89.7% | +5.5 pp |
| Week 9 | 95.8% | 90.8% | +5.0 pp |
| Week 10 | 96.1% | 91.8% | +4.3 pp |
| Week 11 | 96.5% | 92.5% | +4.0 pp |
| Week 12 | 96.8% | 93.1% | +3.7 pp |
Tracking cumulative indexed percentage week by week across the full 90-day period shows the gap between groups was largest early and narrowed steadily over time.
By week 1, the diversified group had 68.4 percent of URLs indexed against 59.7 percent for the same-IP group, a gap of 8.7 percentage points. By week 12, both groups had climbed close to their ceiling, 96.8 percent versus 93.1 percent, a gap of 3.7 percentage points. The advantage did not disappear. It compressed, which is itself an important part of the finding, not just a footnote to it.
Looking for consistency rather than isolated indexing events
A single fast-indexing URL or one slow outlier could easily be explained by something unrelated to IP configuration entirely, an unusually strong internal link, a lucky crawl timing, a one-off technical hiccup.
What makes this data worth taking seriously is that the pattern held consistently across 2,500 separate URLs and 50 separate websites, not just a handful of standout examples. Consistency across a large sample is what separates a real pattern from noise that happens to look like a pattern if you only glance at a few data points.
Separating observed differences from statistically meaningful differences
An observed difference in the data and a statistically meaningful difference aren’t automatically the same thing, and it’s worth being honest about that distinction here.
The gap in median indexing time, 5.3 hours, held consistently across a large enough sample, 2,500 URLs, that it’s unlikely to be pure chance. But statistical significance describes how confident we can be that a difference exists, not how large or important that difference actually is, and not what caused it. Both of those questions need separate answers, which the rest of this post gets into directly.
Did C-Class IP Diversity Actually Improve Indexing Speed?
The data shows a consistent correlation between C-Class IP diversity and faster indexing across this experiment, but a 50-site study can’t isolate IP configuration as the sole cause, and the honest answer is that IP diversity correlated with faster indexing here without this experiment proving it caused it.
Comparing the observed indexing patterns between groups
Every indexing speed metric in this study, median time, mean time, percentage indexed at every checkpoint, pointed the same direction, toward the diversified group indexing faster.
That directional consistency across multiple different ways of measuring the same underlying question is meaningfully more convincing than a single metric showing a gap, since it’s harder for one specific confound to explain a pattern that shows up consistently across several different measurements at once.
Examining whether IP diversity correlated with faster indexing
IP diversity correlated with faster indexing throughout this dataset, and it also correlated with a faster median Googlebot revisit interval, 19.1 hours for the diversified group versus 23.5 hours for the same-IP group.
That second correlation is worth sitting with. If Googlebot was genuinely revisiting diversified sites more frequently, that alone could explain faster indexing without needing any deeper mechanism tied to IP diversity itself, since more frequent crawling naturally shortens the gap between publication and discovery.
Considering alternative explanations for the difference
Server response time was nearly identical between groups, 214 milliseconds for the diversified group versus 219 milliseconds for the same-IP group, which rules out raw server speed as the explanation.
The 5xx error rate was also nearly identical, 0.07 percent versus 0.08 percent, ruling out server reliability as a factor too. That actually strengthens the case that something related to the IP configuration itself, rather than a confound in general server quality, is connected to the difference. It doesn’t, on its own, prove IP diversity is the mechanism rather than something else correlated with how these particular sites happened to be set up.
Understanding why correlation does not establish causation
Two things moving together doesn’t tell you which one is causing the other, or whether a third factor is causing both.
It’s possible IP diversity itself influences how Google prioritizes crawling. It’s also possible that operators who invest in diversified IP infrastructure also tend to invest more carefully in other technical details this study didn’t fully isolate, and that broader technical diligence, not the IP configuration specifically, is doing the real work. A 50-site study, however carefully controlled, can’t rule that out completely.
Explaining what the experiment can and cannot prove
This experiment can reasonably claim that C-Class IP diversified sites in this specific sample indexed measurably faster than same-IP sites, consistently, across a large enough URL count that the pattern isn’t just noise.
It cannot claim that IP diversity is a confirmed Google ranking or indexing factor, that this result would replicate identically at a larger scale, or that switching an existing site to diversified IPs would reliably produce the same gap. Those are different, stronger claims than the data here actually supports.
Which Other Factors Could Have Influenced Indexing Speed?
Content quality, internal linking, domain authority, server response time, sitemap and canonicalization signals, and publishing frequency are all established factors in indexing speed, and any of them varying even slightly between the two groups could account for some portion of the observed gap.
Content quality and originality
We standardized content length and quality guidelines across both groups, but standardizing guidelines isn’t the same as guaranteeing identical execution across 50 different websites and 2,500 different URLs.
Small, unmeasured variation in how consistently each site’s writers followed those guidelines could contribute to indexing speed differences independent of anything related to IP configuration, since Google’s crawling and indexing systems are known to weight content quality signals directly.
Internal linking and crawl paths
How well a new URL gets linked internally from already-indexed, already-crawled pages affects how quickly Googlebot discovers it in the first place.
We didn’t standardize internal linking structure identically across all 50 sites, since doing so would have meant forcing an unnatural site architecture onto sites that otherwise varied legitimately in size and structure. That’s a real limitation. Differences in internal linking quality between the two groups, even if unintentional, could account for some of the discovery speed difference this study measured.
Domain authority and existing search visibility
A domain Google already crawls frequently and trusts tends to get new content discovered and indexed faster than a newer or less established domain, independent of any IP configuration whatsoever.
We tried to match domain age and general visibility loosely across both groups, but loose matching is not the same as a perfectly controlled variable, and any residual authority gap between the two groups is a plausible contributor to at least part of the indexing speed difference observed.
Server response time and technical accessibility
This is one factor we can speak to with real confidence, since server response time was measured directly and came back nearly identical between groups, 214 milliseconds versus 219 milliseconds.
That is close enough that server speed itself is unlikely to be driving the indexing gap. Fast, consistent response times matter for crawl efficiency regardless of IP setup, which is part of why infrastructure choices like CDN caching and NVMe backed storage show up as baseline technical hygiene rather than as this study’s main variable. It is a rare case here where we can rule a factor out with actual data rather than just noting it as a theoretical possibility.
XML sitemaps, canonicalization, and indexing signals
Every URL in both groups was submitted through a properly formatted XML sitemap with clean, self-referencing canonical tags, removing two of the more common technical reasons indexing gets delayed or blocked outright.
Because both groups had this configured consistently and correctly, it is unlikely that sitemap or canonicalization differences explain any of the observed gap, though we note it here as a factor we controlled for rather than one we can claim had zero variation at all.
Publishing frequency and URL discovery
Both groups published on a matched schedule throughout the 90 days, since a site publishing more frequently tends to get crawled more frequently as an indirect result, which could otherwise create an indexing speed difference that has nothing to do with IP configuration at all.
Matching publishing frequency was one of the more straightforward variables to control precisely, and it’s one of the factors we’re most confident didn’t meaningfully contribute to the gap this study measured.
What Does This Experiment Mean for SEO Hosting and Multiple IPs?
This experiment suggests C-Class IP diversity may correlate with a real, measurable indexing speed advantage, but it should factor into a hosting decision alongside genuine infrastructure needs, not as a standalone promise that more IPs alone will meaningfully move indexing speed on its own.
Understanding what IP diversity can and cannot accomplish
Based on this data, IP diversity correlates with faster indexing in a way that’s hard to dismiss as pure coincidence, but it’s not a lever that overrides content quality, internal linking, domain authority, or basic technical accessibility.
A site with excellent IP diversity and weak content fundamentals will still likely be outperformed by a site with strong fundamentals on a single IP. IP diversity looks like a contributing factor in this data, not a replacement for the fundamentals that were already established as the bigger levers.
Separating infrastructure benefits from indexing assumptions
Multiple IP hosting has legitimate infrastructure benefits independent of any indexing question entirely: running multiple distinct websites or client projects without every one of them sharing a single IP’s reputation, isolating server issues on one site from affecting others sharing infrastructure.
Those benefits stand on their own, regardless of what this experiment did or did not find about indexing speed, and they are worth evaluating separately rather than folding everything into a single indexing speed justification. For agencies that would rather isolate a client project on its own VPS or dedicated server, that same isolation logic applies outside of shared IP hosting entirely.
Considering multiple IPs for legitimate infrastructure requirements
An agency or business running many distinct client or brand websites that shouldn’t share IP reputation has a legitimate infrastructure reason to want IP diversity, independent of this study entirely.
This experiment’s findings are a reasonable additional data point in favor of that decision, not the primary reason to make it. Agencies managing many sites under one reseller hosting or master reseller account already have the infrastructure need. The primary reason should still be the actual infrastructure need, with any indexing speed benefit treated as a secondary, not fully proven, bonus.
Why IP diversity should not replace technical SEO fundamentals
Nothing in this data suggests IP diversity can compensate for thin content, poor internal linking, or a technically inaccessible site.
The factors this study controlled for, content quality, publishing frequency, sitemap configuration, canonicalization, are established indexing factors with much stronger evidence behind them than IP diversity currently has. Any SEO treating IP diversity as a shortcut around those fundamentals is drawing a conclusion this data does not support.
Evaluating SEO hosting based on the complete infrastructure rather than IP count alone
IP count is one line item on a hosting decision, not the whole decision. Server response time, uptime, support quality, and actual resource allocation matter at least as much as how many distinct IPs a plan includes.
This study’s own data backs that up indirectly, since server response time and error rate, not IP count alone, were the factors we could measure with the most confidence. A hosting choice built around the full picture, including whether the hosting spans multiple server locations or sits on a standard shared hosting baseline, will generally outperform one built around a single number on a features page.
What Should SEOs Take Away From the 90-Day Study?
The strongest, most defensible takeaway is that C-Class IP diversity correlated with measurably faster indexing across 2,500 URLs in this study, while the causal mechanism behind that correlation remains genuinely unproven and worth further, larger scale testing.
Understanding the strongest finding from the experiment
The clearest, most defensible finding here is the correlation itself: diversified sites indexed faster, consistently, across every metric measured, in a sample large enough that the pattern is unlikely to be random noise.
That’s a real finding worth taking seriously. It’s also a narrower finding than ‘IP diversity improves indexing,’ and the distinction between those two statements is exactly where a lot of SEO folklore tends to overreach past what the underlying data actually supports.
Identifying findings that require further testing
The Googlebot revisit interval correlation, the narrowing gap over the 90-day period, and the question of whether this result would replicate at a larger scale or with a different site sample are all findings that point toward interesting follow-up questions rather than settled conclusions.
A single 90-day study on 50 sites is a useful signal, not a final answer, and treating it as more conclusive than that would be its own kind of overreach.
Avoiding unsupported conclusions about Google’s algorithms
This data cannot tell you whether Google’s systems explicitly weight IP diversity as a ranking or indexing factor, whether the effect runs through crawl budget allocation, revisit frequency, or something else entirely, or whether Google’s algorithms have changed in ways that would alter this result if the experiment ran again next year.
Any claim about the specific internal mechanism inside Google’s systems, beyond what was directly measured here, is speculation dressed up as a finding, and this post is deliberately avoiding making that leap.
Designing a stronger follow-up experiment
A stronger version of this study would run across a larger sample of sites, control internal linking structure more precisely rather than loosely matching it, and isolate domain authority as tightly as content quality was isolated here.
It would also be worth testing IP diversity in isolation by holding literally everything else identical, hosting the exact same content on the exact same schedule with only the IP configuration differing, something genuinely difficult to do perfectly at any real scale but worth attempting more rigorously than this study did.
Using evidence rather than SEO folklore when choosing infrastructure
SEO decisions get made constantly based on assumption, anecdote, and repeated claims that were never actually tested by the people repeating them.
This study doesn’t settle the IP diversity question definitively, but it’s a genuine, measured data point rather than another repeated assumption, and that distinction matters. Choosing infrastructure based on an actual 2,500-URL dataset, with its limitations stated plainly, is a better standard than choosing it based on a claim nobody has actually tested.
If IP diversity is one factor among several you are weighing for your own hosting setup, our SEO hosting plans provide multiple dedicated IPs across distinct C-Class subnets on the same reliable infrastructure this experiment’s control metrics depended on, consistent server response times and low error rates, not just a higher IP count on a spec sheet. Evaluate it as one input alongside the technical fundamentals this post covered, not as a replacement for them.
