Discuss project

Poisoned SERP: How to Track Google Rankings Anyway

A poisoned SERP makes a single rank check unreliable. My November 2026 numbers: top-10 overlap between runs, error by position band and a re-check rule.

Vladislav Krivorutško — founder of ADLAB
Vladislav Krivorutško

November 12, 2026 · 26 min read

From the ADLAB channel on YouTube. Watch on YouTube

Contents
  1. 01Short answer
  2. 02What a poisoned SERP is, and what is known about it
  3. 03How it showed up in my own tracking
  4. 04Three data sources tested against a browser
  5. 05The setup that worked
  6. 06How wrong a position still is
  7. 07When a position change is a drop, and when it is noise
  8. 08The re-check rule in my tracker
  9. 09What it costs
  10. 10Check your own tracker in 15 minutes
  11. 11Who this is not for, and what is not solved
  12. Check yourself
  13. Files from the video

TL;DR - key points

  1. 1A poisoned SERP is a Google results page that looks normal, but most of its organic results are unrelated; a rank tracker saves it as a drop
  2. 2In my test of 12 November 2026, A-Parser with the Bypass poisoned SERP option and a proxy pool of the same country gave 83% good measurements against a browser; the mean position error in the browser's top 5 was 2 places
  3. 3In A-Parser, two runs of the same keyword shared 7.6 of 10 top-10 domains on average, and roughly 1 single measurement in 10 showed a different version of the page
  4. 4Two rules fixed most of it in my tracker: an empty or cut-off page is a failed measurement, and a keyword whose top 10 shares fewer than half its domains with the last check is measured again
  5. 5Trust positions up to 30 as a band, not an exact number; past position 30 the parser and my browser stopped agreeing

Short answer

A poisoned SERP is a Google results page that looks like a normal one, but most of the organic results on it have nothing to do with the keyword. There is no captcha and no error, so a rank tracker saves the page, and the report says your site dropped. Since late September 2026 a single rank check can no longer be read as a position.

I still track rankings, with three changes. The data comes from A-Parser with its Bypass poisoned SERP option and residential proxies from the country and city of the search. An empty or cut-off page counts as a failed measurement. And any keyword whose top 10 suddenly shares fewer than half of its domains with the last check is measured again before I believe it. In my test of 12 November 2026 this setup gave 83% good measurements against a real browser, with a mean position error of 2 places inside the browser's top 5. Below is how far off it still is.

What a poisoned SERP is, and what is known about it

Three public sources described the problem between October and November 2026. I read all three on 12 November 2026; the numbers in the table are theirs, not mine.

SourceWhat it reportsLimit
SE Ranking study, published 3 November 2026On 10,000 US desktop keywords, the share with unrelated results jumped from 0.09% on 16 September to 57.3% on 17 September. In 96.5% of the cases the unrelated results started at position 9 or lower, never in the top 5US and desktop only; they call it "unrelated results"
DataForSEO post, published 23 October 2026A poisoned page has fewer than half of the usual sites for the keyword. 20 to 30% of the pages it collected were affected from 26 September; after two retries and a history check 2 to 3% remain; noticeably fewer since 10 October. All large providers are affectedThe provider's own data, no independent check
A-Parser article, 6 November 2026A new option, Bypass poisoned SERP, in the settings of its Google parser, with the vendor's test on two US pages through residential proxies in New YorkOne test by the vendor; how the option works is not described

Is it deliberate? Nobody knows: neither study claims it, Google has said nothing, and I make no claim either. I can only describe what it did to my numbers.

How it showed up in my own tracking

My setup had two parts: Search Console for sites I can verify, and a rank tracker for everything else. Search Console is the closest thing to ground truth, but it gives an average over all devices and countries for the period, not the position a person sees in one search. And it exists only for verified sites. For PBN projects, where connecting Search Console would leave a footprint, and for competitors, I had only the tracker.

Then its numbers started to jump: on one keyword my site stood third. Over three weeks, from 21 September to 11 October, the tracker found it in 14 of 21 checks and missed it in 7. The misses were not a drop. The page itself had changed: three versions of the top 6, with almost no sites in common.

