I have problem with Alexa tracking for a website (eg: example.com) that redirects from non-www to www.
For some reason, Alexa displays the inbound links from the non-www version istead of the www version. For the www version I have over 2000 inbound links but on the non-www one I only have 10.
Is there any way I could make Alexa show the correct number of inbound links?
Thanks
make sure you are using the correct links in your sitemap and especially your dmoz listing.
Related
I set up our messaging service to allow for link shortening within Twilio. I am particularly interested in link tracking capabilities and webhooks.
Added the website domain, verified it. Put in the DNS TXT records according to their instructions. Everything seems to be in order. Yet when I send a link with the ShortenURL=True the link sends as a shortened link but when clicked it doesn't redirect so it takes the user to a 404 page.
I am wondering if there is an issue with the DNS records... or if I am supposed to configure a special domain exclusively for our own shortened links.
the shortened link:
https://portraitsbychristopher.com/qMqpqUP9Wg
Where it should redirect:
https://portraitsbychristopher.com/Tiaras
Tried reading the Twilio docs.
I host a CDN for static resources. While monitoring some 404 errors came up on old images.
I suspect some partner of ours to still call the images on their site and would like to find out which to contact the appropriate one.
There is no Referer header in the requests, the ip are from residential ISPs, the User-Agent are from mostly up to date browsers so I think the users are legitimate.
I tried to Google the urls or part of them but no luck so far.
I can't crawl partners websites as I don't have a list of the domains they use.
How can I find out what site is still calling theses old images ?
I am whitelisting some of the urls on my corporate firewall for a botframework app. The urls to be whitelisted are provided in this link.
But when I tracked the outgoing traffic from my local development, I saw that url (smba.trafficmanager.net) was also being used which is not listed in the whitelist urls provided in microsoft documentation website. Do I need to whitelist this?
Since this is the ServiceUrl for conversation between user and the bot and is supposed to change in time, do the whole url (including domain, subdomain, port) changes or just the paths?
Yes, you'll need that one as well for proactive messaging, but the base url should be fine - it's just the paths that change (e.g. https://smba.trafficmanager.net/apac/ or https://smba.trafficmanager.net/in/ or https://smba.trafficmanager.net/emea/).
I have universal links implemented, working fine. I send an email to a user, then iOS will open the app if it's installed, or it will go to my website if not. At which point, I use apache mod_rewrite to redirect to a page which gives information on installing the app.
However, some users have hotmail accounts with advance threat protection enabled. So the URL they receive in their inbox is wrapped with https://nam10.safelinks.protection.outlook.com/? ... which when you follow it, eventually redirect to the correct url. Which opens the app fine on iOS 14, however on iOS 13 it takes me to the web site, regardless if the app is installed or not.
So on iOS 13 the safe links protection totally breaks the universal link configuration.
I'm trying to find way around this. My current thought is to use mod_rewrite to forward to a custom URL, but struggling with that, as mod_rewrite likes to add http:// in front of my redirects.
Has anyone else experienced this? I've seen one stack overflow post on the subject, but not with a solution that works for me.
Don't know if this is a common thing, but i realized that any url i share through WhatsApp desktop app (Mac & Windows) will send you to https:// by default.
Any one else had this experience?
Adding rules to redirect https traffic to http didn't work for me.
Any clue how to avoid the error messages clients are seeing when any one shares my url on WhatsApp desktop app?
Thank you