When will traffic data be working ? also whats with the spike in duplicate listing issues with everyone.
-
Hi There, We have no traffic data, is this something we are doing wrong or is this an issue with SEOMOZ ?
Also duplicate listings have gone sky high, check goggle analytics's and all ok ?
Any answers ?
Thanks
Charlie
-
Glad I could help, Charlie. Let me know if you have any further questions.
-Chiaryn
-
Hi Chiaryn,
Thank you for getting back to us so quickly regrading this issue. I have now found our feed was at fault so after our Friday update hopefully this will be resolved.
Stll looking into duplicate listings
Kind Regards
Charlie
-
Hi Charlie,
Thanks for writing in and sorry that some of your campaign data is looking off.
We aren't having any general issues with traffic data at this time, so I am going to give you a run down of how to double-check your organic traffic in Google Analytics so you can see exactly the data we pull from the Analytics profile.
Log in to GA and select the profile that the campaign is connected to
Click 'Traffic Sources' in the left navigation
Click 'Sources' in that sub-menu
Click 'Search' in that sub-menu
Click 'Organic' in that sub-menu (after clicking organic the graph & data refreshes)
Click the down arrow next to the date range in the top right corner (expands a date picker)
From the Date Range dropdown select '1/21' to '1/27' (for example) and click 'Apply' (graph & data refreshes)If you are seeing traffic in that data once you follow the list above, please send us a screenshot so we can look into why we aren't pulling the data in on your account.
As for the duplicate content, our engineers recently made an update to the crawler that made the check for duplicate content more accurate and it seems that your campaign has been affected by this change. I checked a number of the pages that we are listing through the similar page checker here: http://www.webconfs.com/similar-page-checker.php and all of the pages that I checked that our crawler is reporting as duplicates and it looks like all of those pages are showing as 100% similar in that tools, so it does seem we are accurately reporting your duplicate content pages.
I hope this helps. Please let me know if you have any other questions.
-Chiaryn
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
Slow growth in organic traffic
Hi, Recently our website after 5 months of launch started seeing more organic traffic, thanks to the seo effort being put. However, off late the growth is quite slow and we don't see much increase in organic traffic any more. Any idea on what could have happened to cause this or is it normal. Here is the link to the website to check and if you can recommend anything - https://www.keyhub.com Thanks, Search-Console-Search-Analytics-https-www-keyhub-com-1.png
Reporting & Analytics | | kh-priyam1 -
Important updates on Google Analytics Data Retention and the General Data Protection Regulation (GDPR)
Hi Everyone, I'm sure many of you received the email from Google over the past few days with the subject line: [Action Required] Important updates on Google Analytics Data Retention and the General Data Protection Regulation (GDPR). I hope I'm not alone in not knowing what exactly this whole notification was in regards to. I realize it's for Data but are we no longer able to pull stats from the past? If anyone has a "dumbed down" explanation for what this update entails, I would be very interested - I don't want to miss out on any important updates and info, but I'm just not grasping this content. Below is the full email in its entirety for those who are interested as well: Dear Google Analytics Administrator,
Reporting & Analytics | | MainstreamMktg
Over the past year we've shared how we are preparing to meet the requirements of the GDPR, the new data protection law coming into force on May 25, 2018. Today we are sharing more about important product changes that may impact your Google Analytics data, and other updates in preparation for the GDPR. This e-mail requires your attention and action even if your users are not based in the European Economic Area (EEA).
Product Updates
Today we introduced granular data retention controls that allow you to manage how long your user and event data is held on our servers. Starting May 25, 2018, user and event data will be retained according to these settings; Google Analytics will automatically delete user and event data that is older than the retention period you select. Note that these settings will not affect reports based on aggregated data.
Action: Please review these data retention settings and modify as needed.
Before May 25, we will also introduce a new user deletion tool that allows you to manage the deletion of all data associated with an individual user (e.g. site visitor) from your Google Analytics and/or Analytics 360 properties. This new automated tool will work based on any of the common identifiers sent to Analytics Client ID (i.e. standard Google Analytics first party cookie), User ID (if enabled), or App Instance ID (if using Google Analytics for Firebase). Details will be available on our Developers site shortly.
As always, we remain committed to providing ways to safeguard your data. Google Analytics and Analytics 360 will continue to offer a number of other features and policies around data collection, use, and retention to assist you in safeguarding your data. For example, features for customizable cookie settings, privacy controls, data sharing settings, data deletion on account termination, and IP anonymization may prove useful as you evaluate the impact of the GDPR for your company’s unique situation and Analytics implementation.
Contract And User Consent Related Updates
Contract changes
Google has been rolling out updates to our contractual terms for many products since last August, reflecting Google’s status as either data processor or data controller under the new law (see full classification of our Ads products). The new GDPR terms will supplement your current contract with Google and will come into force on May 25, 2018.
In both Google Analytics and Analytics 360, Google operates as a processor of personal data that is handled in the service.
• For Google Analytics clients based outside the EEA and all Analytics 360 customers, updated data processing terms are available for your review/acceptance in your accounts (Admin ➝ Account Settings).
• For Google Analytics clients based in the EEA, updated data processing terms have already been included in your terms.
• If you don’t contract with Google for your use of our measurement products, you should seek advice from the parties with whom you contract.
Updated EU User Consent Policy
Per our advertising features policy, both Google Analytics and Analytics 360 customers using advertising features must comply with Google’s EU User Consent Policy. Google's EU User Consent Policy is being updated to reflect new legal requirements of the GDPR. It sets out your responsibilities for making disclosures to, and obtaining consent from, end users of your sites and apps in the EEA.
Action: Even if you are not based in the EEA, please consider together with your legal department or advisors, whether your business will be in scope of the GDPR when using Google Analytics and Analytics 360 and review/accept the updated data processing terms as well as define your path for compliance with the EU User Consent Policy.
Find Out More
You can refer to privacy.google.com/businesses to learn more about Google’s data privacy policies and approach, as well as view our data processing terms.
We will continue to share further information on our plans in the coming weeks and will update relevant developer and help center documentation where necessary.
Thanks,
The Google Analytics Team6 -
Https Referral Issues
Hi Moz! We are having some trouble passing along referral data to our linked websites. We are an advertising platform that counts on our clients seeing our traffic in analytics. We recently switched to HTTPS and implemented the meta referral <always>however, we are still experiencing issues with clients not seeing our referral traffic. Are there other ways to make a full-proof fix so they will always see us as a referral? I know the referral tag should help but it isn't supported by all browsers. </always> Also, would there be an issue if we have our site (https) linked to their http site that redirects to https? Even with the referral tag, we are seeing issues. I feel so lucky that our actual transition to https went fine but now with all this referral traffic on clients analytics, I am concerned we are losing the credit we should get for the traffic to their site. Thanks Moz Community!
Reporting & Analytics | | GoAbroadKP0 -
Oh Japanese Character and 404 issue
This one has me stumped, so I really hope someone can help. I am assisting a company who are having 404 errors on certain japanese pages of their site. I have checked in web master tools and analytics, can see the 404, but have no idea where it is coming from. I am starting to think it may be a encoding issue of some sort. Just wondered if anyone has come across this before? Site uses site finity. What is happening is reader is going to page domain.com/ja/blog/article then coming to this page /404?aspxerrorpath=/Sitefinity/WebsiteTemplates/App_themes/"website"/fonts/open sans regular Really odd - as we cannot re-create this 404 I don't know how they are getting to it? Also in Analytics some of the pages that are written in japanese that are giving 404's look like this C3%A3%E2%80%9A%C2%BD%C3%A3%C6%92%C2%AA%C3%A3%C6%92%C2%A5%C3%A3%C6%92%C2%BC%C3%A3%E2%80%9A%C2%B7%C3%A3%C6%92%C2%A7%C3%A3%C6%92%C2%B394.8%C3%A3%C2%81%C2%AE%C3%A5%C2%AF%C2%BE%C3%A8%C2%B1%C2%A1/%C3%A9%C2%A1%C2%A7%C3%A5%C2%AE%C2%A2%C3%A3%E2%80%9A%C2%B0%C3%A3%C6%92%C2%AB%C3%A3%C6%92%C2%BC%C3%A3%C6%92%E2%80%94%C3%A6%C2%AF%C5%BD%C3%A3%C2%81%C2%AE94.8 Any help much appreciated
Reporting & Analytics | | Kelly33300 -
Bot Traffic Higher Than Unfiltered?
We filtered bot traffic from one of our Google Analytics accounts and traffic is higher than with the unfiltered view. Does anyone have an idea what might be causing this?
Reporting & Analytics | | Leithmarketing0 -
Will benchmarking only be available in universal analytics or all analytics?
With the announcement of benchmarking in Google Analytics I was wondering if I would have to upgrade to universal analytics or will it be available to everyone?
Reporting & Analytics | | EcommerceSite0 -
Google Making all searches secure - "Not provided" data to increase in Analytics
A lot of you might already be aware of the recent Google change at encrypting all search activity except for clicks on ads. Rand did a whiteboard session on this recently. How is everyone planning to adjust their research data to accommodate for this change?
Reporting & Analytics | | SEO5Team0 -
Webmaster tools traffic on one keyword dropped through the floor - ideas?
Hi there, We design and sell our own product range in a narrow niche, and we are also stocked by Amazon and a lot of other big retailers in the UK. During the first two weeks of Dec 2012 the position of one of our main keywords, which was in google SERPs on page 1 (8 or 9), dropped to page 4. The keyword describes the niche we're in. The drop is shown in the webmaster tools traffic report for that keyword. But it's the only one of our keywords where this has happened, and furthermore it hasn't happened for variations of the keyword. And in Adwords our quality score for the keyword is 10 For example say we were making and selling shopping trolleys - our keyword "shopping trolleys" has dropped through the floor, but "shopping trolleys (on) wheels" is just fine. Can anyone shed any light on what's going on here? Losing this one keyword has cost us some good organic traffic. i1uxSlB.png
Reporting & Analytics | | w1ll1am0