Welcome to the Q&A Forum

There are two ways to handle load balancing, and it appears that your hosting company / server company chose to use the DNS round-robin routing option. According to the Wikipedia page on load balancing: http://en.wikipedia.org/wiki/Load_balancing_(computing) "Load balancing usually involves dedicated software or hardware, such as a multilayer switch or a Domain Name System server process." Round Robin DNS Load Balancing: Basically you use the DNS routing system to handle requests. When someone visits your site, 50% of the people are routed to www.domain.com, and 50% are routed to ww1.domain.com. Both sites contain the same identical content; it's the URLs that are slightly different. Sometimes the domains are the same; but you have different IP addresses for www.domain.com. Advantages: you don't need a dedicated load balancing piece of software or hardware, so it's less expensive. Disadvantages: this technique exposes the individual web servers to the end user seeing the site. You can also suffer from duplicate content penalties, too. Finally, if you are relying on the round robin DNS system for load balancing, and a DNS server or one of the Web servers goes down, there's not an easy fail-over (as many DNS records are cached). More about Round Robin DNS: http://en.wikipedia.org/wiki/Round-robin_DNS Hardware / Software Load Balancer: In this case, your DNS zone file tells the end user to go to one IP address when they type in www.domain.com. The hardware or software load balancer then sees the request, and then hands off the content to one of the web servers in a cluster. Advantages: No duplicate content penalty; to the end user, they just see one web server and not individual sub-domains (www.domain.com and ww1.domain.com). A load balancer can also cache specific items like a CSS page, so the load on the Web server is even more minimal. Disadvantages: You're introducing another piece of hardware or software (i.e. more cost); this piece could also be a single point of failure into the mix. You need someone to figure out how to set this up and make sure it all works. More on this type of Load Balancing: http://en.wikipedia.org/wiki/Load_balancing_(computing)#Internet-based_services Load balancing can get complicated as soon as you have databases involved, but with a good design, multiple front end Web servers can talk to one single backend database server. The goal would be to cache as much content as possible as "static" elements, using caching systems like Varnish, that essentially turn database-driven pages into static, old-school HTML pages. And then only when someone needs to save something from the database (i.e. making a purchase on an eCommerce site), the system then interacts with it. My recommendation: (1) Move from the Round Robin Robin DNS to a hardware or software load balancer. (2) If that isn't an easy solution, implement the Round Robin DNS solution to use identical A records for each server. For example, you might have identical entries in your DNS zone files for both DNS servers: NS1.domain.com: www.domain.com A 69.94.15.10 NS2.domain.com: www.domain.com A 75.64.18.12 This should at least eliminate your duplicate content issue, but you still do have a few disadvantages (described above). This also could lead to server issues, as the servers might be confused if they are the authoritative ones. And if both servers are sending email, pay special attention to your SPF record, to make sure that you are allowing both IP addresses to be able to send email. (This is often overlooked.) Hope this is helpful! -- Jeff

Thanks Erin-That helps, for the time being. We hope it's something you can bring up with the Product Team. Ctrl+F for now!

Thanks Don for your response. My follow up question would be what to you have has the default index page examplesite.com? What content is displayed there?

Good plan, thanks for this and all your help.

Hiya, It really depends on what you want, personally I favor having on the site (option1) that way any SEO work you do helps build up the whole domain. Here are some options to help you (only rough) Option 1. -  Create the product onsite Pro's - helps build up whole domain, less work needed between two sites. Already existing site can help rankings. cons - can clutter site, can backfire with any badly done SEO on the whole domain option 2. - Create a sub domain (e..g sub-domain.example.com) Pros - Can still help build you brand and gain association of site Cons - link juice doesn't tend to flow between subdomains meaning more work Option 3. - Completely separate domain Pros - Can keep it separate from main domain (different link strategies etc.) Cons - Absolutely no link juice flowed between it and main domain could double the effort to maintain two domains  Fresh sites can be harder to rank This is what I came up with in a couple of min and one else feel free to add to my pro's & con's as i'm sure i missed some bits and pieces.

From that screenshot, looks like you have a G+ page associated with your website that lists all of that info. Your best bet would be to disassociate your URL from this page https://plus.google.com/102542416695217785100/

