displayTeaserStandard dmHTML and SEO

[Phillip Rasmussen]

Forgive me if this is a double post, I posted this earlier today and nothing appeared.

I've been heckled by my SEO person about duplicate URLs for the same content. This occurs when a dmHTML content type is referenced through a teaser template.
eg: /about-us (the dmNavigation furl) & /about-us/about-us (dmHTML)

My initial reaction was to put a canonical link tag in the header for a dmHTML content type. (and I did)

<cfif lcase(stobj.typename) EQ 'dmhtml'>
    <skin:buildLink objectID="#request.navid#" r_url="theURL"/>    
    <cfoutput><link rel="canonical" href="http://#cgi.SERVER_NAME##theURL#"/></cfoutput>
</cfif>

But I also thought fixing the issue at the source would be a good idea, ie any teasers for dmHTML.

<cfset tmpNavid = application.fapi.getContentType("#stobj.typename#").getNavID(objectid="#stobj.objectid#", typename="#stobj.typename#", stobject="#stobj#") />
<skin:buildLink objectID="#tmpNavid#">
            <skin:view objectid="#stobj.teaserImage#" typename="dmImage" template="displayTeaserImage" />
</skin:buildLink>

Now all the teasers for dmHTML now reference the navigation furl and not it's own.

If anyone has a better solution, or if I'm making things difficult for myself please let me know. Most things I do originated from molio template way back when so some of the newer skeletons (fandango) might contain newer tricks.

Regards
Phil

[Blair McKenzie]

That is basically what we would recommend, so congrats on your good instincts.

Blair

--
You received this message cos you are subscribed to "farcry-dev" Google group.
To post, email: farcr...@googlegroups.com
To unsubscribe, email: farcry-dev+...@googlegroups.com
For more options: http://groups.google.com/group/farcry-dev
--------------------------------
Follow us on Twitter: http://twitter.com/farcry
---
You received this message because you are subscribed to the Google Groups "farcry-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to farcry-dev+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Might Aswell]

oh my sorry..  I just posted the same issue... someone must have spammed out a white paper on this... 

[Might Aswell]

With this solution what happens in a case where you have more than one dmHTML inside a dmNavigation?

 It doesn't happen often, but I know we do have a few of these..

Can a conditional statement be added?

On Sunday, August 18, 2013 10:10:43 PM UTC-7, Phillip Rasmussen wrote:

[Phillip Rasmussen]

You shouldn't have more than one dmHTML per dmNavigation. tut tut.
There really should be something that stops that practice in the webmin.
But if you do have multiples I guess you don't really need to worry. Perhaps just use the dmHTML furl as the canonical and leave it at that.

<skin:buildLink objectID="#stobj.objectid#" r_url="theURL"/>    


<cfoutput><link rel="canonical" href="http://#cgi.SERVER_NAME##theURL#"/></cfoutput>

Regards
Phil

[Chris Kent]

I have used multiple dmHTML content items for navigation nodes to allow for splitting large pages into smaller items.

There are a couple of webskin tags to assist - multiPageNav.cfm & multiPageTOC.cfm

I have also used multiple dmHTML page on an in-development project using Bootstrap Tabs getbootstrap.com/components/#nav-tabs to display each dmHTML content body.

Chris.