Google SEO - Google indexes nextnewest/nextoldest

[Goose]

Hello all.

Recently, Google have indexes many pages of my forum with parameter action=nextnewest or action=nextoldest.

The bad thing is that Google used this parameter in previously indexed pages for many important threads for me: it have replaced /forum/important-post with /forum/important-post?action=nextnewest (but the Title returned by Google is still the "important-post" one). I can't found anymore in Google index the real /forum/important-post link (without nextnewest/nexoldest).

As suggested in Google SEO plugin, both nextnewest/nextoldest are disallowed in robots.txt, so Google give for this posts a "warning" description ("no description because of robots.txt blablabla").

As any one have a valid solution to hide nextnewest/nextoldest for Google
?

In Google webmaster tool, I now have excluded parameter "action", hoping Google revert back to previous URL...

[frostschutz]

This user has been denied support.

Are you using robots.txt (example included in the Google SEO package)? nextnewest/nextoldest should be blocked by that. Apart from that the redirect / canonical should be taking care of it sooner or later. You can also edit your showthread templates to add rel="nofollow" to the next_oldest / next_newest links, or remove those links altogether if you do not want to have them in your forum.

[Goose]

Yes I used the robots.txt in the package.

Everything was Ok for a year. But I discovered Google had change the links for some post adding this parameters for no reason in remplacement of existing referenced post (then linking to another page !)

[frostschutz]

This user has been denied support.

If it's about the website in your profile, the robots.txt is incomplete.

[Goose]

Could you tell me what is missing ?

Disallow: /forum/captcha.php
Disallow: /forum/editpost.php
Disallow: /forum/misc.php
Disallow: /forum/modcp.php
Disallow: /forum/moderation.php
Disallow: /forum/newreply.php
Disallow: /forum/newthread.php
Disallow: /forum/online.php
Disallow: /forum/printthread.php
Disallow: /forum/private.php
Disallow: /forum/ratethread.php
Disallow: /forum/report.php
Disallow: /forum/reputation.php
Disallow: /forum/search.php
Disallow: /forum/sendthread.php
Disallow: /forum/task.php
Disallow: /forum/usercp.php
Disallow: /forum/usercp2.php
Disallow: /forum/calendar.php
Disallow: /forum/*action=emailuser*
Disallow: /forum/*action=nextnewest*
Disallow: /forum/*action=nextoldest*
Disallow: /forum/*action=weekview*
Disallow: /forum/*year=*
Disallow: /forum/*sort=*
Disallow: /forum/*order=*
Disallow: /forum/*mode=*
Disallow: /forum/*datecut=*
Allow: /

I did get the file from plugin archive and it give the same lines...

[frostschutz]

This user has been denied support.

Yes, but the robots.txt from your link (japancar) does not have those (action nextnewest etc.)

Also, the sitemap protocol is not 100% clear whether sitemap index inside sitemap index should be allowed; but you are allowed to have multiple Sitemap: in robots.txt, so I'd reference the Google SEO Sitemap index directly.

[Goose]

Yes, but the robots.txt from your link (japancar) does not have those (action nextnewest etc.)

Also, the sitemap protocol is not 100% clear whether sitemap index inside sitemap index should be allowed; but you are allowed to have multiple Sitemap: in robots.txt, so I'd reference the Google SEO Sitemap index directly.

I have allowed nextnewest/nextoldest AFTER I saw Google have indexed those pages (to replace the Google warning message in the result description with correctthread content)

I have fixed this for my important thread with hard-coded RewriteCond / RewriteRule.

# Temp rewrite
RewriteCond %{QUERY_STRING} ^action=nextnewest$
RewriteRule ^Thread\-SOME\-TEXT([^./]+)$ showthread.php?tid=***thread id*** [L,R=301]

I can't figure why Google did replace
/forum/Thread-SOME-TEXT by /forum/Thread-SOME-TEXT?action=nextnewest for some of my threads...

[frostschutz]

This user has been denied support.

Okay, in that case what you're probably seeing is not indexed pages, but this:

While Google won't crawl or index the content of pages blocked by robots.txt, we may still index the URLs if we find them on other pages on the web. As a result, the URL of the page and, potentially, other publicly available information such as anchor text in links to the site, or the title from the Open Directory Project (www.dmoz.org), can appear in Google search results.

Such a Google search result will usually also say "A description for this result is not available because of this site's robots.txt – learn more."

I think it's safe to ignore those. They won't be shown normally.

[Goose]

Okay, in that case what you're probably seeing is not indexed pages, but this:

While Google won't crawl or index the content of pages blocked by robots.txt, we may still index the URLs if we find them on other pages on the web. As a result, the URL of the page and, potentially, other publicly available information such as anchor text in links to the site, or the title from the Open Directory Project (www.dmoz.org), can appear in Google search results.

Such a Google search result will usually also say "A description for this result is not available because of this site's robots.txt – learn more."

I think it's safe to ignore those. They won't be shown normally.

Yes. I didn't copy/paste here because I'm using Google in french

What I do not understand is why Google has replaced an existing indexed thread (I watch some specific keywords) with the same URL but suddenly adding the parameter action=nextnewest... Especially for some pages, it was still the old title and the former description, but clicking on the link on the Google results goes on the nextnewest discussion.