• 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.

#9060 – Setting redirects

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.
Wednesday, 21 September 2022 22:54 UTC
wirecreative

I'm getting used to 4SEO after installing it on a few sites. The new redirect rules feature is much more cumbersome than it used to be in sh404SEF.

Let's say I want to redirect the following:
/contact.php
/contact-us
/contact-us.html
/about/contact

to:
/contact

In 4SEO I have to manually create 4 separate rules, each one a 3-step process. Whereas before I could simply paste those 4 URLs into the Aliases tab of the /contact URL.

Is there a way to add an Aliases tab to a page in 4SEO for a more streamlined process? Or, at least be able to enter multiple aliases in one rule? If I could just have one rule for /contact page and include all of those aliases in it, that would be more efficient.

Thanks.

 

 
Thursday, 22 September 2022 10:04 UTC
wb_weeblr

Hi

Thanks for your feedback and request, this is actually an interesting topic and I'm surprised nobody ever came back to me with this. 

Indeed 4SEO design was done around "rules", which are a powerful way to do many different things on the site, with one simple interface, the same in all cases (redirects, canonical, structured data, sitemap exclusion, raw content).

In the case of redirects, my ideas were/are:

- Adding a single redirect is simpler: the concept of going to the target URL and add aliases there is a bit foreign to most people. Entering first the source and then the target makes more sense to most people

- for more complex use case, generic rules will be used. For instance, in your case, you could have one  rule from /contact{*} to /contact , and you'll just need another one for /about/contact

BUT I do agree for multiple one to one redirects, this is more cumbersome. So your message got me thinking about how that can be improved and I think having multiple URLs were the rules run is likely the way to go:

Instead of "Run on this/these page(s)" being a single line input, we could enter multiple lines here and the changes to accomodate that should be acceptable. There are 2 caveats at the moment:

- there may be a significant impact on performance. Or not, I neede to evaluate that

- in any case, if multiple lines are entered, each line cannot have wildcard (ie {*} or {?}). If you use wildcards, there can only be one line (restriction may be lifted in the future but for now, it would be too complex to handle that case)

So I'll try and do some prototype of this and see how that goes, and will get back to you.

Best regards

Yannick Gaultier

weeblr.com / @weeblr

 

 

 
Thursday, 22 September 2022 14:39 UTC
wb_weeblr

Hi

So it took a bit more time than expected, as usual, but I have added something that will certainly help you - and others ;) in that particular use case. 

The "Run for this/these pages" field is now a multiline field rather than a single line. You can therefore enter multiple lines to have a redirect - or any other rule type really, be ran on:

There's a restriction when using multiple URLs: they all have to be "simple", meaning you cannot use wildcards characters either in the source URLs, or the target URL when multiple lines are present.

You can download the latest development version from the development versions download area and test to be sure it works for you.

Best regards

Yannick Gaultier

weeblr.com / @weeblr

 

 

 
Thursday, 22 September 2022 18:12 UTC
wirecreative

That looks great. I'll try it out in the next day or two. Thanks!

 
Thursday, 22 September 2022 18:18 UTC
wb_weeblr

Hi,

You're welcome! I will leave this ticket open in case you need to add something. It will automatically close in 2 weeks if no further comment is made.

Best regards

Yannick Gaultier

weeblr.com / @weeblr

 

 
Sunday, 23 October 2022 05:34 UTC
system
This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.
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.