vBSEO 3.3.0 RC1 Released

Code:

RewriteCond %{REQUEST_URI} !(admincp/|modcp/|cron|vbseo_sitemap)
RewriteRule ^((archive/)?(.*\.php(/.*)?))$ vbseo.php [L,QSA]

I have a question on the "vbseo_sitemap" part of the update to the htaccess. If I have something already added there for another mod, does it matter what order they are in?

Thanks

does it matter what order they are in?

Nope.

Thank you

Upgraded just fine

Thanks

Originally Posted by BillS

Whats the purpose of canonical URL's if vBSEO previously had link consensus and everything handled for removing duplicate content?

I'll assume that since its been 4 days since my question, that its just a useless bloated feature thats being added in that won't help with SEO.

Or should i assume that true link consensus wasn't achieved before, and this is here to make up for it?

Originally Posted by BillS

I'll assume that since its been 4 days since my question, that its just a useless bloated feature thats being added in that won't help with SEO.

Or should i assume that true link consensus wasn't achieved before, and this is here to make up for it?

Hi Bill - vBSEO always had link consensus. Since this canonical attribute is such a minor addition, I would not consider it bloat. Actually - it does serve a function.

vBSEO applies rel=nofollow on any of the sorting URLs. However, it's possible that some people may want to link externally to a sorted version of a URL.

In this case, you can consider that the canonical attribute will actually ensure that Google and other search engines are aware that this is a duplicate format of the page, and where they should find the actual version to index.

In that regard, it adds limited additional value to vBSEO, since link consensus is far more powerful, but it is complimentary when it comes to those sorting URL formats.

Originally Posted by Joe Ward

Hi Bill - vBSEO always had link consensus. Since this canonical attribute is such a minor addition, I would not consider it bloat. Actually - it does serve a function.

vBSEO applies rel=nofollow on any of the sorting URLs. However, it's possible that some people may want to link externally to a sorted version of a URL.

In this case, you can consider that the canonical attribute will actually ensure that Google and other search engines are aware that this is a duplicate format of the page, and where they should find the actual version to index.

In that regard, it adds limited additional value to vBSEO, since link consensus is far more powerful, but it is complimentary when it comes to those sorting URL formats.

The rel=canonical seems like a bad way to handle them, because these pages will still be indexed if someone links to them.

I feel a better way would be to use the hash the same as showpost.php URL's are handled so engines discard the sorting strings. Like:

#daysprune=-1&order=asc&sort=title

Is this technically possible? Also i only just noticed, if you use a sorting URL then select page 1, 2 etc the page URL's change from the rewritten index1.html format to include the sorting query strings also.

#daysprune=-1&order=asc&sort=title
Is this technically possible?

Not unless we employ something like AJAX to fetch the content dynamically after pageload.
That's because the URL part after # isn't transmitted to the server at all.

guys, what about thread prefix?

From announcement

Other new features include LinkBack Hits, Thread Prefix Support, Guest Only Acronym Expansions, Dynamic Metas for Tag and Showpost pages, and Thread Tag Support for Relevant Replacements.

hi Mert, so there is an option for the prefix? how i can enable this feature? i checked my board but i don't see the prefix rewrited ...

Hello Christian ,

You can enable thread prefix support within config_vbseo.php

Please check the following options

PHP Code:

    define('VBSEO_URL_THREAD_PREFIX',      0);
    define('VBSEO_URL_THREAD_PREFIX_NAME', 0); 


edit: nvm it runs! anyway why this option isn't enabled by default?

Because lots of users may not want to include prefixes to rewrite rules. For example i see no value adding prefix to urls.

Originally Posted by webwizzy

It makes notices display via Javascript rather than plain text. I think this is to make them unreadable by spiders and increase content-to-code ratio, as mentioned in the description.

One side effect is that the notice doesn't display at all if a user has javascript disabled. I'll prefer to turn it off as my guest notice isn't noise, nice feature though.

This is beautiful! I almost can't wait for GOLD for this feature alone... I always have a notice that is always up and changes on a daily basis and it really isn't relevant to the specific page content!