Hi, folks
we’re using the YOAST SEO module and have run into couple of minor issues with the theme v 1.71.
* First, since Yoast is already putting our Google publisher ID with rel tag in header, we don’t need it printed second time in footer.
* Second – and far more critical – when putting in the full URL for twitter for an author, under the “user” setup, the URL works properly in the author box on posts, but then breaks Yoast META in the post head so that the full URL vs the author ID is printed:
<meta name=”twitter:creator” content=”@https://twitter.com/AUTHORID”/>
vs
<meta name=”twitter:creator” content=”@AUTHORID”/>
I have tried using Yoast’s “force override” but doesn’t impact that element. We don’t have this issue with other themes we’re using (e.g., “Canvas”), which implies that the theme is “specifying” that information for the META tags.
Is there a function we can use to over-ride any of the theme META data in head to address this? Kind of a big deal when trying to tweet something.
(Also worth noting that Pinterest button still breaks image trying to share when there is a featured image, since the “featured” image is still linked to pagename/# which should NOT be self linked!)
Hi, as quick follow up.
Seems Yoast adds data field for Twitter and Google+ and expects to see
(user setup, per user/author)
Twitter account: @name
Google+: linktogoogle/accountname?rel=author
When the theme uses these same fields for placing in author box, it expects to see:
Twitter account: https://linktotwitter/name
Google+: linktogoogle/accountname
So….. seems either theme or Yoast will break.
Fix options:
1) use @name in user setup for proper author placement in yoast og/twitter card META; and then add new user data record for Newspaper Twitter Account (full URL)
2) or, get Yoast to update to use full twitter account – but with tens of thousands of sites using Yoast, seems more applicable to modify theme behavior at this point
1) Option to remove the Google author data from footer generated by theme, which is redundant with yoast/etc.
2) remove rel=”author” and conform with yoast and others using the full url with ?rel=author already added; but still have option to remove since redundant even without the additional rel=author added.
Right now we either have broken meta data for sharing to author’s @account in twitter/tweets, or broken link under author box — choice of two evils. And for Google author have broken link in footer for rel=author?rel=author
UPDATE:
1) the issue of the ?rel=author in footer is no longer an issue, and Google does now prefer to just use the meta tag in the HTML head:
<link rel="author" href="https://plus.google.com/+ChristopherSimmons/posts"/>
<link rel="publisher" href="https://plus.google.com/+NeotropeNet/posts"/>
* technically you should only be adding that element at bottom if an SEO plugin not running; however we can easily comment it out in the theme functions.php file
2) I have put in a bug track on github (Issue #372) for the Yoast SEO plugin to perhaps create an additional field, perhaps Yoast Twitter ID to be able to properly embed @USERID in head, but retain full twitter URL for use on page for author box, etc.
IDEALLY: we should be able to somehow for the moment turn off the option in author box to pull the @USERID twitter ID as it’s more critical to include the correctly parsed @USERID for the twitter card for the article author, than have link in author box for twitter. Unfortunately, if left alone, we end up with a bad link of:
/site/story-permalink/@USERID … in the author boxes, which will end up generating bad not found errors for Google, which is also really bad.
*POSSIBLE SOLUTIONS* right now
(1) turn off the twitter field link for the author box in theme (I cannot locate this in the snippets)
(2) turn off *all* links at bottom of twitter box temporarily as stop gap fix; better than nothing
(3) add/register new user account data field to functions called “Twitter URL” to add to user data meta for the full twitter.com account URL – and then call this in the theme vs “twitter” field? — for the moment we’d prefer this option, if you folks have your usual nifty arrow-screens on how to do that. This way your theme will work with the huge installed base of YOAST SEO (and possibly others who follow same method of putting @USERID in the twitter field, vs the full URL).
Option #3 would be awesome, in my opinion.
For those interested in what I sent to the Joost and the Yoast team via Github bug track:
REF: http://wordpress.org/support/topic/conflict-with-user-account-twitter-data-in-themes
HI, Joost and co…
ran into one issue with Yoast and several theme devs lately.
Specifically, under each user account setup, the field for Twitter is now common to Yoast and many themes, and themes use the field to put twitter link in things like an author box.
Problem is that Yoast SEO looks for simply @NAME from the user > twitter field to print in the META.
So, this ends up doing this:
<meta name=”twitter:creator” content=”@https://twitter.com/USER”/>
however, if we put just @USER in the twitter field, we would see this in themes under things like author box
LIKELY BEST FIX would be to come up with a new field the user account setup, like Yoast Twitter ID vs simply Twitter.
That way we could have:
Yoast Twitter ID = @USER
Twitter = https://twitter.com/USER
Since the field “twitter” is now a standard in most themes, if not WP, then it seems more logical for Yoast to either filter out the URL when it’s there to just print the @USER .. or setup alternate field for the non URL version of code.
Radu and folks…
I’m unable to change the title of this to
BUG: Twitter user setting incompatibility with Yoast SEO
however, this would be the correct issue; not as I originally entered it.
Need a solution for this as we either have broken author info for twitter, or a 404 error on every author post.
Hello,
thanks for the detailed bug report. I will have a look and see what we can do to fix the field incompatibility. More likely we will either use yoasts format or we will make a separate field.
For the author link in the footer we will check for plugins that already add them.
Sorry for the long delay, I was in a short vacation.
