4

It is not a good idea to let Googlebot crawl URLs that can be constructed with combinations of parameters. When you allow your categories to be filtered, my advice is to only allow Googlebot to crawl pages with a single filter applied, even if you allow users to view multiple filters at the same time. To implement this, you need to change your URLs: /...


3

No. The browser will send the same information on a refresh as if the user had just come to that page, with the same referrer information. Hence the problem of double-POSTing if someone refreshes the destination page for a form. What you could do is have a refresh button on the page (as Google Ads used to have before they removed it), which you could use to ...


2

Have you looked at limiting Google's bot threshold? Per Google, If Google is making too many requests per second to your site and slowing down your server, you can limit how fast Google crawls your site. The one caveat is you cannot limit to a specific folder/directory. Per Google: You cannot change the crawl rate for sites that are not at the ...


2

Browsers do send additional headers, but behavior different. This info in link a bit outdated: stackoverflow question Looks like Cache-control:no-cache is the best solution, to check for Ctrl+F5, but better to check not the only one header. Just checked on Firefox Ubuntu, F5 gives nothing, but Ctrl+F5 request contain this Pragma no-cache Cache-Control ...


2

You cannot change the headers for requests you're not responding to. In this case, the browser will make a request to Google asking for fonts. The browser will receive a response from Google(not you) with headers(cache, encoding, etc) and body(actual resource). Don't forget these tools point you in the right direction but are not always aware of the whole ...


1

To leverage Browser Caching on Windows Host, assuming it's IIS, you have to add this snippet in the web.config file in the document root of your website: <system.webServer> <staticContent> <clientCache cacheControlMode="UseMaxAge" cacheControlMaxAge="30.00:00:00" /> </staticContent> </system.webServer> The cacheControlMaxAge ...


1

Your screen shot has nothing to do with "cache from image short lifetime". The warning from google is about HTTPS. You should get an SSL certificate, which can be free or paid, from your hosting or third party. When it comes to "cache from image short lifetime", what you could do, in case you have access to .htaccess file (usually placed in root directory) ...


Only top voted, non community-wiki answers of a minimum length are eligible