• Resolved rebeccaolson

    (@rebeccaolson)


    I have been using Yoast for over a year, with no issues. I recently added a blog to my site, and am getting an error for the meta tag on the blog page. The page name is “For the Love of Lavender” and in the Yoast settings, I have set the meta title as “For the Love of Lavender | A Sequim Lavender Farm Blog”

    However, in google search results (if you search “For the love of lavender blog”) it is showing up as “For the Love of Lavenderpagesepsitename%%” I have looked everywhere in the Yoast settings and can’t figure out where this is happening. I am not experiencing this issue on any other page, so I believe it is unique to this page alone.

    When I looked into the Yoast sitemap for the page (submitted to google), it is showing the error on two lines:
    <meta property=”og:title” content=”For the Love of Lavenderpagesepsitename%%” />
    <meta name=”twitter:title” content=”For the Love of Lavenderpagesepsitename%% />

    Can you help me find where/how to fix these, either within the plugin settings or by going into the html of the page itself? I’m not a complete newbie, but I’m not sure how to address this.

    Thanks!
    Rebecca

Viewing 14 replies - 1 through 14 (of 14 total)
  • Plugin Support amboutwe

    (@amboutwe)

    Sometimes strange behavior may be caused by a plugin or theme conflict. The fastest way to rule out conflicts is to deactivate all non-Yoast plugins and switch to a standard theme like Twenty Seventeen. If this resolves the issue, you have a conflict and should activate one plugin at a time until you locate the conflict. Finally, after all plugins are active, switch to your theme. This will narrow down the conflict to a specific plugin or theme.

    If you are unfamiliar with checking for conflicts, we wrote a small guide that will walk you through the steps. You can find it here: How To Check For Plugin Conflicts

    Thread Starter rebeccaolson

    (@rebeccaolson)

    Thank you amboutwe – the code is specifically within the Yoast plugin html (I should have made that clear in my original post).

    Just to be sure, I deactivated all plugins, and the html disappeared. When I activated Yoast (as the only plugin) the error re-appeared. I checked the other pages on my site, and the Yoast html on those pages is correct. So the error is only on the blog page, and is directly related to Yoast.

    Any ideas for what could be causing this? If not, can someone explain where to manually edit this code within my WordPress files? I’ve included the entirety of the Yoast html/section below, or you can view it yourself if you go to the page with the error: http://www.lavenderconnection.com/for-the-love-of-lavender

    Thanks!
    Rebecca

    <!– This site is optimized with the Yoast SEO plugin v4.6 – https://yoast.com/wordpress/plugins/seo/ –>
    <link rel=”canonical” href=”http://www.lavenderconnection.com/for-the-love-of-lavender&#8221; />
    <link rel=”publisher” href=”https://plus.google.com/+Lavenderconnection”/&gt;
    <meta property=”og:locale” content=”en_US” />
    <meta property=”og:type” content=”object” />
    <meta property=”og:title” content=”For the Love of Lavenderpagesepsitename%%” />
    <meta property=”og:url” content=”http://www.lavenderconnection.com/for-the-love-of-lavender&#8221; />
    <meta property=”og:site_name” content=”Lavender Connection” />
    <meta property=”og:image” content=”http://www.lavenderconnection.com/wp-content/uploads/2016/02/Barn-Lavender-1.jpg&#8221; />
    <meta name=”twitter:card” content=”summary” />
    <meta name=”twitter:title” content=”For the Love of Lavenderpagesepsitename%%” />
    <meta name=”twitter:site” content=”@lavenderconnect” />
    <meta name=”twitter:image” content=”http://www.lavenderconnection.com/wp-content/uploads/2016/02/Barn-Lavender-1.jpg&#8221; />
    <!– / Yoast SEO plugin. –>

    Thread Starter rebeccaolson

    (@rebeccaolson)

    Sorry – I forgot to add that I also switched to the 2017 theme and followed the same steps (deactivated all plugins, then only activated Yoast). The error disappeared when Yoast was deactivated, and reappeared when it was activated – same as with my current theme.

    Plugin Support amboutwe

    (@amboutwe)

    The title and description templates, which use variables like %%sep%%, can be found here: Admin > SEO > Titles & Metas*

    What do you have for the template for this particular type of page (post, page, category, tag, etc)?

    You can also manually override the template by setting a title when editing this specific URL. If you manually set a title, what did you enter at the post/page level?

    * If you do not see Titles & Metas, the advanced settings can be enabled by following the steps here.

    Thread Starter rebeccaolson

    (@rebeccaolson)

    Thanks for your reply. I have set my Titles & Metas in Yoast, and as I mentioned, they are working correctly on all other pages of my site. Here is what I have set for the following:

    Posts: %%title%% %%page%% %%sep%% %%sitename%%
    Pages: %%title%% %%page%% %%sep%% %%sitename%%

    The blog page is a page, and should default to the “Pages” setting, correct? I have also gone in and adjusted the meta description within the Yoast settings on the blog page itself. I have it set:

    SEO Title: For the Love of Lavender | A Sequim Lavender Farm Blog

    It shows correctly on the page and within the snippet provided by Yoast – but it is obviously not updating within the html of the site. I also find it odd that the twitter:title is showing up with the same mistake – I do not link to or reference Twitter on the blog page, except the social media links that are in the footer (and the footer works and there are no twitter:title errors on any other page of my site.)

    Thanks for your help!

    Plugin Support amboutwe

    (@amboutwe)

    This most commonly occurs when your theme outputs a custom title for static home and blog pages. Does the Yoast title appear correctly if you switch to a standard theme, like Twenty Seventeen?

    Thread Starter rebeccaolson

    (@rebeccaolson)

    amboutwe – Yes, as I mentioned a few comments ago:

    “I also switched to the 2017 theme and followed the same steps (deactivated all plugins, then only activated Yoast). The error disappeared when Yoast was deactivated, and reappeared when it was activated – same as with my current theme.”

    Just to be safe, I tried this again, with the same result. I switched to the 2017 theme, and the error was still there. I deactivated all of my plugins, and the error disappeared. I activated only Yoast, and the error reappeared.

    whileimgonearoundtheworld

    (@whileimgonearoundtheworld)

    Hello,

    I created an account because i had the same problem (only on “category” pages) and found a solution.

    It must be a problem of the plug-in because a lot (like A LOT) of websites are returning this “error” when looking up for an answer on Google (search for “pagesepsitename%%”).

    Anyway, i found a solution :

    I had “%%category%% %%page%% %%sep%% %%sitename%%” in my category field.

    1) Go into your Yoast settings

    2) Titles & Metas

    3) If only category pages are screwing up, change only the “category” field. If it’s only pages, change the “page” field by removing all items but not the first one
    -> So I had left : “%%category%%”

    4) Apply changes and reload the page that was screwing up : it worked

    5) I then added every items one by one
    -> “%%category%% %%page%%” -> 4) -> it worked
    -> “%%category%% %%page%% %%sep%%” -> 4) -> it worked
    -> “%%category%% %%page%% %%sep%% %%sitename%%” -> 4) -> it worked

    In the end, i have no idea what went wrong the first time but it looks like you need to override your default settings by something else in the database then add back your default setting.

    Hope it can help.

    Plugin Support amboutwe

    (@amboutwe)

    Since @whileimgonearoundtheworld fixed the issue by replacing the database entry, it may be related to the database. Have either of you recently changed servers, optimized the database, restored data or anything else that might interact with the database?

    whileimgonearoundtheworld

    (@whileimgonearoundtheworld)

    Not for me.

    Clean install of WordPress / Theme. I configured the theme / WordPress settings, wrote a few articles but that’s it.

    Then, I installed Yoast for the first time (first SEO plugin also) and I noticed this problem but only on category pages.

    Plugin Support amboutwe

    (@amboutwe)

    Please provide the following:

    • All installed theme names and versions indicating the active one.
    • All plugin names and versions indicating the active ones.
    • Do you have any must use or drop in plugins? If yes, does removing these help?
    • Can the issue be reproduced in a new install? If so, please provide the steps.
    • Site details
    • Operating system of your webserver
    • Webserver in use (Apache, NGINX, IIS, other) and what version
    • PHP Version and (extensions if applicable)
    • MySQL Version
    • Name of Webhost
    Thread Starter rebeccaolson

    (@rebeccaolson)

    Site details
    Operating system of your webserver: Linux
    Webserver in use (Apache, NGINX, IIS, other) and what version: servers supports Apache, NGINX
    PHP Version and (extensions if applicable): Php latest version is 7.0
    MySQL Version: MySQL Version is 5.6
    Name of Webhost: Blueost

    Thread Starter rebeccaolson

    (@rebeccaolson)

    Shoot – I created a really long reply above and thought I had submitted it, but I guess there was a glitch. Here we go again:

    @whileimgone – That method didn’t work for me unfortunately.

    However: the workaround that I used is this. I created a new page with a new title, and selected it as the “blog” page for my posts to appear. This new page is working fine, with no taxonomie issues. I didn’t delete the old page, in case @amboutwe wants to research the issue (since others are experiencing problems as well.)

    @amboutwe – here is the info you requested.
    All installed theme names and versions indicating the active one.
    Tower – child (active, no version)
    Tower 2.1
    Twenty Seventeen 1.2

    All plugin names and versions indicating the active ones.
    ACTIVE

    amr shortcode any widget Version 3.4
    Better Search Version 2.1.1
    Boxzilla Version 3.1.12
    Contact Form 7 Version 4.7
    Envato WordPress Toolkit Version 1.7.3
    Google Analytics for WordPress by MonsterInsights Version 6.1.7
    Head and Footer Scripts Inserter Version 4.0
    MailChimp for WordPress Version 4.1.2
    MOJO Marketplace Version 1.1.3
    Order Weight for WooCommerce Version 0.3.5
    Simple Follow Me Social Buttons Widget Version 3.3.
    Slider Revolution Version 5.2.6
    Stop Spammers Spam Control Version 7.0
    USPS Simple Shipping for Woocommerce Version 1.2.6
    WooCommerce Version 3.0.5
    WooCommerce – Gift Cards Version 2.5.8
    WooCommerce Extended Coupon Features PRO Version 2.5.0
    WooCommerce PDF Invoices & Packing Slips Version 1.6.5
    WP Retina 2x Version 5.0.5
    WPBakery Visual Composer Version 5.1.1
    Yelp Widget Pro Version 1.4.3
    Yoast SEO Version 4.7.1

    INACTIVE
    LayerSlider WP Version 5.6.9

    Do you have any must use or drop in plugins? If yes, does removing these help?
    MUST USE

    Endurance Browser Cache Version 0.4
    Endurance Page Cache Version 0.6
    SSO
    – The only one of these plugins that I can disable is “Endurance Page Cache” – disabling it did not resolve the issue.

    DROP IN
    install.php
    – I cannot disable this

    Can the issue be reproduced in a new install? If so, please provide the steps. – I am not sure what you mean by this.

    Hi,

    We’re working on cleaning up these Yoast SEO support forums. Since your thread hasn’t had any activity in the last two weeks, we’ve marked it as resolved.

    Of course, you’re always welcome to open a new topic. We kindly ask you to read this post before doing so.

    Thanks for understanding!

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘Yoast Meta (page title) error: pagesepsitename%%’ is closed to new replies.