Welcome to the Q&A Forum

It's been my experience that if you're going to have additional languages on your site, you can do one of a few things to the URL:

• site.com/us/
• site.com/il/

or

• site.com
• site.il

or

• il.site.com
• us.site.com

Then you can place the content in the respective languages on those sites. They won't necessarily be seen as duplicated content (semantics change as you translate to different languages). However, Google won't necessarily penalize you if you keep your URL to site.com and just switch up the languages because, again, semantics change as you translate languages.

I worked with several sites that translated content from English to Spanish or English to Hebrew and they were never once penalized for duplicated content.

I wouldn't worry about adding the no follow tag - unless you don't want anyone seeing your journal entries. I recommend not linking back to your second blog from the first blog, if you don't want to see traffic.

Google may decide not to index it on their own but they will likely index the pages. Those pages may not get found in SERPs. I do not recommend switching to Tumblr, mainly because it sounds like you don't really want people to see your content and Tumblr will likely find ways to send you traffic (it's a social blog, afterall).

You can keep with your status quo.

I completely agree. Backlinks can't and shouldn't be bought, farmed, or created. They should be acquired naturally by crafting great content that people want to share.

Targeted backlinks utilizing keywords in place of your actual name are not recommended. Google will still recognize the backlink - it just won't have targeted anchor text. If you use targeted anchor text, Google may see the backlink as spam, this is why it's not recommended.

Forums may be a better choice for you, but I would still use caution there.

I think #2 would be a good fit - it's responsive and easier to navigate.

That's amazing! What a leap of faith! My recommendation/advice is to read, read, read. Get your hands on books on UX. Read up on how to perform a content audit. Read through as much about SEO as possible. SEO has been my passion for nearly a decade and I'm still learning.

Also remember not to take yourself too seriously. You WILL have clients that think they know everything. You WILL have clients that make you want to rip your hair out. It's normal. Pick your clients carefully. You're the expert, not them. And never call yourself a 'guru'.

Are both pages being indexed? If so, you won't lose the http:// version because googlebots are treating them as two separate pages.

I would leave the pages up but mark them as "no follow". When I worked in eCommerce, this was a great tactic. For UX purposes, you could try to steer people to similar-products, but keep the originating page as "no follow" or "no index".

Great question! You can always do a site search on Google or use Screaming Frog (best recommendation). You can use Screaming Frog and and keep an eye out for new pages.

Doing it manually can be time consuming but you can always use their content as a basis for new content ideas within your client's site.

How quickly are they adding new content to the site and are they using Twitter/FB/Pinterest/G+ as a resource for getting their URLs crawled more frequently? That's worth checking out.

I would also add Google Webmaster Tools to the site and head to the area where you can ask Google to remove a SERP listing.

Using the keyword tactic is a bad idea. Comments are meant to be personalized so using a fake name or a keyword is not recommended. UX still factors into SEO so you could be harming your site and the site you're commenting on by doing that.

I think it may be a server-side error. I think there's a rule written into the server coding that's causing spiders to read things wrong. The Client is having issues with redirects, as well. Their 301s are turning into 302s.

The robots.txt file is fine and it's coded properly. Unfortunately, due to confidentiality reasons, I can't share the link.

For some reason, my spiders can't see a client's metadata even though I can see it in the source code. Any reason why that would happen?