Unfortunately, in Google Analytics, there is no way to see these old speed reports before you did all the changes. (Unless you saved them to your computer or something.)

That is the way breadcrumbs function. Those links are the categories of the Aruba page. So if you make another page (e.g. Aruba climate) as a subpage of Aruba, you can add that category to the url and you'll see the Aruba breadcrumb (but not 'Climate').

You can use the MozBar (though you have to hit each page individually) to highlight all the links on that page.

Many Travis, A good detailed answer. thanks for your help ,  I will look at doing this. Pete

he he https://twitter.com/sugarrae/status/535823812143497216/photo/1

To my knowledge, there isn't a way to target new phone purchasers. Facebook may have some more specific targeted user groups than Bing or Google, but even the content network doesn't have something that specific at this point, unfortunately. What market are you specifically looking to grasp? Maybe it's not new users, but people who are nervous about breaking their phone? Or who are looking to upgrade that might not know what the best choice is for them? There are ample numbers of ways to target mobile users more specifically with Facebook and twitter than with adwords and bingads.

Moosa, I am currently looking into it. One thing I know for sure is that a lot of my links dropped, because I stopped using the individuals that were building links for me. I know what needs to be done on that end. Thank you for your insight

Hi Scott, I wouldn't recommend tracking or redirecting phone numbers, actually. Google has historically had issues with both. The unique phone number is ideal, but I understand it's quite uncommon in medical practices. Normally, all calls are answered by the front desk in medical practices, so this may not be a safeguard you can comply with. If your clients were realtors or insurance agents, it would be more typical for them to have their own phone numbers, but doctors don't usually seem to. So, the upshot here is going to be that you're likely to have to use the same number on the listings and cross your fingers that the other areas of differentiation will help Google keep the various practitioners separate. Google is better than in the past about preventing merges, but they still happen, so you'll always want to keep an eye on the listings and if you notice details getting mixed up or discover a sudden drop in rankings or something along those lines, you'll need to investigate the presence of merging and duplication. Likely - it won't happen - but it's best to be prepared:)

That's great! I'll do that. Thanks!

This used to be recommended years ago when Google didn't have the crawling power they do now. Today Google does regular crawls everywhere, it is possible that submitting the URL may gain a day or so advantage, it just depends on how often Google crawls the particular site you acquired a link on. Obviously the more popular the site the more likely Google does frequent crawls.

Hi Andy, Thanks for a very good answer. That makes sense. Ill keep my article section and the interview section. My current system is "simple". so it doesnt support all the features a word-press blog have and people can't comment on the articles directly on the site. That might be a problem? In that content a sorta like blog-system would be better, but ill stick to what I have for now then. Thanks. KasperGJ

Thanks Travis, I'll take a look at both.

I have a glossary on one of my websites.  It has been there about ten years and receives between 200 and 1000 visitors per day.  It ranks #1 for "[industry name] glossary", "[industry name] dictionary" and many similar terms and has held those rankings for many years.   It has about 1000 definitions, some that are very close or repeats as you describe. When I made this glossary I decided to place it on 26 pages - one for each letter of the alphabet.  During the first few years it was up, I was tempted to convert it to one page per definition as you propose but decided against that.  I was tempted because I thought that the glossary would rank for lots of different keywords and pull traffic for all of them. In the past two years, I have been really glad that I didn't create all of those pages.  Why?   Panda.   The Panda algo would probably not be kind to those pages.  They would contain an average of about 50 words.  That is too skimpy and I think that my site would be demoted for thin content. What I have done is write substantive article pages for many of the definitions.  These are 500 to 2000 words with photos, graphs, data, etc.  Each of these article pages receives a link from the glossary definition and these page rank really well for very difficult terms.  I only have a couple hundred of these articles but finish one or two more every month - so its growing - slowly. I have ignored the glossary for the past several years but this week I have been adding new words and adding images to many of the definitions where they would be helpful.   I am also adding links within the definitions to pages where I have articles about those topics.  The goal is go move glossary visitors into the rest of the site. Two of my friends have glossaries.  One made his on 26 pages like mine and is getting lots of traffic.  The other made separate pages for every definition, was doing great in the early years, but recently had Panda problems. Good luck with whatever you decide.