In the default theme this is the only H1 tag on topic pages (green arrow)



The problem I have with this is that text isn't even shown on the page, and the forum's name shows twice. Why not delete that (whatever it is) and change the titles (red arrow) to be in an H1 tag? (They're currently in H2).

It would be better SEO-wise :)

I see what you mean, but the title is appearing in an H1, so I'm happy with that. Ideally though my site name would be a suffix in the H1 tag, rather than prefix. H2 appears correct, also.

Agreed, get rid of the site name, just use the topic title.

I see what you mean, but the title is appearing in an H1, so I'm happy with that. Ideally though my site name would be a suffix in the H1 tag, rather than prefix. H2 appears correct, also.

But this is kind of like cloaking because that text doesn't appear anywhere on the visible page.

cloaking your own website title name?

By default the h1 class hide contains the title of your website, so it by all means not cloaking, unless, you modify that codes and display other contents.. which is not IPB's problem

cloaking your own website title name?

By default the h1 class hide contains the title of your website, so it by all means not cloaking, unless, you modify that codes and display other contents.. which is not IPB's problem

I'm not cloaking some other codes :) I'm just suggesting that the visible text should be turned into an H1 instead of this invisible text.

I'm not cloaking some other codes :) I'm just suggesting that the visible text should be turned into an H1 instead of this invisible text.

Iwasnt saying you are, you asked if that would be cloaking and I only said no its not unless you change the content of the hidden text, as for SEO, I agree with you 100%, infact that's what I'm doing on my forum

if you look at the front end it displays only some of the navigation data that i want to show

<h1> my board name (then the rest of my navigation hidden <span class='hide'> Forum Name > <span class='hide'> Sub Forum Name > <span class='hide'> Topic Title
</h1>

All the bold text are hidden although it is displayed for search engines

The codes I'm using are

<!-- Start : SACRED PAGE NAME ABOVE NAV -->

<div id="appNavBar">

<php>$this->xdid_first = 0;</php>

<h1 class='YKReg s60'>

						<if test="xswitchnavigation:|:!$this->settings['remove_forums_nav'] OR ipsRegistry::$current_application == 'forums'">

							RealCustomScripts Community

							<if test="xdidfirstnav:|:$this->xdid_first=1"></if>

						</if>


						<foreach loop="xnavigation:$items['navigation'] as $xidx => $xdata">


							<span class='<if test="xdidfirstappnow:|:$this->xdid_first"> hide</if>'>{$xdata[0]}</span>

							<if test="xforsuredidfirstnav:|:$this->xdid_first=1"></if>

						</foreach>

</h1>

</div>

<!-- END : SACRED PAGE NAME ABOVE NAV -->

The hidden <heading> tags are not for SEO, they are for accessibility. Screen readers assign quite high importance to <heading> tags in order to recognise blocks of content, and we all want IPB to be as accessible as possible. For some customers, it is even a legal requirement!

My personal opinion is that where SEO conflicts with accessibility, accessibility wins hands down.

The site name appears twice in the Search Engine's view.Is there any way to remove one and format the whole H1 title in the following format:
<h1>Topic Title:"Site Name"</h1>

We do hope to change this for IP.Board 3.2, so that the most appropriate title is used for the H1 tag on the page, and it will be visible on screen. :)

I upgraded to 3.1.4 a few days ago and I noticed my traffic dying off.... I just noticed the board name in every bloomin' H1.... I need to get this removed urgently. It's hardcoded, where is it?

EDIT: Started new topic:

The hidden <heading> tags are not for SEO, they are for accessibility. Screen readers assign quite high importance to <heading> tags in order to recognise blocks of content, and we all want IPB to be as accessible as possible. For some customers, it is even a legal requirement!

My personal opinion is that where SEO conflicts with accessibility, accessibility wins hands down.

That's where options should be made available. If coded properly, it could be BOTH accessible and SEO'd.