Last post 6 hours 21 min ago

Posts last week 89

Average response time last week 30 min

All time posts 67739

All time tickets 10468

All time avg. posts per day 21

Helpdesk is open from Monday through Friday CET

Please create an (free) account to post any question in the support area.

Please check the development versions area. Look at the changelog, maybe your specific problem has been resolved already!

All tickets are private and they cannot be viewed by anyone. We have made public only a few tickets that we found helpful, after removing private information from them.

#3496 – Wrong og:url

Posted in ‘sh404SEF’

This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Friday, 07 April 2017 17:17 UTC

altrasoluzione

Hi!
On the site https://www.xxxx.com og:url is being generated correctly only on home page.
For all other pages (except https://www.xxxx.com/le-offerte-pagomeno/... which are managed by HikaShop) og:url is missing the domain part "https://www.xxxx.com/".

For example, on page https://www.xxxx.com/servizi/ og:url is "servizi/" while I think it should be "https://www.xxxx.com/servizi/".

Am I wrong?

Thank you very much
Kind regards

Friday, 07 April 2017 17:54 UTC

wb_weeblr

Hi

Yes, that's more than unusual. Please check the following, for this sample URL:

1 - In your configuratio.php file, is there a value for the $live_site variable?
2 - In the Joomla SEF system plugin, do you have a value (even if just a space or something) for the domain name?
3 - Have you manually set a canonical URL set?

Also be sure to check all settings in Hikashop and maybe ask them. Some pages are fine such as this one: https://www.xxxx.com/le-offerte-pagomeno/pagomeno-standard, so there really is something weird going on here.

Rgds

Friday, 07 April 2017 19:59 UTC

altrasoluzione

Hi, thank you for you quick reply!

Here are the answers to you questions:
1 - public $live_site = '';
2 - Site Domain in System - SEF plugin is empty
3 - Yes. I've setup canonical without domain (only "/servizi"). I've just realized that it works width canonical tag (https://www.xxxx.com/servizi) but it doesn't with og:url which is set to "/servizi".

Why canonical and og:url behave in different ways?

Thank you
Regards

P.S.: As I specified in my O.P., Hikashop pages (https://www.xxxx.com/le-offerte-pagomeno/product_nameXXX) are ok because they are not managed by sh404SEF

Monday, 10 April 2017 07:02 UTC

wb_weeblr

I've setup canonical without domain (only "/servizi"). I've just realized that it works width canonical tag (https://www.xxxx.com/servizi) but it doesn't with og:url which is set to "/servizi".

I don't think you did that. I cannot reproduce this. I think what you did is enter the URL without a leading slash, ie exactly as it was output ("servizi").

When I tried to reproduce, using "/servizi" is correctly transformed into https://www.example.com/servizi and "servizi" is (correctly) left as "servizi".

In my tests, I didn't see any difference between og:url and canonical. If using "servizi", then "servizi" is used in both cases - which is expected and the right thing to do.

I suspect the difference here is that only sh404SEF is touching the canonical, while other extensions can set the og:url, but I would need to look at it directly on your site to try understand why it happens only on your site.

Rgds

Monday, 10 April 2017 08:31 UTC

altrasoluzione

Hi, you are right!
I 've written wrong slash when typing my reply.
It was "servizi/" and not "/servizi".

Thank you very much.
Kind regards

Monday, 10 April 2017 12:45 UTC

wb_weeblr

Hi

Glad to hear that! Closing this ticket now, feel free to open a new one as needed. If you do so, please mention this ticket number in the new one.

If you created any superadmin account for us, be sure to delete or block it now to avoid unnecessary risk in the future.

Be sure to also check out wbAMP, our new Accelerated Mobiles pages plugin for Joomla - the next big thing is SEO, direct from Google themselves!

Rgds

This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.