| 10:43 am on Nov 13, 2005 (gmt 0)|
Do what is right *for the users* and if the common description is not the dominant portion of the text on the page I do not think that it will do you any harm in the SEs.
| 10:54 am on Nov 13, 2005 (gmt 0)|
Bung the text in an <iframe> and the (potential) problem is solved.
| 12:05 pm on Nov 13, 2005 (gmt 0)|
Good suggestion from Kaled.
If the duplicate text is under 10% of the total text on a page I would guess that it is not a problem and just be ignored, like most template stuff, but better safe than sorry.
| 3:37 pm on Nov 13, 2005 (gmt 0)|
Why not add a descriptive byline to your logo graphic? My philosophy is to instantly tell the visitors what the site is about with a few short simple words. You only have a few seconds.
| 3:46 pm on Nov 13, 2005 (gmt 0)|
I had the same problem. What I found worked best was put the site description very close to the "contact us" link, and on my "contact us" page. Solved most of the problem.
But do try to keep it short, as in 3 or 4 short sentences at the most, people just don't read anything like that if it's too long.
I like the I-frame idea, I might make that change myself. I haven't had a duplicate comtent issue from this. But I have changed the wording a couple times and using an I-frame would have made that easier.
| 5:23 pm on Nov 13, 2005 (gmt 0)|
It's worth noting that if the text contains keywords, using an <iframe> could be detrimental to rankings. On the other hand, if it does not contain keywords, using an <iframe> might have a small beneficial effect. In any case, I would add a noindex robots meta tag to the included page.
| 5:49 pm on Nov 13, 2005 (gmt 0)|
I have a small piece of text with a similar purpose that appears on many pages of a site and what I did was write the same thing in about 9-10 different ways, put each one in a .txt file and randomly include them.
This not only deals with the duplicate text issue, but also means the pages change just a little all the time. That works for users because they tend not to become blind to the text.
| 5:50 pm on Nov 13, 2005 (gmt 0)|
Being unfamiliar with iframe, is this the same as an included file in PHP? The site is 100% PHP/MySQL at the moment. The description will end up having a lot of keywords in it, that cannot be avoided due to the topic.
| 6:02 pm on Nov 13, 2005 (gmt 0)|
We had the same problem with a site. We made the text we wanted to include on every page into a graphic.
| 7:07 pm on Nov 13, 2005 (gmt 0)|
|Being unfamiliar with iframe, is this the same as an included file in PHP? The site is 100% PHP/MySQL at the moment. The description will end up having a lot of keywords in it, that cannot be avoided due to the topic. |
<iframe> includes are VERY DIFFERENT.
<iframe> is client-side not server-side.
Moving the text into a server-side include (however implemented) will have zero effect other than, perhaps, increasing the load on your server slightly.
Think of an <iframe> like an <img> however, instead of a graphic you include text. However, there is at least one critical difference... whilst <img> can be sized automatically <iframe> cannot - typically you might set width=100%
| 7:42 pm on Nov 13, 2005 (gmt 0)|
I've dealt with this problem by setting the text into a simple gif image. A very, very easy solution.
It's true that you're probably okay including such things in your code up to 10%(who knows for sure?) of the total content, but these little things have a way of snowballing... a little navbar, a little copyright statement, etc, etc, and suddenly you're 'way over 10% (or whatever limit).
| 8:45 pm on Nov 13, 2005 (gmt 0)|
Thanks for the great tip on using a graphic for something important and "viewable" into a graphic!
Sweet, never heard of that one, but I have a couple of spots for them immediately!