schenke-io / laravel-url-cleaner
check and cleans url from seo or tracking data
Installs: 13
Dependents: 0
Suggesters: 0
Security: 0
Stars: 1
Watchers: 1
Forks: 0
Open Issues: 2
pkg:composer/schenke-io/laravel-url-cleaner
Requires
- php: ^8.3
- ext-curl: *
- ext-json: *
- ext-simplexml: *
- archtechx/enums: ^1.1
- guzzlehttp/guzzle: ^7.9
- spatie/laravel-package-tools: ^1.30
Requires (Dev)
- larastan/larastan: ^v3.9
- laravel/framework: ^12.40
- laravel/pint: ^1.27
- mockery/mockery: ^1.5
- orchestra/testbench: ^10.9
- pestphp/pest: ^4.0
- schenke-io/packaging-tools: ^0.2
- spatie/ray: ^1.40
This package is auto-updated.
Last update: 2026-02-19 19:21:04 UTC
README
Laravel URL cleaner - clean and concise
The Laravel URL Cleaner package sanitizes URLs by removing unnecessary SEO parameters, tracking information, and other clutter, ensuring clean and efficient URL handling in your Laravel applications.
To install just run:
composer require schenke-io/laravel-url-cleaner
Here a code example:
<?php use SchenkeIo\LaravelUrlCleaner\UrlCleaner; $shortUrl = (new UrlCleaner)->handle($longUrl);
Operation principle
The core UrlCleaner class iteratively applies a series of specialized
cleaner classes to a given URL. Each cleaner class performs a specific modification
to check and clean the URL for the following reasons:
- Reducing URL clutter: Removes unnecessary SEO parameters and tracking information.
- Improving data storage efficiency: Stores cleaner, more concise URLs.
- Enhancing performance: Optimizes URL processing and caching.
- Securing sensitive information: Prevents exposure of tracking parameters.
- Enhancing data analysis: Simplifies data analysis by removing noise from URLs.
This cleaner classes are highly extensible, allowing for customization and the creation of new modification types.
Config
A default configuration file can be installed and later modified, you can install it with:
php artisan url-cleaner:install
A typical result could be:
[
'cleaners' => [
MarketingBroad::class,
RemoveLongValues::class,
PreventInvalidHost::class
],
'max_length_value' => 40,
'masks' => ['dd3','vv67'],
'protected_keys' => ['search']
]
| key | type | description | cleaner |
|---|---|---|---|
| cleaners | array | list of cleaner classes applied to the given URL | any |
| max_length_value | int | values longer than this are removed by | RemoveLongValues |
| masks | array | additional masks to be used | RemoveConfigMasks |
| protected_keys | array | key names which are guard against removal | any |
| class name | # masks | description |
|---|---|---|
| Marketing00 | 68 | Marketing00 |
| Marketing01 | 106 | Marketing01 |
| Marketing02 | 43 | Marketing02 |
| Marketing03 | 170 | Marketing03 |
| Marketing04 | 111 | Marketing04 |
| MarketingBroad | 245 | MarketingBroad |
| MarketingNarrow | 333 | MarketingNarrow |
| MarketingUnique | 374 | MarketingUnique |
| PreventInvalidHost | - | PreventInvalidHost |
| PreventLocalhost | - | PreventLocalhost |
| PreventNonHttps | - | PreventNonHttps |
| PreventUserPassword | - | PreventUserPassword |
| RemoveConfigMasks | - | RemoveConfigMasks |
| RemoveLongValues | - | RemoveLongValues |
| RemoveSearch | - | RemoveSearch |
| ShortAmazonProductUrl | - | ShortAmazonProductUrl |
| SortParameters | - | SortParameters |
The use of masks
The core process of URL parameter removal utilizes specific masks.
| Description | Example mask |
|---|---|
| exact match of one query key on any domain | utm_campaign |
| match of some keys on any domain | utm_* *tm_* |
| exact match of one query key on one domain | utm_campaign@test.net |
| exact match of one query key on some domains | utm_campaign@test.* utm_campaign@*test.* |
| match of some keys on one domain | utm_*@test.net *x*@test.net |
| match of some keys on some domains | utm_*@test.* *x*@*test.* |
Some examples are outlined in the table below.
| Mask | URL 1 test.com/?a=1&b=2 |
URL 2 test.net/?a=1&abb=2 |
URL 3 test2.com/?a=1&b=2 |
|---|---|---|---|
| a | test.com/?b=2 | test.net/?abb=2 | test2.com/?b=2 |
| a* | test.com/?b=2 | test.net/ | test2.com/?b=2 |
| test.com@a | test.com/?b=2 | test.net/?a=1&abb=2 | test2.com/?a=1&b=2 |
| test.*@a | test.com/?b=2 | test.net/?abb=2 | test2.com/?a=1&b=2 |
Build your own cleaner by extending special classes
To extend the list of cleaners you can build your own
cleaners and put them in the config
file config/url-cleaner.php
The following cleaners are prepared to be extended for custom applications:
Prevent domain names
Extend PreventLocalhost and overwrite the $hostRegExes array with regular
expressions matching unwanted hostnames.
<?php use SchenkeIo\LaravelUrlCleaner\Cleaners\PreventLocalhost; class MyCleaner extends PreventLocalhost { protected array $hostRegExes = [ '/test\.com/', '/test\.net/', ]; }
Prevent schemes
Extend PreventNonHttps and overwrite the $allowedSchemes array with scheme
you allow to pass.
<?php use SchenkeIo\LaravelUrlCleaner\Cleaners\PreventNonHttps; class MyCleaner extends PreventNonHttps { protected array $allowedSchemes = [ 'https', 'http', 'sftp', ]; }
Use your own masks
Extend RemoveSearch and overwrite the $masks array with masks you want to exclude.
<?php use SchenkeIo\LaravelUrlCleaner\Cleaners\RemoveSearch; class MyCleaner extends RemoveSearch { protected array $masks = [ 'utm_*', 'test*', 'q@test.net' ]; }
Rewrite urls
Extend ShortAmazonProductUrl and overwrite the clean() method using
the class as an example.
<?php use SchenkeIo\LaravelUrlCleaner\Cleaners\ShortAmazonProductUrl; class MyCleaner extends ShortAmazonProductUrl { public function clean(UrlData &$urlData): void { // check if the hostname is right if (preg_match(/* regular expression */, $urlData->host)) { // check for the path to be replaced if (preg_match(/* regular expression */, $urlData->path, $matches)) { // your code $urlData->path = /* new path */; $urlData->fragment = ''; // clean if applicable $urlData->query = ''; // clean if applicable $urlData->parameter = []; // clean if applicable } } } }
AI Skills
| Title | Description |
|---|---|
| url-cleaner-development | Build and work with Laravel URL Cleaner features, including creating custom cleaners and managing URL sanitization logic. |
When to use
Use this skill when you need to:
- Extend the URL cleaning logic by creating new cleaner classes.
- Configure existing cleaners to handle specific URL parameters or tracking data.
- Integrate URL cleaning into Laravel applications using the provided Facade or Service Container.
- Troubleshoot or optimize the URL sanitization process.
Features
Creating Custom Cleaners
You can create new cleaners by extending the BaseCleaner class. Custom cleaners allow for domain-specific or parameter-specific logic that isn't covered by the default cleaners.
use SchenkeIo\LaravelUrlCleaner\Bases\BaseCleaner; use SchenkeIo\LaravelUrlCleaner\Data\UrlData; class MyCustomCleaner extends BaseCleaner { public function clean(UrlData &$urlData): void { // Custom logic to modify $urlData->query } }
Configuration-Driven Sanitization
The package is highly configurable. You can enable or disable cleaners, set maximum value lengths, and define protected keys that should never be removed.
Facade Support
The package provides a convenient UrlCleaner facade for easy integration and mocking in tests.
use SchenkeIo\LaravelUrlCleaner\Facades\UrlCleaner; $url = UrlCleaner::handle('https://example.com/?bad_param=1');
Markdown file generated by schenke-io/packaging-tools
