Hi Jimmy,

Any chance you split that traffic by Mobile vs Desktop and then on Mobile traffic check the direct traffic by device? Sometimes it is related to a specific device or browser that is sending the wrong referral data.

I remember this Cyrus post, about Bing traffic (https traffic) showing as direct traffic. And there is also a post by Shahzad Abbas from Define Media on iOS traffic messing up with analytics reports. Maybe you can read those and have some insights.

Cheers,

Fabio

Just to let you know that the page was indexed in less than 24hrs. We didn't use Tony's tiip (share on G+) but we did all the following:

• Used GWT tool - fetch as googlebot
• Submit the URL using the button that appears after fetching as googlebot
• Included some sidewide links to the page
• Included the page in our sitemap.xml

Thanks all folks who added some insights and tips!

Thanks for the tip Tony! We didn't try this yet.

Hi folks,

A client of mine created a new page and used meta robots noindex to not show the page while they are not ready to launch it. The problem is that somehow Google "crawled" the page and now, after removing the meta robots noindex, the page does not show up in the results.

We've tried to crawl it using Fetch as Googlebot, and then submit it using the button that appears. We've included the page in sitemap.xml and also used the old Google submit new page URL https://www.google.com/webmasters/tools/submit-url

Does anyone know how long will it take for Google to show the page AFTER removing meta robots noindex from the page? Any reliable references of the statement? I did not find any Google video/post  about this.

I know that in some days it will appear but I'd like to have a good reference for the future.

Thanks.

In my experience, Google does not ranking lower longer URLs. I know Rand published once a correlation study that shows this, but I can show you many examples that I've used the first approach and got good rankings. Same for the second approach.

I think you should keep your website architecture solid, following the correct path and not removing one level.

Another thing is that dropping that specific level may cause you some duplicate URLs problem. You will need some database check before enable each URLs. Pay attention if you choose the second approach.

My tip here is to use this geotarget feature only, and if only, you want to target ONE specific country. Otherwise, let Google decide.

My tip here is to use this geotarget feature only, and if only, you want to target ONE specific country. Otherwise, let Google decide.

In my experience, Google does not ranking lower longer URLs. I know Rand published once a correlation study that shows this, but I can show you many examples that I've used the first approach and got good rankings. Same for the second approach.

I think you should keep your website architecture solid, following the correct path and not removing one level.

Another thing is that dropping that specific level may cause you some duplicate URLs problem. You will need some database check before enable each URLs. Pay attention if you choose the second approach.

Hi Jimmy,

Any chance you split that traffic by Mobile vs Desktop and then on Mobile traffic check the direct traffic by device? Sometimes it is related to a specific device or browser that is sending the wrong referral data.

I remember this Cyrus post, about Bing traffic (https traffic) showing as direct traffic. And there is also a post by Shahzad Abbas from Define Media on iOS traffic messing up with analytics reports. Maybe you can read those and have some insights.

Cheers,

Fabio

Just to let you know that the page was indexed in less than 24hrs. We didn't use Tony's tiip (share on G+) but we did all the following:

• Used GWT tool - fetch as googlebot
• Submit the URL using the button that appears after fetching as googlebot
• Included some sidewide links to the page
• Included the page in our sitemap.xml

Thanks all folks who added some insights and tips!