vBSEO Optimization Tips

my host adviced me not to put anything because i use cpanel and each time i update cpanel. All changes gone. But i am not sure can i use it with a cpanel installed server?

Do you mean to put anything in Apache configuration file? There are no issues related to CPanel with vBSEO.

i mean for httpd.conf, if i put the htaccess datas in it and then when cpanel updated i may lost these settings...

You should be able to put rewrite rules in custom config file and include it in the main Apache config.

Quick Question

Move rewrite rules from .htaccess to httpd.conf

For users with dedicated servers, the vBSEO rewrite rules applied in the .htaccess files can be moved directly into the httpd.conf file for more efficient performance.

What's the big difference? can anyone technically explain that to me? i'm just curious

More here:
Optimizing Apache Server Performance

When (not) to use .htaccess files

In general, you should never use .htaccess files unless you don't have access to the main server configuration file. There is, for example, a prevailing misconception that user authentication should always be done in .htaccess files. This is simply not the case. You can put user authentication configurations in the main server configuration, and this is, in fact, the preferred way to do things.
.htaccess files should be used in a case where the content providers need to make configuration changes to the server on a per-directory basis, but do not have root access on the server system. In the event that the server administrator is not willing to make frequent configuration changes, it might be desirable to permit individual users to make these changes in .htaccess files for themselves. This is particularly true, for example, in cases where ISPs are hosting multiple user sites on a single machine, and want their users to be able to alter their configuration.
However, in general, use of .htaccess files should be avoided when possible. Any configuration that you would consider putting in a .htaccess file, can just as effectively be made in a <Directory> section in your main server configuration file.
There are two main reasons to avoid the use of .htaccess files.
The first of these is performance. When AllowOverride is set to allow the use of .htaccess files, Apache will look in every directory for .htaccess files. Thus, permitting .htaccess files causes a performance hit, whether or not you actually even use them! Also, the .htaccess file is loaded every time a document is requested.

More here:
Apache Tutorial: .htaccess files - Apache HTTP Server

oh interesting i always learn a lot with you guys. Thanks

Now my next question (i'm a beginner to those things) besides my unix classes i wasn't scared but i've never tested anything on my server afraid of breaking something lol

How do i do it? i'm on a dedicated server

See here:
http://www.faqs.org/docs/securing/chap29sec245.html

Once you edit the file, you need to re-start Apache.

Hi,

I'm new.

May I know what is CRU format?

How to include [forum_id] in the CRU format? include through vBulletin control panel? or vbSEO control panel?

Thank you.

Regards,
Eric

I have an ignorant question: what is the topic for and how to apply it? (what's CRU...). Thanks.

CRU stands for "Content Relevant URL", which typically means that keywords related to the page topic are included in the URL.

Static or rewritten URLs are considered CRUs if they contain keywords.

You can configure your URL Rewriting for vBSEO within the control panel (vbseocp.php).

Originally Posted by Joe Ward

More here:
Optimizing Apache Server Performance


When AllowOverride is set to allow the use of .htaccess files, Apache will look in every directory for .htaccess files. Thus, permitting .htaccess files causes a performance hit, whether or not you actually even use them! Also, the .htaccess file is loaded every time a document is requested

If this is true, it seems then that moving rewrite rules from .htaccess to httpd.conf might not actually result in much of a performance gain if AllowOverides is not also disabled, no?

Originally Posted by 711

If this is true, it seems then that moving rewrite rules from .htaccess to httpd.conf might not actually result in much of a performance gain if AllowOverides is not also disabled, no?

No response to this observation/question?

With AllowOverride enabled, there still IS a difference when moving rewrite rules to httpd.conf, since Apache will not parse rewrite rules for every request.

I have moved the rewrite rules from .htaccess to httpd.conf, and I can see a very noticable improvement on performance.

Thanks for the suggestion!