Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Robert Foster 367 posts 1376 karma points admin c-trib
    Feb 24, 2017 @ 00:07
    Robert Foster
    0

    seoTitle is not updating the live content properly

    We have seoChecker installed on our site - https://koben.com.au - and have just noticed that the rendered page Title does not reflect the Snippet Preview on the content node. For example:

    On the rendered page, the title might be "Umbraco CMS | KØBEN Digital"

    On the snippet preview it is "Your Umbraco Certified Gold Partner | KØBEN digital"

    Our setup for this particular document type for the seoTitle is as follows:

    • title
    • @nodeName

    When I look at the Umbraco Cache file for this particular node, I see the following:

    <metaData><![CDATA[<SEOChecker>
      <focusKeyword></focusKeyword>
      <seoTitle></seoTitle>
      <seoKeywords></seoKeywords>
      <seoDescription>KOBEN digital is a multi-disciplined digital agency with a range of services that goes well beyond simple website development.</seoDescription>
    </SEOChecker>]]></metaData>
    

    It appears that for some reason publishing the node is not saving the seoTitle correctly.

  • Richard Soeteman 3234 posts 9118 karma points
    Feb 24, 2017 @ 06:29
    Richard Soeteman
    0

    Hi Robert,

    Make sure to set up the page title template correctly on the document type and make sure to render HTML in template. Then it should be good.

    Best,

    Richard

  • Robert Foster 367 posts 1376 karma points admin c-trib
    Feb 24, 2017 @ 07:14
    Robert Foster
    0

    Hi Richard,

    Yes - we're doing all of that. We're actually using

    @meta.AllTags
    

    to render them out, and the description, canonicalUrl, etc. are all rendering correctly. As I pointed out in the original post, the seoTitle property is actually blank in the umbraco cache file - this is the case for all nodes.

    Configuration for this particular node:

    SEOChecker Configuration

    Title Property: Title Property

    SEO Checker Rendering: enter image description here

    However, it's rendering the @nodeName instead of the title property.

  • Robert Foster 367 posts 1376 karma points admin c-trib
    Mar 03, 2017 @ 05:28
    Robert Foster
    0

    Hi Richard,

    I figured out what was going wrong - the Title pre-value property on SEOChecker was configured to @pageName - I would have thought that the individual Document Type settings would override this?

  • Richard Soeteman 3234 posts 9118 karma points
    Mar 03, 2017 @ 07:38
    Richard Soeteman
    0

    Hi Robert,

    Not sure what you mean but there is inheritance. The manual describes best how to configure.

    Best,

    Richard

  • Robert Foster 367 posts 1376 karma points admin c-trib
    Mar 10, 2017 @ 23:31
    Robert Foster
    0

    Hi Richard,

    The problem was that the Data Type had the Title pre-value property configured to @nodeName - no matter what I set the individual Document Type configuration (Default SEO Properties) for the Title property, the Data Type pre-value was overriding it.

    My expectation was that the Document Type configuration would take precedence? It doesn't talk about this at all in the manual though.

    Thanks, Rob.

  • Richard Soeteman 3234 posts 9118 karma points
    Mar 13, 2017 @ 07:24
    Richard Soeteman
    0

    Hi Rob,

    You don't have to map the title on the datatype. That is only if you are installing on an existing site which already contains some properties.

    If you don't map SEOChecker uses its own fields.

    Best to use that in the future.

    Hope this helps,

    Richard

  • Robert Foster 367 posts 1376 karma points admin c-trib
    Mar 14, 2017 @ 07:54
    Robert Foster
    0

    Hey Richard,

    Yep, as soon as I saw the configuration on the Data Type I realised what had happened; however would have thought that the document type configuration overrode it, which caused my confusion.

    Anyway, all good now.

    Rob.

Please Sign in or register to post replies

Write your reply to:

Draft