I am setting up a website for a client that I will be hosting and maintaining, and I am trying to determine what will be the most pain free setup. My thought is to do the following:
- Set up the clients domain at
client.mydomain.com - Have the client update their DNS records for
*.client.comto CNAMEclient.mydomain.com
From a practical perspective, this feels best for me because then I don't have to maintain access to their DNS control panel especially if they want to do other things with it. Furthermore, if I decide I need to move the website to a different host, I can do it seamlessly without their even knowing just by updating where client.mydomain.com points.
This being said, my concern is that I will affect the SEO for client.com. If I impact SEO at all, I will just go with the A-Record route and call it good, but if there is no impact, the CNAME route seems nicer to me.
Thoughts?
(As an aside, I do have Google Maps included in this app, and the API key is yelling at me when I hit the app from a different tld... client.mydomain.com and client.com. Is there a way to ask for a single google API key that can work with CNAME'd domains? I can work this out in code, but didn't know if there was a simpler solution.)
Using a CNAME does not impact search engine ranking. It is common practice to use a CNAME. A classic way of setting up DNS is to have (servernames).company.com and then create (servicenames).company.com as CNAME's pointing to server names (where service names are fx "www").
If your DNS setup is particularly convoluted and it takes a looong time to resolve your DNS hostnames, then you could maybe rank a little lower with services like Google Adwords. Adwords takes the site 'quality' into account, and speed is a part of this. Generally DNS lookups are quick, so I think this is highly unlikely to be an issue.