• Resolved yankiara

    (@yankiara)


    Hi,

    I have two problems with Bricks and meta description generation and I think Slim has something to do with them.

    1. It seems that Slim doesn’t use post extract, if it is filled, to generate meta description for posts, but renders the content of the post and keep the first few words.

    But in Slim’s post metabox, if no meta description is filled, post extract is displayed as placeholder, if filled, so users believe extract is used, this is very confusing and misleading.

    I think Slim should ALWAYS use post extract if it is filled and if description in metabox is empty. ONLY if BOTH are empty, then render content.

    I added this PHP snippet to fix this:

    add_filter( 'slim_seo_meta_description', function( $desc ) {
        if ( is_singular( 'post') )
            $desc = get_the_excerpt();
        return $desc;
    } );

    2. When Slim generates meta description from content, H1 title is included at the beginning.

    But most of the time, if not all the time, my H1 titles are equal to meta titles, so meta description always replicates the meta title, which is useless and harmful since there’s few characters left for the actual description.

    Sometimes there are also category tags or post meta like date or comments at the beginning of post content, and they are included in description, which is not wanted.

    As a conclusion of this and also for performance purposes, I really think Slim should not mess with meta descriptions and leave user decide if he wants to leave them empty or not.
    Google renders them better than Slim, anyway, and it will push user to write a correct description.

    Thx and have a good day!
    Yan

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Anh Tran

    (@rilwis)

    Hi @yankiara ,

    Thanks a lot for your detailed feedback!

    1. Regarding post excerpt and manual meta description, I agree with you and I’ve updated the code to prefer using post excerpt if it’s available.

    2. Regarding the H1 and post meta in the content, it’s quite hard for the plugin to detect which is included and which is not, since it can’t know the position of the elements. I’m open to any idea to update the plugin if you have any suggestion.

    feezlinkzcooperation

    (@feezlinkzcooperation)

    Can your plugin be customized to have Like an SKU Auto generator for each car in the listing. and the search that car using the search on the frontend to get the only car with that SKU

    Plugin Author Anh Tran

    (@rilwis)

    Hi @feezlinkzcooperation ,

    I’m afraid that’s not the purpose of the plugin. We do the SEO only and have no relations with SKU or car listings website functionality. You probably want to check the WP Auto Listings plugin for that.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Issues with Bricks and meta descriptions’ is closed to new replies.