Home Messages Index
[Date Prev][Date Next][Thread Prev][Thread Next]
Author IndexDate IndexThread Index

Re: Advice

__/ [ Stacey ] on Sunday 26 February 2006 18:35 \__

> "News" <news@xxxxxxxxxxxxxxxx> wrote in message
> news:dtsqj4$st4$1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>>I have a client that would change the content, meta tags and occasionally
>> the design of his home page whilst I was in the middle of optimising his
>> site (I only ever had access to his index page) He is now very upset
>> because
>> he doesn't rank for his main keyword. I have explained the detrimental
>> effect his changes have but he refuses to accept this. Does anyone have
>> any
>> advice on how to deal with issue? Any articles or "expert" opinions would
>> be
>> very useful.
>> Thanks in advance

What promises were made to the client and did the client promise to abstain
from getting involved? I was in a situation before when one edit suprseded
another. It can be enormously frustrating and often difficult to recover
from (by obtaining both versions after the collision occurs), especially if
edits are done directly on the server's filesystem or via a CMS


Hi Stacey,

> Why would anyone SEO a site with the only access is to the index page?

Many people still think of their front page as the one and only facet. That's
why people are so obsessed with the perceived value (e.g. PageRank )of their
front page and are reluctant to leak some of it onto other pages/domains.
The matter of fact is that subpages (additional, sub-categorised content)
often help attract more traffic than a high-ranked front page or a
highly-optimised front page.

> Mistake #1. Mistake #2 Don't ever take on a client with the only access to
> the index page and allowing changes to be done on top of changes(while
> optimizing). Advice learn by your mistakes.:-)

CVS or SVN the Web site? It's probably an overkill for small sites, but we do
so on our internet. It involved either file locking or version control
(merging) with the notion of checking out and committing pages as to avoid
or treat simultaneous edits.

[Date Prev][Date Next][Thread Prev][Thread Next]
Author IndexDate IndexThread Index