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
uri(n)						    Tcl Uniform Resource Identifier Management						    uri(n)

NAME
uri - URI utilities SYNOPSIS
package require Tcl 8.2 package require uri ?1.1.1? uri::split url uri::join ?key value?... uri::resolve base url uri::isrelative url uri::geturl url ?options...? uri::canonicalize uri uri::register schemeList script DESCRIPTION
This package contains two parts. First it provides regular expressions for a number of url/uri schemes. Second it provides a number of com- mands for manipulating urls/uris and fetching data specified by them. For the latter this package analyses the requested url/uri and then dispatches it to the appropriate package (http, ftp, ...) for actual fetching. COMMANDS
uri::split url uri::split takes a single url, decodes it and then returns a list of key/value pairs suitable for array set containing the con- stituents of the url. If the scheme is missing from the url it defaults to http. Currently only the schemes http, ftp, mailto, urn and file are supported. See section EXTENDING on how to expand that range. uri::join ?key value?... uri::join takes a list of key/value pairs (generated by uri::split, for example) and returns the canonical url they represent. Cur- rently only the schemes http, ftp, mailto, urn and file are supported. See section EXTENDING on how to expand that range. uri::resolve base url uri::resolve resolves the specified url relative to base. In other words: A non-relative url is returned unchanged, whereas for a relative url the missing parts are taken from base and prepended to it. The result of this operation is returned. For an empty url the result is base. uri::isrelative url uri::isrelative determines whether the specified url is absolute or relative. uri::geturl url ?options...? uri::geturl decodes the specified url and then dispatches the request to the package appropriate for the scheme found in the url. The command assumes that the package to handle the given scheme either has the same name as the scheme itself (including possible capitalization) followed by ::geturl, or, in case of this failing, has the same name as the scheme itself (including possible capi- talization). It further assumes that whatever package was loaded provides a geturl-command in the namespace of the same name as the package itself. This command is called with the given url and all given options. Currently geturl does not handle any options itself. Note: file-urls are an exception to the rule described above. They are handled internally. It is not possible to specify results of the command. They depend on the geturl-command for the scheme the request was dispatched to. uri::canonicalize uri uri::canonicalize returns the canonical form of a URI. The canonical form of a URI is one where relative path specifications, ie. . and .., have been resolved. uri::register schemeList script uri::register registers the first element of schemeList as a new scheme and the remaining elements as aliases for this scheme. It creates the namespace for the scheme and executes the script in the new namespace. The script has to declare variables containing the regular expressions relevant to the scheme. At least the variable schemepart has to be declared as that one is used to extend the variables keeping track of the registered schemes. SCHEMES
In addition to the commands mentioned above this package provides regular expression to recognize urls for a number of url schemes. For each supported scheme a namespace of the same name as the scheme itself is provided inside of the namespace uri containing the variable url whose contents are a regular expression to recognize urls of that scheme. Additional variables may contain regular expressions for parts of urls for that scheme. The variable uri::schemes contains a list of all supported schemes. Currently these are ftp, file, http, gopher, mailto, news, wais and prospero. EXTENDING
Extending the range of schemes supported by uri::split and uri::join is easy because both commands do not handle the request by themselves but dispatch it to another command in the uri namespace using the scheme of the url as criterion. uri::split and uri::join call Split[string totitle <scheme>] and Join[string totitle <scheme>] respectively. CREDITS
Original code by Andreas Kupries. Modularisation by Steve Ball. KEYWORDS
uri, url, fetching information, www, http, ftp, mailto, gopher, wais, prospero, file uri 1.1.1 uri(n)
All times are GMT -4. The time now is 05:25 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy