frikafrax

Yes, that’s right. You should switch those pages back to Follow.

Here’s a video where Google Software Engineer Matt Cutts answers a user question regarding NoFollow and internal links.

In a nutshell, Matt advises NOT to use NoFollow on internal links. Aside from very specific cases, you SHOULD allow page rank to flow freely throughout your site via its internal link structure.

Follow/NoFollow is actually for specifying which links should, or should not influence the page ranking that the link points to.

From what I understand, Follow/NoFollow is a way for site owners to control the flow of “link juice” (to use the parlance) and was introduced by Google as a way to mitigate the attempts by spammers to manipulate page ranking via link juice harvesting and manipulation.

Follow/NoFollow is not really used for controlling content access by search bots. That’s still robots.txt’s job.

Google Webmaster Tools has an easy-to-use robots.txt generator which you can find under Site Configuration -> Crawler Access -> Generate Robots.txt tab

Once generated, you simply upload it into your site’s root directory.

Note: If you have your blog installed into a sub-directory AND you have a subdomain for your blog (.e.g https://myblog.mydomain.com) then you have to upload your robots.txt into your blog’s sub-directory and not the site’s root directory.

I used these generic directions I found via Google to successfully add featured image support to an older theme.

https://markjaquith.wordpress.com/2009/12/23/new-in-wordpress-2-9-post-thumbnail-images/

Just a follow-up to my original post…

I confirmed that this is not a theme issue or a browser issue.

I tested post pagination with WordPress SEO enabled with three different themes under Firefox and Chrome.

In all cases, all post pagination page links fail to function properly and multi-page posts will only display the first page, regardless of which page number link is clicked.

Disabling WordPress SEO restores post pagination functionality in all cases.

I went through the configuration pages for WordPress SEO and there doesn’t appear to be any provisions within the plugin itself to exclude specific URLs.

In my case, I used the robots.txt file to prevent search engines from crawling specific URLs.

Excluding URLs using robots.txt is probably the preferred method as it is independent of any plugin and it’s old web standard that compliant search bots follow.

In addition to excluding URLs using robots.txt, I also logged into Google Webmaster Tools and requested a removal of all pages that I didn’t want listed in the Google SERP.

I’m just posting a follow-up to my post.

Previously, I had suggested having your site return a “Content removed” code (410) whenever a URL with WP Mobile Pack parameters was requested.

I inquired over at Google Webmaster Central and was told that it was a better idea to strip the Mobile Pack parameters from incoming requested URLs and do a 301 redirect to the appropriate content.

This can be done internally in WordPress using something like the Redirection plugin, or via .htaccess.

To cover all your bases, you may want to consider, as an additional step, editing your .htaccess file to return a “410 – Gone” code whenever a URL with the WP Mobile Pack parameters is requested.

This will prevent all other search engines and crawlers from attempting to index those bad URLs and help you avoid further penalization for duplicate or unreachable content.

Just supplementing my response…

If you have access to .htaccess on your host, you can use it to strip the Mobile Pack parameters from the URL and redirect visitors and search engines with a “301 – Moved Permanently” status code back to the original content:

(I’m a bit of a newbie so anyone experienced with Apache, please chime in if I’ve got this part wrong.)

RewriteEngine On
RewriteCond %{REQUEST_URI} (.+)?(wpmp_switcher.+|wpmp_tp.+) [NC]
RewriteRule .* %1 [R=301]

In my case, I did the parameter stripping and redirection internally from within WordPress using a plugin called “Redirection”.

The regular expressions used for the Redirection plugin’s source and destination URLs are the same as you’d use in .htaccess:

Source URL:
(.+)?(wpmp_switcher.+|wpmp_tp.+)

Target URL:
$1

Hope this helps!

You can tell Google to ignore any URLs that have WordPress Mobile Pack parameter using Google Webmaster Tools.

In Google Webmaster Tools, go to:

Site Configuration -> Settings -> Parameter Handling tab.

The parameters “wpmp_switcher” and/or “wpmp_tp” should be listed there.

Set the “Action” to “Ignore”.

If they aren’t listed, click on the “+Add parameter” option at the bottom of the parameters list, above the “Save” and “Cancel” buttons.

While I like the concept of the Mobile Theme Pack, I’m also removing it from all my blogs.

Are you by chance using a plugin called “Theme My Login“?

I run four blogs and the only one that was having 404 errors with “MiniMeta Widget” was the blog that had both “MiniMeta Widget” and “Theme My Login” activated.

Turning off “Theme My Login” fixed the 404 issue for me.

I’m experiencing the same thing.

It appears that the WP-ReportPost plug-in is affecting Visitor Maps’ “Last URL” data.

Ever since I installed Wp-ReportPost, all my visitors are listed by Visitor Maps as having this URL as the last URL they visited on my blog:

“/wp-content/plugins/wp-reportpost/loading.gif”

The URL that Visitor Maps lists as their Referer URL is actually the last URL they visited on my blog.

I, too, have uninstalled WP-ReportPost but Visitor Maps is still displaying that “loading.gif” URL as visitors’ Last URL visited.

I did a bit more poking around and found that if I’m not logged in, then WP-PageScroll works properly, Firefox included.

After I log in, that’s when WP-PageScroll no longer works properly. This happens in Internet Explorer and Chrome in addition to Firefox.

I found that it’s a compatibility issue with the particular theme I’m using. It’s not necessarily a problem with the plugin.

I realize this question is four months old but the answer can still help others.

To modify the width of the sidebars, open style.css in the theme’s root directory and look for the ID called #sidebars, and modify the width element.

E.g.

/* Sidebars */
#sidebars {
  margin: 15px 0 0 0;
  float: right;
  width: 340px;
  color: #C5C5C5;
  }

To modify the article column width, look for the ID called #contentwrapper:

#contentwrapper {
  float:left;
  width: 580px;
  margin: 0 0 15px 0;
  padding: 0;
  }