New answers tagged

1

What I would suggest is to create a brand new set of URLs for search result pages and then for anyone requesting the old URLs, produce an error page with an HTTP 410 status code. Also, make your search pages only accessible via the POST request method. Google won't crawl pages that are requested via POST if it is requested as a result from filling out a ...


1

Google supports Noindex: in robots.txt as an experimental feature. It sounds like this would be the perfect case for using it: User-Agent: * Disallow: /search/ Noindex: /search/


1

Google won't crawl the disallowed path specified in robots.txt but you can't control through robots.txt the references to your site search results from other sites. While Google won't crawl or index the content blocked by robots.txt, we might still find and index a disallowed URL from other places on the web. As a result, the URL address and, ...


1

Should there be a 301 redirect to the canonical link on all pages with any kind of old format URL, or will the rel="canonical" and domain change request be enough to tell Google to drop the indexing of the old ones and start indexing the specified canonical URLs instead? Google treats rel="canonical" as hints that a page is substantially duplicate to ...


0

This problem started soon after a google ad-sense application... I will assume your problem may be temporary in nature because when a new ad unit is created and the site is tested right away, instead of an ad appearing, a browser message similar to "the page cannot be displayed" will appear in the ad box. Once the ad unit receives enough views, an ad will ...


-1

Do you use Google's Search console? If you do, are there any messages to you? If you are not yet using Search console, it should be your first step to do. You can create your Search console account here. If your blog has xml sitemp, you should upload it to the Search console (Crawl > Sitemaps). This helps Google to index all of your content. Next check ...


2

In a sitemap, this <mobile:mobile/> tag is required and only needed for an URL that serves content especially designed and optimized for feature phones (source). Therefore, you only need to use it in that case and you shouldn't declare the same URLs without this tag in a new sitemap.


2

The main problem you're having is that you expect numbers put out by Google to be accurate, but they aren't. This isn't specific to Google, it's true for all major web search engines. The total result count is just an estimate, and it's easy to see: http://searchengineland.com/why-google-cant-count-results-properly-53559 The numbers published by Webmaster ...



Top 50 recent answers are included