Service name differs from our URL

[TheaterMania]

Hi there, we are launching a theater tickets membership service in the New England area.

We've named our site the New England Theater Club everywhere: site header, footer, FAQ, email correspondence, logos, you name it.

The URL, however, will read http://boston.theaterclub.com.

It'd be a fair amount of technical work to instead use newengland.theaterclub.com (and a nonstarter to use a subdirectory e.g. theaterclub.com/newengland, but that's for another post).

My question is - what would the upside be if we invested the resources to change the URL name to newengland.theaterclub.com?

[Linda-Vassily]

Can you have newengland.theaterclub.com redirect to boston.theaterclub.com? Or at least no one else is going to use newengland.theaterclub?

Those urls are long enough that no one is likely to be just typing them in, so that's probably not your biggest hurdle. And most people searching for theater tickets in New England will be looking more specifically [I live in New England] and Boston is likely your biggest target anyway.

So, ideally your url should match your other naming, but in this context I wouldn't make changing it your first priority. [I mean the Foxborough Patriots are managing to get by using a more general name...]