Hello Lawrence,

I think this is a question best asked of the Cloudflare support team, but don't be surprised if they blame it on your host. Here are some folks having similar issues. Let us know if you find something out that could help others in your situation in the future.

Good luck!

Hello Heahea,

1. I would agree that you should go with the Superpages option: Name = Name of the Location

2. I would go with Organization Schema Type using JSON-LD script, as outlined here:

https://developers.google.com/structured-data/customize/social-profiles

I wouldn't have two Schema Types on that page. Use Organization and provide the URL using the URL property as defined here:

https://schema.org/Organization

This is how we do it on http://www.GoInflow.com. View source and look for the following code, which is the start of our JSON-LD script:

Hello Claire,

From what I have observed Google seems to give a boost to fresh content, or even re-freshed content. I have seen this effect in the following situations:

• When updating the publish date on the page- When updating the last-mod date in the sitemap
• When refreshing a page WITHOUT updating the publish date (though I don't know if the dateModified tag was updated.)

As for empirical data, none that anyone is willing to share publicly. But this is a real effect that has been seen over and over again by myself, and several people I trust. Take it for what it's worth, but going back through old content and looking for ways to improve it, bring it up-to-date, and ensuring the last-mod tag in the sitemap gets updated is a very good use of your time as a marketer.
 

Hello Kevin,

Which meta tags are you trying to update?

Have you had any developers work on the site who may have hard-coded something else into the template instead of the Magento default? For example, maybe your product page Title Tags are based on the product name and the Meta Descriptions use the product description?

Are you using your own subdomain or one somewhere else (e.g. akamai.com)? You should use your own subdomain, if possible.

Was this a change from a previous version that didn't use a CDN? If those images were/are hosted on your primary domain be sure to match the filenames and paths as closely as possible to what they were before.

If you're doing that you shouldn't have a problem once the sitemap is submitted.

For more information please check out this post:
http://www.goinflow.com/four-seo-best-practices-for-using-a-content-delivery-network-cdn/

How do you know that Google only attempts to crawl the primary domain URL (i.e. the .html page)? Are you checking log files?

Is the crawler you're using set to crawl external URLs? If not, that could be the issue. Technically a subdomain is a totally separate website so most tools don't crawl them by default.

Hello John,

I don't understand how blocking /wp-admin/ would keep /wp-content/ from being accessed and rendered by Google.

Google doesn't need to see anything in the /wp-admin/ folder so you should keep it blocked. They do need to see the /wp-content/ folder though.

WOW, this is an interesting thread. In theory, rel next prev is what Google wants you to go with. In practice, however, I haven't not seen this work as advertised by Google, and end up going to rel canonical in most cases. Here's one way to think about it:

Allow non-filtered pagination for top-level categories to be followed, but NOT indexed. Give them their own rel canonicals (self referencing) and ensure the intro content (or any other static content on the page) only shows on the first page (which should rel canonical to / instead of /?page=1). This will ensure your product pages all have a path going to them. Use rel next prev here, which "may" help the main/first page rank better by consolidating ranking signals from the paginated set.

For sub-categories and/or filters/facets use rel canonical pointing to the canonical version of that category page.

None of this, however, takes care of the crawl budget issue on enterprise eCommerce sites with crawlable filtered URLs. Therefore, I also use the robot.txt file, or nofollow attributes in links to handle this. I don't often use the nofollow robots meta tag for a variety of reasons.

Again, in the real world rel next/prev doesn't seem to be working very well. I haven't tried it in awhile, but it just doesn't seem to do what Google says it's supposed to do. This is why you see a lot of sites using rel canonical instead. I think we should think about this in terms of where you are in the architecture instead of trying to fit all pages into a single scheme. For example, some sites may even want to allow the first facet/filter to be indexable - such as "Filter by Brand" - because people are searching for it. If that's the case, I'll often advise they turn that into a real category instead of a filter. Another example, if you sell kitchenware and Pots & Pans is a category but Material is a filter you're missing out on a lot of searches for things like "Copper Pots & Pans" or "Stainless Steel Pans". It all depends on the situation, and has to be evaluated on a case-by-case basis.

Hello Texture Media Inc,

It's tough to keep up on what the various parts of different SERPs are these days. They're constantly expanding and changing. The only person I know who can keep up is Dr. Pete, and that's just barely.

I think what you're wanting to do is get content in the Answers Box, as opposed to the Knowledge Graph. This should answer your questions: http://cognitiveseo.com/blog/6121/total-serp-domination-using-the-new-google-answer-box-technique/

SameAs should be used for connecting various pages about the entity, including social but also Wikipedia pages and other official "About" pages. It's a good idea to use this tag, but isn't going to help with what you're trying to do, specifically.

In that case I would say a phased approach would be fine. It is an issue that should be addressed, but I wouldn't classify it as "critical".

Hello Geoff,

It looks like you've installed the Yoast plug-in now and the category pages have a noindex,follow robots meta tag. That might do the trick, but you should make sure the posts are in an XML sitemap that you list in your robots.txt file and submit to Google Webmaster Tools - or whatever they're calling it this week.

I checked several things and it looks fine:

• No robots meta tag blocking on posts.

• No robots.txt blocking of posts.

• Followable Read More links from category pages

• Mostly unique content on posts (though they may be seen as thin affiliate pages in some cases).

At this point you should focus on getting your posts into an XML sitemap and also look into the following:

• Lots of pages that shouldn't be indexed, such as /contact pages with various parameters and redirect.php with various parameters: http://tinyurl.com/qdne3g2

• Security errors. I see several popping up in Firefox, including "This website does not supply identify information". I'm assuming you have a valid SSL Cert?