Before you blame the SERP, rule out the boring cause. If the tracker shows a different URL of your site from one check to the next, that is two of your pages competing for the keyword, and the fix is in the article on keyword cannibalization, not in the data source. In my case the URL was the same; the competitors around it were not.

Three data sources tested against a browser

My reference was my own browser in the same city as the proxies, in the local language: what a real searcher sees. All tests ran on Estonian Google, mobile.

  1. Bright Data SERP API, 11 October. On that keyword it put my site third in 5 runs out of 5, the same as my browser.
  2. 30 keywords, two runs each, on Bright Data and DataForSEO, 15 October. Two runs of the same source shared only about half of the top 10: 0.51 on one and 0.52 on the other. Between the two sources the overlap was 0.28. At 5 parallel threads Bright Data lost 68% of the calls; it can probably be tuned, but I found no setting that made it cheaper or steadier for this job.
  3. Search Console as the judge, 26 October. 31 keywords of a verified site, four rounds 10 minutes apart. Where Search Console had the site in the top 30, DataForSEO found it in 38% of cases, Bright Data in 21% and A-Parser with my first settings in 13%. A-Parser returned only 51% valid measurements then, blocked by captchas, against 97% for DataForSEO. The number one result stayed the same across all four rounds for 68% of keywords in A-Parser and 33% in DataForSEO.

After A-Parser added its option in early November, I took the keyword for which I had written down the real top 30 from my browser on 10 November. With the option, 9 of the browser's top 10 were in A-Parser's top 10, and all 5 of the top 5. DataForSEO had 4 of 10 and none of the top 5. One keyword and one browser is a hint, not proof, so on 12 November I ran a wider comparison: 6 keywords, 8 runs each, 48 measurements per source. A measurement counted as good if it did not fail and at least 7 of its top-10 domains matched the browser.

Setup, 12 November 2026Good measurements of 48Top-10 overlap with the browserMean position error in the browser's top 5
A-Parser, proxy pool of the same country40 (83%)0.682.0 places
A-Parser, pool of IPs from mixed countries25 (52%), about 70% once it settled0.572.1 places
Hosted SERP APIs, two providers, three configurations, default settings15 to 44%0.20 to 0.492.7 to 5.7 places

The hosted APIs ran on default settings, without deep tuning, and these products may have changed since. DataForSEO itself reports fewer poisoned pages since 10 October. Its post calls the problem industry-wide and tells clients to treat a one-day drop as unconfirmed until two readings agree. I agree; I just needed a measurement I could act on the same day.

The setup that worked

The tool is A-Parser, which I run on my own Enterprise licence, and its SE::Google parser. Five settings made the difference:

  1. Bypass poisoned SERP (smartSessionWarmup in the API). Inside the parser it is a session warm-up. It did not change which results came back, but it made runs finish: with the option 3 runs of 3 completed, without it 2 of 3, and one of them returned nothing for 8 keywords. At 5 pages neither run without the option finished.
  2. Residential proxies from the same country and city as your reference. A worldwide pool does not work: Google redirects to the domain of the proxy's country, and the parser reports a mismatch. A pool of mixed countries gave 52% good measurements against 83%, and one site in one keyword moved between places 1 and 4 from one IP to the next. Without proxies, and with datacenter proxies, A-Parser returned 0 results in my tests of 11 October.
  3. Language, country, Google domain and city set the same as in the browser.
  4. Device: mobile. All my projects are tracked on mobile, and a mobile page differs from a desktop one.
  5. Three pages, not five. Past position 30 the parser and my browser stopped agreeing.

What did not help: the full browser engine gave 0 successful queries, an experimental split option gave 0 results, and the single main browser, the duplicate filter and the results-language parameter all stayed inside the noise. Three runs per variant is a tendency, not proof.

The A-Parser recipe in the files below packs this into a ready addTask body and a Python wrapper (3.8 or newer, standard library only). The wrapper sends the task, waits, parses the result, retries failed keywords and prints one status per keyword: FOUND, NOT_FOUND or FAILED. A page counts as failed when it has no organic results, or fewer than 8 per page while Google reports 200 or more results. Its --dry, --parse and --selftest modes need no network; the self-test runs 33 checks against a mock A-Parser. The wrapper itself has not been run against a live A-Parser yet, only the integration in my tracker that it was taken from.

