Working with WordPress Backbone Websites

I am in the process of finishing up and readying for launch a new website built on the back bone of WordPress. I have to say the website has turned out nice, but I wanted to share with you a few of my thoughts on using website built like this for search engine placement.

I think that if you want to save money on webmaster services, like the control of being able to add and update your content at will; a well designed website using WordPress has no comparison. But for people, like me, who are used to full and complete source code control for SEO purposes a website built with WordPress leaves much to be desired.

Professionals in my industry know that template based websites (and that is really what a WordPress built site is-  a custom template) do not allow you full source code control. Although the designers that have worked with me on building this site have really done a great job, there are instances when I wanted to name my uploaded images my own way; I wanted to custom design my site architecture and be able to change the names and structure easily if I needed to down the road; I wanted to add special design or style elements to my pages without having to create hacks to make the page work the way I wanted it to within the template constraints. In other words, there is an element of control, subtle though it may be, that is simply missing with a WordPress site versus a custom created, built from the source code up, website.

I guess with all new improvements to allow customers to control their own content there are trade offs, but I’m not sure that I want to lose that control for every customer.

Share