How to Use the WordPress Hosting Kinsta the Feature of binding redirect

How to Use the WordPress Hosting Kinsta the Feature of binding redirect

Now you can add rules to redirect from your panel MyKinsta! Redirect to perfection the rules allow you to direct traffic from one location to another. It is especially useful to avoid errors 404, ensuring proper SEO when you make changes and the placement of the visitors to the correct locations on your site.

Free use of WordPress plugins to implement redirects can sometimes cause performance problems since most of them use the function wp_redirect, which requires the execution of code and additional resources. Some of them also add to automatically upload data to the table wp_options, which increases the oversizing of the database. By adding them in MyKinsta means that the rules are applied at the server level, which is much more optimal. Just follow the following steps on how to add them.

How to add a Redirect rule

Using Regex

How to bulk import rules to redirect

How to export redirects

How to add a Redirect rule

Step 1

Add a redirection, click on your site in MyKinsta and go to "redirect". Then click on "Add Redirect rule".
Add Redirect rule
Rules to redirect

Step 2

You can then choose the type of rule you want to redirect. Take a look at this article about the redirection to learn more about what type of rule you should use. The tool Kinsta makes use and support Regex expressions.

301: Redirection is used for URLs and content that is "Moved Permanently". Typically, this is the one that you want to use for the purpose of SEO.

302: is used to redirect URLs and content that is "found" or "temporarily moved".
In this example, we can then add a redirect 301 for a blog URL that was amended and updated to something else. This ensures that all traffic, backlinks, and link juice of Google is now sent to the new URL. 301 redirects to spend between 90-99% of link juice. You can select the prefix of the domain that you want to be added. In this case, we want both www and non-www to redirect traffic.

Add 301 redirection
Add 301 redirection
Note: This will automatically redirect the UTM parameters or nothing at the end of the URL. For example, if the URL Antigua is shared on social media using a tool like Buffer, might appear as
follows:

Https://wpdev.ink/blogpost/?utm_content=buffer

This will automatically be directed to:

Https://wpdev.ink/newblogpost?utm_content=buffer

You will also notice that we add ^ in the "previous" URL Redirection. This is because it uses the tool of the regex Kinsta Redirection automatically. Therefore, you must add ^ at the beginning of each "of" the path unless you want to match in other places that the start of the route. For example, using just /posts by if I could create a loop of redirection to another URL, such as /category/posts.
It is also important to revise its current reverse in a tool such as Ahrefs. For example, you could have backlinks on third-party sites that they point to two different versions of your URL:

Https://wpdev.ink/BLOGPOST

Note that the second has a progress bar on the end of it. If you do not take this into consideration, it could break the redirect. Therefore, if you are not sure which version to third-party sites are linking, you can always use a regex command wildcard (?) in place to make sure they work. See the following

example:

Wildcard redirect
Wildcard redirect
In the above example, all links to both /posts and /posts/ (with the backslash) would get redirected to /new blog post. Then you can easily manage all its rules to redirect from the board.

Using Regex

A regular expression is a sequence of characters that define a search pattern. Below are some additional examples that can be used with the tool MyKinsta redirect. The "redirect" field supports regular expressions and the "redirect" field allows you to capture group references and some variables (e.g. $HOST, $scheme).

Here are some important things to keep in mind:


Redirects are checked in the order in which they are added. The best practice is to have the most specific before the Assembly redirects.
By default, the tool Kinsta redirect is case sensitive (see below for use case-insensitive redirection).
Restricted characters: #, space, and linebreak characters.
You can not redirect via arguments.

Here is an uncommon regex syntax:


  • ^ - only if the next party is at the beginning of the line.
  • $ - only if the previous party at the end of the line
  • ? - Match the previous 0 or 1 times (this is optional).
  • . - Matches any single character
  • * - Agree with the previous 0 times or more
  • \ - Escape special characters
  • (?I) - case-insensitive
  • .* - The wildcard to match anything (any character at any time that will match any string)
  • (*) - Capture group that contains a wildcard match for any string in the given place


 Examples of regular expressions