The README lists the traps that cost me hours. \n and \t in the result format must be typed as text, a backslash and a letter: real newline characters made all 6 keywords of a live test come back empty. Result variables need the $p1. prefix. A task without configPreset is rejected. An option given as a [name, value] pair is accepted by the API and silently ignored. And A-Parser tells proxies apart by address:port, so two pools with the same ports merge into one set.

With my proxy pools the warm-up passed for 7 countries (Estonia, Norway, Sweden, Finland, Lithuania, Slovakia, Bulgaria) and failed for 3: the United Kingdom, the United States and Hong Kong. On 12 November, 5 US keywords at 3 pages gave 0 successes and 47 failed warm-ups. The vendor reports a passing US test, so this is most likely a property of one pool, not of the country. Test your pool on 10 keywords before you buy traffic.

How wrong a position still is

Against my browser, on one keyword, with the option and a same-country pool, page 1 shared 70 to 90% of its domains, page 2 50 to 75%, page 3 10 to 44%, and pages 4 and 5 almost nothing. The exact position matched in 7 to 16% of cases. Google does no better against itself: two searches in my browser, one right after another, gave the same exact position 7% of the time.

Where to trust a positionPage 1 · positions 1–1070–90%Good enough for trendsPage 2 · positions 11–2050–75%Read it as a bandPage 3 · positions 21–3010–44%A miss is not a dropPages 4–5 · positions 31–50almost noneDo not read0%50%70%100%70%: the threshold at which page 1is good enough for trends
Domains that A-Parser (Bypass poisoned SERP, same-country proxy pool) shared with my browser, by results page; one keyword, Estonian mobile results, November 2026. The dashed line is the 70% threshold of the 15-minute test.

So I measured noise separately. On 12 November I ran 30 neutral Estonian keywords (weather, recipes, public services, transport) through A-Parser four times, and the same set twice through DataForSEO, plus 30 English keywords twice through DataForSEO for the United States. This measures how a tool agrees with itself, not accuracy: there is no browser reference on these 60 keywords.

Two runs of the same sourceA-Parser, EstoniaDataForSEO, EstoniaDataForSEO, United States
Mean top-10 overlap0.760.600.48
Pairs with 8 or more of 10 in common60%39%33%
Pairs with 4 or fewer of 10 in common7%26%50%
Shift of a top-3 site, median / 90th percentile0 / 40 / 120 / 14
Shift at positions 4 to 10, median / 90th percentile1 / 73 / 101 / 10
Shift at positions 11 to 20, median / 90th percentile2 / 51 / 61 / 7

Two limits matter here. DataForSEO had two runs per market sent back to back, so its numbers rest on 23 and 30 pairs of runs. And part of its US results came back as Google redirect links without a readable domain; without those rows the US overlap reads 0.59 instead of 0.48. Between A-Parser and DataForSEO on the same Estonian keywords the overlap was 0.37. Which of them looks more like what a person sees, this data does not say.

The nastiest error is the outlier. On 58 keywords of one project on 11 November, 32 shared 8 to 10 of 10 domains with a fresh measurement and 14 shared 4 or fewer. My rough estimate: 10 to 15% of single measurements show the other version of the page. One site appeared second for a keyword; in 22 of the next 24 measurements it was not second, my browser agreed, and its real place was around 20th. One bad measurement in ten hardly shows in a report of a thousand keywords, but it matters for the one keyword you are deciding on.

When a position change is a drop, and when it is noise

The "plus or minus 2" for the top 3 is the mean error rounded, not an interval: the 90th percentile of the run-to-run shift there is 4 places. From these numbers I made a short decision table; the full version is the rank error bars cheat sheet, where every number carries its date, sample size and limit.

What I seeWhat I doWhy
One keyword drops hard on one day, one measurementDo not report a drop; measure again with the same settings10 to 15% of single measurements show the other page
The cell is empty or the page is cut offTreat it as a failed measurement and retry only that keywordAn empty page is not a lost position
A move within the band's median: top 3 up to 2, positions 4 to 10 by 1, 11 to 20 by 2Ignore itThat is ordinary run-to-run noise
A move between the median and the 90th percentileWait for a second measurement before writing it down90th percentiles: 4, 7 and 5 places
A site vanishes from positions 21 to 30Not a drop on one measurementOnly 10 to 44% of page-3 domains matched the browser
Many keywords flagged on the same daySuspect the data source first and rerun the next dayThird-party episodes reached 20 to 30% of pages

