Google index problems – ?tdb_action=tdb_ajax

Hi,

why some of my sites have this domain ending – ?tdb_action=tdb_ajax

Here a link for example

– https://www.frisuren-magazin.de/trend-long-bob/?tdb_action=tdb_ajax

it does not shown the site complet without the ending (?tdb_action=tdb_ajax)

https://www.frisuren-magazin.de/trend-long-bob/

How can i fix it?

Hello,

I am using tech news demo and activated autoload feature.

While looking at the analytic data I found a real-time visitor comes to one of my post ending with ?tdb_action=tdb_ajax

I wonder how he/she reach this URL?

Tried to access the URL with ?tdb_action=tdb_ajax and found, it has no header,footer and page was also not scrolling, and in the source of the page, it has two meta robots tags.

I don’t know what is it and how to fix it.

It is similar like – https://demo.tagdiv.com/newspaper_tech_news_pro/2019/05/13/td-post-hands-on-google-pixel-3a-xl-review/?tdb_action=tdb_ajax

Please investigate it.

Ok i have the same problem. Google disabled my adsense for some reason because of this particular link:

http://playsiders.com/i-microstrategy-kanei-to-tetarto-megalytero-stoichima-tis-sto-bitcoin/?tdb_action=tdb_ajax

Can’t this be fixed?

Hello,

I deleted the Infinite Scroll function and deactivated the cloud template, as it unfortunately had a negative effect on the individual pages.

Unfortunately, I now have thousands of error messages like this:

https://www.ratgeber-haus-garten.com/wp-json/oembed/1.0/embed?url=https://www.ratgeber-haus-garten.com/bambusdielen-als-robuster-terrassenbelag/

https://www.ratgeber-haus-garten.com/wp-json/oembed/1.0/embed?url=https://www.ratgeber-haus-garten.com/rosa-deko-romantische-einrichtungsideen/

How can I delete these pages?

Should I also delete the cloud template plugin from you, also?

Thanks for Help…

Best regrads,

Jan

Hi Bettina,

thank you very much for your attention.

I don’t know why these pages are generated as described above.

“ubersuggest” shows me these pages as SEO errors and I understandably don’t want these pages either.

I also brought it to your attention last year but it seems Tagdiv team is unable to fix it.

Though, the same issue is with the official newspaper demo pages. Ex: https://demo.tagdiv.com/newspaper_tech_news_pro/2019/05/13/td-post-hands-on-google-pixel-3a-xl-review/?tdb_action=tdb_ajax

If you can’t believe it, check the above URL.

After loading the page, it will also disable the scroll bar and freeze the page completely.

That’s why I had switched to another theme and removed the newspaper theme entirely from my website.

Hello

As I said many times before that this issue is from your side not any individual site or theme package.

Many people are posting threats on it so it can not belong to some limited sites.

Why do you need someone’s – admin url and credentials, – cpanel url and credentials and – a link to this topic in order to identify you when it is clearly showing problem on your demo theme?

Discover here: – https://demo.tagdiv.com/newspaper_tech_news_pro/2019/05/13/td-post-hands-on-google-pixel-3a-xl-review/?tdb_action=tdb_ajax

You should fix it from your end, in your original theme package.

You should ask your developers to investigate the bug and fix the theme.

English is not my native language but still, I am trying to describe the issue.

I hope you will understand and fix the issue asap and will not ask anyone to share their site’s login credentials because this issue from your product ?

Thanks

The year 2024 has already arrived, and the problem that existed in 2019 has not been solved.
If endless loading is enabled, the template starts creating pages with the address: ?tdb_action=tdb_ajax

Okay, pages can be blocked from indexing in robots.txt by adding Disallow: *?tdb_action=tdb_ajax

But why are there two meta tags:
<meta name=’robots’ content=’index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1′ />
<meta name=”robots” content=”noindex, nofollow” />
????

Are you not going to solve this problem at all?
They have been writing to you about this since 2019, but there is still no solution.