SEO report & "search queries vs search results" return 500 ("Cannot read properties of undefined (reading 'map')")
Two MCP tools have been returning a 500 error for us since 17 June 2026, still failing
as of 23 June (re-tested today):
- search_queries_vs_search_results
- generate_seo_report (SEO report)
Error in both cases:
500 — { "error": "An error occurred while processing the request",
"message": "Cannot read properties of undefined (reading 'map')" }
Isolating the pipeline (same account, same query, all tested today):
- analyze_google_search_results — works
- analyze_related_search_queries — works
- search_queries_vs_search_results — 500s when combining them (also with
includeSearchQueriesOnly:true)
So both inputs to the comparison succeed and only the comparison step crashes. It looks
like an unguarded .map() on an undefined value in that step. generate_seo_report (which
builds everything fresh from a URL) fails with the identical error, so it isn't a missing
saved graph on our side.
Repro (via the MCP connector):
- search_queries_vs_search_results with queries: ["ecommerce personalization platform"]
- generate_seo_report with url: https://www.helloretail.com/en/
It reproduces on a single generic query that definitely has SERP results, so it doesn't
seem query-specific. Other tools (graph generation, content gaps, text analysis) and auth
all work fine on the same account.
I emailed Dmitry on 17 June with follow-ups on 18 and 22 June but haven't heard back, and
couldn't get through the Discord human-verification step, so flagging here too. Happy to
share the account email and a full reproduction privately. Thanks!
-
Official comment
Hey Rasmus Leth Skjoldan Thank you for providing the details!
We are going to reproduce your exact workflow and let you know when we test it and fix it on our end if there are any errors!
Thank you! -
Trying again :-)
0 -
Rasmus Leth Skjoldan this is to confirm that we have now verified our fix and it's working absolutely fine.
I also added promotional credits of €40 to your account to compensate you for any inconvenience.
0
Please sign in to leave a comment.
Comments
3 comments