So we see that in a classic tech audit,
Posted: Wed Feb 12, 2025 5:08 am
So yes, you've moved a little further, but you're still out of the running, and so it's a net loss. Or maybe you could rank for lower variations of the key phrases on those pages. However it happens, you can't be sure that just putting high-volume keyword phrases on your pages will lead to better performance. So that's surprising result number one. Surprising result number two is probably not so surprising, but I think it's very important.
Conclusion #2: 30-40% of typical tech audit recommendations don't matter
A up to 30% or 40% of the common ukraine number data don't make a difference. You do all this website auditing. You follow SEO best practices. You find something that theoretically improves the website. You go and make a change. You test it.
Nothing, flatlines. You get the same performance as predicted, as if you didn't make any changes. This is a big deal because it's making these kinds of recommendations that erode trust with engineers and product teams. You're constantly asking them to do things. They feel like it's pointless. They do it all, and it doesn't make a difference. This is what often burns authority with engineering teams.
One of the reasons we built this platform is so we can then take our 20 recommendations and hypotheses, test them all, find the 5 or 6 that move the needle, just go to the engineering team to build them, and it builds so much trust and relationship over time, and they work on things that move the needle towards the product.
Conclusion #2: 30-40% of typical tech audit recommendations don't matter
A up to 30% or 40% of the common ukraine number data don't make a difference. You do all this website auditing. You follow SEO best practices. You find something that theoretically improves the website. You go and make a change. You test it.
Nothing, flatlines. You get the same performance as predicted, as if you didn't make any changes. This is a big deal because it's making these kinds of recommendations that erode trust with engineers and product teams. You're constantly asking them to do things. They feel like it's pointless. They do it all, and it doesn't make a difference. This is what often burns authority with engineering teams.
One of the reasons we built this platform is so we can then take our 20 recommendations and hypotheses, test them all, find the 5 or 6 that move the needle, just go to the engineering team to build them, and it builds so much trust and relationship over time, and they work on things that move the needle towards the product.