This is probably a strange request from this long-time lurker, – - but I’m wondering if someone could take a look-see at this gent’s problem with a page of his website seemingly duplicating itself, and showing up on his search-pages, yet not in his files. Here’s the link on the contractor-site (contractortalk) where he discusses the problem. As you’ll see anyway, – - I’m ‘Tom R’ over there. Thanks in advance for any input . . . http://www.contractortalk.com/f101/know-how-remove-duplicate-webpage-cant-locate-136930/
Thanks, Senff, – - yes, I was on that same page earlier today while searching for an answer, – - thing is, – - these aren’t ‘variations’ of pages he managed to generate on his own, – - these seem to be generating themselves from some outside force or someone else, no??
>these seem to be generating themselves from some outside force or someone else, no??
oooooo… must be haunted
seriously, @Senff is right. The query string _is_ considered part of the URI, and so is treated as a different resource. The solution is to add a `
` tag to the page, to point out that it is _not_, in fact, a separate page.
They are all the same actual pages. It doesn’t matter what comes after “.html”, it will all just lead to products.html. And so in that file you’ll need to add the canonical tag, so that Google knows that http://www.vanguardhomedesigns.com/products.html is the only page of these that should be indexed.
>traq, – - I appreciate the wisecrack, – - but maybe you didn’t catch that he can’t locate the offending page, – - therefore he can’t add anything to it’s ‘alleged’ head section.
sorry, I guess I didn’t explain myself clearly enough. (Thanks, @Senff.)
I addition to what Senff said, even though those URLs will all display the same “page”, the different query strings might affect what content is shown on the page. (They don’t actually appear to do so, in this case – the content is identical each time – but that’s what GET params are intended for. That’s why Google indexes each URL as though it were a different page.)
Thanks, traq, – - that does make it clearer, although I am still a little confused on why they would appear rather suddenly, and why, for instance, it’s only happening on that particular page. I guess you could say I’m now understanding the cure better than the cause . . .
The _specific_ cause is less certain. It could be any number of things – like Senff said, someone might be linking to it that way; it might even be something generated under some circumstance by your CMS.