Skip to content
    Moz logo Menu open Menu close
    • Products
      • Moz Pro
      • Moz Pro Home
      • Moz Local
      • Moz Local Home
      • STAT
      • Moz API
      • Moz API Home
      • Compare SEO Products
      • Moz Data
    • Free SEO Tools
      • Domain Analysis
      • Keyword Explorer
      • Link Explorer
      • Competitive Research
      • MozBar
      • More Free SEO Tools
    • Learn SEO
      • Beginner's Guide to SEO
      • SEO Learning Center
      • Moz Academy
      • MozCon
      • Webinars, Whitepapers, & Guides
    • Blog
    • Why Moz
      • Digital Marketers
      • Agency Solutions
      • Enterprise Solutions
      • Small Business Solutions
      • The Moz Story
      • New Releases
    • Log in
    • Log out
    • Products
      • Moz Pro

        Your all-in-one suite of SEO essentials.

      • Moz Local

        Raise your local SEO visibility with complete local SEO management.

      • STAT

        SERP tracking and analytics for enterprise SEO experts.

      • Moz API

        Power your SEO with our index of over 44 trillion links.

      • Compare SEO Products

        See which Moz SEO solution best meets your business needs.

      • Moz Data

        Power your SEO strategy & AI models with custom data solutions.

      Let your business shine with Listings AI
      Moz Local

      Let your business shine with Listings AI

      Learn more
    • Free SEO Tools
      • Domain Analysis

        Get top competitive SEO metrics like DA, top pages and more.

      • Keyword Explorer

        Find traffic-driving keywords with our 1.25 billion+ keyword index.

      • Link Explorer

        Explore over 40 trillion links for powerful backlink data.

      • Competitive Research

        Uncover valuable insights on your organic search competitors.

      • MozBar

        See top SEO metrics for free as you browse the web.

      • More Free SEO Tools

        Explore all the free SEO tools Moz has to offer.

      NEW Keyword Suggestions by Topic
      Moz Pro

      NEW Keyword Suggestions by Topic

      Learn more
    • Learn SEO
      • Beginner's Guide to SEO

        The #1 most popular introduction to SEO, trusted by millions.

      • SEO Learning Center

        Broaden your knowledge with SEO resources for all skill levels.

      • On-Demand Webinars

        Learn modern SEO best practices from industry experts.

      • How-To Guides

        Step-by-step guides to search success from the authority on SEO.

      • Moz Academy

        Upskill and get certified with on-demand courses & certifications.

      • MozCon

        Save on Early Bird tickets and join us in London or New York City

      Unlock flexible pricing & new endpoints
      Moz API

      Unlock flexible pricing & new endpoints

      Find your plan
    • Blog
    • Why Moz
      • Digital Marketers

        Simplify SEO tasks to save time and grow your traffic.

      • Small Business Solutions

        Uncover insights to make smarter marketing decisions in less time.

      • Agency Solutions

        Earn & keep valuable clients with unparalleled data & insights.

      • Enterprise Solutions

        Gain a competitive edge in the ever-changing world of search.

      • The Moz Story

        Moz was the first & remains the most trusted SEO company.

      • New Releases

        Get the scoop on the latest and greatest from Moz.

      Surface actionable competitive intel
      New Feature

      Surface actionable competitive intel

      Learn More
    • Log in
      • Moz Pro
      • Moz Local
      • Moz Local Dashboard
      • Moz API
      • Moz API Dashboard
      • Moz Academy
    • Avatar
      • Moz Home
      • Notifications
      • Account & Billing
      • Manage Users
      • Community Profile
      • My Q&A
      • My Videos
      • Log Out

    The Moz Q&A Forum

    • Forum
    • Questions
    • Users
    • Ask the Community

    Welcome to the Q&A Forum

    Browse the forum for helpful insights and fresh discussions about all things SEO.

    1. Home
    2. SEO Tactics
    3. Intermediate & Advanced SEO
    4. Are pages with a canonical tag indexed?

    Moz Q&A is closed.

    After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.

    Are pages with a canonical tag indexed?

    Intermediate & Advanced SEO
    3
    17
    17827
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as question
    Log in to reply
    This topic has been deleted. Only users with question management privileges can see it.
    • fablau
      fablau last edited by

      Hello here,

      here are my questions for you related to the canonical tag:

      1. If I put online a new webpage with a canonical tag pointing to a different page, will this new page be indexed by Google and will I be able to find it in the index?

      2. If instead I apply the canonical tag to a page already in the index, will this page be removed from the index?

      Thank you in advance for any insights!

      Fabrizio

      1 Reply Last reply Reply Quote 0
      • fablau
        fablau @mememax last edited by

        Yes, I will look into doing that on GWT.

        Was a nice and useful chat indeed! Thank you again.

        1 Reply Last reply Reply Quote 0
        • mememax
          mememax @fablau last edited by

          Sorry Fabrizio I got mad with my old answer 🙂

          that canonical doesn't make sense with a noindex, with noindex follow.you're completely fine.

          Summing up I think that you have many parameters so you should try to write them down and define the role of each one.

          Then add them in GWT and choose there which are the ones which doesn't add any value and which you want to "block" (instead of putting a noindex).

          The valuable ones (the one which adds value and changes content) should contain the self canonical and paginated next/prev. If you can get rid of unesful parameters it could be better so to have cleaner and shorter urls.

          Just be sure that you're mainly using the most important parameters so you're consistent with your strategy.

          Hope this will clear your doubts, it was a nice chat! 🙂

          fablau 1 Reply Last reply Reply Quote 0
          • fablau
            fablau @Dr-Pete last edited by

            Yes, actually I could get rid of the lpg parameter (it wasn't really needed!), so now the tag definitions are (for the 3rd page of the Guitar index):

            <LINK rel="<a class="attribute-value">next</a>" href="[http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=4](view-source:http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=4)"> <LINK rel="<a class="attribute-value">prev</a>" href="[http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=2](view-source:http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=2)"> <LINK rel="<a class="attribute-value">canonical</a>" href="[http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=3](view-source:http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=3)">
            

            Now, the only doubt I still have is to add or not add the noindex tag to the page when it is requested to be displayed in a different way (such as the "table view" or a different item display order). In my opinion, if I stick with the canonical tag I don't need a noindex directive. What do you think?

            mememax 1 Reply Last reply Reply Quote 0
            • Dr-Pete
              Dr-Pete Staff @mememax last edited by

              Yeah, to be fair, I'm not clear on what all of the additional parameters (like "lpg=") do, so this can get tricky fast. Basically, look at it this way:

              If the URL is:
              example.com/page=3?param=x

              Then the tags should point to:

              Rel=prev:
              example.com/page=2?param=x

              Rel=next:
              example.com/page=4?param=x

              Rel=canonical:
              example.com/page=3 (no parameters)

              Some parameters may not be indexed and/or functional, though, so individual cases can vary. You may choose to ignore some parameters in Google Webmaster Tools, for example. It gets tricky as the parameter list grows.

              fablau 1 Reply Last reply Reply Quote 0
              • fablau
                fablau @mememax last edited by

                Mememax, after thinking I have some doubts though about what you have suggested.

                Why I want to put a noindex tag to the page displaying the list in "table view" if I already have a canonical tag pointing to the "regular view" page? Wouldn't the canonical tag be enough for the purpose of telling that the "real" canonical page is the "regular view" version? I am asking this because if I want to apply a noindex tag to that kind of different view, I may want to do the same to the list displayed with a different order, and for any other different way of displaying the list, etc... hence just using the canonical tag would be appropriate, pointing always to the "regular list" view, no matter what kind of "filtering" or "different view' option is selected. What do you think?

                In other words, I don't think I need to include a noindex tag for any different kind of view the user requests as long as I provide a canonical tag pointing to the regular view list.

                Am I correct?

                1 Reply Last reply Reply Quote 0
                • fablau
                  fablau @mememax last edited by

                  Yes, thank you Mememax, I agree with you 100%. That makes perfect sense and I will work on that tomorrow morning. I am eager to know Dr. Peter thoughts and confirmation.

                  On my side, I think I got it cleared-up now. Thank you very much again!

                  1 Reply Last reply Reply Quote 0
                  • fablau
                    fablau @Dr-Pete last edited by

                    Thank you ! That makes sense now.

                    1 Reply Last reply Reply Quote 0
                    • mememax
                      mememax @fablau last edited by

                      Hey Fabrizio, I think that what Google states in their guidelines is that you have two choices:

                      • if you have a view all page, you should noindex and follow all your other pages so google will deliver only that page
                      • if you don't have a view all page or if you prefer to show paginated series (i.e. to make pages lighter and quicker to deliver to users) you may consider to use rel next/prev.

                      In this second case it may happen that you also add filters or session ids in the urls of those pages, in that case you should consider adding a self referentail canonical tag to avoid duplicates. But this is only if you cover this case, if you're looking to canonicalize correctly your paginated series you may not use the self canonical tag, because if not properly implemented this may get you a bit of extra work.

                      In this page for example

                      I found this:

                      http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=3&lpg=0">

                      Which  I don't think is what you want to do.

                      Also if you set the page to view as a table: your url changes to http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=3&viewlistflag=1

                      and while the canonical should remain the same (well done but I think you should get rid of the lpg parameter in the canonical), the rel next prev should change accordingly IMO.

                      So instead of being:

                      prev: http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=2&lpg=20
                      next: http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=4&lpg=60

                      you should offer the next and prev page of the filtered url:

                      next: http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=4&lpg=60&viewlistflag=1
                      prev: http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=2&lpg=20&viewlistflag=1

                      Or in this case (since the content is almost the same you may consider the list page as the canonical of the table one putting there a noindex.

                      Summing up, IMO: in this page http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=3

                      you'll have:

                      prev: http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=4&lpg=60
                      next: http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=2&lpg=20
                      (optional) a self canonical to http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=3

                      In this page (and in other filtered pages if you have apply the same idea):
                      http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=3&viewlistflag=1

                      You'll have:

                      noindex,follow and canonical to the list page:
                      http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=3

                      maybe dr peter can correct me if I'm wrong but I think this should be more consistent like this. Sorry for the huge answer

                      fablau Dr-Pete 3 Replies Last reply Reply Quote 0
                      • Dr-Pete
                        Dr-Pete Staff @fablau last edited by

                        Wow, yes - sorry about that. I've updated it. Google original write-up actually covers this case, too (it's toward the end):

                        http://googlewebmastercentral.blogspot.com/2011/09/pagination-with-relnext-and-relprev.html

                        fablau 1 Reply Last reply Reply Quote 0
                        • fablau
                          fablau @Dr-Pete last edited by

                          Please, have a look at the page below, I have modified the canonical tag as suggested:

                          http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=3&lpg=40

                          Is that correct?

                          Thank you again very much.

                          mememax 1 Reply Last reply Reply Quote 0
                          • fablau
                            fablau @Dr-Pete last edited by

                            Thank you Peter, I guess you meant to have the "canonical" tag as last tag in your example above, and also the previous rel=next and rel=prev definitions should be inverted:

                            Am I correct? That makes sense. If so, I will update my site to reflect this.

                            Thank you for the link!

                            Dr-Pete 1 Reply Last reply Reply Quote 0
                            • Dr-Pete
                              Dr-Pete Staff @fablau last edited by

                              This gets tricky fast. Google currently wants rel=prev/next to contain the parameters currently in use (like sorts) for the page you're on and then wants you rel-canonical to the non-parameterized version. So, if the URL is:

                              http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=3&lpg=40

                              ...then the tags should be...

                              Yeah, it's a bit strange. They have suggested that it's ok to rel-canonical to a "View All" page, but with the kind of product volume you have, that's generally a bad idea (for users and search). The have specifically recommended against setting rel-canonical to Page 1 of search results, especially if you use rel=prev/next.

                              Rel=prev/next will still show pages in the index, but I've found it to work pretty well. The other option is the more classic approach to simple META NOINDEX, FOLLOW pages 2+. That can still be effective, but it's getting less common.

                              Adam Audette has generally strong posts about this topic - here's a good, recent one:

                              http://searchengineland.com/the-latest-greatest-on-seo-pagination-114284

                              fablau 2 Replies Last reply Reply Quote 0
                              • fablau
                                fablau @Dr-Pete last edited by

                                Thank you for your post, and I think you have just opened a doubt I had, and that's exactly what also concerned me.

                                Have a look at this typical category page of ours:

                                http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html

                                For that category pagination, I have implemented the rel=prev/next as suggested by Google, but being afraid to be penalized for duplicate content, I also put a canonical tag pointing at the first page of that index. Should I have put the canonical tag pointing to the page series itself?

                                Something like:

                                http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=2

                                
                                for the second page instead of the general:
                                
                                

                                http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html

                                as I am currently doing?

                                Thanks!

                                Dr-Pete 1 Reply Last reply Reply Quote 0
                                • Dr-Pete
                                  Dr-Pete Staff last edited by

                                  I have to disagree on this one. If Google honors a canonical tag, the non-canonical page will generally disappear from the index, at least inasmuch as we can measure it (with "site:", getting it to rank, etc.). It's a strong signal in many cases.

                                  This is part of the reason Google introduced rel=prev/next for paginated content. With canonical, pages in the series aren't usually able to rank. Rel=prev/next allows them to rank without clogging up the index (theoretically). For search pagination, it's generally a better solution.

                                  If your paginated content is still showing in large quantities in the index, Google may not be honoring the canonical tag properly, and they could be causing duplicate content issues. It depends on the implementation, but they recommend these days that you don't canonical to the first page of search results. Google may choose to ignore the tag in some cases.

                                  fablau 1 Reply Last reply Reply Quote 4
                                  • fablau
                                    fablau @mememax last edited by

                                    Thank you very much, that makes perfect sense. In my case, I am talking exactly about paginated content, and that's probably why all pages are in the index despite they are canonicalized to point to the main page. So, I guess that even if you have thousands of paginated pages indexed (mine is a pretty big e-commerce website), that's not going to be an issue. Am I right?

                                    1 Reply Last reply Reply Quote 0
                                    • mememax
                                      mememax last edited by

                                      Normally the only thing which will prevent a page from ranking is noindex tag. If you don't want to have it indexed just noindex it, if that page has been laready indexed, put the noindex tag and delete from index using GWT option.

                                      Concerning the canonical tag thing, it will consolidate the seo value in one page but it won't prevent those page to appear in rankings, however you may have two cases:

                                      1. the two or more pages are identical. In that case google may accept the canonicalization and show always the original page.
                                      2. the two or more pages are slightly different, it's the case of paginated pages which are canonicalized using rel next/prev. In that sense the whole value will be consolidated in page 1 but then the page which will be shown in the rankings will be the one which responds to that query, for example if someone is looking for blue glass, google will return the page which shows blue glass listing if that's different from the first one.

                                      Hope this may help you!

                                      fablau 1 Reply Last reply Reply Quote 4
                                      • 1 / 1
                                      • First post
                                        Last post

                                      Got a burning SEO question?

                                      Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.


                                      Start my free trial


                                      Browse Questions

                                      Explore more categories

                                      • Moz Tools

                                        Chat with the community about the Moz tools.

                                      • SEO Tactics

                                        Discuss the SEO process with fellow marketers

                                      • Community

                                        Discuss industry events, jobs, and news!

                                      • Digital Marketing

                                        Chat about tactics outside of SEO

                                      • Research & Trends

                                        Dive into research and trends in the search industry.

                                      • Support

                                        Connect on product support and feature requests.

                                      • See all categories

                                      Related Questions

                                      • chelseaskirtinguk

                                        My product category pages are not being indexed on google can someone help?

                                        My website has been indexed on google and all of its pages can be found on google except for the product category pages - which are where we want our traffic heading to, so this is a big problem for us. Our website is www.skirtinguk.com And an example of a page that isn't being indexed is https://www.skirtinguk.com/product-category/mdf-skirting-board/

                                        Intermediate & Advanced SEO | | chelseaskirtinguk
                                        0
                                      • Ben-R

                                        E-Commerce Site Collection Pages Not Being Indexed

                                        Hello Everyone, So this is not really my strong suit but I’m going to do my best to explain the full scope of the issue and really hope someone has any insight. We have an e-commerce client (can't really share the domain) that uses Shopify; they have a large number of products categorized by Collections. The issue is when we do a site:search of our Collection Pages (site:Domain.com/Collections/) they don’t seem to be indexed. Also, not sure if it’s relevant but we also recently did an over-hall of our design. Because we haven’t been able to identify the issue here’s everything we know/have done so far: Moz Crawl Check and the Collection Pages came up. Checked Organic Landing Page Analytics (source/medium: Google) and the pages are getting traffic. Submitted the pages to Google Search Console. The URLs are listed on the sitemap.xml but when we tried to submit the Collections sitemap.xml to Google Search Console 99 were submitted but nothing came back as being indexed (like our other pages and products). We tested the URL in GSC’s robots.txt tester and it came up as being “allowed” but just in case below is the language used in our robots:
                                        User-agent: *
                                        Disallow: /admin
                                        Disallow: /cart
                                        Disallow: /orders
                                        Disallow: /checkout
                                        Disallow: /9545580/checkouts
                                        Disallow: /carts
                                        Disallow: /account
                                        Disallow: /collections/+
                                        Disallow: /collections/%2B
                                        Disallow: /collections/%2b
                                        Disallow: /blogs/+
                                        Disallow: /blogs/%2B
                                        Disallow: /blogs/%2b
                                        Disallow: /design_theme_id
                                        Disallow: /preview_theme_id
                                        Disallow: /preview_script_id
                                        Disallow: /apple-app-site-association
                                        Sitemap: https://domain.com/sitemap.xml A Google Cache:Search currently shows a collections/all page we have up that lists all of our products. Please let us know if there’s any other details we could provide that might help. Any insight or suggestions would be very much appreciated. Looking forward to hearing all of your thoughts! Thank you in advance. Best,

                                        Intermediate & Advanced SEO | | Ben-R
                                        0
                                      • muzzmoz

                                        How (or if) to apply re canonical tags to Shopify?

                                        Anyone familiar with Shopify will understand the problems of their directory structure. Every time you add a product to a 'collection' it essentially creates a duplicate. For example... https://www.domain.com/products/product-slim-regular-bikini may also appear as: https://www.domain.com/collections/all/products/product-slim-regular-bikini https://www.domain.com/collections/new-arrivals/products/product-slim-regular-bikini https://www.domain.com/collections/bikinis/products/product-slim-regular-bikini etc, etc It's not uncommon to have up to six duplicates of each product. So my question is twofold: Firstly, should I worry about this from an SEO point of view? I understand the desire to minimise potential duplicate content issues and also in focussing the 'juice' on just one page per product. But I also planned on trying to build the authority of the collection pages. If I request Google not to index the product pages which link off the collections, does this not devalue these collections pages? Secondly, I understand the correct way to fix these is using 'rel canonical' tags, but I'm not clear about HOW to actually do this. Shopify support has not been very helpful. They have provided two different instructions, so just added to the confusion (see below). Shopify instruction #1: Add the following to the theme.liquid file... <title><br />{{ page_title }}{% if current_tags %} – tagged "{{ current_tags | join: ', ' }}"{% endif %}{% if current_page != 1 %} – Page {{ current_page }}{% endif %}{% unless page_title contains shop.name %} – {{ shop.name }}{% endunless %}<br /></title>
                                        {% if page_description %} {% endif %} Shopify instruction #2: Add the following to each individual product page... So, can anyone help clarify: The best strategic approach to this inherent SEO issue with Shopify (besides moving to another platform!)? and If 'rel canonical' tags is the way to go, exactly where and how to apply them? Regards, Murray

                                        Intermediate & Advanced SEO | | muzzmoz
                                        1
                                      • Caro-O

                                        Home page suddenly dropped from index!!

                                        A client's home page, which has always done very well, has just dropped out of Google's index overnight!
                                        Webmaster tools does not show any problem. The page doesn't even show up if we Google the company name. The Robot.txt contains: Default Flywheel robots file User-agent: * Disallow: /calendar/action:posterboard/
                                        Disallow: /events/action~posterboard/ The only unusual thing I'm aware of is some A/B testing of the page done with 'Optimizely' - it redirects visitors to a test page, but it's not a 'real' redirect in that redirect checker tools still see the page as a 200. Also, other pages that are being tested this way are not having the same problem. Other recent activity over the last few weeks/months includes linking to the page from some of our blog posts using the page topic as anchor text. Any thoughts would be appreciated.
                                        Caro

                                        Intermediate & Advanced SEO | | Caro-O
                                        0
                                      • redgatst

                                        Google Ignoring Canonical Tag for Hundreds of Sites

                                        Bazaar Voice provides a pretty easy-to-use product review solution for websites (especially sites on Magento): https://www.magentocommerce.com/magento-connect/bazaarvoice-conversations-1.html If your product has over a certain number of reviews/questions, the plugin cuts off the number of reviews/questions that appear on the page. To see the reviews/questions that are cut off, you have to click the plugin's next or back function. The next/back buttons' URLs have a parameter of "bvstate....." I have noticed Google is indexing this "bvstate..." URL for hundreds of sites, even with the proper rel canonical tag in place. Here is an example with Microsoft: http://webcache.googleusercontent.com/search?q=cache:zcxT7MRHHREJ:www.microsoftstore.com/store/msusa/en_US/pdp/Surface-Book/productID.325716000%3Fbvstate%3Dpg:8/ct:r+&cd=2&hl=en&ct=clnk&gl=us My website is seeing hundreds of these "bvstate" urls being indexed even though we have a proper rel canonical tag in place. It seems that Google is ignoring the canonical tag. In Webmaster Console, the main source of my duplicate titles/metas in the HTML improvements section is the "bvstate" URLs. I don't necessarily want to block "bvstate" in the robots.txt as it will prohibit Google from seeing the reviews that were cutoff. Same response for prohibiting Google from crawling "bvstate" in Paramters section of Webmaster Console. Should I just keep my fingers crossed that Google honors the rel canonical tag? Home Depot is another site that has this same issue: http://webcache.googleusercontent.com/search?q=cache:k0MBLFcu2PoJ:www.homedepot.com/p/DUROCK-Next-Gen-1-2-in-x-3-ft-x-5-ft-Cement-Board-172965/202263276%23!bvstate%3Dct:r/pg:2/st:p/id:202263276+&cd=1&hl=en&ct=clnk&gl=us

                                        Intermediate & Advanced SEO | | redgatst
                                        1
                                      • boostaman

                                        How to check if the page is indexable for SEs?

                                        Hi, I'm building the extension for Chrome, which should show me the status of the indexability of the page I'm on. So, I need to know all the methods to check if the page has the potential to be crawled and indexed by a Search Engines. I've come up with a few methods: Check the URL in robots.txt file (if it's not disallowed) Check page metas (if there are not noindex meta) Check if page is the same for unregistered users (for those pages only available for registered users of the site) Are there any more methods to check if a particular page is indexable (or not closed for indexation) by Search Engines? Thanks in advance!

                                        Intermediate & Advanced SEO | | boostaman
                                        0
                                      • desmond.liang

                                        Our login pages are being indexed by Google - How do you remove them?

                                        Each of our login pages show up under different subdomains of our website. Currently these are accessible by Google which is a huge competitive advantage for our competitors looking for our client list. We've done a few things to try to rectify the problem: -  No index/archive to each login page Robot.txt to all subdomains to block search engines gone into webmaster tools and added the subdomain of one of our bigger clients then requested to remove it from Google (This would be great to do for every subdomain but we have a LOT of clients and it would require tons of backend work to make this happen.) Other than the last option, is there something we can do that will remove subdomains from being viewed from search engines? We know the robots.txt are working since the message on search results say: "A description for this result is not available because of this site's robots.txt – learn more." But we'd like the whole link to disappear.. Any suggestions?

                                        Intermediate & Advanced SEO | | desmond.liang
                                        1
                                      • PaulRogers

                                        Should I prevent Google from indexing blog tag and category pages?

                                        I am working on a website that has a regularly updated Wordpress blog and am unsure whether or not the category and tag pages should be indexable. The blog posts are often outranked by the tag and category pages and they are ultimately leaving me with a duplicate content issue. With this in mind, I assumed that the best thing to do would be to remove the tag and category pages from the index, but after speaking to someone else about the issue, I am no longer sure. I have tried researching online, but there isn't anything that provided any further information. Please can anyone with any experience of dealing with issues like this or with any knowledge of the topic help me to resolve this annoying issue. Any input will be greatly appreciated. Thanks Paul

                                        Intermediate & Advanced SEO | | PaulRogers
                                        0

                                      Get started with Moz Pro!

                                      Unlock the power of advanced SEO tools and data-driven insights.

                                      Start my free trial
                                      Products
                                      • Moz Pro
                                      • Moz Local
                                      • Moz API
                                      • Moz Data
                                      • STAT
                                      • Product Updates
                                      Moz Solutions
                                      • SMB Solutions
                                      • Agency Solutions
                                      • Enterprise Solutions
                                      Free SEO Tools
                                      • Domain Authority Checker
                                      • Link Explorer
                                      • Keyword Explorer
                                      • Competitive Research
                                      • Brand Authority Checker
                                      • Local Citation Checker
                                      • MozBar Extension
                                      • MozCast
                                      Resources
                                      • Blog
                                      • SEO Learning Center
                                      • Help Hub
                                      • Beginner's Guide to SEO
                                      • How-to Guides
                                      • Moz Academy
                                      • API Docs
                                      About Moz
                                      • About
                                      • Team
                                      • Careers
                                      • Contact
                                      Why Moz
                                      • Case Studies
                                      • Testimonials
                                      Get Involved
                                      • Become an Affiliate
                                      • MozCon
                                      • Webinars
                                      • Practical Marketer Series
                                      • MozPod
                                      Connect with us

                                      Contact the Help team

                                      Join our newsletter
                                      Moz logo
                                      © 2021 - 2025 SEOMoz, Inc., a Ziff Davis company. All rights reserved. Moz is a registered trademark of SEOMoz, Inc.
                                      • Accessibility
                                      • Terms of Use
                                      • Privacy

                                      Looks like your connection to Moz was lost, please wait while we try to reconnect.