Redirect parameter to its parent post url

Question

i have several set of error URL with parameter that i need to redirect to the parent post URL

    http://www.mysite.co/post1.html?amp=1
    http://www.mysite.co/post1.html?amp=0
    http://www.mysite.co/post1.html?utm_source=xxxxx

so what im trying to achieve http://www.mysite.co/post1.html?amp=1 (status 404 ) should redirect to http://www.mysite.co/post1.html (200 ok)

i tried to add htaccess code but it always gave me 500 errors, can someone help me with the proper htaccess code

Htacess

    # BEGIN WordPress
    # The directives (lines) between "BEGIN WordPress" and "END                 
    
    RewriteEngine On
    RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
    RewriteBase /
    RewriteRule ^index\.php$ - [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    

    # END WordPress

current permalinks are set to

/%postname%.html

Parameter in url ?amp, ?utm_source are added by third party service/plugins which resulted 404 error

user_369434 · Answer

Try the following at the top of the .htaccess file, before the # BEGIN WordPress section:

RewriteCond %{QUERY_STRING} ^(amp=[01]|utm_source=[^&]+)$
RewriteRule ^[\w-]\.html$ /$0 [QSD,R=301,L]

This matches any URL-path that ends in .html. Only the specific query strings as mentioned in the question are matched. ie. amp=0 or amp=1 or utm_source=. It will not redirect amp=2 or utm_source= or utm_source=&foo=1 etc.

The QSD flag (Apache 2.4) discards the original query string.

Test first with 302 (temporary) redirects to avoid potential caching issues.

UPDATE:

#REDIRECTION UTM CLEAR

RewriteEngine On
RewriteBase /
RewriteCond %{QUERY_STRING} "utm" [NC]
RewriteRule (.*) /$1? [R=301,L,QSD]

which one you thing serves better?

What do you mean by "better"?

As written, this code is strictly invalid (and contains superfluous directives). But (when corrected) this code arguably matches too much (and does not handle the amp URL parameter at all). It matches utm anywhere in the query string which could potentially create conflicts with existing code. It also matches any URL-path, so is potentially checking 1000s of requests that don't need checking. eg. It would match /image.jpg?nutmeg=5 and /?scoutmaster=1 - which clearly have nothing to do with utm tracking parameters (which all start utm_).

The code I posted above matches precisely the criteria you've stated in the question. And thus avoids potential conflicts. So, from that perspective, the code I posted above is "better".

However, to match amp or any URL parameter that simply starts utm_ and only whole URL parameters that might occur anywhere in the query string then use something like the following instead:

RewriteCond %{QUERY_STRING} (?:^|&)(amp|utm_\w+)=
RewriteRule ^[\w-]\.html$ /$0 [QSD,R=301,L]

This matches URLs of the form /%postname%.html - your permalink structure. It does not match /image.jpg etc.

You do not need to repeat the RewriteEngine directive. The RewriteBase directive is entirely superfluous. You should not wrap these directives in a container.

Note that if you have any legitimate URL parameters mixed in then they will also be removed.

This matches the following:

/.html?amp=
/.html?utm_source=
/.html?utm_campaign=&bar=1
/.html?foo=1&utm_=
etc.

But does not match:

/.html?wamp=
/.html?nutmeg_source=
/image.jpg?utm_source=
etc.

Redirect parameter to its parent post url

1 Answers