This post was originally published on White.net
You have just spent the last week knee-deep in data and technical issues whilst crawling through a website. You have identified a large number of technical issues, and a major blocker that will drastically help improve search engine rankings. You have put together the document, talked the client through it, who thanked you for putting it together and said that it looks great, and can’t wait to see the results of the changes.
A couple of days later, you get the call. Oh don’t you hate it when you get THE call! We can do the implementations no problem, but! Oh no, not the dreaded but. It’s going to take some time, the IT team have said they need to spec out the requirements, work out how to do half of it, and it’s probably going to take six months to implement the basic recommendations. Head, smack!, desk!
How many times have you heard that story? But whose fault is it? Is it the IT team, who didn’t inform you of what is required for each change, or is it yours because you didn’t ask about the process to get website changes made, no matter how simple they may be?
Below I have provided five key questions to ask before you start your technical audit.