• Hi there,
    unfortunately I have problems with the output of my SEO title tag on posts using the Neve template. I thought installing the extension “Title Fix” would solve the problem but it doesn’t. I contacted the developers of Neve and they said, it is the problem of the TSF plugin. I hope you have an idea of how to fix this. I am wondering why the page sites are with correct title tag but the posts are not and are using the title of the post instead the given SEO title with TSF. When using the theme Twenty Twenty-One everything SEO related is okay.
    Kind regards, Tanja

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Sybre Waaijer

    (@cybr)

    Hi Tanja,

    Do you have a URL of the problematic page with the template?

    I assume you’re using the commercial version of the Neve theme. Because of strict guidelines, such issues shouldn’t arise with themes directly available on the WordPress repo.

    Often, when these issues arise, the requested template isn’t registered with WordPress but on top of an existing page (or worse, a dynamic page), where developers patch every issue individually with filters — these patches do not trickle down to other plugins. Because of this, WordPress doesn’t know the page exists, and so The SEO Framework can’t either.

    Thread Starter tier1304

    (@tier1304)

    Thanks for your reply! Yes, it is the commercial Neve Pro version.
    Here’s the link to a post of my test website (because it’s only my test environment, I don’t have https:// ) :
    https://shapewear-damen.de/staedtereisen/bierreise-duesseldorf/
    The title there should be the same like in meta property=”og:title
    But the pages work well with the title tag : https://shapewear-damen.de/bierreisen/

    Plugin Author Sybre Waaijer

    (@cybr)

    Hi again!

    Thank you for the links.

    The page appears to be registered correctly, but the title seems to be overwritten/filtered, which TSF tries to prevent.

    I wonder what causes this, and I also wonder if the Title Fix extension could address this.
    You can get it for free at https://tsf.fyi/e/title-fix.

    I also looked at a few pages’ source code, and the pages without the issue have the body class nv-without-title, which is missing on the problematic page. Perhaps they have added a “title” toggle to the page options, but I’d assume this would toggle how the title is outputted in the content itself. Still, it’s worth a try to find and use this toggle.

    Please note that since I do not have access to the Neve Pro code, I cannot help pinpoint the issue immediately. The theme authors are free to contact me at any time so we can resolve the conflict.

    Thread Starter tier1304

    (@tier1304)

    Thank you for taking care.
    Unfortunately, as mentioned in my first post, the “Title Fix” has no effect. I have contacted (again) the developers of Neve, I hope they will contact you or have an idea how to fix this.
    It’s just weird that it seems I am the only one having this problem.

    Thread Starter tier1304

    (@tier1304)

    Just to let you know or for other users with the same problem:
    it seems that the problem only happens when the custom layout of Neve is used. So this issue is only in this specific case, with the custom layout for posts and the SEO Framework plugin.
    I assume that I have to delete TSF and use YOAST or SEOPress instead. Pity!

    Plugin Author Sybre Waaijer

    (@cybr)

    Hi again, Tanja!

    Thank you for forwarding my concerns to Themeisle.

    Is it not possible to assign the custom layout to a Post or Page? This should resolve the issue immediately.
    Also, should the custom layout even be publicly queryable? From their documentation, I understand it’s used as a boilerplate to implement in other pages, not intended to be visited itself.

    But that’d be a pity indeed! Though neither SEOPress nor Yoast SEO can resolve such an issue without patching. If those do appear to work, then the Neve Pro Addon plugin authors have specifically added patches for these SEO plugins, and those make break any day. The only correct way to ensure compatibility is to abide by the WordPress APIs, and only use patches as a last resort.

    I hope I can clarify that I am unable to address every plugin and theme that forgo the WordPress APIs because that’d make me maintain north of 1000 patches every year. Therefore, I try to educate fellow developers, so we can focus on features instead of fixes.

    Still, I might not be understanding the intent and setup of these templates. I’d love to have a closer look at how it’s set up, but we’d need to wait for Themeisle for a clarification.

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.