The same logic applies when you judge whether SEO work is paying off. A move of two places inside the top 10 is inside the noise, so in the month-by-month view of SEO results I look at the direction over several checks, not at one day.

The re-check rule in my tracker

The tracker I use for client and own projects is my own; the source of positions is switchable per project, DataForSEO or A-Parser, and nothing breaks if I switch back. Two rules came out of these tests.

Rule one: an empty or cut-off page is a failure, not "site not found". On the first large runs, 18% of 613 keywords came back empty on one project, and 206 of 487 failed on another, after one retry. Now the tracker retries failed keywords by itself, up to three rounds, and starts a new round only if the previous one recovered at least 15%. After that, 1 to 3 failures remained per run of about 500 keywords. In the table, cells have three states: found, not found and failed, and failed is red, so a failed measurement cannot be mistaken for a lost position.

Rule two: re-measure the jumps. After a run, the tracker compares each keyword's top 10 with the previous check from the same source. If fewer than half of the domains match, the page probably flipped, and the keyword is measured once more. The second measurement is kept only if it is closer to the previous check than to the first one. If the site really dropped, both new measurements agree with each other, so the new result stays. If the first one was a flipped page, the second looks like the old check and replaces it. Re-measures are capped at 40% of the keywords of a check, so a real Google update cannot blow up the proxy bill; in practice they add about 25% traffic.

The re-check ruleNew measurementIs the page empty or cut off?yesnoFailed measurementretry this keyword,up to 3 roundsFewer than half of the top 10match the last check?noyesAccept itas it isMeasure againcapped at 40%of the checkIs the second measurement closerto the last check than the first?yesnoKeep the secondthe first onewas a flippedpageKeep the firstboth new onesagree: the sitereally moved
The two rules in my rank tracker, November 2026. Retries after a failure continue while a round recovers at least 15% of the keywords.

Does it work? It is new. On its first live run of 12 November, a check of 9 keywords, 3 looked like jumps, 2 were re-measured (the third was over the cap), and both times the second measurement was taken. That is a smoke test. So I also replayed the rule on the four A-Parser runs of the neutral set: 44 of 624 cases (7%) looked like jumps, the rule took the second measurement in 21 and kept the first in 23. On those cases the overlap with a control run rose from 0.62 to 0.86. The cases overlap, since they come from the same 30 keywords, so read it as a direction.

The repeat-check script applies this rule to your own exports. It takes three CSV files with the columns keyword, position, domain: the last check you trust, the new check and, on the second run, the re-measured keywords. It prints which keywords flipped, which to measure again under the 40% ceiling and which measurement stands. It is one Python file without packages or network access, with a self-test of 22 checks. Two warnings from its README: the last check must come from the same tool, country, city and device, and the rule picks the measurement that is consistent with the last check, which is not the same as the true one.

What it costs

A-Parser does not report proxy traffic, so I read it from the proxy dashboard: 0.19 GB for about 6,050 requests to Google, or about 1.7 MB per keyword at 3 pages. My tracker's own estimate is 1.3 MB. Taking 1.0 to 1.7 MB per keyword, 1,000 keywords cost:

Proxy price1.0 MB per keyword1.3 MB1.7 MB
$1.70 per GB (small pack)$1.70$2.21$2.89
$1.00 per GB (large pack)$1.00$1.30$1.70

The prices are from my proxy provider's list of 12 November 2026. For scale, a hosted API queue at depth 30 cost about $1.50 per 1,000 keywords when I checked on 15 October and again on 12 November. Retries and re-measures add traffic only for the keywords involved, and the A-Parser licence comes on top; check which edition includes the HTTP API. So a check costs about the same as through an API; what I pay for is numbers closer to my browser on my keywords.

Check your own tracker in 15 minutes

This test needs no A-Parser:

  1. Pick 10 keywords where you know the real result. Search them in an incognito window with the right language and country, and write down the top 10.
  2. Run the same keywords through your tool three times.
  3. For each keyword, count how many top-10 domains match between runs. Fewer than half means a flipped page: do not trust that day.
  4. Compare the average with your browser. If page 1 shares 70% or more, the tool is good enough for trends.

