The post address of the Google search results is different from the actual one

[sebastiangreger]

The most recent version of the Retour plugin requires Kirby 3.6.1+ – updating your Kirby version is always a good idea to stay up-to-date, but there might of course be breaking changes between major versions. 3.6.3.1 is the most current Kirby version from three days ago.

If you can’t update to a version that supports Retour at this point, there are some alternative options. The plugin kirby3-redirects seems to work for Kirby 3.5+:

Kirby3 Redirects - setup HTTP status code redirects from within the panel

I am creating posts for my plugins to make it easier to find them using the forum search and not just the docs search. Kirby 3 Redirects can handle Request-URIs like projects?id=123 , project/cool.html and send Response-URIs like https://exter.nal . This makes it the ideal choice when porting a non Kirby project (like wordpress). You can assign HTTP Status Codes like 302 to each redirect individually. site/blueprints/site.yml sections: # ...other sections redirects: extends: plugi…

…or you could try this solution, which does not provide a Panel UI as the plugins do, but instead the redirection rules are stored in a JSON file:

A minimalist redirect solution that intercepts 404 errors

Sharing this in case it is of value to somebody else, but also because I am curious did I overlook something – almost feels a bit too simple to be true? Pointers to possible issues and improvement suggestions are of course most welcome. I was looking for the most simple solution to intercept 404 errors and redirect some of them to alternative URLs instead. My website is almost 17 years old and has accrued dozens of odd forwarding rules as its blog’s URL structure has changed over ti…

You could also deal with the redirects directly in your server configuration (the .htaccess file on Apache, or the.conf files in Nginx).