Welcome to the Q&A Forum

I have a client who has several locations for their business.

The company and the original location have one name - let's call it "National Clinic".  Then, they have a series of urgent care clinics, named with the structure "National Clinic Urgent Care:  Main St." and "National Clinic Urgent Care:  Central Plaza".   The

When I'm creating my directory listings, for the urgent care locations, which option would you use for the name?

a) National Clinic
b)  National Clinic Urgent Care
c)  National Clinic Urgent Care:  Main St.

If this were me (or my client), I would focus on claiming and taking over the Google Local page.  While that can be a complicated process, and communicating with Google can be slow, if you keep at it they will eventually help you get control of the page.   Can you share the Google page that is causing the issues?

Thanks.   I submitted a feature request:

https://seomoz.zendesk.com/entries/49105990-Make-email-address-an-optional-field-for-Moz-Local

Overall, I think a combination of all 4 of your ideas will help tremendously.

How about using a tagline to get the message across?    If the client is opposed to changing the official brand tagline, even an unofficial "Title tag tagline" would allow you to build on your title tag suggestion.   Such as:

page-name | World-wide Cheese | HCM

Another thought - is it possible to list multiple addresses around the world, or at least several around the U.S.?  Listing Sales offices or distribution centers would help send the right signals.

On the schema side of things, some possible helpers:

• http://schema.org/isicV4 if you have an SIC code that distinguishes you as more than a local business.
• http://schema.org/brand - identifying the geo term inside the brand tag seems like a good idea.
• Also, I'd avoid using any of the schema that are specific to http://schema.org/LocalBusiness, such as opening hours or payment

Thanks for your help.   While we are on the topic, any idea why it is required?   I'd love it if there was a "Moz Local Light" that submitted to only the sites that do not require an email.   That would be helpful for medical practices, as well as for any other business that prefers not to use (or at least publish) an email address.

I agree, they should.   But you  might be surprised at the number of medical practices that simply do not have a knowledgeable security advisor.

Agreed, this is precisely the option I recommend...    at the same time, I'm trying to be creative about alternatives.   In some cases, the issue is NOT keeping the email secure, as required by HIPAA, but the ability to respond in a timely fashion.   The autoresponder should handle this issue, but not all clients understand.

I work with medical practices, who due to HIPAA do not want to publish an email address in listings.

Would it cause a problem if I just submitted a non-working address (like noreply@client.com) that is not set up at all, so any email sent there would just bounce?

Obviously, one option is to use a HIPAA compliant email account, but there are other considerations (timeliness of responses related to clinical issues, for example) that make it less than ideal for a many medical practices to publish a public email address of any sort.

I'm interested in any options or solutions that could allow me to use Moz Local (which requires an email address) for businesses with HIPAA concerns.

Ira

In answering questions about the speed of MOZ Local, I've seen this a few times:

"The time it takes our partners to update the listing really depends on whether or not they have an API. If they do have an API, the listing will be updated pretty much immediately."

Can someone provide a list of which Partners have an API, and which do not?

Thanks for the answer...   just to clarify, we will definitely get rid of the duplicate content.   The question is if the individual location pages should be maindomain.com/location 1, maindomain.com/location2, etc., or if maindomain.com/locations should point to location1.com, location2.com, etc.

I'm taking over a site with multiple domains that are almost entirely duplicate content.  The business has a main site, then 5 different location sites with unique domain names, a slightly different homepage, then exact duplicate for the rest of the site.

Should I get rid of the individual location domains entirely, and just 301 redirect to pages on my main domain?  Or might it be worth keeping a unique microsite online at each of the location domains (with one general location page on the main url, then the location-specific info on the microsite)?

Currently, some of the location domains rank better than the main one, and in other areas the main one outranks the location domain.