We have added the date and num keywords in a tooltip in the Position Distribution graph. Mouse over to see details.

 

Sometimes it could happen that sorting by the number of keywords does not work well in the projects list.

This has been fixed.

Now you can close (again) the keywords detail pop up by clicking outside of the box, and even pressing the ESC key in your keyboard. Work faster, not harder!

In the keywords table the URL column was shown encoded for non-Latin alphabets.

Now it shows proper characters of the according alphabet.

The top 10 results displayed in the keyword detail could be hidden on small screens.

This has been fixed.

Sub users could not export keywords due to a bug.

This has been fixed.

In some cases the SEO analysis score was not shown in the top 10 list for the keyword, despite having been done previously.

This has just been fixed.

In the keywords table the sorting by the average position of Google Search Console column was not working correctly.

This has been fixed now.

Notes page at account level, without selecting project, was not accessible.

This bug has been fixed.

If a custom default time period had been saved in the project date picker, when loading a project that had no data in that period it could give an error.

This is now fixed.

There were certain cases where the grouped views did not correctly display the order of the column headers, resulting in data being displayed in the wrong fields.

This has now been fixed.

Some keywords did not show GSC data because a case sensitive search was performed and the result was not found.

Now the search is case insensitive and if there is data it should find it regardless of how it is written.

In the last two weeks we have had some problems with the Sistrix API to obtain the visibility index.

Some projects may have gotten a score of 0 incorrectly.

This bug has now been resolved and there should be no problems again, although the index for the wrong weeks will not be updated.

The URL filter could not work when not all keywords were updated today.

This has been fixed.

On some cases it could happen that after creating a new report, the language of the page would change from English to Spanish.

This issue has been fixed.

The tag filter did not work in combination with other filters.

When it was used, all other filters were bypassed and only the tag filter was taken into account.

This has just been fixed.

Sorting by traffic column in tables grouped by URL, location or tag was not working properly.

This is now fixed.

Since a few weeks ago the Sistrix visibility index for desktop was not correct.

It was getting the mobile version from the Sistrix API, so you may have seen that it was the same value for both devices.

This was due to a change in the Sistrix API that they have not notified.

From the next calculation of the visibility indexes, the correct value for desktop will already appear.

Since the values are usually very similar, and it would take us a lot of work to correct it, the data of these last weeks will not be recalculated.

When exporting a project to CSV, the column with the tags had disappeared from the file.

This has been fixed.

Depending on certain actions we performed in a project dashboard, the large distribution chart was not displayed when its header was clicked.

This has been fixed.

The grouped views in the keywords table (URLs, locations and tags) had stopped working due to a bug.

It is now fixed.

There were users who got the project stuck with "We are loading data of your Project, one moment please ...".

This was due to the time difference between the user and the system. It has been fixed.

Now in the date picker the maximum date will be the current system day, not the user's day.

Some columns of the keywords table did not perform a correct sorting when clicked on.

It has been fixed.

When a project had thousands of keywords and 3 months or more of data was loaded into the distribution chart, it could fail and not load the chart.

This has been fixed.

When saving the status of the keywords table (order, visibility, etc.) it also saved the pagination by mistake.

This caused that if you moved to another page, when you loaded another project it would start from that page, and might not even show anything if that page did not exist.

This has been fixed and now it always starts from the first page.

In projects connected to a Google Search Console account, when adding new keywords, the GSC data for these keywords was not being retrieved.

Now it works correctly.

When you kept the page of a project open for a long time, the session could expire and when opening the popup with the history of a keyword, the loader was frozen and did not show any error.

This has been fixed, closing the popup and showing the related message that you have to log in again.

If you do not want your session to expire, when you log in, check the box to keep your session signed in.

The distribution chart data for some projects were not calculated for June 22, 23 and 24.

The bug has been fixed.

Unfortunately, this data will no longer be calculated.

We apologize for the inconvenience if you have been affected.

Some keywords of non-Latin alphabets showed a search volume equal to 0, as for the rest of Google Ads data.

This has been fixed.

Not to be confused with other reasons why it may show 0.

We use Google Ads API to get the search volume for the keywords, which is quite peculiar.

On the one hand, there are many characters in the keywords that it considers invalid, so no data can be obtained through the API, although it can be obtained through Google Keyword Planner.

On the other side, Google does not show keyword data related to certain topics due to "privacy".

URLs with non-Latin characters were not displayed properly in the keywords table and in the keyword history.

This is now fixed.

Since several weeks, a few times Google returns only the first page for mobile searches, instead of showing 100 results.

This means that if your project does not appear on the first page, it stops ranking and shows a 101 position in TrueRanker.

We have greatly reduced the cases where this happens, but it still happens sometime (0.02% of searches).

We will continue to monitor how this problem evolves.

PS: do not confuse this problem with the fact that for certain keywords your project can appear and disappear from Google's top 100. You can always check it by looking at the SERP we have obtained with the magnifying glass button in the actions column.

When connecting a TrueRanker project to a Google Search Console account that did not have that domain linked to it, a 500 error occurred.

Now, in that situation, access to that GSC account is revoked and a message is displayed informing that there is no matching property for the user's project.

In some cases, when sorting alphabetically by project name, unexpected results were obtained on the project page.

This has been fixed.

The button on the project settings page to connect to Google Search Console was not working.

It is now fixed.

There was a bug that did not allow to re-run a SEO analysis of a URL.

It has been fixed.

When exporting project data to CSV it was always considered as if the project type was single domain, showing positions and URLs that might not be as expected.

This has been fixed.

Fixed a bug when adding a keyword that already existed, the history was lost and started over.

The functionality to sort the list of competitors by the position of one of the competitors was not working correctly.

The problem has been solved.

In the keyword density section of the SEO analysis, information was cluttered and unreadable if the keywords were in an RTL language.

This has now been fixed.

We have discovered a bug in the cannibalization detector. In some cases the red ladybug was not displayed in the keywords list 🐞

We have fixed the problem 🐞

Corrected several translation errors throughout the website.

Since Friday, some users were experiencing problems when adding some related keywords 😞.

We apologize to these users 🙏

We have fixed the problem and it is working properly 🎉

There was a technical limit that prevented adding more than 1,000 keywords at a time.

When this happened, no keywords were added and no message was displayed.

This has now been fixed and there is no limit.

Corrected several translation errors throughout the website.

On the competitor's screen, the fixed header did not work correctly when scrolling to the right. The problem has been fixed

Since yesterday we were experiencing an error when getting the competitors of a certain country. The problem has been solved.

In some SERPs, some paid results were coming in as organic results. The problem has been resolved.

Some links led to Spanish language pages. The problem has been fixed.

When you changed pages and wanted to see the history of keyword positions, the modal did not open.

This problem has been fixed.

We have fixed a bug that occurred when sorting data by the change on the last day in the keyword table.

When adding keywords from Google Search Console suggestions, sometimes it could show error due to not allowed characters in some keyword.

Now it is fixed.

In the form for adding keywords, while typing a keyword that was too long, it was not displayed at all and it seemed that what had been entered before had disappeared.

Now it is displayed completely all the time, giving no place for error.

On the competitors page, sometimes the ranking of the competitors shown in the table was not the most recent. However, when clicking on the keyword and displaying the details, it was fine.

This has been corrected and now if it has already been monitored today, it will show today's rank in the table.

Corrected several translation errors throughout the website.

Due to a change in Google SERPs, local pack feature had stopped getting results.

It is now fixed and working properly.

When the favorites filter was used, it did not affect the distribution chart.

Now it works correctly. Please note that favorites data for this chart will start to be calculated starting today.