Reviewing site Architecture
now that we've taken stock of our website, we know how many girls we have and relatively how those girls are performing. It's time to focus on site architecture. Site architecture is basically the study of how websites are structured. We want to make it very easy for google to access our site and understand what it's about. And we want to make it very easy for our internal teams to work on the website, add new pages and optimize templates and folders. And so that's what side architecture is. All about. two other tools I should mention for controlling your site architecture Dino Mapper. All you do is you put in your you are all here, your base, your and I don't work with left. I just crawled their site using Dino Map or you can crawl any site. Um it'll give you the homepage, it'll tell you what each folders name is and then what are all the urals associated with each folder. If you're connected to google analytics, you can see traffic data and you can leave comments if you're working wi...
th a team and say, hey, I want us to update this or change this with the page. It makes it really easy to work with content teams. Dino map or does the other tool is sem rush some rush does have uh site audit feature kind of like site bulb. And the nice thing about it is you go to site audit and then you go to crawled pages and then you can see each individual page if it has google analytics traffic, it'll say it if you're connected a number of issues or problems that is found with this page. And then you can see the site structure which allows you to see how many euros they have in each folder. Allows you to even click down two subcategories. So you can get a sense of how much content is in each folder. Now if you don't have any of these, but you were able to print out all the rankings from sight from some rush and match it with um site bulb. Then what you can do is just dump all of your that list into your scr research spreadsheet which I highly recommend doing because this is a great spreadsheet to use to work with different teams. So we're already working with the development team on the S. C. O. Recommendations here. And if some of these recommendations are redirect this pattern of us. Well you should just be able to give them examples from this sheet. And this is also why I recommend exporting your errors from sight bulb into this sheet rather than google search council because through site bulb and the sem rush the look up, we're going to have traffic and all these things that we can filter on and to really work with our different teams. So if you're working with engineers and looking for problems that problem you identified using psychic bulb, you can filter for it here and then find all those examples of that problem. Here is one example and then I would just put action is 301 redirects that tells the engineer what kind of redirect to use. And then the target can be the base CRL or you can actually put in the base euro, which is kids health dot org slash en slash parents slash Kawasaki. That is a basic moral and you can do that for each one of those. So it makes it really easy to coordinate with development teams and then content teams. What I usually use with this is I'll filter by traffic or by keywords and find the ones that aren't ranking well. And then we'll decide do we want to cut these pages entirely? No index them or redirect them to another page. Or if we need to optimize this page. So if it has a lot of content and not a lot of links, maybe we just need to optimize it. Rather than just cut the page entirely. So that's kind of how I think about side architecture and how I use it to work with different teams and hope that was helpful and see in the next lesson