Welcome to the Q&A Forum

We have some URLs that are being flagged as poor inside Search Console in the Web Core Vitals report. For example, the report is saying that some pages have too many CLS issues. When looking into things we can do to update we have noticed that when we run the same page using the PageSpeed Insights tool we are not getting the same bad scores. This is making it hard for us to actually know what needs to be addressed. Nor can we tell if a change actually fixed the issue because in PageSpeed Insights there is not an issue.  Has anyone else had similar issues. If so have you found a way to fix it?

For the most part in the past our company has worked on location. So filtering internal traffic was as simple as filtering out our company IPs as well as a few remote workers IPS. Now a large number of employees are working from home due to Covid-19. I am seeing an uptick in traffic that is clearly employee-related. I am hoping some of you who work with large remote teams may have some suggestions on how to best filter out traffic from remote working employees.  I found a few articles from a couple of years ago where people were using a cookie but not sure we can get that implemented in time as our Dev team is backed up. Any help is much appreciated.

For sever work- load enhancements we are planning to move our images to a sub-domain. so the files would be located at something like images.domain.com Rather than domain.com/images/ We are a large Ecommerce site so we have a lot of images. These will be self hosted so we are not using a CDN. I'm hoping someone has done the same and if there were any steps they had wished they had taken before making the move/ if they noticed any traffic impacts things like that.

Large ecommerce site that has been around for a long time (15+ years.) During that time technology has changed a lot and we are running into issues maintaining 301 redirects for very old urls. For example we have a good amount of links to product and category pages. Some of the old links are to products that still exist and will exist for many years to come.(of note little to no traffic comes via these links. Most of them are close to 9 years old so they are buried deep within articles, forums, or websites) However as we make changes to the site and URL structure these old urls are taking up more resources to continue to maintain 301 redirects. I am Leary of no longer supporting them because I do not want it to impact rankings however there is concern on how much development time and technology resources it takes to continue to support as time goes on. Does anyone have experience handling redirects 3 or 4 url structures old? Looking for insight from someone who has crossed this bridge before.

I am looking for help on using Googles Reverse an Ecommerce Transaction in Analytics work flow documented here: https://support.google.com/analytics/answer/1037443?hl=en&ref_topic=1037062 Essentially an incorrect transaction was processed that was for such a large number that it is really messing up reporting. I have never used Googles outlined process and from my research it looks like it might not reverse the transaction for the date it was placed but ad a negative amount to offset it on the date submitted. This will still work for year of year reporting but it will mess up the data for two different days in one month. If someone who had done this before has any insight please chime in thanks! Here is a support thread about the reverse transaction messing up a different days data. https://productforums.google.com/forum/#!searchin/analytics/reverse$20transaction/analytics/gDiVNJDwx5I/BwlNJ9D6Lp8J

We are working on a site redesign which will change/shorten our url structure. The primary domain will remain the same however most of the other urls on the site are getting much simpler. My question is how should this be best handled when it comes to sitemaps because there are massive amounts of URLS that will be redirected to the new shorter URL how should we best handle our sitemaps? Should a new sitemap be submitted right at launch? and the old sitemap removed later. I know that Google does not like having redirects in sitemaps. Has anyone done this on a large scale, 60k URLs or more and have any advice?

We are making significant URL changes to our website. Because the URL is changing the social sharing buttons are not showing previous shared counts. I have read several resources like the one below that is linked to in several other similar questions. http://searchenginewatch.com/article/2172926/How-to-Maintain-Social-Shares-After-a-Site-Migration However I would love to get some insight from someone who has done this and there thoughts on the outcome. As an ecommerce site the "Social Proof" of products that have received social shares is a big deal to us. In Mike Kings example above the counts are being attributed to the OLD URL which is problematic over time. Our site has been up for over 12 years and has had several major changes to it, and I am certain there will be more in the future, being able to preserve the count on the current URL is ideal. While I agree with him that over time I believe social platforms will let data pass through 301 redirects, until then I need to find the best way to do this.  Also with his example and others I have seen people mention than new likes from the new url can reset the counter. If you have gone through this and have ideas pleas share them. I look forward to your thoughts thanks.

I recently took over as the SEO for a large ecommerce site. Every Month or so our webmaster tools account is hit with a warning for a high number of URLS. In each message they send there is a sample of problematic URLS. 98% of each sample is not an actual URL on our site but is an AJAX request url that users are making. This is a server side request so the URL does not change when users make narrowing selections for items like size, color etc. Here is an example of what one of those looks like Tire?0-1.IBehaviorListener.0-border-border_body-VehicleFilter-VehicleSelectPanel-VehicleAttrsForm-Makes We have over 3 million indexed URLs according to Google because of this. We are not submitting these urls in our site maps, Google Bot is making lots of AJAX selections according to our server data. I have used the URL Handling Parameter Tool to target some of those parameters that are currently set to let Google decide and set it to "no urls" with those parameters to be indexed. I still need more time to see how effective that will be but it does seem to have slowed the number of URLs being indexed. Other notes: 1. Overall traffic to the site has been steady and even increasing. 2. Google bot crawls an average of 241000 urls each day according to our crawl stats. We are a large Ecommerce site that sells parts, accessories and apparel in the power sports industry. 3. We are using the Wicket frame work for our website. Thanks for your time.