Hi Everybody,
I - like many of us - frequently re-do pages, many times by cloning, etc. Then file away the old page under a different name and publish the new one in its place.
I believe this creates a duplicate page / content / text problem with the SEs, possibly penalizing the new page.
How to get the old pages safely out of the way? (say, I may want to keep them for my own references).
1. Deleted the old html.s from cPanel; de-published... (I know it will take time to take effect.)
2. I then remove the old, renamed (usually with an "old" tag) pages from my main BV directory to a folder I created within, called "Unused files" = ???
Is this procedure (the combination of points 1 and 2) enough to prevent "duplicate page" conflict with SEs?
Thanks,
Gabor
I - like many of us - frequently re-do pages, many times by cloning, etc. Then file away the old page under a different name and publish the new one in its place.
I believe this creates a duplicate page / content / text problem with the SEs, possibly penalizing the new page.
How to get the old pages safely out of the way? (say, I may want to keep them for my own references).
1. Deleted the old html.s from cPanel; de-published... (I know it will take time to take effect.)
2. I then remove the old, renamed (usually with an "old" tag) pages from my main BV directory to a folder I created within, called "Unused files" = ???
Is this procedure (the combination of points 1 and 2) enough to prevent "duplicate page" conflict with SEs?
Thanks,
Gabor
Comment