If you have all these ideas and previously you're asking your team to build all of them, but if you run tests and you find that some of your ideas were negative, some of them were ineffective and weren't going to benefit you, you're now only asking your product and engineering team to maintain the ones that turn out to have a positive SEO impact. We've seen that be up to an 80% drop in SEO tickets for engineering.
So that's one business case right there. But, of course, sometimes your tests australian email list look like this, and so actually the business case is about avoiding those negative impacts on your website. Tactical examples So I've got a couple of tactical examples that I thought would be good to run through that might be useful in your situations as well. The first one is a case of removing SEO text. So we've seen many cases where think, say, a category page on an e-commerce website, for example.
listings, and then somewhere down at the bottom of the page, there's a bit of copy. Maybe it's in a div, seo_text. Maybe it's a really small font, gray, not exactly white on a white background, but clearly not designed for human eyes. We have run some experiments where we had situations like that, with pretty poor-quality text on category pages. We tested removing it and actually saw a statistically significant drop in organic visibility, which is a shame, because we know that this isn't high-quality text, we know it's not where Google wants us to be, and yet removing it was a bad idea.