[How To] Add H1 Tags to your vBulletin Templates for Long Tail Search Optimization

Originally Posted by Brian Cummiskey

You basically need to change <if to <vb:if and </if > to </vb:if>

It is not work, because on vb4 they are different. I tried many combinations like:

Code:

<vb:if condition="THIS_SCRIPT == 'blog'">{vb:raw pagetitle}</vb:if>

None of them didn't work. Something missing?

It looks like vb has changed variable scope.

{vb:raw threadinfo.title}
should work for showthread pages, however, in the navbar, it is blank. It must either be out of scope or they kill the reference template pointers before the navbar is included.

In otherwords, i'm stumped, and you will need to consult vb support for more help.

I'm using this instead.

Code:

<if condition="is_array($navbits)">
<br />
<table class="tborder" cellpadding="$stylevar[cellpadding]" cellspacing="$stylevar[cellspacing]" border="0" <if condition="THIS_SCRIPT == 'showthread'">width="65%"<else />width="50%"</if> align="center">
<tr>
    <td class="alt1" style="background: #FFFFFF url(skin/gradients/gradient_thead.gif) repeat-x top left; text-align: center" width="100%">

<if condition="THIS_SCRIPT == 'showthread'">
<!-- Tag SEO  -->
<h1 style="color: #FFFFFF; font-weight: bold; margin: 0; padding: 0;">$navbits[lastelement]</h1>
<!-- ### -->
<else />
<!-- Tag SEO  -->
<h1 style="color: #FFFFFF; font-weight: bold; margin: 0; padding: 0;">$navbits[lastelement]</h1>
<!-- ### -->
</if>


</td>
</tr>
</table>
</if>

<br />

Can you please update this thread how to have it work with vBulletin 4.0 please?

If you are using RR's, you don't need to do this. vb4 comes with heading tags in the template by default now, and with using the RR's, this thread is obsolete for vb4.

Hi all and thanks for the information.

I have now added H1 tags where appropriate.

I would like to ask if it's ok in forumdisplay for exampe to have the title of the forum as H1 and the thread titles as H2?

I would not recommend making every thread title in the list an h2, but the h1 is ok.

Thanks again Brian.

Would you put them as H3 or there is no need for that? Also in a forumdisplay what would you put as H2?

I would not make them headings at all, as they are not a logical outline heading-- they are the 'data' that supports the heading.

Think of headings as an outline to a document, as that is exactly what they are

h1
support1
support2

• h2
• support1
• support2
  
  • h3
  • support1
  • support2
    
    • h4
    • and so on.

Brian I got confused about Headings :(

I've set my vbseo RR's like this :

Code:

<h1 class="vbseoRR-1">[forum_title]</h1><h2 class="vbseoRR-2" id="relevant_replacement">Below you will find a list of discussions in the <b>[forum_title]</b> forums at the [bb_title]. The [forum_title] forum [forum_description]</h2>

and

Code:

<h1 class="vbseoRR-1">[thread_title]</h1><h2 class="vbseoRR-2" id="relevant_replacement">This is a discussion on <em>[thread_title]</em> within the <b>[forum_title]</b> forums, part of the [parent_forum_title] category; [first_post_30_words]...</h2>

are these ok ?
if no would you please suggest a better one please ?

Regards

I personally do not use them. I have hard-coded headings based on sections in my templates.
We recommend
VB4 RR's? - vBulletin SEO Forums

Originally Posted by Brian Cummiskey

I personally do not use them. I have hard-coded headings based on sections in my templates.
We recommend
VB4 RR's? - vBulletin SEO Forums

Thanks so much brian,

Brain would you please tell me how to hard-code headings based on sections in my templates ?

Sorry if I ask , but Its long time that I am looking to ask this question, and I think its the second time that I ask it.

please give me some tutorial or something like that.

I will be so thankful.

Best Regards.

It's the first post of this thread...

oh thanks, but would you please tell me which one of the methods is better ?
in other words which one do you prefer ?

thanks for the support

Doing it manually is far more flexible, but it requires more work for upgrades/reverting templates/etc.