YuriV

Yes, but that is still quite complex. I’m going to continue playing with it.

Apologies for the confusion. In the past, I had an amp-redirect and it ensured that all article amp-urls went correctly to the original post. Currently, an amp-redirect is no longer active. However, I recently discovered that amp-urls for my site can still be found in the Google-results.

These are taxonomy urls. Above are some examples I found in Google.

I am looking for a way to redirect these urls in a neat way. I am not getting this done and was wondering if you have any tips on how to redirect the urls properly?

Hello, I am slightly worried about this. We turned on the Complianz plugin yesterday. Do I understand correctly that the plugin creates an additional thumbnail for every uploaded image we need in regular articles?

And does this happen even if we don’t show a logo in the consent banner at all?

In other words: is the snippet given above necessary for every user or only in some cases (depending on plugin settings).

@mrlhd This issue has also been reported and registered as a bug with the creators. See: https://features.wobbie.nl/34

Dag Arjan,

Good to hear that you are going to maintain the plugin again! I will follow the developments and am certainly also interested in the pro version. We use autolinks for internal links to our encyclopedic content (and not for affiliate links).

Hi Thomas,

Thanks for the reply. I was alarmed by Google Search Console. We have a lot of reports about CLS errors there. We then optimized the page so that the CLS errors disappeared from the online reports of web.dev and Google Pagespeed. Case resolved we thought. However, Google Search Console continues to give errors after weeks, so we looked further and used the mentioned chrome extension. After scrolling, CLS-errors do indeed appear (below the fold, when the page reaches the sticky widget), but if they don’t count, the errors at Google Search Console should eventually disappear. Unfortunately, they have a long delay in their results. We’ll wait a bit longer.

Regards, Yuri

Hi Thomas, thanks for the reply. You could check for example this page: https://histobron.nl/wilhelmus-alle-coupletten-van-het-volkslied/

• No CLS warning in the Chrome extension when the page opens
• No warning when scrolling down
• No warning when the user reaches the sticky widgets
• WARNING when scrolling up again, exactly on the place where the sticky widgets end

Regards, Yuri

Hi,

I am testing these kind of issues as well. A very good tool to monitor the CLS is the Web Vitals chrome-extension: https://chrome.google.com/webstore/detail/web-vitals/ahfhijdlegdabablpippeagghigmibma

You can also activated it in incognito mode and see the CLS change while scrolling the page.

I can see CLS-errors while scrolling on my end as well.

Regards, Yuri

• This reply was modified 4 years ago by YuriV.

Thanks.

Didn’t find any pending translations. But after updating Jetpack to version 8.7.1 the search engine displayed dutch terms.

Thanks for fixing this!

FYI: WordPress had an update for a translation file one hour ago. Installed it and cleared caches afterwards. Unfortunately this didn’t change anything for the Jetpack Search Module. It’s still in English.

Hi Jeremy.

Just checked again. Still no pending translations and the search engine is still in English unfortunately.

Also cleared cache and checked it in incognito mode.

Thanks. I don’t see any waiting translation-updates at the moment.

I will check this tomorrow again.

That’s fine. Hopefully this will be solved.

I guess we should post the fix here then as well because I think it can help other users too.

Regards, Yuri

Where did you place it? It’s working on our install.