So some people just say,

[kexej28769@nongnue]

So this is the same chart and the same situation. This is the actual traffic that you're getting and the hypothetical traffic that you could get. But what's really happening is that your technical issues are preventing you from realizing the potential traffic that you could be capturing. In other words, there are technical issues that are preventing us from capturing all the traffic that we could be capturing. Now, once you've framed the problem this way, how do you solve it?

“Okay, I have this big problem. I need to bulgaria number data how all those things could be going wrong with this site. I’m just going to dive in. I’m going to go page by page, and I’ll finish when either I run out of pages or more realistically I run out of time or my client runs out of budget. So what happens?

Okay, that's the framework I'm going to present to you. The way we would recommend doing this is to take the big problem, the overall technical SEO problem, and break it down into sub-problems and break them down again until you have enough small problems that they're trivially solvable. Now, I'm going to give you exactly how we accomplish this, and it's going to be a little bit abstract.

Perspective
So if you want something concrete to follow along with, I would recommend checking out the blog post at this URL. It's dis.tl/tech-audit . Okay. So when you have a big problem that you're trying to break down, a lot of people's first attempt looks like this Venn diagram. So we take a problem, break it down into three sub-problems, but there's some kind of overlap between those problems.