Author archives not having the correct title

  • Resolved Babak Fakhamzadeh

    (@mastababa)


    4 months ago

    I use Co-Authors Plus.

    The author archives show an incorrect page title. This, because the %name variable for some reason doesn’t use the name of the author, but uses the list of authors associated with the first article in the archive in question.

    So, instead of “Mr. X, Author at My Website”, when the first article in the list was authored by “Mr. X” and “Mr. Y”, the title of the archive for both Mr. X and Mr. Y is “Mr. X, Mr. Y, Author at My Website”.

    Removing any value for the “SEO title” for the “Search appearance” of the Author archives reverts to the problem above. Only the %name variable outputs the author name, and, when used, picks up the list of names of the first article in the archive.

    This seems like a bug.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Maybellyne

    (@maybellyne)

    Hello @mastababa

    Thanks for reaching out. I tried to re-create the scenario you described. Since you cannot specify the main author in a series of guest authors, it’s impossible to know which author name should be replaced when %%name%% is used. As such, I don’t see this as a bug in Yoast SEO.

    • This reply was modified 3 months, 4 weeks ago by Maybellyne.
    Thread Starter Babak Fakhamzadeh

    (@mastababa)

    thanks, and thanks for trying to replicate the problem, but I think you’re not completely understanding my situation.

    in my example, both Mr. X and Mr. Y are users, not guest authors. And the incorrect title is showing in the author archives for both users.

    so, the titles of the author archive for the user Mr. X, and the title for the author archive for Mr. Y are both “Mr. X, Mr. Y, Author at My Website””.
    in both cases, the author archive is requested, so something like /author/mrx and /author/mry.

    therefore, it’s very clear what author should be named in the title.

    and so, this does appear like a bug in Yoast.

    Plugin Support Maybellyne

    (@maybellyne)

    Please create a new issue for our developers here. We’re actively using the bug tracking on our GitHub repository.

    You will need an account to create a new issue. Please provide as much information about the issue, including the URL to this conversation. This guide will help you submit a complete report which may result in a faster resolution.

    Thread Starter Babak Fakhamzadeh

    (@mastababa)

    Done.

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