Tuesday, March 26, 2019<\/p>\n
\n Sometimes a web page can be reached by using more than one URL. In such cases, Google tries to
\n determine the best URL to display in search and to use in other ways. We call this the
\n “canonical URL.” There are ways site owners can help us better determine what should be the
\n canonical URLs for their content.\n<\/p>\n
\n If you suspect we’ve not selected the best canonical URL for your content, you can check by \n Please be aware that if you search using the \n We’ve also changed URL Inspection tool so that it will display any Google-selected canonical for a
\n entering your page’s address into the
\n URL Inspection tool<\/a>
\n within
\n Search Console<\/a>. It
\n will show you the
\n Google-selected canonical<\/a>.
\n If you believe there’s a better canonical that should be used, follow the steps on our
\n duplicate URLs<\/a> help page
\n on how to suggest a preferred choice for consideration.\n<\/p>\nsite:<\/code> o inurl:<\/code> commands,
\n you will be shown the domain you specified in those, even if these aren’t the Google-selected
\n canonical. This happens because we’re fulfilling the exact request entered. Behind-the-scenes, we
\n still use the Google-selected canonical, including for when people see pages without using the
\n site:<\/code> o inurl:<\/code> commands.\n<\/p>\n
\n URL, not just those for properties you manage in Search Console. With this change, we’re also
\n retiring the info:<\/code> command. This was an alternative way of discovering canonicals. It
\n was relatively underused, and URL Inspection tool provides a more comprehensive solution to help
\n publishers with URLs.\n<\/p>\n