• Home
  • Get help
  • Ask a question
Last post 25 min ago
Posts last week 81
Average response time last week 44 min
All time posts 70349
All time tickets 10858
All time avg. posts per day 20

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.

#9236 – Feature request: Pages sorting & Language filter

Posted in ‘4SEO’
This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Tuesday, 22 November 2022 08:12 UTC
Mediage

Hi,

We're using FaLang for translations on a J4 website and using 4SEO as our SEO component. However, we used to have some useful features in SH404SEF that we would love to retain in 4SEO:

1) Sort the Pages by url. Currently the sorting looks kind of random. Would be good to be able to sort the Page URL's by clicking the columns on top (so also for example by duplicates, Google Speed, etc.)

2) Filter by Language. In SH404SEF we would be able to filter a URL by its language. I imagine this now has become a little more difficult because of the way both systems work (scanning for URL's in stead of generating URL's), but this feature would be really useful. Maybe you could utilize the hreflang tag on the page to do this? That would also give us a good tool to find incorrect hreflang tags. :-)

Thanks for your help!

Kind regards,

Pieter

Tuesday, 22 November 2022 08:43 UTC
wb_weeblr

Hi

1) Sort the Pages by url. Currently the sorting looks kind of random. Would be good to be able to sort the Page URL's by clicking the columns on top (so also for example by duplicates, Google Speed, etc.)

4SEO is designed differently and sorting is indeed not the most important thing here:

- Ordering is done in 2 ways: alphabetical sort based on the URL itself or "Item" which means grouping URLs by their content (and then run an alphabetical sort). 

Item is the most interesting in terms of SEO as it groups first duplicates URLs. So if you have 5 URLs to the same articles, then they will be grouped together. And then the entire list is also sorted alphabetically. This IS sorting by duplicates.

Likewise, "Sorting by Google Speed" is not really a thing. There's no order in Google speed: you pass or your fail, but not page is "higher" or "lower" than another one. Which is why we don't sort by "Speed" (we could not do that anyway, there's no Speed score to sort) but instead have a filter for it: Show all or show failing URL.

2) Filter by Language.

That's a bit trickier and simpler at the same time. The way you would select URLs for a language is just by typing the language code in the search box: en/ or fr/

Of course, if you don't have a language code in the default language, then you won't be able to select that.

There's no issue with the data, we have the page language. 4SEO does not "just" scan for links. Once a link has been found, it is stored and later on, in the background, that page is loaded, it's content analyzed and stored. That's how duplicates are detected for instance.

Right now it's more a matter of priorities, and also a bit about user interface.

What's the reason to select URLs per language? what operation are you doing?

Best regards

Yannick Gaultier

weeblr.com / @weeblr

 

 
Tuesday, 22 November 2022 10:13 UTC
Mediage

Hi Yannick,

Thanks for your quick reply.

1) Regarding the sort: I missed that button! It was on Item appearantly, so it looked like a random sort. My bad!

2) We are a hotel marketing agency, so we create multi-lingual hotel websites. Usually they consist of 6 or more languages and also SEO is sometimes prioritized per language: when we see performance of a hotel website in one language is better than the other, we analyse and improve per language. Exactly for the reason you mentioned (default language without language tag) we would like to be able to select the language of the URL in stead of searching for nl/, en/, etc. (which is indeed a work-around that works for all non-default languages). When we have larger websites with many pages (40-50 for each language), it is quite annoying to do SEO for the default language.

Additional language-specific analysis (incorrect/inconsistent/missing hreflang, incorrect/missing x-default, etc.) could then also be added to 4SEO as a side-effect of adding this language-aware feature. We are currently using Screaming Frog SEO Spider, GSC and other tools to optimize this, but we'd rather have as much as possible in one place of course. :-)

Thanks again!

Tuesday, 22 November 2022 10:38 UTC
wb_weeblr

Hi

(which is indeed a work-around that works for all non-default languages)

I have added that to the list of requested features, maybe I can add something when the list of languages is not too long and it can be done with buttons.

Additional language-specific analysis (incorrect/inconsistent/missing hreflang, incorrect/missing x-default, etc.) could then also be added to 4SEO as a side-effect of adding this language-aware feature. 

Well, you can always use SEOInfo for that, it does the best job at analyzing and verifying hreflang. But verifying hreflang is very, complex and requires a lot of resources: you need to load all the pages linked (through the hreflang of the current page) to the current page and:

- check them for existence

- check that they don't have a canonical pointing at another URL

- check that the language code and language region are valid against the RFCs list

- check that they are not blocked by robots.txt or have a meta noindex

So in your case, to check the hreflang of one page, I have to load in the background 5 or 6 other pages, then parse their HTML to extract the hreflang links, any canonical, match against robots.txt, search for meta noindex.

That's what SEOInfo is doing, but only on one page at a time. 

Screaming Frog actually is not that thorough but even without doing all these checks, they have the advantage of running on your local, very powerful and not CPU-constrained by a hosting company, while 4SEO must run, often on a few $/month shared host.

We have a more basic version where we only do the initial test of having all related hreflang existing but that most basic test still requires loading all the related pages in the background, which is too much to ask.

And if you don't do that, then there's no point in just checking the hreflang syntax, that's not the problem really.

By the way, did not realize Falang was working on Joomla 4, is that recent?

Best regards

Yannick Gaultier

weeblr.com / @weeblr

 

 

 
Tuesday, 22 November 2022 11:22 UTC
wb_weeblr

Hi

Sometimes you don't have to wait too long: I made a change to the latest dev version to have a language filter on the Pages page.

You can download that version from the development versions download area  and just install over. I think it should work the same with Falang, although we do not support Falang officially (frankly, I did not expect it would make the cut to Joomla 4), it should still be ok.

The filter should only show if the site is multilingual (ie native Language Filter plugin is enabled) but I also have the code to detect Falang in there, at least the code that worked on Joomla 3, so maybe it'll work the same on Joomla 4.

Best regards

Yannick Gaultier

weeblr.com / @weeblr

 

 
Tuesday, 22 November 2022 12:16 UTC
Mediage

Great work, works like a charm! Even with FaLang. 

Yes, FaLang was rewritten to work with J4 luckily. Already for quite some time, I think about a year ago. In combination with SP Pagebuilder and SP Pagebuilder Translate (by Faboba) it works great, so much easier than the native J4 system. (which is pretty useless if you ask me!). Performance-wise (always the biggest critique on FaLang) it's no issue since we're caching all pages anyway. Maybe for  other more dynamic sites this is more of an issue than for us.

Thanks for your super quick responses & resolving of the issue! I will give SEOInfo a look as well, thanks for the tip!

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.