Is the meta fb:page_id still alowed on a website ? - facebook-opengraph

I'm implementing Open Graph on website.
As mentionned on Facebook insights documentation, it's allowed to put meta like this one :
meta property="fb:page_id" content="your_page_id"
But the Facebook debugger tool showed an error :
Extraneous Property: Objects of this type do not allow properties
named fb:page_id.
Other websites seems to have the same error like Mashable.com
In other hand, on another documentation page, the page administration seems to be only working with fb:admins and/or fb:app_id. But no mention of the fb:page_id.
So what the states of the fb:page_id meta on a website ?

The behavior you describe appears to be a bug. The issue has been submitted to Facebook and accepted:
http://developers.facebook.com/bugs/144705805635591/?browse=search_4f0323eb790c29273088132.
It has now been resolved.

I don't have an answer for that but I'm looking for one as well. It wasn't a requirement for OGP to function but was for page insights.
As of late I can't seem to see fb:page_id referenced anymore on ogp.me or facbook's docs.

Related

Weglot Translation Not able to translate the checkout payment section

I am using Weglot Translation Plugins in WordPress. Everything working fine except checkout payment section not updating that's why the translation not working for that particular section
Check below the screenshot
https://prnt.sc/1zs8ptj
I'm Edson from weglot developper team.
Regarding your problem there are 2 things:
1- first of all, you should check from the dahboard if your translation is present. If not, one of the first ways is to see if you haven't gone over your word limit.
2- The error you are reporting seems "normal" because the Visual Editor must be used for "static" pages. In your case, you seem to be using the tool to translate an order page containing Ajax calls which notably causes CORS header issues.
I hope this will help you and do not hesitate if you have any questions to contact our support team
Best

Had all relavant opengraph social meta (created by AIOS) but facebook debug failed to recognize

I know this is an old topic but I've digged dozens of related questions and solutions but neither of them works.
Some of questions I've read:
Can't fix: 'og:image' property should be explicitly provided, even if a value can be inferred from other tags
Wordpress All In One SEO plugin not sharing to Facebook wall
My test url for facebook debug:
https://trangthietbiytehcm.com
Also, I debuged via Facebook sharing debug and Facebook Object debug
Here is Facebook Object debug:
Here is Facebook Sharing debug:
here is the post's head tab:
I also add that sometimes this post could be displayed well (including image thumbnail) on my facebook page but most of time it did not.
I've cleared my wordpress caches.
Absolutely, I can read the social opengraph tab on my post but facebook failed to read them. I do not know the reason behind this problem. Please help me to be clear! thanks
EDIT:
This is a capture of the fact that sometimes Facebook receives my blog post well. And the post link is: https://trangthietbiytehcm.com/uncategorized/san-pham-test-lan-2/
And I wnat to add that the above test link (https://trangthietbiytehcm.com/uncategorized/bai-viet-mau/) also has the same fact as this
EDIT (UPDATE):
After months of be frustrated with this problem, I even tested on another new web on new host server. I've finally found that the reason of this problem is the page cache function of the W3 total cache
We've found this issue to be related to W3 Total Cache, too. Specifically, it's the Wordpress Dashboard > Performance > Minify > Eliminate render-blocking CSS by moving it to HTTP body feature. What this does is shove all the CSS right after the tag, moving all the other header tags down.
And it seems Facebook (and Twitter?) only parse a fixed amount of the page before deciding to try and render... and if your CSS is long, well, it never sees your og:image tag (or any others, like Title, etc).
We have yet to find a good fix which still allows this feature to be used.

Meta tags appear correct but Facebook sharing is empty (no title, description, or image)

This problem exists for all pages on this site. The meta tags appear correct but whether you use the share link on the site, or try to share direct on FB, the image, title and description are not used.
There must be a legitimate issue as the Sharing Debugger also shows an empty/plain sharing dialog. But the Facebook share debugger isn’t given me any helpful info. It sometimes shows a 302, which I don’t understand as there is no redirect on the site. Refreshing the scrape sometimes shows an error Unknown Image Error, which also doesn’t seem to be a legitimate issue.
Almost always the Facebook share debugger shows a 302 the first time and then follows with other unhelpful errors.
Maybe a DNS issue, weird that it would be site wide.
Example Links:
[http://pikespeakharleyownersgroup.com/group-riding-pphog-405/][1]
[http://pikespeakharleyownersgroup.com/tell-tires-toast/][2]
[http://pikespeakharleyownersgroup.com/30th-annual-high-country-toy-run/][1]
Any and all help is very appreciated.
Try debugging your page URL on below link:
https://developers.facebook.com/tools/debug/
Once you scan your URL, on the link I provided, you will see "Warnings That Should Be Fixed" section. Try resolving warnings mentioned in that section.
Hope this will help you!

AMP Test Shows No Errors by GSC says So

Here are the two pages that the Google Search Console shows 2 Critical Errors for:
1. https://www.hillwebcreations.com/fix-product-markup-errors-avoid-google-manual-action/amp/
2. https://www.hillwebcreations.com/google-image-guidelines/amp/
Both (out of 80+ post are the only two with issues all use the exact same AMPforWP plugin) show the same 2 issues:
Details:
(1) The mandatory tag 'amphtml engine v0.js script' is missing or incorrect.
(2) The mandatory tag 'link rel=canonical' is missing or incorrect.
But then when I run the link to the AMP TEST, both say "Valid AMP page
Page is eligible for AMP search features in Google search results".
https://search.google.com/test/amp?utm_source=wmx&utm_medium=link&utm_campaign=wmx-agg&id=KWGeOzUCXJ7fBP9azfDLIw
https://search.google.com/test/amp?utm_source=wmx&utm_medium=link&utm_campaign=wmx-agg&id=Josb4P-x6poP3B_96qRJhw
And oddly, the one URL has a strange "v" added to the end. Where does that come from?
https://www.hillwebcreations.com/fix-product-markup-errors-avoid-google-manual-action/amp/v/
Thanks in advance for any help to sort this out.
You may refer with this thread regarding your issue The mandatory tag '%1' is missing or incorrect. It might be a conflict with another plugin that's modifying the output of AMP pages. Best option is to disable it for any URLs that end in /amp/?. Based from this documentation, the fix is to add (or correct) the mandatory HTML tag.
It sounds like Google Search Console has a different copy of your web page than the AMP Test tool. Google Search Console doesn't fetch your page live, it is using Google's last crawled version. It is possible that the page has changed since then and this issue will resolve itself after some crawling time has passed.
Try refreshing the version that Google has cached in the amp-cache by using the update-ping url (include the full path to the page after the domain):
https://cdn.ampproject.org/update-ping/c/s/example.com/
See details here: https://developers.google.com/amp/cache/update-cache

Google Adword not working /conversion.js not found

I'm currently working on a wordpress site. My task is just to add the conversion script in a thankyou page. I added the script here: http://www.livingedge.co.nz/thanks-for-getting-in-touch/ , unfortunately does not work. It says that a conversion.js was not found.
See the attached screenshot: http://screencast.com/t/52ixQUzHKNxZ
I added the conversion script on the footer put it in a conditional so that it will load only on the thakyoupage.
I'm new to this and can't figure out what would be the possible cause of such problem.
I tried adding the script in the header, on the page editor, on a form redirect.
Q: What could be the possible cause of this issue?
The URL you are using for the conversion script is incorrect — the correct one has "www" in the domain name.
The fact that you've got this link wrong makes me think you may be looking at incorrect directions.
Follow the instructions given in the Google documentation page "Setting up conversion tracking" precisely.

Resources