How to do a technical SEO audit | Barry Adams at Optimisey

[Music] [Applause] thanks for coming out tonight first usual disclaimers I swear apologize to the people watching this on YouTube this is 18 plus video I'm gonna talk about technical SEO I do a lot of technical SEO probably too much and because I don't like people and I still have to explain my recommendations to people sometimes people say things like this about me this was actually typed in a slack channel by alley deaf as I was talking through an SEO audit but the lead deaf hadn't realized that his CTO who was also on the call was sharing his screen with me while he had slack open I wish I was fast enough to take a screenshot but a CTO very quickly switch tabs I'll come back to this later on by the way but yeah I rub people the wrong way sometimes but I see that as that's part and parcel of what I do as you know my job as an SEO consultant um I'm gonna talk about SEO audits how I do them and the kind of thinking that goes into crafting audits and audit reports who here is agency side by the way who here does SEO audits regularly specifically technical SEO audits so yeah I might not be able to teach you much but you know at least you get a glimpse into what goes onto this warped brain of mine web search engines are information retrieval systems information retrieval is a sub-discipline of computer science it's interesting reading material if you ever the cing inclined Stanford University where the two Google founders were studying before they found at Google have their entire information retrieval book for free to read online the mathematics in it get complicated quite quickly but it is still worthwhile reading through at least the first few chapters just to get a bit of an idea of how they think about building search engine technology information retrieval technology because it will help you become a bit more aware of how search engines work what are capable of and what are not capable of and why they need help for most webmasters and SEO still get that in order so yeah all of you maybe we'll go back to that slide have three main components and crowd : in external rancor and Googlebot terminology the koalas Googlebot the indexer is the caffeine infrastructure the rancor is Google's front end where you type stuff in and you get the results this is how Google describing the cell this is a fairly old slide fairly old diagram from them engineering wise so it's probably not entirely accurate anymore but it shows you you know you got the calling infrastructure the indexing infrastructure and then this is the search front-end when I do SEO I have a three peels of SEO model I see that my phone's didn't properly download sorry Andy that's nine did will not Jesus really up you will notice that there's not a coincidence that my three pillars of SEO aligned with the three main processes of a search engine what technical SEO is primarily about caller relevancy on-page optimization is primarily about the indexer an authority link building is about ranking first in google so there's a bit of overlap between the different tactics but generally speaking when we do one thing to optimize our website's we tend to optimize for one particular component of Google service so for me technical SEO is primarily about call optimization making sure things get called very fast very efficiently by the caller and fairly quickly get parsed by the call of mobile SEO signals javascript and international SEO signposting is also part of that particular limit on page optimisation that's classic old-school SEO that's just title tags meta descriptions good content internal linking etc etc structured data is part of relevancy not necessarily part of technical SEO but I always deal still cover it as part of technical CEO because it's code and code is a key for people with a marketing background and therefore all the icky stuff falls on the technical SEO and authority in ranking that's just about making sure that you were ranked first in Google you know spamming the at Google basically before you get caught technical SEO audits for me like I said focus primarily on the corner with quite a hefty chunk also looking at the relevancy aspect I don't really do much a link analysis as part of my technical audits in the old bells and those full range orders yes I do but in technical SEO how our website link to that website is not really my problem it's more about making sure that the website itself is fully optimized and it can be crawled and indexed as efficiently as possible with as little obstacles as possible so what is an SEO audit and what do we mean when we use this terminology of an SEO audit is it a stack so is it a report that you've won from screaming for called deep qual and you slap your own brand on it no I hate it that people do didn't do this and call it an order that really pisses me off anybody can want a coral port from a tool like screaming for signed Bob or whatever and slapped on Brandon and say hey we've audited your website and I cannot begin to express how annoyed that makes me feel because that's not an order that that has no analysis no contacts nothing to it that's just an automated system and automated systems no matter how good they are lack any sort of context any sort of awareness any sort of depth Google is one of the smartest automated systems in the world and they get wrong all the time so don't pretend as an SEO or the tool can can do your job for you it's also not a stack of papers that sits on somebody's desk gathering dust if your audit is apt then sorry unfortunately this is not something you tend to have a lot of control over once you've delivered an audit you have a certain level of influence with how you phrase the actions coming out of the audit and try to make them as actionable and implementable as possible but in the end it is up to the client up to the person the people you deliver the order to to actually makes it happen and that doesn't always happen and that can be real pain in the ass I think if if if I'm lucky when I deliver in order to have my recommendations will get implemented the other half just never happens no matter how important they may or may not be if it's more than half I'm working with what I call a good client that's for me and all that is the start of a process it is identifying the opportunities using SEO theory to find opportunities to make a website improve its organic search visibility and it's always the start of a process the oddity is the beginning never the end the order for me orders are primarily an end product it's mainly what I do as a service but I always realize that it's always a start of a process for the client the order needs to initiate something needs to begin a certain process on the end of the recipient the people who commissioned the audit to make happen to make stuff improved on the website say that they see graphs go up that's what the old care about they want the graphs to go up traffic sales everything that comes with it I love this particular diagram this is not mine some guy could gange clear I was first pointed this by Richard Baxter from Bill visible and I've started including it in the introduction text of every single order that I ever do it's the aggregation of marginal gains where a little improvement here and there over a long period of time will yield massive results anybody here follow Formula One racing a little bit that's what Formula One does they start with a car at the start of the season at the end of the season their car was three seconds a lot faster than many started because they make tiny little improvements every single race making it slightly faster slightly better and the end of the season is three four seconds faster than a lap that's not a for an Formula One team can make the difference between ending up with twenty million dollars pay off or one hundred million dollars pay off at the end of the season depending on where they end up in the Constructors Championship and I see audits and websites in general websites in general are the same if you do not constantly improve a website you're on the red line you didn't even have to do anything to make it worse just let it sit there statically you're already making a worse website it's going to get worse new doing nothing is walking backwards you have to constantly improve you have to put the effort in make small tweaks make it faster make it better optimise conversions optimize search up to my social to my email every single part of it constantly all the time if the website just sits there doing its thing you're going to lose and quite painfully so so before I even start an audit before anything after the paperwork usually assorted I ask for search console access I do not touch the website before I have access to Google search console I can't just this is the single most important source of I have for SEO to analyze the website this is the old Google search console we will be saying goodbye to this in less than two weeks and typical Google fashioned they've made it worse and call it an improvement you google so very shortly but only of this yay so we'll have to work with what we're giving we don't really have a choice even then no this is not an improvement it is still the best data source you have you know the call hours report you should be my go-to for mainly technical SEO scenarios now we have to work with index coverage the next couple of weeks we'll live with it you know you don't necessarily get the same granular data but you know you can make it work if you don't get search console access you can't properly audit a website in my opinion you can do it without a lot of data I mean I like getting Google Analytics data I like getting server log files but if I don't get them I'm fine I can't do all that without search console I'm just you know a man sitting in a cave watching shadows walk by if I don't have search console so yeah the must have a search console analytics and log files are nice to have and I don't really need more data than that because in the end it is about you know you don't need back-end access to websites you know it's sometimes nice there but you don't really need it because the backend Google never sees the backup search engines don't lead it back and they see the front end and the front end you can look at yourself you can open your browser and you can look at the front end of the website you can have tools like deep core screaming for whatever you use look at the front end that's what Google sees so that's what you analyze that's what you base your orders recommendations on it helps to know what the back end this so you can formulate to write recommendations and put them in the right context because if you know what sort of platform a website is built on you know or learn from experience that that can be easy to fix and that because it's built on that platform can be real pain in yes for example you can do an analysis on a Magento website which has like 200 different CSS and JavaScript files that it calls and loading a single page and you give the recommendation we'd use that but you know because it's Magento it's not going to be reduced it's you might as well recode the entire website and start from scratch that's just Magento is a beast of a system you end up with certain weaknesses in Herrin the tools that are used to audit I like a little warden little warden is intended initially just to keep an eye on when goes wrong on websites and saying you were warning it's it's an hourly or daily monitoring of websites that the triggers things like checking if he has robots meta tags longer checking the Canonical's checking for for all that stuff but even just launching it and doing a first scan of a website you'll tend to get pointed in certain directions that stuff might go wrong might be wrong with the website for example little warden will check if a for for not found even non-existent ul actually gives a 404 HTTP status code of something else happens it'll check if you redirect from HTTP to HTTPS is it 301 or not it'll check every XML sitemap is valid so off the bat you already have a few starting points for your order for your analysis I'm a huge fan of deep crawl disclaimer I am a member of the customer advisory board so I get a free account yay but I was a paid subscriber for multiple years before they asked me to be a member of the customer advisory board I really really liked it too it's a cloud-based crawler you have to be a bit careful with the credit systems that start with a small limited quote before you do a full core otherwise you run out of credit for you know it but it built in reporting it's second to none and stuff you can find with deep call is amazing also because you can plug it into search console plug it into analytics plug it into majestic order link tools plug it into server log files even even and do comparisons between the different data sources so it's incredibly powerful platform that combines everything and of course screaming frog is my go-to desktop-based quarrel I use this primarily for limited calls calling sitemaps calling lists of files etc etc because I don't know about you but anything over by 10,000 you ELLs on my laptop start smoking and getting a life on its own and just you know trying to melt food my my desk search console like I said you can't do proper analysis without search console both old and new I like GT metrics as a performance and an analysis tool how fast enough site load primarily because the people behind GT metrics have a commercial incentive to give you scores they sell load speed optimization service so if you get a good score or in Keating metrics you'll really see it hot it's very easy to get a bad score in GT metrics I mean you got a lighthouse and then PageSpeed insights wiki based on lighthouse and you got webpagetest which says great waterfall charts are always really useful to include as well in order to report but GT metrics for me is the go-to bit also because things like that you know how many actual requests does it take to build a page that's a very piece of useful piece of information to have how many kilobytes is the actual page anybody here better we know what the average size is of a web page on the internet nowadays take a guess ouu naive it's two and a half megabytes two and a half megabytes is the average page weight of web pages on the web nowadays I'm old enough to you've played a computer game called doom remember doom that was two megabytes the entirety of doom is smaller than the average web page on the internet nowadays what the I use plugins as well by the way I'm six-two Firefox in January you all see tricks - Firefox - because I don't know about you but I don't think chrome need 7.9 of my 80 gigabytes of RAM really doesn't when she switched to Firefox it's like the whole new world will open up to you and I holy it's actually fast it's amazing also because the extension ecosystem of Firefox has now moved on to such an extent you don't need Chrome anymore to get all the data you need Firefox I love the SEO info plugin which is basically almost the only plugin you need to SEO on five there's also a chrome version you can try it on a chrome I am it's lots and lots and lots of info in there directly in that one plug-in I also have the rap eliezer plugin which is similar to the built with plugin and tells you the kind of technologies that are used on that particular webpage I'll give you a strong indication of a kind of platform that's built on all the plugins that they might use etcetera etcetera and the link redirect race is similar as the a gimmick video back passages you read about hops HTTP status codes and all of that which is really useful for analysis as well beyond that I don't really use an awful lot of tools that's pretty much it and some times I have other tools depending on the context was necessary but generally this is my entire tool stack for most of my technical SEO wallets you don't you don't need to hide yourself behind tools the best tool you have is write down your score and the action will audit then I have a checklist the checklist I always assume clients eventually will share that without a party I send it to the client complete with color codings and everything you know Green is go and yellow is where we might need to look at that or here you definitely need to look at that red is stop the presses you need to look at this right now like you know what what's the teak see this all rules that a good work or something like that but because I know this is going to be shared if I send it to a client I always assume a competitor at some stage is going to see this or people who think they compete with me so I de faire Li inscrutable they're just little not just for me to look at certain aspects of a site little hints to go in certain directions for DES diving into a rabbit hole I'm not giving away the entirety of my SEO audit process with my checklist I'm just you know showing that yes I am checking your website for all these different types of elements or highlight what I've checked and how problematic I feel that it is the checklist is not a report it's just the initial thing and it keeps me on track it makes sure I do actually check the website for all the things I should be checking the website for so it keeps me on track keeps me engaged keep make sure that you know I don't just do a half-assed effort basically I key to a really really good SEO audit is always to look at the patterns take a step back and look at the patterns that make up the website itself it's all about the context in which an issue exists and the recommendations that you make I have seen audits that a lot of people have done I'm not going to name them although sometimes I'm tempted to well there's like a hundred thousand pigs web site and one of the recommendations is there are seven title tags on your website that are a little bit too long you need to shorten them and like get the I can't believe you paid money for that that's not a proper recommendation you need to put everything in the right context if it's a 20 page website and seven title tags are up yeah okay if it's a hundred thousand page website now come on don't put that in your audit report let's just use this put it in the right context context always matters and you need to understand the purpose of a website before you can make those recommendations I think there's a real risk in the SEO industry that we only look at websites through the lens of a tool or multiple tools multiple reports we look at a website through search console through a deep crawl through screaming for work to a majestic link analysis Co before you even start an audit just go and use the website dive into it become very familiar with it how it works how it takes over well what you like about or what you dislike about it just become a user of the website first before you become a critic of the website and that for me always helps placed with recommendations in the correct context because it's very easy to make recommendations based on what comes out of a report like you might be making recommendations for pages that are not really that important in the context of the wider website that I really deeply hidden for example yes that might be absolutely terrible pages and they probably do need to improve them but there's so much other stuff on the key pages that actually people look at all the time and the search engine should be focusing on so if you're not a user of the website you can't make that evaluation you can't make that judgment so become a user before you become an auditor of the website websites will one of different templates you'll have the home page you'll have category pages you'll have product or service pages etc etc and you need to make sure you keep that in mind when you make those recommendations because problems on websites tend to appear across all types all templates of pages and sometimes you know you have some odd pages of floating around here and there but generally speaking if there's something wrong on one product page it tends to be wrong on most if not all product pages so identify which templates a website has and make sure you analyze every single one of those even if your call report from deepwater scheming fork doesn't necessarily hide I highlight the problem make sure you double check every single on the website on the code level as well to make sure that okay this page is functioning as intended or maybe there's nothing they can improve about that to an actual writing of the report and if you have your checklist completed and ten points by the way and a freebie if anybody knows what movie that's from good man the original the real ghost in the writing of the report is of course when you create your deliverable that's the product that you have been paid or get paid money from your employer to deliver so don't skimp on that I know for me writing the SEO orders report it's probably nearly half the work of the orders report itself maybe not maybe it depends on the size of the website but at least a third of my time goes into writing the report because that determines if anything is actually going to happen with that output if someone is actually going to take that up and make stuff improve on the website again always assume it will be shared beyond the confines of the organization you send it to and many how many NDA is yourself I know this because I get orders reports from other agencies all the time and sometimes I I wondered to myself if the people who wrote that report realized that I'm going to be reading them and I think might be good to keep in mind when you write an ordered report but and I'm not going to be done reading it really because probably I will at some stage I might get angry with you make it actionable by the way action Jackson is a massively on the rated 1980s early 1990s action film Carl Weathers is one of my favorite action actually movie stars of all time and I think he could have deserved an Oscar for his acting talent he's fantastic beside the point make it actionable again it comes down to context it's very easy to make a very generic official recommendation and just shoot it over to the client and forget about it but you have to put it in the right context you have to make sure they can actually do something with that now I have had a few cases where I made a recommendation knowing that it is very easy for me to make and very hard for the client to implement for example I ordered a website a year and a half ago which was entirely server-side JavaScript entirely from start to finish so my recommendation to them was actually just a simple email client doo-doo-doo entire service so they were a client-side rendering and I told them go to server-side rendering because the client shouldn't be seeing any JavaScript and after you've done that then I can order the rest of the website because up until that is fixed there's no point in me spending any effort on all of the University website fortunately for them they know they decided to test a fart with pre-rendered on IO and then we moved on to the second stage of the audit but sometimes it can be very hard for for clients to action a certain recommendation no matter how much you want them to up until today I was on those people who told clients to put pagination meta tags imaginated pages anybody been following the Twitter drama on that today yeah John Willie came out I said oh no we haven't paid attention to that for years how much development time is wasted on that right again that can be very easy recommendation to make not necessarily easy to implement if you are familiar with the systems that the website runs on it becomes easier to change that a little bit what I do find is helpful I'll touch upon this a bit later on as well is if you if you don't necessarily tell a client how to do something but you give them some signposts then if there's a wordpress website and you know there's a program that helps with that maybe point him towards that or point them towards an online tool that can help them find out certain issues but don't necessarily from hims because people who end up implementing it the developers don't tend to like being told what to do if you do that they call you a dick in the slack Channel - the CTO only include what actually needs improved in my color coding system grey green and yellow never make it to the final report orange and red are the only ones that do stuff that actually needs fixed and was need fixed urgently stuff that might be nice to fix the yellow I don't even bother to put it in the report no point in that and again with experience you tend to find out what the biggest bang for your buck is going to be and I'll talk about that a little bit when I talk about prioritization but I see massively loaded ordered reports sometimes where every tiny little possible improvement point is listed and I'm like nobody's gonna read that nobody's gonna do anything with that make it concise make it short include only the stuff that actually needs to be improved and will have a meaningful impact again there's seven title tags that are slightly over 70 characters don't put that in your audit report no no nobody's gonna do anything without it that's not useful the trivia stuff needs to stay the out if it's not gonna have a big bang a meaningful impact don't put it in the report maybe put it in the excel sheet like I said in the actual checklist that you can send to a client so that maybe they will ask you or what about this you might do that but really move the needle put stuff in there that's actually going to move the needle and prioritize properly it is important to make the client understand what the biggest bang is going to be one they start making those recommendations and in that regard I tend to do what I call reverse prioritization we talked about the three main components of a search engine crawling indexing and ranking I prioritize the other way around ranking comes first because that's that's the low-hanging food that's the bang for your buck if it's called an index but it's not ranking why is that let's fix that first if it's being called but it's not being indexed why why not that's the second step and then the last step if it's not being called at all why not again sometimes you have to mix things up a little bit if the entire website isn't being called that's a fairly important issue but that won't happen very often you know in the part of a sales process of an SEO that I always emphasize to my clients there are no silver bullets anymore you're not going to find I'm not going to find one major change that's gonna massively reverse your fortunes and that cliff upward is going to magically play that's not going to happen it's going to be small incremental improvements small little things if they can very quickly see a result from what they implement from your audit it's stuff that starts to rank and in traffic straight away then they have that internal momentum they will get an internal buy-in to implement more of your recommendations so that's the high-priority stuff stuff that that's the quick payoff then the stuff that takes a bit more time and lastly the stuff that might need complete redesign of the websites information architecture for example that can be hard to sell but if they've seen the improvements from the first few in recommendations and they have that internal Buy in an internal momentum to get done try to make it concise and light in jargon I am a huge fan of who was it that that said that if you can't unexplained it simply you don't understand it properly a thing hmm I think it was least it's attributed to him a lot of the times if you can't explain it simply you don't understand it I really do believe that the same is true in SEO if you hide all this stuff behind heavy jargon and acronyms and all that craft and you're not really sure about it yourself you know and sometimes that's okay I I don't know everything there is to know about websites either and I'm almost with my clients I just know when something goes wrong and I tell them and you might want to have to look at it but I do try to explain it simply try to explain it to somebody who comes from a non-technical background so they please get a general gist of it but also don't dumb it down too much that you lose some of the nuance in it because nuance is quite important the context always matters but you have to be concise don't write 5,000 words about one single issue nobody's going to read that you know keep it as concise as you possibly can give examples always provide example screen source code snippets whatever it is because it also makes the document come alive a little bit it's it easier for people to read and if you provide direct examples of pages where a problem occurs then developers can directly look at those pages see the problem for themselves and then hopefully find a good way to fix it always explain the why don't just say Google likes this say why you think Google likes that and yes of course you know we don't always know why ourselves because Google tells us make great content but we as SEO specialists and at least the basics of how search engines work I can at least explain what this is part of its crawling system if they can't follow links and they can't crawl pages or this is part of the indexing ecosystem and if you do clean up the code with the h1 tags and at least Google have very clear signals about what the headline on the pages etc so provide a bit of context explain the why behind it and if you do that you were very quickly realized that delivering and all that in the form of PowerPoint slides just isn't going to work because you can't do any of what I just said in PowerPoint there's not enough room on PowerPoint sighs I hate all the reports that are delivered in PowerPoint it is so lazy and you just know that's just a template that's a copy/paste job with the new website and the new screenshots phone and which standard content in it no I write my reports in words that try not to make them too long they were about 20 to 30 pages and that's about it and I do write them nearly entirely from scratch every single time because I made a copy miss paste error from the same issue once and I forgot to change the website name that shit's gonna haunt you too don't do that you only make that mistake once no write it down properly you know I tend to make it an easily readable digestible document as well so one issue per page and sometimes it's just one or two paragraphs sometimes it's a bit longer so screen shots in their next issue with this is the problem this is why it's a problem and this is just a recommended solution next problem this is a problem this is why it's a problem this is the recommended solution one after the other and 20 30 pages max that should be it unless it's a real awful website but if that's the case you can do with just a one-page you're saying start over right so I don't like using PowerPoint i old-fashioned word document that I save as PDF so they can around with it and then I send them to the client and always understand your audience there will be multiple types of people in an organization who will be reading that document they tend to comment one or three forms you've got the c-suite the executives the CEOs CMO CTOs we've got the marketers and you got the tack of the deaf people the CEOs will never read the hosts yet think it's not going to so you have to have an executive summary and do call it an executive summary or something like that highlight that's that's what the eye is gonna go towards and that's it they're gonna read keep that as jargon free as possible don't blame anybody don't say your developers really up because the same developers are gonna have to implement your recommendations so don't report some blame just described very briefly what the problems are and the kind of solution that would be required and show them the money it can be very hard to estimate how much traffic is going to improve but you sorta get a bit of a gauge sometimes and I get these questions probably way too often and I always again put them in the right contact saying well we don't know it's a moving target but I expect if you do that you might see one or two percent off lift up lift if you do that you might see 15-20 percent of that in X amount of time in my experience at cetera Suffolk you know the more you do the better you get it up and it becomes important to do that at least provide a bit of context and meaning and again it will help build internal momentum build that internal mandate that the marketers in the tech team need to actually make happen the marketing then the marketers they tend to be the ones who hire you most of the time so you have to make them look good even if they up make sure that they look good in the order your entire job is to make marketing look good to make them look smart to make them look like they make the right decision in hiring you to do that audit for you to make that report and to make stuff happen sometimes I work with marketers and I pity them to a certain extent we work in-house who know exactly what the is wrong with their website they know there will be no surprises in my audit report none but they need that because otherwise nobody else is going to listen to them so you make sure you align what you say with the market all right what do you think the main problems are I'll make sure to highlight them in my report and sometimes you can you can surprise them most of the time you know they tend to already have a bit of an idea yeah this is what the problem is and then you need to pay someone else to several thousand pounds to actually get done in the one organisation right I used to be that person I spent 15 years of my career in-house and it's also why I will never go back in-house market or sometimes have an unhealthy obsession with their competitors I sometimes get asked why do we need to do this we're doing that because I compared the lunette Android ranking us yeah but that's not why they were ranking you you shouldn't always try to imitate what everybody else is doing as a real risk in them and try to educate them a little bit as well you know if you have a screaming Fogo or the typical output for them show them the tool and maybe get them to use it as well make it part of their processes the developers then they can be the hardest to win over but once you've got them on site it actually moves it actually gets done it helps if you have some basic development awareness yourself if you don't at least try to understand some of the lingo I don't think you need to be able to code to be good SEO I do think you need to know HTML HTML is not a coding language it's a markup language and it's more or less human readable if you want to be really really good at SEO you need to be able to look at the source code of a web page the HTML source code and sort of have an idea of what each component does I don't think that's really optional of them Italiano's but knowing JavaScript or Python or PHP now you don't need to do that I think I'm a fairly competent technical SEO and I haven't coded in anger for the better part of 17 years now so when you talk to developers that help to really impress some of the really basic concepts that they sometimes not don't necessarily realize can be a problem like for example that URLs are how search engines crawl index and rank content you guys don't crawl on index and rank websites nor do you rank web pages in fact they rank URLs individual web addresses and and once you cram that into a web developers had for example they'll never make problems with single page apps anymore because they know they don't know every single piece of content needs its own URL search engines you know secretly all web developers want to work for Google deep down they'll all admit they love to work for Google so if he lifts a bit of that veil you tell them a little bit this is how Google actually works this is how they interact with your website they tend to get excited about the prospect you can point them to certain documentation on the Google developers web site that tends to help as well because they take them as gospel and then see it actually starts to happen and always make sure that you emphasize that by building good SEO into their website it'll make them look good as well they'll because they're the ones who building websites that are faster that are better that rank better and get more traffic and earn more money and pay you a salary in the end and I want to be outcome focused I never want to tell a developer how did you do their job I sometimes point them to certain tools and certain platforms but I'm not religiously telling them to do it one certain way but I tell them what the ideal outcome is going to be this is the ideal outcome of this particular recommendation how you get there was up to you but kept as close to that as you possibly can and they figure it out themselves you do need to tell them how to do their own jobs most of the time if you do that you tend to get them onside that guy I have a really good working relationship with him now and the company he worked for in fact they commissioned me to do a second order once they updated the entire code base of their website and he actually is based in Portugal and he's got an open invitation for me to come and drink beers with him when I'm there because after that initial hurdle he realized that I wasn't his enemy that I could make his job easier if he just did what the I told him to but really all I have if that talk wasn't depressive enough I hope those logos impress you thank you very much [Applause]

Channel: Optimisey

Views: 2,763

Rating: 4.8709679 out of 5

Keywords: technical seo, seo, search engine optimisation, search engine optimization, digital marketing, internet marketing, online marketing, site audit, barry adams, optimisey, seo expert, how to do a site audit, screaming frog, google search console, tech seo, seo audit, how to, how to do an seo audit, seo tutorial, seo help, seo video, website audit, technical seo audit, how to audit my website, polemic digital, polemic seo

Id: OOTaHjM8DBg

Length: 36min 42sec (2202 seconds)

Published: Mon May 20 2019