1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

[PBN Question] Rebuilding old pages vs 301 redirect to index page?

Discussion in 'Black Hat SEO' started by 7yearitch, May 3, 2015.

  1. 7yearitch

    7yearitch Regular Member

    Joined:
    Dec 5, 2013
    Messages:
    489
    Likes Received:
    143
    Occupation:
    dog food tester
    Location:
    growing on trees
    Hi,

    I read somewhere that if you redirect old 404 pages from your PBN to the root domain, it's considered a "soft 404", and doesn't pass link juice. I know a lot of pbn builders who use wayback machine to rebuild the original content and they say it preserves the link juice.

    The most convincing argument I've found for someone to rebuild the old site is to hide the pbn. It's not always possible, but if you can do it you can pass manual reviews with flying colors.

    But the link juice I'm not too sure about and I just want to open this up for discussion. What are your thoughts, guys?
     
  2. cottonwolf

    cottonwolf Regular Member

    Joined:
    Jan 20, 2015
    Messages:
    469
    Likes Received:
    239
    discussing linkbuilding and pbns in general on open public forums where google employees frequest is a bad idea, imho.just look up matt cutts on wickedfire, if you don't believe me

    for wordpress, there's a plugin called linkjuice keeper that redirects 404 pages
    or in .htaccess (from an evernote note):

    "This seems to be what people think htaccess was meant for, but it is only part of the general use. We'll be getting into progressively more advanced stuff after this.
    Successful Client Requests200OK201Created202Accepted203Non-Authorative Information204No Content205Reset Content206Partial ContentClient Request Redirected300Multiple Choices301Moved Permanently302Moved Temporarily303See Other304Not Modified305Use ProxyClient Request Errors400Bad Request401Authorization Required402Payment Required (not used yet)403Forbidden404Not Found405Method Not Allowed406Not Acceptable (encoding)407Proxy Authentication Required 408Request Timed Out409Conflicting Request410Gone411Content Length Required412Precondition Failed413Request Entity Too Long414Request URI Too Long415Unsupported Media TypeServer Errors500Internal Server Error501Not Implemented502Bad Gateway 503Service Unavailable 504Gateway Timeout 505HTTP Version Not Supported In order to specify your own ErrorDocuments, you need to be slightly familiar with the server returned error codes. (List to the right). You do not need to specify error pages for all of these, in fact you shouldn't. An ErrorDocument for code 200 would cause an infinite loop, whenever a page was found...this would not be good.You will probably want to create an error document for codes 404 and 500, at the least 404 since this would give you a chance to handle requests for pages not found. 500 would help you out with internal server errors in any scripts you have running. You may also want to consider ErrorDocuments for 401 - Authorization Required (as in when somebody tries to enter a protected area of your site without the proper credentials), 403 - Forbidden (as in when a file with permissions not allowing it to be accessed by the user is requested) and 400 - Bad Request, which is one of those generic kind of errors that people get to by doing some weird stuff with your URL or scripts.
    In order to specify your own customized error documents, you simply need to add the following command, on one line, within your htaccess file:
    ErrorDocument code /directory/filename.ext

    or

    ErrorDocument 404 /errors/notfound.html

    This would cause any error code resulting in 404 to be forward to yoursite.com/errors/notfound.html



    Likewise with:

    ErrorDocument 500 /errors/internalerror.htmlYou can name the pages anything you want (I'd recommend something that would prevent you from forgetting what the page is being used for), and you can place the error pages anywhere you want within your site, so long as they are web-accessible (through a URL). The initial slash in the directory location represents the root directory of your site, that being where your default page for your first-level domain is located. I typically prefer to keep them in a separate directory for maintenance purposes and in order to better control spiders indexing them through a ROBOTS.TXT file, but it is entirely up to you.
    If you were to use an error document handler for each of the error codes I mentioned, the htaccess file would look like the following (note each command is on its own line):
    ErrorDocument 400 /errors/badrequest.html
    ErrorDocument 401 /errors/authreqd.html
    ErrorDocument 403 /errors/forbid.html
    ErrorDocument 404 /errors/notfound.html
    ErrorDocument 500 /errors/serverr.html

    You can specify a full URL rather than a virtual URL in the ErrorDocument string (http://yoursite.com/errors/notfound.html vs. /errors/notfound.html). But this is not the preferred method by the server's happiness standards.
    You can also specify HTML, believe it or not!
    ErrorDocument 401 "<body bgcolor=#ffffff><h1>You have
    to actually <b>BE</b> a <a href="#">member</A> to view
    this page, Colonel!

    The only time I use that HTML option is if I am feeling particularly saucy, since you can have so much more control over the error pages when used in conjunction with xSSI or CGI or both. Also note that the ErrorDocument starts with a " just before the HTML starts, but does not end with one...it shouldn't end with one and if you do use that option, keep it that way. And again, that should all be on one line, no naughty word wrapping!
    Next, we are moving on to password protection, that last frontier before I dunk you into the true capabilities of htaccess. If you are familiar with setting up your own password protected directories via htaccess, you may feel like skipping ahead.

    "

    therefore such a line in htaccess would redirect your 404 I think:

    ErrorDocument 404 /index.php

    OR

    ErrorDocument 404 /index.htm

    don't know if the above 2 are right, use one of them
     
    • Thanks Thanks x 1
    Last edited: May 3, 2015
  3. 7yearitch

    7yearitch Regular Member

    Joined:
    Dec 5, 2013
    Messages:
    489
    Likes Received:
    143
    Occupation:
    dog food tester
    Location:
    growing on trees
    Thanks for the detailed answer. But my question wasn't on how to redirect 404 errors to domain. I was wondering how effective it is for preserving link juice. What difference does it make if a page doesn't exist anymore and instead of a 404 error page we redirect to the domain? Isn't that better for the user than a 404 page?

    And if we were to build the original page it would be a better user experience i guess but it shouldn't effect link juice that much should it?

    I'm asking because I got some domains that were meant to host government programs in my country that has since been discontinued. So if I were to rebuild the site it may cause confusion where visitors might think the program still exists.

    So I just built a personal blog on it and I'm wondering what to do with the previous pages on the site. The pages are gettting good links themselves, and I would like to preserve the linkjuice.
     
  4. asap1

    asap1 BANNED BANNED

    Joined:
    Mar 25, 2013
    Messages:
    4,961
    Likes Received:
    3,185
    I noticed this soft 404 on a PBN site I added to a new webmaster account to check if it had any penalties.

    I have a plugin that redirects all 404's to the homepage .

    I would like to know what this soft 404 is.
     
  5. 7yearitch

    7yearitch Regular Member

    Joined:
    Dec 5, 2013
    Messages:
    489
    Likes Received:
    143
    Occupation:
    dog food tester
    Location:
    growing on trees
    According to what I've read so far, a soft 404 does not transfer link juice. anyone have any input on this?
     
  6. laur.laurix

    laur.laurix Power Member

    Joined:
    May 8, 2013
    Messages:
    730
    Likes Received:
    271
    Occupation:
    Reverse Engineering Maniac
    Location:
    Mars
    Soft what? There are 4 types of redirects 301, 302, 303, 304 that apply in this situation. If u want to keep all the link juice i recommend redirecting all 404 by 301. U can do that via plugings in wordpress, funtions.php, .htaccess or 404.php. I recommend the .htaccess or plugin way. Doing a 302, 303 or 304 , temporary redirect, will not pass any link juice.