Hi Jan

These links are from using the old  Url linking control in the Html editor, which creates these linkclick urls.  The link click url works by doing a 302 redirect to the correct Url (which is determined by the 'tabid' parameter.

The good news is that this is easily fixed, because all these links are internal to your site, so you have control.

The bad news is that there is no other way to do it then to go through your site Html page by page and identify and fix these links by removing the 'linkclick' url and replacing with an actual link  - which means finding /linkclick.aspx?link=xx etc and replacing with actual links like /customerservice.aspx.

Until you do this, you'll keep the internal 302 redirects and your internal linking will not provide as much SEO benefit as it could.

You can see the extent of your issue by doing a search in google like this : site:www.anteater.com.au/LinkClick.aspx?link=192&tabid=238&mid=620

While you're at it, you should also consider the Urls of the pages you have on your site and how you can best match them to what your customers might be searching for.

Jan - I'm not sure what version the linking control switched over.  It might be prior to 5.x, I don't recall exactly when it changed. 
If you have 5.5 I doubt you have this version now, but you can check by inserting a link using your Html editor, and see whether it takes the full page name format (ie example.com/pagename.aspx) or if it inserts a 'linkclick.aspx?tabid=xx' style Url. 

The linkclick Urls are also created if someone ticks the 'track clicks to this link', which is an option in some versions, and also on things like the annoucnements model.  There is no real reason to use this value because your analytics package should be tracking the details anyway. 

So as long as you have your DNN version setup (and you might want to look into switching to the Telerik html editor if you arent' already - google this for guidance) and you are not ticking 'track clicks' for the links, then you should no longer be having the issue.  At this point it's just a case of going back and finding and replacing all the old versions.  I think Mitchel Sellers might have created a find/replace tool for text/html module content, but I didn't look into it myself.