Try using a different redirect type (especially if you’re using Cloak or Pretty Bar).
Thank you so much for your fast response! I use clocked because I want to hide my affiliate IDs etc. Switched it to 301 permanent and the page loaded but took several seconds too. So is the problem with Cloaked then? How do I resolve this? Or what is the best redirect type to still have the url cloaked? Thank you
Will note that the 301 permanent shows my affiliate id in the URL bar. How do I keep this cloaked?
Depending on the reason for the blank page, there may be no way to get it working.
You can try setting the target URL to https instead of http.
If that doesn’t work, then the merchant may not be allowing iframes any longer.
However 30x redirects are still a form of cloaking: https://prettylinks.com/user-manual-2/cloaking-vs-cloaking/
Thank you for your response again.
I already tried https on my one site that uses https, so it automatically set to that.
So are you saying that Cloaking simply doesn’t work anymore? That is the one reason we purchased the plugin in the first place.
Since this sounds like a plugin issue, when will this be looked into and resolved?
Cloaking (iframe) works in more limited circumstances every year as the industry works to push out iframes as too many people were using them in malicious ways.
However, newer browsers will not load up insecure (http) resources on a page that uses https. An iframe is viewed as a resource, so it won’t be loaded by modern browsers if the iframe (target url) url is http but the page being viewed by the user is https.
Also, many webserver’s set the X-Frame-Options HTTP headers now, which also tells browsers not to allow itself to be iframed unless the domain name including the iframe is allowed: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Frame-Options
So cloaking does still work, and it has its place. But it’s definitely frowned upon as far as SEO practices go – and the industry is moving more and more towards blocking cross-origin iframing.
