EC
09-01-2006, 06:23 PM
I can't seem to find this anywhere. If anybody knows, or knows where I might find the answer (I tried the google webmaster guidelines, google search, blah blah -- maybe I just have my vocabulary confused or something).
Ok the issue is, my client wants no two URLS to contain the same content. This has been quite a workaround since I'm using a content management system and pages are generated on-the-fly, sorted by category, archived, etc. The nature of online publishing, blogging, etc.
I could never find anything that would tell me that this was a 'no-no' so I had to work around it.
Now, we're just about to launch, and there is another concern.
I've created internal anchor links to aid the user, for example -- an article on the home page is an excerpt, then a link to the full article if you want to read on. If you've read the excerpt, my feeling is that -- why link them to a page and make them scroll down, why not do a <a href="http://sitename.com/page/#extended"> situation where you are taken directly to <a name="extended"> on the page. With me?
Well what happens is, he's concerned that search engines will read this:
http://www.sitename.com/page/
and http://www.sitename/page/#extended
As him trying to duplicate content on more than one page because the URLS are different.
Any ideas?
Ok the issue is, my client wants no two URLS to contain the same content. This has been quite a workaround since I'm using a content management system and pages are generated on-the-fly, sorted by category, archived, etc. The nature of online publishing, blogging, etc.
I could never find anything that would tell me that this was a 'no-no' so I had to work around it.
Now, we're just about to launch, and there is another concern.
I've created internal anchor links to aid the user, for example -- an article on the home page is an excerpt, then a link to the full article if you want to read on. If you've read the excerpt, my feeling is that -- why link them to a page and make them scroll down, why not do a <a href="http://sitename.com/page/#extended"> situation where you are taken directly to <a name="extended"> on the page. With me?
Well what happens is, he's concerned that search engines will read this:
http://www.sitename.com/page/
and http://www.sitename/page/#extended
As him trying to duplicate content on more than one page because the URLS are different.
Any ideas?