Tag Info

Hot answers tagged

7

Browsers do not try one protocol and then fall back to the other. The browser will use which ever protocol it is linked to. If that protocol isn't supported, the user will get an error. If you want to force users to use one protocol, you can redirect from one to the other. For example, to force secure connection on your site use the following rewrite ...


5

Putting the ID near the beginning of a URL is better than putting it near the end. URLs often get truncated in emails or by CMS systems that show them to users. When the ID is at the end the truncation will often lop it off and cause 404 errors on your site. When it is near the beginning, your site can still redirect to the full URL. When Googlebot ...


4

From the SEO prospective, i bet there might be a difference: In you first example, the ID is separated from the title, making it clear to the crawler it is a different resource (as the / character does it naturally). In your second example, the ID is mixed with the title. It requires more brains from the crawler to determine the meaning of it. Imagine ...


3

// basically means that the a resource will be requested in the same protocol, thus if someone is browsing httpS://yourwebsite.com, and you include a stylesheet like //yourwebsite.com/style.css, it will load httpS://yourwebsie.com/style.css. If you request resources from http when the page is https, the browser may give an error. To answer your questions: ...


2

At https://developers.google.com/speed/libraries/devguide Google recommends using <script src="//ajax.googleapis.com/ajax/libs/jquery/2.1.1/jquery.min.js"></script> to link to jQuery, for example. Google hosts the jQuery libraries at both http and https. The browser will use the same protocol as was used to reach your site to fetch the included ...


2

There are two things you have to keep in your mind: The easier to remember, the better you have to be able to remove each part in the url without breaking it This makes your 3 examples rather easy: A http://www.example.com/category/sub-category/sub-sub-category/article/ID B http://www.example.com/ID/category/sub-category/sub-sub-category/article C ...


2

For SEO, I would say an id doesn't permit to easy remember the URL for users. Therefore, no matter on which URL you choose; an id in the middle or at the end of an URL doesn't change anything regarding SEO. However, an id in an URL can be very useful in case of you would have two pages with the same URL. This is the case for StackOverflow because the URL is ...


2

You should be doing a 301 redirect from the .php URLs to the rewritten URLs. If that is not possible for some reason you need to add a canonical URL to the .php URL pointing to the rewritten URL.


1

products1.php simply needs to output the canonical link in the head section of the page. Presumably it knows the information needed to build your friendly URL: category subcategory product name product id Then the canonical tag appears in both the page for the friendly URL and the page for the parameterized URL. That is fine. Google says that a ...


1

It should just work fine provided that the URL is enclosed in double-quotations, for example: Old URL: http://www.example.com/folder%20name/page%20name.html New URL: `http://www.example.com/folder/page Redirect 301 "/folder/page%20name.html" http://www.example.com/folder/page


1

JBoss does support rewrite rules which can be used to support this. From the documentation, you would first have to add this configuration in the server.xml file: <Valve className="org.jboss.web.rewrite.RewriteValve" /> Then you would have to create a rewrite.properties file with something like this: RewriteRule ^/$ /web/app?environment=UAT ...



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