Sponsored Content
Top Forums Web Development Removing VBSEO for vbulletin – Reverting back to vbulletin URLs Post 302869061 by Neo on Tuesday 29th of October 2013 02:47:23 PM
Old 10-29-2013
Got some email and private messages how there should be some magic "one liners" that can rewrite all the 404s "file not found" errors when all the URLs of a forum change when they remove vBSEO.

Some, oddly enough, who have no experience with vBSEO (or rewriting all the URLS of a forum with a half a million pages indexed in Google) seemed to find my very clear explanation of how to change 404s to 301s cryptic, as if their is some "magic bullet" that works for all forums.

In my original post, I gave "the core examples" (from the now defunct vBSEO web site) about rewrite URLs for forum threads. There are three different examples based on three different vBSEO configuration.

However, a forum has a lot more pages than "threads". There are forum pages, and forum indexes, and archives and archive indexes, and there are single posts and their are RSS feeds and their are other pages where the URLs were rewritten by vBSEO.

If the vBSEO product is removed, all of these links, indexed in search engines, will break, and cause a 404 error. Each of these URLs need to be properly rewritten based on how the forum vBSEO setup was configured. There are many configuration switches for vBSEO, so there is not one "magic bullet" mod_rewrite rule which will work for every forum. Even 100 rewrite rules for our forums will not work for another forum because their configuration is different.

So, having said this; I outlined how to correctly do this; and obviously the method I outlined worked because our forums (this forum) has actually seen an increase in traffic and (so far) no negative SEO hit after removing vBSEO. Our traffic has increased since removing vBSEO.

Did the traffic increase because we removed vBSEO and there was some "magic bullet" one or two liner mod_rewrite rule that magically worked for posts, threads, forums, index pages, archives, print friendly pages, archive indexes, forum indexes, and more?

No, removing vBSEO without careful planning and observing 404 errors and then writing mod_rewrite rules to insure the old vBSEO URL were correctly 301'ed to working forum pages is not a trivial task.

This is why many people who have removed vBSEO and tried to use a quick "one or two liner" mod_rewrite rule have seen their search referral traffic drop. That is not what happened here. Our search referral traffic has actually increased since removing vBSEO because of careful mod_rewrite rule implementation via the technique outlined in earlier posts.

And don't forget that it is important to property use the canonical directive when doing a move like this. Search engines need to know that pages with duplicate content (old URLs and new URLs that point to the same content) have a pointer to the "authority" page, the canonical page.
 

We Also Found This Discussion For You

1. Post Here to Contact Site Administrators and Moderators

vbulletin addon for ads?

i'm wondering what vbulletin addon is used here to manage ads if the admin could let me know :) (1 Reply)
Discussion started by: disgust
1 Replies
Gedcom::Individual(3pm) 				User Contributed Perl Documentation				   Gedcom::Individual(3pm)

NAME
Gedcom::Individual - a module to manipulate Gedcom individuals Version 1.16 - 24th April 2009 SYNOPSIS
use Gedcom::Individual; my $name = $i->name; my @rel = $i->father; my @rel = $i->mother; my @rel = $i->parents; my @rel = $i->husband; my @rel = $i->wife; my @rel = $i->spouse; my @rel = $i->siblings; my @rel = $i->brothers; my @rel = $i->sisters; my @rel = $i->children; my @rel = $i->sons; my @rel = $i->daughters; my @rel = $i->descendents; my @rel = $i->ancestors; my $ok = $i->delete; my @fam = $i->famc; my @fam = $i->fams; DESCRIPTION
A selection of subroutines to handle individuals in a gedcom file. Derived from Gedcom::Record. HASH MEMBERS
None. METHODS
name my $name = $i->name; Return the name of the individual, with spaces normalised. cased_name my $cased_name = $i->cased_name; Return the name of the individual, with spaces normalised, and surname in upper case. surname my $surname = $i->surname; Return the surname of the individual. given_names my $given_names = $i->given_names; Return the given names of the individual, with spaces normalised. soundex my $soundex = $i->soundex; Return the soundex code of the individual. This function is only available if Text::Soundex.pm is available. sex my $sex = $i->sex; Return the sex of the individual, "M", "F" or "U". Individual functions my @rel = $i->father; my @rel = $i->mother; my @rel = $i->parents; my @rel = $i->husband; my @rel = $i->wife; my @rel = $i->spouse; my @rel = $i->siblings; my @rel = $i->older_siblings; my @rel = $i->younger_siblings; my @rel = $i->brothers; my @rel = $i->sisters; my @rel = $i->children; my @rel = $i->sons; my @rel = $i->daughters; my @rel = $i->descendents; my @rel = $i->ancestors; Return a list of individuals related to $i. Each function, even those with a singular name such as father(), returns a list of individuals holding that relation to $i. More complex relationships can easily be found using the map function. eg: my @grandparents = map { $_->parents } $i->parents; delete my $ok = $i->delete; Delete $i from the data structure. This function will also set $i to undef. This is to remind you that the individual cannot be used again. Returns true iff $i was successfully deleted. Family functions my @fam = $i->famc; my @fam = $i->fams; Return a list of families to which $i belongs. famc() returns those families in which $i is a child. fams() returns those families in which $i is a spouse. perl v5.14.2 2012-04-12 Gedcom::Individual(3pm)
All times are GMT -4. The time now is 08:54 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy