When WCF svc web services hosted in IIS, the links within WSDL for xsd schemaLocations uses local machine name, the will cause issues when 3rd parties try to obtain the complete WSDL reference from the server unless they modify the main WSDL file to change those schemaLocations links to use domain name for the xsd:import. (An example of IIS hosted services can be found in my previous blog entry WCF SOAP, JSON, POX Coexists if interested).

To use domain name e.g. http://www.example.com/yourService.svc?wsdl across your WSDL references,
firstly, you need to find out the website id of your IIS website that hosting the WCF web services. Run this VBS script to find out the id, ListWebSiteId.vbs Thanks to Chris Crowe’s blog

Once you get the id of the hosting website in IIS, you can open command prompt a.k.a. cmd and run ( run it as in one line!) command below to display all the properties of the website.

Lastly, restart the IIS by running iisreset in the same command prompt

iisreset

To test, browse your http(s)//www.example.com/yourService.svc and see if the WSDL link uses domain name www.example.com that you defined above, and
check out if xsd:import schemaLocations uses the same domain name to link the XSDs.