To compare your numbers with mine, the repeatability dataset holds the raw measurements of 12 November: 4,642 result rows, 60 keywords, 237 measurements, one row per organic result with source, market, run, keyword, position and domain. The analyze.py script reproduces every number in the noise table above and runs on your own CSV with the same seven columns; use at least 2 runs, better 4. The data is licensed CC BY 4.0, the script MIT. All four files from the video are below this article.

Who this is not for, and what is not solved

This approach does not fit if you need positions deeper than 30, if you cannot get residential proxies for your country, or if you track thousands of keywords with nobody to watch the share of failed measurements: the proxy pool is the weak point. And if your current tracker passes the 15-minute test, do not switch.

What I have not solved:

  • Coverage. With some proxy pools the warm-up fails on a captcha and almost every query comes back empty.
  • Depth. Thirty positions, no more.
  • The reference. One browser of one person, a handful of keywords, everything dated 12 November 2026. Google itself reorders the first three results between two searches.
  • Languages and markets. I tested local-language Estonian keywords on mobile. Other languages, countries and desktop pages were not tested for accuracy.
  • Terms of service. Automated queries are against Google's terms. I use this to monitor my own and client sites; how much risk you accept is your call.
  • Permanence. DataForSEO says it tests new approaches every day. The fix may land in your own tool next month, and this method may become unnecessary.

One last check before you blame any tool: if a page disappears from every measurement and from your browser as well, the problem is not the SERP. Start with why Google is not indexing your pages. If you want the data source and the reports checked on your own project, I do that as part of a technical SEO audit.

Quiz

Check yourself

A few questions on the article. The answer and the reasoning appear as soon as you pick; nothing is sent anywhere.

0/4

answered

  1. 1.Your tracker shows a site falling from 3rd place out of the top 30 overnight, on one measurement. What do you do first?
  2. 2.A keyword comes back with no organic results at all. How should the report read it?
  3. 3.A site in the top 3 moved 2 places between two runs. What is it?
  4. 4.In the 15-minute test, page 1 of your tool shares 75% of its domains with your browser, and the three runs agree. What does that mean?

ADLAB · files from the video

Files from the video

Scripts, prompts, templates and data shown in the video. Text files open as plain text; the zip holds every file of one item.

  1. 01Config · Template5 files · 52 KB · MIT

    A-Parser recipe: check Google rankings in poisoned SERPs

    Ready addTask body, a Python wrapper and rules for measuring Google positions with A-Parser SE::Google and Bypass poisoned SERP, plus proxy cost per 1,000 keys.

    What's inside · 5 files
    • README.md

      3-step run, status rules, API actions, traffic table, gotchas

      8.0 KB
    • task-body.example.json

      The addTask body for SE::Google: 3 pages, mobile, proxy pool, smartSessionWarmup, escaped result format

      1.5 KB
    • aparser_rank_check.py

      Wrapper: Python 3.8+, standard library only; --dry, --parse and --selftest need no network

      33 KB
    • keywords.example.txt

      10 synthetic keywords

      272 B
    • sample-results.txt

      A synthetic A-Parser result file with found, not found, empty and cut-off pages

      8.9 KB
  2. 02Dataset3 files · 281 KB · CC-BY-4.0

    Do rank trackers repeat themselves? Top-10 overlap data, 2026-11-12

    Two runs of the same query share 7.6 of 10 domains in A-Parser, 6.0 in DataForSEO Estonia, 4.8 in DataForSEO US. CSV of 4,642 rows, CC BY 4.0.

    What's inside · 3 files
    • serp-repeatability.csv

      One row per result: source, market, run, query, position, domain. 237 query measurements of 60 queries

      258 KB
    • analyze.py

      Python 3.8+, standard library only; reproduces every number on this page, with an offline self-test

      10 KB
    • README.md

      Method, definitions, columns, the unreadable-domain rows, limits

      12 KB
  3. 03Checklist · Template4 files · 19 KB · CC-BY-4.0

    Rank error bars: when a position change is a drop, and when it is noise

    One-page cheat sheet: error bars by position band, outlier rate and thresholds for jumps and retries. Each number has a date, a sample size and a limit.

    What's inside · 4 files
    • rank-error-bars.md

      Bands, outliers, third-party numbers, the decision table, thresholds and the traffic formula on one page

      10 KB
    • thresholds.csv

      Every threshold and number as a row: value, sample, date, own or third-party, limit, source

      5.0 KB
    • example-readings.md

      One synthetic tracker day read with the rules

      1.7 KB
    • README.md

      3 steps and what to check before you rely on the numbers

      2.3 KB
  4. 04Script5 files · 43 KB · MIT

    Rank tracker jumped? Repeat-check script with a 40% ceiling

    Python script, stdlib only: flags keywords whose top 10 flipped, remeasures only those, keeps the second result only if it is closer to the last check.

    What's inside · 5 files
    • README.md

      3-step run, rules and thresholds, decision table, gotchas

      12 KB
    • serp_repeat_check.py

      The checker: Python 3.8+, standard library only, with an offline self-test of 22 checks

      17 KB
    • sample-prior.csv

      Synthetic last check: 9 keywords, example-*.com domains

      5.3 KB
    • sample-first.csv

      Synthetic new check: 10 keywords, five of them flipped

      6.1 KB
    • sample-remeasure.csv

      Synthetic second measurement for the keywords to repeat

      3.1 KB

