Welcome to the Q&A Forum

Face palm ;).  Thanks, Oleg.

The crawler isn't blocked; we checked that first.  According to SEOmoz and Ahrefs, there's zero backlinks, but it does have some social shares.

A website was built and launched eight months ago, and their domain authority is 1.  When a site has been live for a while and has such a low DA, what's causing it?

Thanks for the insight!

Do you both know, on average, how much it matters, when it matters and how extensive should the ordering get?

We do a lot of local SEO, and we're wondering if it's better to target "keyword location" or "location keyword"?

Does it affect ranking and keyword difficulty if we're trying to rank for "plumbing appleton" or "appleton plumbing"?

Any insight would be great.

We have a client who wants to rank locally, nationally and internationally for their products.

I wrote a line that goes, "We can ship our products to you whether you’re here in Illinois, nationwide, or international."

I added that line after a paragraph or two of unique product description on each of their 30-odd product pages.  Will this damage their ranking?

I tried researching this but only found full page duplicate content topics.  Any advice would be great.

Thanks Miriam!  That was very helpful.

We're having trouble finding reliable traffic numbers for long-tail local keywords (ex. - "computer repair green bay").  We tried using Google Insights but it doesn't display long-tail keyword information, only broad keyword keywords searched for in a certain locale.

We also tried using Wordtracker, but that hasn't been too reliable either.

Is there a single tool that provides real traffic for local long-tail keywords?

Traditional Share of Voice (SOV) used to be calculated by how much your industry on the whole spent on marketing and how much you're spending on marketing.

But how do you calculate SOV for the web with different page rankings for multiple keywords, social mentions, and so on?

Anyone have any ideas?

First, we would love to use the new Google Experiements intergrated into analytics but its not rolled out to us.  We tried to get it expideted roll out to us but no luck...

So we are stuck with a soon to be discontinued Website optimzer.  I can't get past the first step however, I get the follow error: "The original page and the conversion page URLs must share the same domain.", see attached.

The convertoin page is on a subdomain.  There is quite a bit of help online about this.  You need to tweak the script code.  There is nothing about how to get past this page though.  It simply says its a on a different domain (which its not) and won't let me go any further...

Thanks!

Website%20Optimizer.jpg

The focus below is mainly on the domain name, what about the actual business name?  Think this would be equally (or more important) from an SEO standpoint as it would appear multiple times in the pages, title etc.

The queries have more of a educational intent to them.  The SERP is not spammy, we could do a better job I am sure though.

Just seems the numbers Google is providing seem way off.

One of our clients is in the top 3 spots on high volume keywords that get 20-70k hits in the US each month (per adWords keyword tool), but their daily traffic is in the low hundreds.  What's going on?

We have a client that's changing the name of their medical practice from the doctor's name to their region + "eye care."  However, they recently told us they're changing it from "eye care" to "eye center."

Many of their direct competitors use "eye care" in their name.  I ran a quick keyword analysis and it shows "eye care" gets a million US searches a month, whereas "eye center" gets 450k searches a month.

While that alone would make me suggest they keep "eye care," I ran a keyword difficulty analysis and found that "eye center" has a KW difficulty of 41 and "eye care" has a KW difficulty of 78.

Should we recommend they stay with "eye care" because it gets more searches?  Or is it better to go with "eye center" because it'll be easier to rank for?

Thanks John!  It's exactly what I needed.