Скачать или смотреть How to Create SEO-Friendly URLs with .htaccess for Your PHP Pages

Learn how to craft SEO-friendly URLs in your PHP web application using the `.htaccess` file. This guide will help you convert complex paths into user-friendly links, enhancing your site's visibility.
---
This video is based on the question https://stackoverflow.com/q/64445748/ asked by the user 'lewandowsky91515' ( https://stackoverflow.com/u/8006742/ ) and on the answer https://stackoverflow.com/a/64447962/ provided by the user 'anubhava' ( https://stackoverflow.com/u/548225/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: htaccess rewrite rule /en/support/my-tickets/ to my-tickets.php page

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Crafting SEO-Friendly URLs in PHP with .htaccess

In the world of web development, creating SEO-friendly URLs is essential for both user experience and search engine optimization. If you find yourself struggling with URL rewriting in your .htaccess file, you're not alone. In this post, we will tackle a specific challenge: redirecting a given path in your application to the corresponding PHP page while keeping your URLs clean and user-friendly.

The Problem

You aim to rewrite URLs in your application hosted in the same root folder, such that they resemble the following:

/en/support/new-ticket/

/en/support/all-tickets/

Currently, you're encountering an issue where you're redirected to support.php rather than the intended pages. This underscores the need for a correct .htaccess rule to ensure your rewriting logic points to the appropriate PHP files.

Current Structure

Your application's directory includes:

css/ (folder)

js/ (folder)

includes/ (folder with vocabularies and config.php file)

index.php

support.php

new-ticket.php

all-tickets.php

my-profile.php

You already have working rules for simpler URLs, such as /en/ leading to index.php?lang=en, but the rules for deeper paths are causing confusion.

The Solution

To fix the issue, we need to adjust your .htaccess rules. Here's a breakdown of the ideal rule for handling requests to specific support paths and ensuring they route correctly to the PHP files.

Updating the Rewrite Rule

Your existing rule for handling support pages needs to be revised. Here’s the corrected version you should implement:

[[See Video to Reveal this Text or Code Snippet]]

Explanation of the Rule

RewriteCond %{REQUEST_FILENAME} !-f: This condition checks to ensure that the requested file does not already exist. If it does, the rewrite does not occur, preventing unnecessary processing.

RewriteRule ^([A-Z]{2})/support/([\w-]+ )/?$: This part of the rule captures the language code (e.g., en, fr) and the specific support page you want to access (like new-ticket or all-tickets). The regex matches any lower or upper case letter combination followed by /support/, and it allows for word characters and hyphens ([\w-]).

$2.php?lang=$1: This tells the server to redirect the request to the appropriate PHP file based on the page you want ($2) while also passing the language code ($1) as a query parameter.

Full Example of the .htaccess Code

Incorporating this new rule, your complete .htaccess file might look like this:

[[See Video to Reveal this Text or Code Snippet]]

Conclusion

Creating SEO-friendly URLs through proper use of the .htaccess file simplifies your user's experience and enhances your site's search presence. By implementing the revised rule, you can now successfully navigate to your desired support pages without encountering unwanted redirects.

Feel free to adjust the paths or rules further based on your specific project needs. Happy coding!