Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
"The url 'http://mysupport.dk' could not be resolved. Correct the error or leave it for now when the production domain isn't live yet."
But it says in your documentation that's how im suppose to use it.
Don't worry about this error, it's more of a warning but as long as the domain is ok, you can ignore the error.
Quality Umbraco packages | http://www.soetemansoftware.nl
Well it didnt work. Don't know if i've set it up the correct way.
The content node for the root of the site has 2 domains attachted to it: "www.mysupport.dk" and "mysupport.dk" - on the ISS I have all the misspelled domains directing to this umbraco solution. With the forced www-prefix set to true, shouldnt it "catch-all" requests where the http-host is not on any content node and redirect them to the main domain?
I should say that im running multiple domains on this umbraco instance.
Futher more, how does it know what domain to redirect a request to? Say for each site i have on this umb instance i have multiple "miss-spelled"-domains that i want to redirect permanently to my main domains. Can I set that up with SEO Checker or do I have to write all of these rewrite rules in the config-files of .NET and Umbraco?
Ah now I understand,
It will not redirect domains, not for canonical and also not for miss-spelled domains, you should configure that using Url rewriting in IIS. what the canonical domain feature does is generate a canonical domain with the correct domain name when you use the SEOChecker library to generate the meta tags.
Okay I might have missunderstood the functionality of the "canonical domain".
is working on a reply...
Write your reply to:
Image will be uploaded when post is submitted