Short answer
Chrome has added experimental Core Web Vitals fields to CrUX, its real-user data report, that also count in-app page changes in single-page applications. Stable scores do not change for now. Sites that reload the page on every click will see no difference; sites that swap pages with heavy JavaScript can compare both versions.
Highlights
- The new fields are experimental versions of LCP, INP and CLS, available in BigQuery, the CrUX API and the History API.
- Most sites are unaffected: most have little soft navigation traffic.
- Search Console will adopt the new data once the metrics leave experimental status.

2 min readAuthor: UNIT Journal EditorEditor-in-chief: Uğur Deniz İlhan
Chrome has added experimental versions of three Core Web Vitals to the Chrome User Experience Report (CrUX). They count soft navigations: the in-app page changes a single-page application (SPA) makes without a full reload. Search Engine Journal reports that the data went live with the release published on 13 October in BigQuery, the CrUX API and the History API, and that CrUX Vis has a new toggle.
Why was this change needed?
Until now CrUX measured only an SPA's first load; interactions and layout shifts from later in-app changes were attributed to the landing URL. Under the new method, when both the URL and the visible content change, Chrome treats it as a separate navigation and ties the metrics to the destination URL.
Which sites will notice?
According to Google's data, most origins in CrUX have very little soft navigation traffic; the sites affected are the relatively few that depend heavily on SPAs. In Annie Sullivan's words: "If your site doesn't use JavaScript to dynamically swap out page content and update the URL without a full browser reload, you shouldn't expect to see any changes in your metrics."
On sites dominated by soft navigations all three metrics improve. That is not because SPAs are faster overall but because follow-up clicks are faster on any site. INP is now measured per page view, and CLS groups layout shifts by view rather than by session.
What is the timeline for Search Console?
Stable scores stay the same for now. Chrome aims to end the experimental status in May 2027, and Search Console will adopt the new data after that. The November CrUX release is expected to add soft-navigation versions of FCP and navigation types.
What should companies do?
The source gives no Turkey-specific data, but teams building e-commerce and corporate sites as SPAs with frameworks such as React or Vue can take these steps:
- Work out from your analytics what share of page views are full loads and what share are in-app navigations.
- If you are SPA-heavy, use the "Include soft navigations" option in CrUX Vis to compare both versions side by side and note which metric changes.
- If your site loads a full page on every click, nothing needs to change; keep up your current Core Web Vitals work.
- Do not make decisions on experimental scores; Chrome expects month-to-month shifts, so rely on the stable score until Search Console adopts the new data.
Frequently asked
- What is a soft navigation?
- When a user action changes both the URL and the visible content without a full page reload, Chrome counts it as a soft navigation. Single-page applications use this approach.
Sources
- Search Engine Journal ·
Follow UNIT Journal
What's new in search, AI and technology, in your feed every day.


