React and Next.js in Vibe-Coded Websites: 1,072 Domains
React and Next.js were the most frequently detected technologies across 1,072 VCL domains. Their overlapping counts describe website stacks, not a head-to-head race.
Updated November 1, 2026. This article uses dataset v10, with a November 1 cutoff and measurements recorded through October 31. This is a new frozen edition; changes in sample membership, recorded classifications and measurement timing are not within-project growth.
React appeared on 488 measured custom domains and Next.js on 484 in VCL’s November 2026 report. Both were detected on roughly 45% of the 1,072 domains with a successful technology lookup.
Those are the two most frequently detected technologies in the report’s framework table. But their near-equal counts are not a head-to-head comparison: the categories overlap, and the same domain can contribute to both.
What was detected
The report identifies 1,145 eligible unique custom domains. DataForSEO technology lookups succeeded for 1,072, or 93.6%; the remaining domains are outside this table’s denominator.
| Detected technology | Domains | Share of 1,072 successful lookups |
|---|---|---|
| React | 488 | 45.5% |
| Next.js | 484 | 45.1% |
| Astro | 50 | 4.7% |
| jQuery | 25 | 2.3% |
| Express | 23 | 2.1% |
| jQuery Migrate | 16 | 1.5% |
| Nuxt.js | 11 | 1.0% |
| Vue.js | 11 | 1.0% |
Only technologies detected on at least five domains are shown. Each name counts once per domain, even if the provider places it in several categories. Successful lookups with no detected technology remain in the denominator.
A website stack is not an AI-tool history
The table comes from provider observations of public websites, not builders selecting their coding assistants. It cannot tell us whether a React site was created with Claude, Cursor, another assistant or substantial manual coding. VCL’s reported AI-tool analysis answers a separate question.
Nor can the two leading counts reveal exactly how many domains used both technologies: that requires an intersection, which this table does not publish. Adding their percentages would double-count any overlap.
These findings describe successful lookups within a selected VCL sample, not global framework adoption. A missing detection is not proof of absence, and the provider’s website observation may predate VCL’s collection date. The median collection was 25.7 days old at cutoff, and the oldest was 74.7 days old. The result is a documented technology footprint, not an exhaustive source-code audit.
Data and source. State of Vibe Coding 2026, Dataset v10: detected frameworks, cutoff November 1, 2026 at 00:00 UTC. The methodology explains coverage, detection rules and observation dates.
See the full State of Vibe Coding report for the accompanying infrastructure and performance measurements.