The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
Google sitemap for the vB Archives. Redirect human and robots. Details »» | |||||||||||||||||||||||||||
Google sitemap for the vB Archives. Redirect human and robots.
Developer Last Online: Nov 2023
Release V1.2 (9 Nov 2005)
* Higher sitemap priority rate is given to threads with new posts. So Google can index fresh threads first. * Not recommending the original optional STEP 3 hack. To avoid potential Google penalty, my advice is to remove the STEP 3 hack. Release V1.1a (12 Oct 2005) * Bug fix only Release V1.1 (9 Oct 2005) * Can handle very large forums with more than 50,000 URLs per forum URLs will be spanned through multiple files for each large forum. * Created a function to detect search engine crawlers. The vB built-in search engine detector can only identify about 3 or 4 search engines. My function will detect over 20 search engine crawlers. * Support forums hosted by web servers that do not support 'fix_pathinfo' ie. instead of the usual 'archive/index.php/f-10.html' link. These forums have a link as 'archive/index.php?f-10.html'. * Alert about wrong directory permissions to help newbies. * Automatically write index file to archive directory if the php script can not write into the base vB directory. * Bug fixes. Objectives ==============
Q and A ============== Q. Would the sitemap contain the links for hidden forums? A. No, the forum permission was consulted while generating the sitemap files. Q. How often are the sitemap files generated? A. You decide and set in the Scheduled Tasks. The script can not be called by external user by default to prevent boring people killing your server. Q. Is the sitemap file compressed. A. Yes, the multiple sitemap files are gunziped according to Google sitemap standard to save bandwidth. Sitemap index file is not compressed, it is submitted as a normal xml file. Q. Would the sitemaps include links for the normal threads? eg. showthread.php?t=1234... A. No, it is unlikely Google will index your entire site if you feed it with all the combination of showthread links. It is better to let Google going through the more static archives. You will have a better chance for sure to have more thread contents indexed by Google this way. Q. Why don't you go crazy about rewrite rules and do things like including thread title as the url. A. I won't deny having keywords in the url is a good SEO strategy, but Google also does not like "Over Search Engine Optimized" web sites. Google has recently penalized a huge number of such sites. Sending them from page rank of 5, 6 to 0. Q. Does sitemap really help? A. Definitely, Google has done over 60,000 pages since I submitted my sitemaps a few days ago. Yahoo bots were visiting more pages than Google before the sitemap. I expect the total Google visits for this month will be exceeding Yahoo in the next one or two days. What is involved? ================== I have divided this hack into two steps. The first step involves unloading a php file. This enables the sitemap to be generated and submitted to Google. The second step involves installing a Plugin using AdminCP. This sends all robots to the archive pages, preventing them viewing the actual threads. For example, Google/Other Crawlers follows an external link to visit: http://forums.mysite/showthread.php?t=1234&page=2 It will be told this page is permanently relocated to: http://forums.mysite/archive/index.php/t-1234-p-2 This way you don't lose page rank gain from external links. Install ========= To install, follow the readme file. To let me know you have installed this and let me send update information to you. Please click INSTALL . Strategy ========= It is unlikely Google/other Search Engine will index your entire site, especially due to the dynamic nature of the vbulletin forums. An archive sitemap will let Google concentrate on the real contents of your forums -- the threads. If Google needs to go through the endless member profile pages. It will get sick of it and just become tired.(sorry, perhaps robots can not become tired). What we can do is disallowing the crawling of unneccessary pages. My robots.txt contains: #ALL BOTS User-agent: * Disallow: /admincp/ Disallow: /ajax.php Disallow: /attachments/ Disallow: /clientscript/ Disallow: /cpstyles/ Disallow: /images/ Disallow: /includes/ Disallow: /install/ Disallow: /modcp/ Disallow: /subscriptions/ Disallow: /customavatars/ Disallow: /customprofilepics/ Disallow: /announcement.php Disallow: /attachment.php Disallow: /calendar.php Disallow: /cron.php Disallow: /editpost.php Disallow: /external.php Disallow: /faq.php Disallow: /frm_attach Disallow: /image.php #Disallow: /index.php Disallow: /inlinemod.php Disallow: /joinrequests.php Disallow: /login.php Disallow: /member.php? Disallow: /memberlist.php Disallow: /misc.php Disallow: /moderator.php Disallow: /newattachment.php Disallow: /newreply.php Disallow: /newthread.php Disallow: /online.php Disallow: /payment_gateway.php Disallow: /payments.php Disallow: /poll.php Disallow: /postings.php Disallow: /printthread.php Disallow: /private.php Disallow: /profile.php Disallow: /register.php Disallow: /report.php Disallow: /reputation.php Disallow: /search.php Disallow: /sendmessage.php Disallow: /showgroups.php Disallow: /showpost.php Disallow: /subscription.php Disallow: /usercp.php Disallow: /threadrate.php Disallow: /usercp.php Disallow: /usernote.php You perhaps have noticed I included index.php in there. Apparently Google regards http://forums.mysite/index.html as same as http://forums.mysite/ ...but http://forums.mysite/index.php as a different file. The default vB templates include index.php as the internal link. That will spread your page rank on your home page! So it is better off not letting Google see this file. If you have rewrite installed. Perhaps you could add to the .htaccess file: RewriteCond %{QUERY_STRING} ^$ RewriteRule ^index.php$ / [R=301,L] (if your forums are under http://site/forums/. Try: RewriteRule ^forums/index.php$ forums/ [R=301,L]) That will redirect /index.php to /, but only if no query_string is presented. ie. /index.php?do=mymod will not be redirected. Show Your Support
|
Comments |
#22
|
||||
|
||||
Quote:
|
#23
|
||||
|
||||
Hello,
I am running on a unix machine, my forums are in the root directory and not a sub directory. I uploaded the forums_sitemap.php to the archive folder and then I chmod it to 775. (meaning the archive directory) I then chmod my root directory (public_html) to 775. Then I went in, and added the scheduled task. Then I ran the scheduled task and got these errors: Fatal error: Call to a member function on a non-object in /home/habitats/public_html/archive/forums_sitemap.php on line 98 which is: $forums = $vbulletin->db->query(" Fatal error: Call to a member function on a non-object in /home/habitats/public_html/includes/functions.php on line 4240 which is: $vbulletin->db->unlock_tables(); Did I miss a step? I believe I covered everything.(I have complete access to my db including telenet authorization as well as query running ability. All of my usernames and passwords are set correctly.) |
#24
|
|||
|
|||
See the third post within this thread.
Quote:
|
#25
|
|||
|
|||
If I call the script directly: I get these errors:
Warning: array_keys(): The first argument should be an array in /includes/class_core.php on line 1375 Warning: Invalid argument supplied for foreach() in /includes/class_core.php on line 1375 Warning: array_keys(): The first argument should be an array in /includes/class_core.php on line 1390 Warning: Invalid argument supplied for foreach() in /includes/class_core.php on line 1390 |
#26
|
||||
|
||||
i don't understand this part of the install ? i'm very new to the new setup.. 2 nights now..lol
Code:
You need to change the directory permission so that the script can write to the base and archive directory. If your server runs apache and apache is run under apache user and apacher group. I normally assign the permission this way: #chown apache.MYUSER_GROUP archive #chmod 775 archive MYUSER_GROUP is the user group my login belongs to. #ls -l will show that. 775 will let apache (the script) and me (after I log in) add/change files. Set the same permission to the base vB directory. |
#27
|
|||
|
|||
Which version of vB do you use? The line numbers do not match. Otherwise, have you modified class_core.php file? perhaps due to the installation of another hack?
Quote:
|
#28
|
|||
|
|||
Quote:
I did not realise many amdins are newbies when comes to system admin. Basically you need to change the permission of the directories so that the php script can write files (sitemaps) to them. I understand some of your providers probably do not even provide shell access to the server, only some sort of user control panel for admin purpose. I am afraid I can not explain how to use these control panels as I have not seen one. Users of such ISP control panel may be able to provide more information. People who do not know what to do should provide information such as what sort of control panel do you use, what is in there, what have you tried. I will try to explain in general: When I refer to the base directory, I refer to the forum base directory. Some of you might have set up the forums this way: http://www.mysite.com/forums/ That means http://www.mysite.com/index.html will be in the root directory of the domain. The base directory for the vB will be ./forums under the web root. If your forums are set up as http://forums.mysite.com/ Then the base vB directory will be the root directory for the domain (forums.mysite.com) This hack needs to write to 1) The base vB directory (where you find showthread.php file) 2) The archive directoy (where you find archive.css file) So you need to make these two directories writable for the php script, OR world writable. A little info for the Unix chomd command. 1: executable 2: writable 4: readable 1+4 = 5 means readable and executable. Directories should be at least 1, 5 for a directory means visitor can read (list) directory contents, unless a index file is found. php files only need to be readable: 4 If we need to write to the directory, then the permission needs to be: 1+4+2 = 7 There are three permission for each file/directory. 1) User, 2) Group, 3) World/anyone User means the Unix logged in user, or the user the script runs as (typically apache or nobody is used by web servers). Group means the user group the user belongs to. Typically the apache server runs the script as 'apache' or 'nobody' group. World means the permission for everyone. They can be any user who logs into the web server. Naturally it includes the user that the php scripts runs as. If you do a #chmod 777 a_directory The first 7 means the user can read, execute, write to a_directory. The second 7 means the user group can read, execute, write to a_directory. The third 7 means anyone can do these tasks. So a 777 permission will sure let scripts write stuff to the directory, but with less security. chown is another Unix command to change the owership of a file/directory. #chown myusername.mygroupname a_directory will change the directory's owner to 'myusername', and make the directory belongs to 'mygroupname' group. All above refers to Unix/Linux usage, Windows probably uses some mouse clicks, but the essence should be the same regarding user/group and permission. Now that I have spent time and effort to write, I hope the people who ask questions can also take the time and effort to write questions. |
#29
|
|||
|
|||
Quote:
|
#30
|
||||
|
||||
Quote:
i know how to chmod, as you notice my question is where is the file if i'm chmoding... you said something about shell access ? whats that mean, i'm my own hosting reseller, i have full access to my host. If you woul be so kind to tell me where this file is,, thats all i ask btw its vb 3.5.0 rc2 the newest one as of this post thank you, -LM |
#31
|
|||
|
|||
Quote:
Quote:
|
Thread Tools | |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|