There are many acceptable ways to structure your site for both SEO and internationalization. Each have advantages and disadvantages.
Top Level Domains
Buy the same domain name at multiple top level country domains like example.com, example.es and example.de.
Fully supported by Google. You can add the sites to Google Webmaster Tools where ...
URLs are not case-sensitive, only parts of them.
For example, nothing is case-sensitive in the URL https://google.com,
With reference to RFC 3986 - Uniform Resource Identifier (URI): Generic Syntax
First, from Wikipedia, a URL looks like:
(I've removed the user:password part because it is not interesting ...
It's a little-known fact, but fully-qualified (unambiguous) DNS domain
names have a dot at the end. People running DNS servers usually know
this (if you miss the trailing dots out, your DNS configuration is
unlikely to work) but the general public usually doesn't. A domain
name that doesn't have a dot at the end is not fully-qualified ...
Simple. The OS is case sensitive. Web servers generally do not care unless they have to hit the file system at some point. This is where Linux and other Unix-based operating systems enforce the rules of the file system in which case sensitivity is a major part. This is why IIS has never been case sensitive; because Windows was never case sensitive.
Hostnames without a trailing dot are potentially ambiguous. A trailing dot means that the hostname is fully qualified and may not be relative to the local search domain.
Imagine you are a student of the (fictive) Example University which has the second-level domain example.edu. Inside the university's campus network you can omit the .example.edu suffix for ...
URL -- Uniform Resource Locator
Contains information about how to fetch a resource from its location. For example:
/other/link.html (A relative URL, only useful in the context of ...
I disagree with the comment that SEO is extremely complex. Actually, it is common sense stuff. There is no magic, voodoo, special formula, incarnations, specific sequence of buttons and switches, etc. You do not need the voodoo priestess Bloody Mary to come to your house or office. How search engines work is very simple and only a handful of techniques that ...
There are several reasons to remove extensions from URLs:
To make the URLs look cleaner
To make URLs easier to type
To make URLs easier to remember
To make URLs more SEO keyword friendly
To be able to change technologies -- if you ever want to move your site from one technology to the other, its easiest to do so without users even knowing if there are no ...
Yes, all mainstream browsers "append a slash" to the HTTP request when requesting a bare domain URL (ie. the homepage). This is actually necessary in order to make the HTTP request valid, which for http://example.com/ is:
GET / HTTP/1.1
Note the / (slash) in the first line - this is the URL being requested. It is not valid to have nothing ...
Google doesn't put much (if any) ranking weight directly on the keywords that are in the URL right now. Any effects on SEO with or without them are caused indirectly through user interaction and usability.
From a better usability standpoint:
Keywords in URLs can increase the clickthrough rate (CTR) from the SERPs. Check out these two search results for "...
Why 410 gone?
Since the page once existed the correct header status return would be 410 gone, this will inform Google and other search engines to drop the page from its index. You should avoid using status 400 bad request since this implies the server did not understand the request due to malformed syntax. Using undesirable status codes will populate your ...
A unix convention that represents a users homedirectory. Some providers allow users to get content from a certain directory in their home directory delivered by the webserver.
URLs claim to be a UNIFORM Resource locator and can point to resources
that predate the web. Some of these are case sensitive (eg many ftp servers)
and URLs need to be able to represent these resources in a reasonably intuitive fashion.
Case insensitivity requires more work when looking for a match (either in the OS or above it).
If you define URLs as case ...
The use of 'stop' words have never worked negatively unless it was considered excessive word spam... in the late 90's they were treated as noise and to some degree ignored. Thankfully times have changed and Google looks at common words completely different than it did almost 2 decades ago. I highly recommend SEO guides written in the past 2 years.
It's important to start a URL with a / so that the intended URL is returned instead of its parent or child.
Let's say if your browsing /cream-cakes/ then you have a link on the page that has blah.html without the forward slash it is going to attempt to visit page /cream-cakes/blah.html while with the forward slash it'll assume you mean the top level which ...
No, it will not affect the final letter case format of your domain whatever letter case you choose while registering it.
The Domain Name System (DNS) names is case insensitive and you can not manipulate this by any mean when you register it or even define it to search engines for "good looking" purposes.
All cases (upper and lower) will be accepted when ...
All questions on Stack Exchange contain a numeric ID (28070 for this question) which is the only thing that uniquely identifies a question.
So when a question title is changed, the URL such as /28070/old-question-title still shows the question because the ID is still there. The ID is looked up and the new title returned, meaning that the new URL can be ...
To know the age of an URL you can follow this link by replacing www.example.com by the URL you want:
For example, here's the result from Google for the Meta site of Stack Overflow:
Otherwise, the Wayback machine is ...
UPDATE Sept-2019: Google's recent changes to Google Search Console has made my original answer (below) a bit outdated and in some respects incorrect.
You can now submit two different types of properties in GSC:
"URL-prefix property", which is the same as the property type mentioned here. In this case you would still submit all variations as required, ie ...
Officially, yes. Any 4xx status may be interpreted as 400; the same goes for the other status groups. (E.g. a 503 service unavailable error may be interpreted as a 500 internal server error.)
The RFC is written this way to allow for implementations that may not support every status, and also to allow additional status codes to be defined without breaking ...
According to RFC 2616 (HTTP/1.1), section 3.2.2, the URLs http://www.example.com and http://www.example.com/ are equivalent, and HTTP clients must normalize the former to the latter before sending the request to the server:
"If the abs_path is not present in the URL, it MUST be given as "/" when used as a Request-URI for a resource (section 5.1.2)."
In the root of the directory of the subdomain website, add a file called robots.txt containing:
This will tell web crawlers not to index the site at all. They do not have to obey, but the main ones will.
In your header you have a canonical link (on line 11, just under <title>).
It looks like this on your page:
<link href="http://escene.ir/component/products/?task=view.12" rel="canonical" />
This element tells Google your preferred URL for a page which has several urls to choose from. This is to prevent you from being penalized for having ...
The web server software looks at the hostname in the HTTP request and uses that to determine which website to serve. For example, Apache has the NameVirtualHost configuration option which controls this behaviour. You can find a detailed explanation of how this process works in its documentation: https://httpd.apache.org/docs/2.2/vhosts/name-based.html
There is a book called, "In and Out of Africa". If Amazon used URIs the way you are questioning, the URI would be `https://amazon.com/Africa". How would that be helpful in searching for this one book?
Does that answer the question? Does this make you question your source?
Does the leading '/' mean the path is starting from the site root?
Technically this is referenced in section 4.2 of RFC 3986 as an "absolute-path reference":
A relative reference that begins with a single slash character is
termed an absolute-path reference.
It ensures the path is absolute to the root directory and not the current directory (termed a ...
Parenthesis are "reserved sub-delims" as defined by the RFC 3986. That means that the character may have special meaning in certain parts of the URL. Here is what the RFC says about how they should be treated:
URI producing applications should percent-encode data octets that
correspond to characters in the reserved set unless these characters
The problem with reusing a 301-URL is that some browsers will cache the redirect for a very long time, see, for example:
How long do browsers cache HTTP 301s?
301 Redirects: The Horror That Cannot Be Uncached
So, theoretically, there could be users that are automatically redirected from contact to contact-us, even though you have disabled the redirection ...