Tag Info

Hot answers tagged

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 ...


2

It's been a while since i have been in google webmaster's tools but I do remember that in there is a tool for removing indexed pages for any website.. **You will need to link the website with the particular webmaster's tool account to do so... https://www.google.com/webmasters/tools/dashboard login or create new account (link the website as mentioned ...


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.


2

Google recognizes your URLs with parameters and as different because the id is different. I suppose that the product pages have not the same content; therefore, there is no duplicate content between your URLs; thus, you don't need to use the rel="canonical" tags between pages.


2

You can remove it with URL Rewriting like that : <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^(.*)$ /product.php/$1 [L] </IfModule> Place this code in .htaccess at root.


1

Try <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^(.*)$ /gallery/$1 [L] </IfModule>


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

First, you don't have to go through the trouble of removing the old URLs with the hash. If your content is getting crawled and indexed appropriately under the new hash-bang URL, it'll soon get replaced. It's not entirely clear what the problem is without troubleshooting against the live site, but hopefully these steps will help you discover a solution. ...


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