Google indexing issue duplicate url , how to prevent this? | Community
Skip to main content
Manu_Mathew_
Community Advisor
Manu_Mathew_Community Advisor
Community Advisor
September 3, 2021
Solved

Google indexing issue duplicate url , how to prevent this?

  • September 3, 2021
  • 5 replies
  • 3045 views

Currently I have noticed multiple urls like this in Google Search Console (which means Google is indexing them)

https://www.test.com/mypage.2.html, 

https://www.test.com/mypage.3.html, 

where it should have only https://www.test.com/mypage.html indexed.

Because of this, ‘a duplicate url exists’ and ‘page indexed without content’ issue is being raised by Google and which has resulted a significant drop in rankings.

 

Any Suggestion?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Lokesh_Shivalingaiah

Hi @manu_mathew_ 

 

Do you see these pages with the selectors in your dispatcher cache ? If not, one of the way to avoid is to configure your dispatcher to not allow anyone to access the pages with the selector.

 

Also, here is a tip to delete them from the google index if needed : https://developers.google.com/search/docs/advanced/crawling/remove-information

 

5 replies

Shashi_Mulugu
Community Advisor
Shashi_MuluguCommunity Advisor
Community Advisor
September 3, 2021

@manu_mathew_  Are you using selectors to access pages? if yes will the content differ based on the selector passed? will it also differ the metadata of the page? Based on the above questions, we can guide you better

    Manu_Mathew_
    Community Advisor
    Manu_Mathew_Community AdvisorAuthor
    Community Advisor
    September 3, 2021

    Hi 

     

    No for this particular page we don't use any selectors, but the page seem to be accepting selectors.  The contents however is same for all the request when any number of selectors are added.

      Shashi_Mulugu
      Community Advisor
      Shashi_MuluguCommunity Advisor
      Community Advisor
      September 4, 2021

      @manu_mathew_ in that case, go with Canonical url.

       

      https://developers.google.com/search/docs/advanced/crawling/consolidate-duplicate-urls

       

        mayank_saklech1
        mayank_saklech1
        Level 2
        September 3, 2021

        Please use canonical tags in page header. More on canonical tags: https://moz.com/learn/seo/canonicalization#:~:text=A%20canonical%20tag%20(aka%20%22rel,content%20appearing%20on%20multiple%20URLs.

          Lokesh_Shivalingaiah
          Lokesh_ShivalingaiahAccepted solution
          Level 10
          September 3, 2021

          Hi @manu_mathew_ 

           

          Do you see these pages with the selectors in your dispatcher cache ? If not, one of the way to avoid is to configure your dispatcher to not allow anyone to access the pages with the selector.

           

          Also, here is a tip to delete them from the google index if needed : https://developers.google.com/search/docs/advanced/crawling/remove-information

           

            V
            VKumar2
            Level 2
            September 4, 2021

            Hi @manu_mathew_  - Assuming the pages are not supposed to access by using selectors, you could write re-write rule at apache redirect module to the original URL without selector.

            Canonical URL is another option that you can try implementing and give the self page URL, this way it would force the selector pages to adhere canonical functionality, However if pages are already indexed on google - you might raise a google re-crawler request after implementing the required changes.

            Thank you.

              arunpatidar
              Community Advisor
              arunpatidarCommunity Advisor
              Community Advisor
              September 5, 2021

              Hi,

              Canoncal url address the same problem

              https://developers.google.com/search/docs/advanced/crawling/consolidate-duplicate-urls

              Arun Patidar
                Terms & ConditionsAccessibility statement

                Loading footer...