If your rank tracker showed gaps, delays or odd numbers this week, there is a simple reason. Google requires JavaScript to use Search now. The change took effect around 15 January 2025. Browsers and bots that do not run JavaScript get a prompt to turn it on instead of a results page.
Here is the short version. Your own rankings did not change because of this. Your website does not need to change either. What changed is how hard it is for tools to collect Google results, and that affects the data many of us use every day. In this article I explain what happened, what Google said, why SEO tools broke, and what I would check right now.
What Changed in Google Search This Week
Until now, you could load a Google results page without JavaScript. You got a plainer page, but you still got results. That is no longer the case.
From around 15 January, if a browser has JavaScript turned off, Google asks the person to enable it before it will show results. The same thing happens to any simple script that fetches a results page as raw HTML. It does not get the full results it used to get.
JavaScript is the code that makes web pages interactive. Almost every normal browser runs it by default. So most searchers will never notice this change. The people who notice are:
- Users who turn JavaScript off for privacy or speed.
- People using text-only browsers or some older devices.
- Tools and scripts that read Google results automatically, which includes most rank trackers.
That last group is why the SEO world felt this one straight away.
Why Google Requires JavaScript Now
Google did not announce this on its blog. It explained the change in a statement to the press on 17 January 2025. A Google spokesperson said that enabling JavaScript allows Google to “better protect our services and users from bots and evolving forms of abuse and spam.” The spokesperson also said it helps Google provide the most relevant and up-to-date information.
Google gave two more points in that statement:
- Many Google Search features do not work properly without JavaScript, and the quality of results tends to drop.
- On average, fewer than 0.1% of searches are done by people who have JavaScript disabled.
So the official reason is protection against bots and abuse. JavaScript lets Google run checks inside the browser. A real browser passes those checks easily. A cheap script that just downloads HTML does not.
Under 0.1% sounds tiny, and as a share it is. But Google handles a huge number of searches every day. Even a fraction of a percent is still a lot of people. That is why some users with accessibility or privacy setups were unhappy about it.
My honest view: the bot-protection reason makes sense. Automated scraping of Google has grown a lot, and some of it is not friendly. I also think it is fair to say that making scraping more expensive suits Google in other ways. You do not have to pick one explanation. Both can be true at once.
Why SEO Tools Broke When Google Started Requiring JavaScript
Most rank trackers do not have special access to Google. They work by running searches and reading the results page, just like a person would, only at a much bigger scale. This is called scraping (a program reading a web page and pulling data out of it).
For years, many tools did this with simple HTTP requests. A request asks Google for the page, the tool gets back HTML, and it reads the positions. That was fast and cheap.
When Google started requiring JavaScript, those simple requests stopped returning full results. Several rank-checking tools reported delays, outages or missing data around the time the change came in. As I write this, tool makers are still changing how they collect data.
What Tools Need to Do Instead
To get results now, a tool has to load Google in something that behaves like a real browser. Usually that means a headless browser (a real browser like Chrome, run by software with no screen). The browser runs the JavaScript, waits for the page to finish, and then the tool reads it.
This works, but it is slower and costs more. A headless browser needs much more computer power than a simple request. Tools also need more proxies (other IP addresses to send requests from) so Google does not block them.
Which Tools Are Affected Most
Not every tool is hit the same way. In my experience, it helps to think about where a tool gets its data:
- Daily rank trackers that check Google directly for your keywords are hit hardest. They depend on fresh scraping every day.
- Large keyword databases also scrape Google, but many use several data sources. They may cope better, though some numbers could update more slowly.
- SERP data APIs (services that sell Google results to other tools) had to change their systems quickly. If your tool buys data from one of them, it shares their problems.
- Your own scripts, like a Python script that checks a few rankings, probably stopped working completely.
One thing to keep in mind about home-made scripts. Google’s robots.txt file has long blocked automated access to its search pages, and its terms tell people not to use automated means against those instructions. If you have been running your own scraper, this is a good moment to rethink it. I cover what robots.txt does in my guide to robots.txt rules.
What This Does Not Change
I have already seen some confusion about this, so let me be clear. This change is about people and tools using Google Search. It is not about how Google crawls or ranks your website.
- Googlebot is not affected. Google still crawls your pages the same way it did last week.
- Your site does not need JavaScript. A plain HTML site is still perfectly fine for SEO.
- Your rankings did not move because of this. If a tool shows a sudden drop on 15 or 16 January, check the tool before you blame Google.
- Your Search Console data is not affected. It comes straight from Google, not from scraping.
It is easy to mix this up with JavaScript SEO, which is a different topic. JavaScript SEO is about whether Google can read pages that your own site builds with JavaScript. Google processes those pages in three steps: crawling, rendering and indexing. Rendering means Google runs your JavaScript in a version of Chromium to see the final page. Google explains this in its JavaScript SEO basics guide. None of that changed this week.
If you want to use this week as a reason to review your site anyway, my SEO checklist for 2025 is a better place to start than worrying about Google’s front end.
What to Do If Your Rank Tracker Data Looks Wrong
When something like this happens, my rule is simple. Do not make decisions on data from the days the tools were broken. Wait, check and compare first.
Here is the process I am following this week:
- Check your tool’s status page or announcements. Many rank trackers have posted updates about the change. Find out if they had an outage and on which dates.
- Look for gaps or flat lines from 15 January onward. Missing days, keywords marked “not found” or rankings that all jump at once are signs of a data problem, not a ranking change.
- Mark the dates in your reports. Add a note for 15 to 17 January in your rank reports and any client dashboards. Months from now, you will want to know why the line looks odd.
- Compare with Search Console. Open the Performance report and look at the same pages and queries. If clicks and impressions are steady, your rankings are almost certainly fine.
- Spot-check a few keywords yourself. Search in a private browser window with JavaScript on. Personal results and location will make it a little different, but big drops will be obvious.
- Re-check once the tool is stable. Give it a few days of clean data before you judge any trend.
I would not cancel or switch tools in a panic this week. Almost every tool that scrapes Google had to deal with the same problem. What matters is how quickly and reliably yours recovers.
Use Search Console as Your Baseline
If there is one lesson here, it is this. Third-party rank data is an estimate collected from outside Google. Search Console is Google’s own data about your site.
The Performance report in Search Console shows clicks, impressions, click-through rate and average position for your pages and queries. It is not perfect. Average position is an average across many searches, and it is not the same as a daily rank check. But it does not break when Google changes its front end.
When I review a site, I always look at Search Console first and rank trackers second. Rank trackers are great for watching competitors and specific keywords. Search Console tells you what actually happened to your traffic from Google.
Will SEO Tools Cost More Now?
I expect some will, at least over time. Running headless browsers and extra proxies costs tool makers more money. Some of that cost will likely reach customers through higher prices, smaller plans or fewer daily checks.
You may also see changes like these:
- Rank checks that update less often, such as every few days instead of daily.
- Limits on how many keywords you can track on cheaper plans.
- More tools offering “on demand” checks instead of constant tracking.
Nobody has announced big price changes because of this yet, and I do not want to guess at numbers. My advice is simpler. Look at the keywords you track and remove the ones you never act on. A smaller, focused list is cheaper and easier to read anyway.
What About Users Who Turn JavaScript Off?
For most businesses, this group is very small, and Google’s own figure of under 0.1% of searches backs that up. They will either turn JavaScript on for Google or use a different search engine.
The change does matter for people who rely on text-only browsers or very locked-down setups. I think it is fair to point that out. Many screen readers work inside normal browsers that run JavaScript, so most of those users will not notice a difference. But not everyone uses a standard setup.
For your own site, the lesson is the opposite of what Google did. Google can afford to require JavaScript. A small business website usually should not. If your key content, menus and contact details work without JavaScript, more people and more tools can use them. That is still good practice. My on-page SEO checklist covers the basics I check on every important page.
What This Tells Us About Where Google Is Heading
I do not want to read too much into one change. But it fits a pattern I have watched for years. Google keeps making its results pages more interactive and more tied to JavaScript. Features like AI Overviews and other rich elements depend heavily on JavaScript.
Google is also clearly trying to control who can collect its results at scale. Requiring JavaScript is not a wall. Tools are already working around it. But it raises the cost and effort, and that is probably the point.
For marketers and business owners, the practical takeaways are:
- Expect third-party SEO data to have gaps from time to time. Treat it as a guide, not as the truth.
- Keep Search Console set up, verified and checked regularly.
- Do not change your site in response to this. There is nothing on your side to fix.
- Ask your tool provider how they collect data and how they handle changes like this.
Google Requires JavaScript: The Bottom Line
Google has required JavaScript for Search since around 15 January 2025. Google says the goal is to protect Search from bots, abuse and spam, and that fewer than 0.1% of searches come from people with JavaScript turned off. The real impact for SEO is on the tools that scrape Google, not on your website or your rankings.
Your next step is easy. Open Search Console, compare this week’s clicks and impressions with last week’s, and mark 15 to 17 January in your rank reports. If Search Console looks steady, you can relax and wait for your tools to settle.
