Finding a specific link - Duplicating my own content

[ATP]

Hi Mozzers,

This may be a bit of a n00b question and i feel i should know the answer but alas, here i am asking.

I have a page  www.website.co.uk/page/ and im getting a duplicate page report of www.website.co.uk/Page/

i know this is because somewhere on my website a link will exists using the capitalised version. I have tried everything i can think of to find it but with no luck, any little tricks?

I could always rewrite the urls to lowercase, but I have downloadable software etc also on the website that i dont want to take the capitals out of. So the best solution seems to be finding the link and remove it.

Most link checkers I use treat the capitalised and non capitalised as the same thing so really arent  helping lol.

[ATP]

Managed it with screaming frog, I was just being a little thick and and not taking into account some other rewrites I had that were hiding these links :).

Sorry to waste your time! But thanks anyway

[PatrickDelehanty]

Hi ATP

Did your internal links or your sitemap have the uppercase variation as well, or was it just the rewrite? Just wondering - your answer could help some others that have the same issue!

Thanks!

[ATP]

Hi Patrick,

No, turns out I had been thorough and changed all the link in the sitemaps and on every page previously pointing to it. Having screaming froged it and follows the path through the rewrites etc it turns out What was causing the problem was the inbuilt layered navigation in Magento.

Each CMS created page produces a navigational path to the current page just above the content in this case

Home > Page1 > Sub Page  etc  each of these is a link to the hierarchy so the user can easily navigate.

The page in question (and only this page) seems to have a special rule set up for it (must have been back in development) where the navigation becomes Home > Page1 > Page1 > Subpage where the first 'Page1' is linked to via     website.co.uk/Page1    instead of    website.co.uk/page1/   like the rest of the website.

I have found a temporary way around it for now, having located the link until i can address the source code causing the issue