We have been working with Mikare.net since 1999.
By today we have finished together 3 homepages.
info @ mikare.net
(+372) 600 6000
Testimonial see more
Jan Lepamaa, Isku IT spetcialist
Recent blog posts
Tip of the day
.jpg)
CRM shares the knowledge of passed events to owners and employees. CRM gives security to our customers. Everyone has an overview of passed events. CRM is our dynamic memory in quickly changing business environment!
CRM - the dynamic memory - Mikk Orglaan
What you think of swallowing your own old SEO mistakes?
Posted 03.06.2010
Today I faced a very surprising case. One of respected competitor of ours commented my answer to our mutual customer. My tone to customer was, of course a bit sharp, as I thought I was right years ago and customer decision to replace us was wrong. Our competitor's comment was more-less, like I have hurted them deliberately in front of customer eyes and without any respect towards him/his firm.
The issue was simple, in my eyes, of course. We did a web-site for customer years ago. It lasted ~5 years, which is a lot. After that respected competitor took over. But by surprise we found that:
- design didn't go very much better, our opinion was that it was even worse,
- CMS SEO was done quite badly, like we used to do before year 2002,
- lot of move-over default things were not thought over and done within rush,
- customer suffered a lot from bad Google requests and bad visibility in other search engines,
- customer constantly kept turning towards us asking why things were not as they used to be and we explained that yes, this is something your new partner has not considered while developing web-site.
So, what you think is right?
It is common knowledge that it is impossible to make a perfect IT solution at the time. Everithing changes too fast and requirement "perfect" costs too much and no customer is able to pay for it.
- How far back in time should we go to say: "Yes, we had bad CMS software back then, now we have improved these mistakes"?
- Or should we claim that: "This is so old CMS software that it should not meet to today's requirements"?
- But if there was a competitive CMS software better before your "bad" software replaced the old "good" CMS software?
- Who you think would need to pay for correcting these mistakes?
- Should "bad" CMS software developer correct mistakes on their own budget?
Share your thoughts with us in Facebook!
