\n no action required from the current users of the tool.\n<\/p>\n
![\"Screenshot](\"https:\/\/alienroad.com\/wp-content\/uploads\/kb-gorsel\/g-8833e210288a.png\")
\n When the URL Parameters tool launched in \n Over the years, Google became much better at guessing which parameters are useful on a site and \n Going forward you don’t need to do anything to specify the function of URL parameters on your \n If you need more control, you can use \n If you have questions or comments, you can catch us on
\n 2009<\/a> in Search Console’s
\n predecessor, Webmaster Tools, the internet was a much wilder place than it is today.
\n SessionID<\/code> parameters were very common, CMSes had trouble organizing parameters, and
\n browsers often broke links. With the URL Parameters tool, site owners had granular control over
\n how Google crawled their site by specifying how certain parameters affect the content on their
\n site.\n<\/p>\n
\n which are —plainly put— useless. In fact, only about 1% of the parameter
\n configurations currently specified in the URL Parameters tool are useful for crawling. Due to the
\n low value of the tool both for Google and Search Console users, we’re deprecating the URL
\n Parameters tool in 1 month.\n<\/p>\n
\n site, Google’s crawlers will learn how to deal with URL parameters automatically.\n<\/p>\n
\n robots.txt rules<\/a> (for example, you can specify
\n parameter orders in an allow<\/code> rule) or use
\n hreflang<\/code><\/a> to specify
\n language variations of content.\n<\/p>\n
\n Twitter<\/a>.\n<\/p>\n