Frequently asked questions

What is a poisoned SERP?
It is a Google results page that looks like a normal page, with no captcha and no error, but most of the usual organic results for the keyword are missing and unrelated sites stand in their place. DataForSEO defines it as a page where fewer than half of the usual sites for that keyword appear. Rank trackers that scrape Google save such a page as a real result, so the report shows a drop that did not happen.
My rankings dropped overnight in the rank tracker. Is it real?
Not on one measurement. Run the keyword again with the same settings and compare the top 10 with the previous check. If fewer than half of the domains match, the results page flipped, not your site. DataForSEO gives its clients the same advice: treat a one-day drop as unconfirmed until a second reading agrees.
How accurate are rank trackers in 2026?
In my measurements of November 2026 on Estonian mobile results, the best setup matched a real browser on 70 to 90% of the domains on page 1 and hit the exact position in only 7 to 16% of cases. Two searches in the browser itself, one right after another, gave the same exact position 7% of the time. A position is a band: in the top 3, about plus or minus 2 places.
How do I check whether my rank tracker can be trusted?
Take 10 keywords, search them in an incognito window with the right language and country and write down the top 10. Run the same keywords through your tool three times and count how many top-10 domains match between runs. If page 1 shares 70% or more with your browser and the runs agree with each other, the tool is good enough for trends.
Is Search Console more accurate than a rank tracker?
Search Console is the closest thing to ground truth, but its position is an average over all devices, countries and searches for the period, not the place you see in one search. It also exists only for sites you can verify. For competitors, new sites and projects where Search Console cannot be connected, a tracker remains the only source, which is why its error has to be measured.
Is A-Parser a replacement for a SERP API?
Not for everyone. In my tests it came closest to the browser, but it needs your own licence, residential proxies of the right country and someone to watch the share of failed measurements. With my proxy pools the warm-up failed for the United States, the United Kingdom and Hong Kong. If your current API passes the 15-minute test described in this article, there is no reason to switch.
Vladislav Krivorutško — founder of ADLAB

About the author

Vladislav Krivorutško

Founder of ADLAB OÜ · SEO and Google Ads

Over 20 years in search traffic and monetization, and on the Estonian market since 2017. I work solo: I run the audit, build the strategy and deliver the project myself — no subcontractors, no templates. I only write about what I have tested on my own and client sites.

  • 20+ years in search traffic
  • 50+ end-to-end projects
  • Own sites in competitive niches
  • SEO for ru/et/en in one market
More about me

Conclusion

Since September 2026 a single rank check is a sample, not a fact. I got usable numbers back with one A-Parser setting, residential proxies of the right country and two rules in the tracker: an empty page is a failure, and a jump is measured again before anyone reacts to it. Even then, a position in the top 3 moves by up to 2 places from noise alone, and anything deeper than 30 is not worth reading. If your reports keep showing drops that nobody can explain, start the technical audit with the data source: in my practice that is a cheaper fix than rewriting pages that never actually fell.

Read next