Content available only on log-in/ sign up - how to optimise?
-
Hi Mozzers.
I'm working on a dev brief for a site with no search visibility at all. You have to log in (well, sign up) to the site (via Facebook) to get any content. Usability issues of this aside, I am wondering what are the possible solutions there are to getting content indexed.
I feel that there are two options:
1. Pinterest-style: this gives the user some visibility of the content on the site before presenting you with a log in overlay. I assume this also allows search engines to cache the content and follow the links.
2. Duplicate HTTP and HTTPS sites. I'm not sure if this is possible in terms of falling foul of the "showing one thing to search engines and another thing to users" guidelines. In my mind, you would block robots from the HTTPS site (and show it to the users where log in etc is required) but URLs would canonicalise to the HTTP version of the page, which you wouldn't present to the users, but would show to the search engines. The actual content on the pages would be the same.
I wonder if anyone knows any example of large(ish) websites which does this well, or any options I haven't considered here.
Many thanks.
-
Thanks Justin and Bruce,
I think I will try and push for the "limited view until signed in" solution. The HTTP/ HTTPS one just feels a bit too much like a dirty hack that will end up hurting in some way, at some point!
Thanks for your responses.
-
Could you model your approach after other subscription sites? Take, for example, the online version of the Wall Street Journal: http://online.wsj.com/home-page. They present enough content in preview mode to be relevant to both users and Google. You know from the blurb what the story is basically about.
Once someone logs in, they get the rest of the content. But I don't think they get a separate URL.
I wouldn't do the duplicate HTTP/HTTPS approach. In the future, you may want the whole site to be HTTPS, so you'd have to face this issue again.
-
Hi Pascale
If the content is visible to the "not signed in end user" then it is visible to google. If it is not, it is not visible to Google.
I might have this wrong, but it would appear that you have a pinterest style site and that you want further content only be visible when the user is logged in? This then would be a site settings and not crawl issue. This is a trgger on the website server to require the guest to log in after XYZ. The whole site is opened to crawl but you set these parameters for the guest user in your sites back office
I think it is a case of either or, not both
Bruce
edit typo
-
Hi Bruce,
Thanks for your response. I agree - that the whole point of login is to to stop unwanted visitors seeing private content. For the most part.
This is not a log in in that same way - it's more of a "sign up" so like Pinterest or DueDil - you have to sign up in order to view the content.
I hope that makes more sense and I will modify the title (if I can) to make it clearer.
Thanks
-
If the content is for Logged in Users, why would you want it crawled?
Google crawls sites open to the public, therefore if the site is behind a login, then google will not crawl it. If google crawls it, then the content will show up in search results, hence making the login process redundant.
If you want to offer subscription content, then this is a marketing issue, not a crawl issue. You will need to have open content available that the viewing will perhaps then make a call whether to subscribe to your site or not.
Remember login is a cloaking devise, designed to stop unwanted visitors viewing the content, hence why google will view this in the same way.
Hope that helps
Bruce
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
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.
Related Questions
-
Http://newsite.intercallsystems.com/vista-series/sales@intercallsystems.com
I keep getting crawl errors for urls that have email addresses on the end. I have no idea what these are. Here is an example: the-audio-visual-system/sales@intercallsystems.com Where would these be coming from, how are they created? How can i fix them? When I try to do a 301 redirect it doesn't work. Thanks for your help,
Technical SEO | | renalynd27
Rena0 -
Duplicate Page Content
Hello, After crawling our site Moz is detecting high priority duplicate page content for our product and article listing pages, For example http://store.bmiresearch.com/bangladesh/power and http://store.bmiresearch.com/newzealand/power are being listed as duplicate pages although they have seperate URLs, page titles and H1 tags. They have the same product listed but I would have thought the differentiation in other areas would be sufficient for these to not be deemed as duplicate pages. Is it likely this issue will be impacting on our search rankings? If so are there any recommendations as to how this issue can be overcome. Thanks
Technical SEO | | carlsutherland0 -
Duplicate content. Wordpress and Website
Hi All, Will Google punish me for having duplicate blog posts on my website's blog and wordpress? Thanks
Technical SEO | | Mike.NW0 -
Correct linking to the /index of a site and subfolders: what's the best practice? link to: domain.com/ or domain.com/index.html ?
Dear all, starting with my .htaccess file: RewriteEngine On
Technical SEO | | inlinear
RewriteCond %{HTTP_HOST} ^www.inlinear.com$ [NC]
RewriteRule ^(.*)$ http://inlinear.com/$1 [R=301,L] RewriteCond %{THE_REQUEST} ^./index.html
RewriteRule ^(.)index.html$ http://inlinear.com/ [R=301,L] 1. I redirect all URL-requests with www. to the non www-version...
2. all requests with "index.html" will be redirected to "domain.com/" My questions are: A) When linking from a page to my frontpage (home) the best practice is?: "http://domain.com/" the best and NOT: "http://domain.com/index.php" B) When linking to the index of a subfolder "http://domain.com/products/index.php" I should link also to: "http://domain.com/products/" and not put also the index.php..., right? C) When I define the canonical ULR, should I also define it just: "http://domain.com/products/" or in this case I should link to the definite file: "http://domain.com/products**/index.php**" Is A) B) the best practice? and C) ? Thanks for all replies! 🙂
Holger0 -
Duplicate Content - Products
When running a report it says we have lots of duplicate content. We are a e-commerce site that has about 45,000 sku's on the site. Products can be in multiple departments on the site. So the same products can show up on different pages of the site. Because of this the reports show multiple products with duplicate content. Is this an issue with google and site ranking? Is there a way to get around this issue?
Technical SEO | | shoedog1 -
Build links to / or without ./ on root
Hi there for linkbuilding what is better, building with / or without / www.domain.com www.domain.com/ I have been told it depends what your webserver is doing, also i was told they are the same? what does Google see? I know i need to stay consistent, just wondering which practice is better? Any help as always much appreciated.
Technical SEO | | pauledwards0 -
Duplicate Homepage: www.mysite.com/ and www.mysite.com/default.aspx
Hi, I have a question regarding our client's site, http://www.outsolve-hr.com/ on ASP.net. Google has indexed both www.outsolve-hr.com/ and www.outsolve-hr.com/default.aspx creating a duplicate content issue. We have added
Technical SEO | | flarson
to the default.aspx page. Now, because www.outsolve-hr.com/ and www.outsolve-hr.com/default.aspx are the same page on the actual backend the code is on the http://www.outsolve-hr.com/ when I view the code from the page loaded in a brower. Is this a problem? Will Google penalize the site for having the rel=canonical on the actual homepage...the canonical url. We cannot do a 301 redirect from www.outsolve-hr.com/default.aspx to www.outsolve-hr.com/ because this causes an infinite loop because on the backend they are the same page. So my question is two-fold: Will Google penalize the site for having the rel=canonical on the actual homepage...the canonical url. Is the rel="canonical" the best solution to fix the duplicate homepage issue on ASP. And lastly, if Google has not indexed duplicate pages, such as https://www.outsolve-hr.com/DEFAULT.aspx, is it a problem that they exist? Thanks in advance for your knowledge and assistance. Amy0