According to John Mueller, the answer is no (at least in the long term)

https://www.seroundtable.com/google-long-term-noindex-follow-24990.html

Hi Moz Community,

I have a question about personalization of content, can we serve personalized content without being penalized for serving different content to robots vs. users? If content starts in the same initial state for all users, including crawlers, is it safe to assume there should be no impact on SEO because personalization will not happen for anyone until there is some interaction?

Thanks,

Hi Moz community,

Our tech team has recently decided to try switching our product pages to be JavaScript dependent, this includes links, product descriptions and things like breadcrumbs in JS. Given my concerns, they will create a proof of concept with a few product pages in a QA environment so I can test the SEO implications of these changes. They are planning to use Angular 5 client side rendering without any prerendering. I suggested universal but they said the lift was too great, so we're testing to see if this works.

I've read a lot of the articles in this guide to all things SEO and JS and am fairly confident in understanding when a site uses JS and how to troubleshoot to make sure everything is getting crawled and indexed.

https://sitebulb.com/resources/guides/javascript-seo-resources/

However, I am not sure I'll be able to test the QA pages since they aren't indexable and lives behind a login. I will be able to crawl the page using Screaming Frog but that's generally regarded as what a crawler should be able to crawl and not really what Googlebot will actually be able to crawl and index.

Any thoughts on this, is this concern valid?

Thanks!

Thanks for your help on this Nigel

Hey Nigel,

These parameters are already in my search console but Moz is still picking them up as duplicates.

Hi Nigel,

Thanks for the response and the post, I've actually read the article before and used the rel=next and rel=prev to fix some duplicate content issues because of pagination in the past.

Right now, the rel=next and rel=prev is not solving my duplication problems because pagination isn't the issue so the speak. The duplication is occurring because i have two page types (one at view 60 items and one at view 180 items - kind of like a filter) Each view (60 & 180) has their own set of pagination rules but it looks like page 4 of the 60 view is a duplicate of page 2 of the 180 view if that makes sense.

It becomes really tricky here to try and find a solution.

Hi Moz Community,

We're an eCommerce site so we have a lot of pagination issues but we were able to fix them using the rel=next and rel=prev tags. However, our pages have an option to view 60 items or 180 items at a time. This is now causing duplicate content problems when for example page 2 of the 180 item view is the same as page 4 of the 60 item view. (URL examples below) Wondering if we should just add a canonical tag going to the the main view all page to every page in the paginated series to get ride of this issue.

https://www.example.com/gifts/for-the-couple?view=all&n=180&p=2

https://www.example.com/gifts/for-the-couple?view=all&n=60&p=4

Thoughts, ideas or suggestions are welcome. Thanks

Does anyone have insight into the session percentage lift for their blog or their site after making the move from a subdomain blog to a subfolder? I'm seeing a lot of people talk about improvements in rankings for keywords on their blog and site but haven't seen anyone list out session numbers to go with that data.

Thanks

I recently filtered query information by week and day. The impression and click totals were different depending on whether I looked at totals by a full weeks or by day.

So for example, the impression and click totals when I choose a date range of  monday-sunday are different when I look at impressions and clicks that same week by day and then add up the click and impression numbers to get a weekly total. At first i was expecting a slight difference since I know the data is heavily sampled but the totals were very different.

Any explanations for this?

Thanks

Hi Moz Community,

We've been implementing new canonical tags for our category pages but I have a question about pages that are found via search and our filtering options. Would we still need a canonical tag for pages that show up in search + a filter option if it only lists one page of items? Example below.

www.uncommongoods.com/search.html/find/?q=dog&exclusive=1

Thanks!