GET parameters create the same content at many URLs \u2014 tracking tags, filters, session identifiers \u2014 and Yandex may treat the results as duplicates. This tool tells the robot which parameterised URLs to crawl and index and which to ignore, which reduces crawl load and makes the intended page the one that appears.<\/p>\n
Under Indexing \u2192 Configure GET parameters, the console lists every parameter the robot has found on the site. You can add your own; you can delete parameters you added, but not<\/strong> ones the robot discovered. Each parameter gets a value in the “Consider the parameter?” column:<\/p>\n For manually added parameters you can also scope the rule: all pages, the home page only, or a specific section. Changes take effect within a week.<\/p>\n The same behaviour can be configured in Analytics and campaign tags ( Yandex exposes this as an explicit control, whereas Google leaves you inferring from canonical tags and hoping. Being able to see the full list of parameters the robot has actually encountered is itself an audit: parameters nobody on the team recognises usually mean a tracking integration or a filter generating URLs nobody planned.<\/p>\n","protected":false},"excerpt":{"rendered":" GET parameters create the same content at many URLs \u2014 tracking tags, filters, session identifiers \u2014 and Yandex may treat the results as duplicates. This tool tells the robot which parameterised URLs to crawl and index and which to ignore, which reduces crawl load and makes the intended page the one that appears. How the […]<\/p>\n","protected":false},"menu_order":40,"template":"","meta":{"footnotes":""},"ar_ykb_kategori":[758],"ar_ykb_etiket":[],"class_list":["post-28464","ar_ykb","type-ar_ykb","status-publish","has-post-thumbnail","hentry","ar_ykb_kategori-indexing"],"_links":{"self":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_ykb\/28464","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_ykb"}],"about":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/types\/ar_ykb"}],"version-history":[{"count":2,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_ykb\/28464\/revisions"}],"predecessor-version":[{"id":29055,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_ykb\/28464\/revisions\/29055"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media\/28846"}],"wp:attachment":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media?parent=28464"}],"wp:term":[{"taxonomy":"ar_ykb_kategori","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_ykb_kategori?post=28464"},{"taxonomy":"ar_ykb_etiket","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_ykb_etiket?post=28464"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
The conflict rule, which is the important part<\/h2>\n
robots.txt<\/code> with Clean-param<\/code>. When the console and the file disagree, Yandex applies the rule that prevents indexing<\/strong>. The strictest setting wins, not the most recent. So a site with a forgotten Clean-param<\/code> line cannot re-enable those URLs from the interface \u2014 the file has to be edited. Anyone debugging “I set it to Yes and nothing happened” is looking at this.<\/p>\nWhat to mark as not considered<\/h2>\n
utm_*<\/code>, click identifiers), session identifiers, sort order, and view-mode switches \u2014 anything that changes presentation or tracking rather than content. What to leave alone: parameters that genuinely select different content, such as a category or a product variant that should rank on its own.<\/p>\nWhy this matters more on Yandex<\/h2>\n