Occasionally we come across clients who only want to use the IDX feed of our platform. While this is a fringe case, it happens from time to time.
This is also something that we do not recommend, when possible. In order for a client to receive full functionality of the Real Geeks Platform, it is highly recommended that they use our nameservers. When not using our nameservers, they lose access to features such as the Drip/Workflow system.
IF they still insist on not using our nameservers and want to use their own site, here is how to take these types of clients live:
1. Instead of pointing their domain to our nameservers, the client must create a CNAME record that points to a subdomain for our IDX feed. e.g. - "search.domainhere.com". They should have the value of this CNAME record be "ssl.realgeeks.com".
2. Once the CNAME is created, confirm it is in AWS. (This may be not appear until after the subdomain has gone live)
3. In MCP change the site domain and site name to "search.domainhere.com", the email from and email updates from to "search.domainhere". Save.
4. In MCP home, search for "search.domainhere.com" and then select "Syncdns ssl" to take it live.
5. Wait a few minutes (sometimes a little longer) for the sync to propagate, confirm the website is live, and done!
Side note:
Some sites may not be SSL (https) and would then need to have the CNAME value of "hosted.realgeeks.com" added, instead of "ssl.realgeeks.com". However, "http" is not really a good option, since Google tends to take action against non-SSL sites. Getting the site to be SSL should be recommended. To be sure if the client's site is SSL or not, you can go to "domainhere.com" and check to see if it says "https" in the URL.