Sorry if this is the incorrect area.
I develop websites using Yootheme and Rockettheme. they have a coded area in the backend where you simply enter the code from Analytics.
however lately im getting emails stating the following;
Message summary
Webmaster Tools sent you the following important messages about sites in your account. To keep your site healthy, we recommend regularly reviewing these messages and addressing any critical issues.
http://www.anigmabeauty.co.nz/: Googlebot can't access your site
Over the last 24 hours, Googlebot encountered 1 errors while attempting to connect to your site. Your site's overall connection failure rate is 50.0%.
You can see more details about these errors in Webmaster Tools.
I've deleted them and re-added the websites, works for a while then does the same thing. Any ideas on how to fix this.
When I open http://www.anigmabeauty.co.nz/ I get 303 See other redirect. It may cause the issue since 303 redirect is not so good for SEO.
Try to replace 303 redirect with 302 redirect.
Related
Recently I've been experiencing a large amount of (what I think is) ghost traffic.
I need help in creating a filter to exclude this traffic from my Google Analytics.
URL's are showing up that have other websites appended to them.
Almost all articles I've read mention including only relevant hostnames but this doesn't seem to apply to my situation.
Here you can see the URL's with other random website addresses.(overworlf.com/evite.com/shmoop.com and many others)
Here is a screenshot of the hostnames none of them are out of the ordinary. I suspect this ghost traffic is using my main domain looking at the huge amount of users.
Posted the same question at stackexchange, someone there was able to help me
https://webmasters.stackexchange.com/a/118666/94264
"Almost all the analytics spammers insert data into your stats by pinging the GA tracker directly with fake data. They never visit your site and they usually just guess at the tracking id without knowing website host name associated with it. They won't send a host name, so it wouldn't appear in that report. See How to fight off Google Analytics referrer spammers?
That appears not be the case here. In this case these appear to be actual hits to your website. I tried one of those "top active pages" and it gives a 404 error. It looks like your 404 template has the GA tricking snippet installed on it. I don't think that is best practice. You could try taking the snippet off your 404 page. Then if you did get actual hits to such URLs, GA wouldn't count them as pages."
This can happen when there are search and replace or advanced filters. Are there filters on your view that alter the Request URI?
EDITED AFTER IT WAS CONFIRMED THAT THERE WERE NO FILTERS:
Typically, tracking 404 pages is best practice (referring to your other post).
I don't believe that removing the tracking from that page will help anyway. Like the other poster mentioned, these hits are sent from bots most of the time and they never actually land on your site. The hit is sent directly to your property with an http call. It bypasses the site completely, so whether there is a 404 page or not, the hit will show up in GA.
Adding an exclusion filter to exclude traffic with a page path (not hostname) ending in ".com"
When sharing the URL on LinkedIn, the OpenGraph data won't show up. I did validate the data. Is this maybe a domain issue?
The url i tried to share was:
https://overons.kpn/en/news/2017/kpn-and-major-suppliers-aim-for-circular-operation-by-2025
edit: following error was thrown on just the domain: i18n_url_preview_error
So LinkedIn share was working fine for me.
Today I started facing this error after moving on HTTPS.
Here is what I did :
While sharing URL, use http instead of https on LinkedIn and it will work (assuming that http redirects to https on your website).
I tried it for my site CoverMyStartup today. If this doesn't work, let me know.
The LinkedIn system does not recognize many of the new top level domains as being valid, as many of them have become a huge source of spamming and scamming.
Works perfectly fine for me. As usual, make sure you are URL-encoding your parameters...
https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwww.overons.kpn%2Fen%2Fnews%2F2017%2Fkpn-and-major-suppliers-aim-for-circular-operation-by-2025
See:
Maybe it was rejecting .kpn domains previously, but it seems to be good and working now!
When I try to use Linkedin to login to my site on Google App Engine I get a 999 error. I think it must be blocked there because on my local machine the login does work fine.
Some other sites on app engine seem to have the same problem. My only conclusion is that the ip range of app engine must have been banned by linked on purpose or by accident. I think it must be by accident because of how many sites this must affect.
I do not think that it is only related to the Google App Engine, but rather kinda strict blocking policy at LinkedIn. Check out this post here: 999 Error Code on HEAD request to LinkedIn
It seems that LinkedIn also blocks request based on user-agent.
and HTTP Error 999: Request denied
and How to avoid "HTTP/1.1 999 Request denied" response from LinkedIn?
I'm testing out a plugin on a Wordpress site to prevent referral traffic. The default setting is a redirect to google.com. I can override this and display a 403 error instead.
Do you see any advantage with one over the other?
From what I have read when researching how to deal with this issue, most of the referral 'spam' you are getting in google analytics doesn't actually come from hits to your site, but instead it is done by spammers exploiting google's analytics code, by using random tracking IDs, and they up end up using your ID too.
Having said that, I don't think a wordpress plugin can do anything to prevent that kind of spam as they don't ever reach your site, and I believe the vast majority of referral/analytics spam being done currently is using the method mentioned above.
So the best way to get rid (or at least largely reduce the amount) of referral spam you're getting is to set filters within your google analytics dashboard. Even the methods for that are constantly changing, as google keeps improving that service, but here's two fairly recent articles that may help you configure those:
https://www.distilled.net/resources/quick-fix-for-referral-spam-in-google-analytics/
http://www.shivarweb.com/4635/filter-analytics-spam/
I have a wordpress site with Membership and Events. I am using Paid Membership Pro for memberships and Event manager Pro for events. I am using Authorize-net payment gateway and most event bookings are successful.
But I can see some booking in the Admin with the status Processing(Authorizenet AIM).
I have log to the Authorizenet and there is no processing transaction for this booking.
Could you please help me to solve this. What is the reason for that status?
Thanks
You will need to have SSL enabled for you site otherwise this will not work. Events manager will always force the https connection if a booking form accepting Authorize.net is used.
Wideload Shipping may be correct here, if you don't have a valid SSL certificate or SSL enabled then the booking process won't work with Authorize.net since you must be able to send card info securely.
I'd suggest you ask this on our pro forums, as a pro customer we'd be happy to help you troubleshoot there. If you supply us a link we can also probably have a better idea about what's going wrong and provide you with further steps to remedy the issue.
I noticed this same behavior starting to happen on my Events Manager Pro as well. Seemingly randomly some bookings will show "Processing (Auth.net)" while others show "Completed" (as they should).
From this thread's suggestion, I took a look at my https URLs. I found that sometime in the last month, we ran an update that has inserted some link hrefs and other unsecured URLs in the source code.
I had been using HTTPS plugin to force https on the events pages, but since the site URL was http only, it was pulling in these "external" files as http. I noticed in Firefox that my SSL connection showed broken. While in Chrome, it felt it was secure. My GUESS at this time is that the ones that go thru are where the page in the browser looks to be secure. While the ones that only get "Processing" are happening on the broken SSL browser views.
I've now changed my site URL to https as the base URL which ensures Wordpress uses it throughout. I now don't get a broken SSL in Firefox. My presumption is that this will fix this issue. Time will tell. I'll come back to update IF I'm wrong. But hopefully that might help for you to look at URLs, such as wp-json and other link rel URLs.
Of note, it seems the credit cards ARE authorizing/captured for those transactions. So it's more likely the return trip from Auth.net for the silent URL to changes the status of the booking?