I have questions about “? db_action=tdb_ajax ”
1. These pages get into the index and then in search results of Google and Yandex. When opened, only part of the page is displayed, which KILLS(!) behavioral factors. How can I prevent these pages from being indexed?
2. Can I delete a fragment ?tdb_action=td b_ajax from tdb_ajax.php, but still save infinite scrolling?
3. During infinite scrolling, the analytics (Google analytics and others) of visited pages gives statistics about visits to pages with the prefix “? Tdb_action = tdb_ajax”, and not about the original page. This leads to the fact that pages with the prefix ?db_action=td b_ajax improve the position in the search results, and the original page is ranked poorly. This makes pointless your infinite scrolling algorithm.
https://<original-page>
https://<original-page>/?db_action=td b_ajax
Third-party plugins are not used. The theme is installed according to the requirements and instructions.
Hi,
This tdb_action=tdb_ajax is related to the infinite loading functionality, the ?tdb_action=tdb_ajax can be found in wp-content/plugins/td-cloud-library/includes/tdb_ajax.php but once that is remove it will no longer work correctly the infinite loading.
I will make a note to our developers to check the infinite algorithm/code and to see if is not a better way to implement the code.
Thank you for your understanding!
Unfortunately, I didn’t find the answer to my questions in your reply post. According to messages on the forum, I see that this problem has been relevant for over a year and you have already promised to inform the developers about it. It remains unresolved, and the Support answers are the same, using Copy/Paste. It is very sad..
Hi Genkokov, unfortunately I do not have the skills of developers therefore the only thing that I can do is to announce our developers about this situation and they will deal with it. I’m sorry for this inconvenience! but if the infinite loading is not improve the position/rank on google index, the only solution for the moment is to disable it until our developers will check the problem.
Also the problem with indexing the ?tdb_action=tdb_ajax was solved in last version -> wp-content/plugins/td-cloud-library/includes/tdb_functions.php -> https://i.imgur.com/Ft4mnaH.png
Thank you for your understanding and sorry for the inconvenience!
Hi Genkokov, actually I think that for you for fix i not working because you have two meta set in header for index/noindex, on if from our theme and second on is from an extra plugin or it can be also set custom.
How you can check this, you can inspect the source page using the right click -> https://i.imgur.com/1n9lFRH.png -> https://i.imgur.com/0ZdSVXq.png what you can do is to change the priority for the fix that we’ve made, go -> wp-content/plugins/td-cloud-library/includes/tdb_functions.php and change priority 1 in 11 or more -> https://i.imgur.com/NgvI6IR.png -> https://i.imgur.com/NPAaryJ.png after that clear all cache open again the page from your website and check if the meta from our theme is loading the last one or not (check again the source page), usually the last meta that is set should be use by Google.
Let me know if there are some improvements!
Thanks.
Hello, has this problem been solved? I see the last post on this thread was on december 2020.
I get the same variable in url’s from analytics and it really makes it hard to accurate data.
Please fix it!!!
Hello, @willlevith,
Our developers created a fix for this issue here https://www.screencast.com/t/Y8bZNbYnyYC in this path => wp-content/plugins/td-cloud-library/includes/tdb_functions.php
Normally it shouldn’t be a problem, I made a notification for this to be verified, and if this happens to you it may be a more special situation and please give more details and screenshots to be able to recreate this problem.
Thank you!
Hi FalconSam,
Normally in the latest theme version this problem should no longer be present, but if this appears, the only quick solution is to disable the infinite loading -> https://tagdiv.com/infinite-loading-for-single-posts/
I reported this to our developers to check it and to see if there can be some problems.
Thank you!