Welcome to the Q&A Forum

Thanks Dirk, this is the direction we were leaning.

Thanks for the suggestions Patrick.

The first question to answer is if the site itself is a blog... or if it's a website that also has a blog. If it's the latter and the blog lives at www.yoursite.com/blog/, then the structure should obviously always include the /blog/.

Responding to your 3 examples in order:

Quicksprout's structure is a little odd in that their blog lives at /blog/, but the individual posts do not. A bit strange from both a human usability and bot crawling hierarchy standpoint. Other than that, including the date is helpful in terms of telling the user/bots how current the post is and differentiating it from similarly named posts on the same blog. That said, it pushes the title/topic keywords further out in the URL.

Moz uses /blog/, which again makes the most sense, but they've foregone including the date. This, however, lets them get the topic/title keywords to appear earlier in the URL.

SEO Book, like Quicksprout, oddly strips out the /blog/ directory from the URL. Other than that, their strategy is the same as Moz.

The winner here, in our opinion, seems to be Moz. The /blog/ remains when you're on individual posts which makes sense to both humans and bots. They don't include the date, but historically that's not been critical.

We have a client whose WMT shows a ton of "Not found" crawl errors after a new site launched. The URLs are largely a bunch of files that they had previously uploaded on their old site which have external links pointing at them.

What is their best course of action, if they don't have files on the new site that correspond with these old files? Redirect to the home page? Leave them 404ing? Customize 404 message?

(Note: They're mostly generic, non-human friendly URLs that are difficult to identify like /gallery3.php/ppage/3, g/interior.php/pid/3/sid/24,  /uploads/1213196781.pdf)

Thanks for the tip StreamlineMetrics... Curious though, how are you able to get keyword data, etc. to pass through when Google strips it out. Do we not run the risk of violating some other Google policy?

Thanks for the replies - I think you nailed it JaneCopland! This was our gut, but figured it couldn't hurt to have a few other SEOs weigh in.

Thanks for the quick reply, but after Googling it sounds like they've actually built a feature to allow for what we need, it just works differently than I was describing - data is imported back to GA. https://support.google.com/adwords/answer/2998031?hl=en

And then there's also the Measurement Protocol - https://developers.google.com/analytics/devguides/collection/protocol/v1/

Thanks for the quick reply, but after Googling it sounds like they've actually built a feature to allow for what we need, it just works differently than I was describing - data is imported back to GA. https://support.google.com/adwords/answer/2998031?hl=en

And then there's also the Measurement Protocol - https://developers.google.com/analytics/devguides/collection/protocol/v1/

I have a client who tracks leads via URL destination goal completions in Google Analytics - when a visitor hits their "quote form" thank you page, a "goal" is completed and thus a lead is tracked in GA. After that, none of the sales process is passed through to GA - The client enters data from form submissions into their CRM software, without any way of knowing which leads came specifically from PPC, email marketing, social, organic, etc., making determining true ROI impossible.

We're wondering what the best way is to pass through the traffic source to our client, so they can attach it to the individual lead in their completely manual CRM. Mainly they care about CPC traffic.

Any ideas?

My client started a subdivision of their company, along with a new website. There was already an individual page about the new product/topic on the main site, but recognizing a growth area they wanted to devote an entire site to the product/topic. Can we/should we redirect that page on the old corporate/main site to the new domain, or just place a link or two?

Thoughts?

The first question to answer is if the site itself is a blog... or if it's a website that also has a blog. If it's the latter and the blog lives at www.yoursite.com/blog/, then the structure should obviously always include the /blog/.

Responding to your 3 examples in order:

Quicksprout's structure is a little odd in that their blog lives at /blog/, but the individual posts do not. A bit strange from both a human usability and bot crawling hierarchy standpoint. Other than that, including the date is helpful in terms of telling the user/bots how current the post is and differentiating it from similarly named posts on the same blog. That said, it pushes the title/topic keywords further out in the URL.

Moz uses /blog/, which again makes the most sense, but they've foregone including the date. This, however, lets them get the topic/title keywords to appear earlier in the URL.

SEO Book, like Quicksprout, oddly strips out the /blog/ directory from the URL. Other than that, their strategy is the same as Moz.

The winner here, in our opinion, seems to be Moz. The /blog/ remains when you're on individual posts which makes sense to both humans and bots. They don't include the date, but historically that's not been critical.

I have a client, a plumber, who bought another plumbing company (and that company's domain) at one point. This other company was very old and has a lot of name recognition so they created a dedicated page to this other company within their main website, and redirected the other company's old domain to that page.

This has worked fine, in that this page on the main site is now #1 when you search for the other old company's name. But for some reason the old domain comes up #2 (despite the fact that it's redirecting). Now, I could understand if the redirect had only been set up recently, but I'm reasonably sure this happened about a year ago. Could it be due to the fact that there are many sites out there still linking to that old domain?

Thanks in advance!