Include your page https://domain.com/store
^/store
Include your https://domain.com/store (with case-insensitive redirection)
(?I)^/store
Include only a single file, such as https://domain.com/store.php:
^/store\.php
Include all files of the same type, such as all PHP files.
^/store/.*\.php

Include everything that contains a particular phrase, such as https://domain.com/*store*
It is recommended that you specify the string of redirection "/" in order to reduce the likelihood that redirect something unwanted. Note: from the Tool Kinsta automatically applies the regex, .* are applied automatically and are not necessary in this case.

/Store or /store/
Include both of the following URL: https://and Https://mydomain.com/fast-car-racing mydomain.com/fast-racing
^/fast( racing cars?

Here is another example of the Kinsta article on disabling Google AMP. We needed to redirect all blog posts containing /a/ to its original non-AMP URL to make sure they have re-indexed to your original URL. In other words, we can throw everything before /a/ in the URI and append-only instead of "$1".
^/(.*)//AMP

Redirect traffic to www non-www (and vice versa)
Add a redirect for all traffic 301 www to non-www.
Www.mydomain.com - ^(.*)$ - https://mydomain.com$1

Too many redirects

If you set up you're redirected incorrectly, you may cause an infinite redirect loop, in which case you would see it as an error ERR_TOO_MANY_redirects. If this is the case, you will want to go back through their rules to redirect and check. This happens when the URL location is included in both "Redirect from" and "Misdirection".

For example, the following could lead to a redirection loop:

Redirect from: ^/blog/About Redirect to https://domain.com/blog/about-me
Why? Because once the process went ^/blog/on, the remaining part of the "I don't care, and that would cause an infinite loop. You have to specify the end of the string and the starting point. Here is what you need to do to correct this:

Redirect from: ^/blog/about$ https://domain.com/blog/about-me Redirect to:
The $ character tell Nginx to stop and to match the request only if the string is there exactly, but anything after it.

Continue Reading Regex

Here are some useful links to read more about what you can do with regex, and description of the basic concepts:

Regexone.com
Regular-Expressions.info
Regex101.Com
Regexpal.com

How to bulk import rules to redirect


Perhaps you have a more complex configuration or want to get rid of your 301 Redirection plugin on your WordPress site. We also have the option to redirect the rules of mass import from a CSV file.

Step 1

To add bulk import redirection click your site in MyKinsta and go to "redirect". Then click "Import in bulk".
Add Redirect rule
Rules to redirect

Step 2

Paste the contents of a CSV file in the field. The CSV file must contain information separated by commas in this order: the status code, domain (for all domains), route and redirect to the URL. Each rule to redirect should be placed on a new line. Then click "Import" redirects.

Massive elimination of rules to redirect is also supported.

How to export redirects


We realize that some of you have hundreds or even thousands of redirects. Have the ability to export them facilitates offline editing and re-import, as well as the ability to easily transfer redirects to another tool or service as needed. Here is where the "Export to CSV" option comes in handy.

Export redirects from WordPress

If you want to migrate your current redirects from a WordPress plugin for MyKinsta, many of them have export options available in your configuration (the Export option example below the EPS redirects the plugin). Just make sure that is formatted properly before the bulk import.

 Export redirects

EPS plugin redirects from export
If you are using the Simple 301 redirects the plugin you can use this simple export to CSV 301 redirects plugin.

Notes

For more complex redirects you may need to open a support ticket. Since it is not running Apache, you cannot use .htaccess files. In contrast, we run NGINX that has its own rewrite rule of syntax; what can be done with .htaccess can "translate" to the syntax of nginx and add to your site of nginx config.

Show Popular Posts

Best Software to share your Affiliate links to others Website: Number one way to sell your products and share your affiliate links!

Hindu baby names wonder full collection , are you searching baby names in Tamil.

Commercial - JZP RANKREEL by ABHI DWIVEDI Comment: A breakthrough all-in-one CLOUD APP THAT PUTS THEIR VIDEOS IN FRONT OF THOUSANDS OF PREMISES AND CUSTOMERS ONLINE FOR FREE and without advertising or know anything about SEO.