A URL is the address of a file on the Web, such as www.example.com, or foo.example.com.
During the blog creation process, you'll have to select a URL for your blog. Visitors can access your blog by typing this URL into the address bar of their browsers.
Since there are already a large number of Blogspot blogs, you'll need to get creative and possibly try a few different URLs before you find one that's available. The format for your URL will be nameyouchoose.blogspot.com.
When selecting your blog's URL, remember that you can only use letters, numbers, and hyphens. Special characters such as $, #, &, etc. are not permitted.
You can also host your blog on a custom domain.
From Wiki: In computing, a Uniform Resource Locator (URL) is a Uniform Resource Identifier (URI) that specifies where a known resource is available and the mechanism for retrieving it. It is also referred to as a Universal Resource Locator and in many technical documents and verbal discussions it is often used as a synonym for URI.
History
The Uniform Resource Locator was created in 1994 by Tim Berners-Lee and the URI working group of the Internet Engineering Task Force as an outcome of collaboration started at the IETF Living Documents BoF in 1992. The format combines[citation needed] the pre-existing system of Domain Names (created in 1985) with Unix file path syntax, where forward slashes are used to separate folder and file names. Conventions already existed where server names could be prepended to complete file paths, preceded by a double-slash (//).
File formats may also be specified using a final dot suffix, so that requests for file.html or file.txt may be served directly whereas file.php needs to be sent to a PHP pre-processor before the processed result is served to the end user. The exposure of such implementation-specific details in public URLs is becoming less common; the necessary information can be better specified and exchanged using Internet media type identifiers, previously known as MIME types.
Berners-Lee later regretted the use of dots to separate the parts of the domain name within URIs, wishing he had used slashes throughout. Berners-Lee has also said that, given the colon following the URI scheme, the two forward slashes before the domain name were unnecessary. For example, http://www.example.com/path/to/name would have been written http:com/example/www/path/to/name.
Syntax
Every URL consists of some of the following: the scheme name (commonly called protocol), followed by a colon, then, depending on scheme, a domain name (alternatively, IP address), a port number, the path of the resource to be fetched or the program to be run, then, for programs such as Common Gateway Interface (CGI) scripts, a query string,[8][9] and an optional fragment identifier. The syntax is scheme://domain:port/path?query_string#fragment_id
The scheme name defines the namespace, purpose, and the syntax of the remaining part of the URL. Software will try to process a URL according to its scheme and context. For example, a web browser will usually dereference the URL http://example.org:80 by performing an HTTP request to the host at example.org, using port number 80. The URL mailto:bob@example.com may start an e-mail composer with the address bob@example.com in the To field.
Other examples of scheme names include https:, gopher:, wais:, ftp:. URLs with https as a scheme (such as https://example.com/) require that requests and responses will be made over a secure connection to the website. Some schemes that require authentication allow a username, and perhaps a password too, to be embedded in the URL, for example ftp://asmith@ftp.example.org. Passwords embedded in this way are not conducive to secure working, but the full possible syntax is scheme://username:password@domain:port/path?query_string#fragment_id
The domain name or IP address gives the destination location for the URL. The domain google.com, or its IP address 72.14.207.99, is the address of Google's website.
The path is used to specify and perhaps find the resource requested. It is case-sensitive, though it may be treated as case-insensitive by some servers, especially those based on Microsoft Windows. If the server is case sensitive and http://en.example.org/wiki/URL is correct, http://en.example.org/WIKI/URL/ or http://en.example.org/wiki/url/ will display an HTTP 404 error page, unless these URLs point to valid resources themselves.
The query string contains data to be passed to software running on the server. It may contain name/value pairs separated by ampersands, for example ?first_name=John&last_name=Doe.
The fragment identifier, if present, specifies a part or a position within the overall resource or document. When used with HTTP, it usually specifies a section or location within the page, and the browser may scroll to display that part of the page.
Hope this was helpful,
The PushYourRank Team
Author: Nicholas Coriano
About The Author: Nicholas Coriano is an Entrepreneur, Web Developer, Social Media Marketer, SEO Consultant and the founder of this blog and The NewYorkWebsiteDesignCenter.com. While developing websites for his own businesses and marketing his entrepreneurial ventures online, he began blogging useful tips and "how-to" articles on PushYourRank.com for reference purposes. To retain Nicholas for help with your Website, Social Media, SEO or other online/technology needs, email PushYourRank@Gmail.com
About PushYourRank.com: PushYourRank.com (the Blog) is a blog that helps small businesses, start-ups, developers, amateurs website builders, bloggers and entrepreneurs develop their websites, their social media presence, their search engine optimization techniques and more ....online. The Blog publishes articles about Ecommerce, Email Marketing and How To Make Money Online...as well as any topic that pertains to the Internet or Online. If you need help developing a website, SEO or Social Media outsourcing, see NewYorkWebsiteDesignCenter.com, if you would like to advertise or have us publish an article on a certain subject, please email us at PushYourRank@Gmail.com
During the blog creation process, you'll have to select a URL for your blog. Visitors can access your blog by typing this URL into the address bar of their browsers.
Since there are already a large number of Blogspot blogs, you'll need to get creative and possibly try a few different URLs before you find one that's available. The format for your URL will be nameyouchoose.blogspot.com.
When selecting your blog's URL, remember that you can only use letters, numbers, and hyphens. Special characters such as $, #, &, etc. are not permitted.
You can also host your blog on a custom domain.
From Wiki: In computing, a Uniform Resource Locator (URL) is a Uniform Resource Identifier (URI) that specifies where a known resource is available and the mechanism for retrieving it. It is also referred to as a Universal Resource Locator and in many technical documents and verbal discussions it is often used as a synonym for URI.
History
The Uniform Resource Locator was created in 1994 by Tim Berners-Lee and the URI working group of the Internet Engineering Task Force as an outcome of collaboration started at the IETF Living Documents BoF in 1992. The format combines[citation needed] the pre-existing system of Domain Names (created in 1985) with Unix file path syntax, where forward slashes are used to separate folder and file names. Conventions already existed where server names could be prepended to complete file paths, preceded by a double-slash (//).
File formats may also be specified using a final dot suffix, so that requests for file.html or file.txt may be served directly whereas file.php needs to be sent to a PHP pre-processor before the processed result is served to the end user. The exposure of such implementation-specific details in public URLs is becoming less common; the necessary information can be better specified and exchanged using Internet media type identifiers, previously known as MIME types.
Berners-Lee later regretted the use of dots to separate the parts of the domain name within URIs, wishing he had used slashes throughout. Berners-Lee has also said that, given the colon following the URI scheme, the two forward slashes before the domain name were unnecessary. For example, http://www.example.com/path/to/name would have been written http:com/example/www/path/to/name.
Syntax
Every URL consists of some of the following: the scheme name (commonly called protocol), followed by a colon, then, depending on scheme, a domain name (alternatively, IP address), a port number, the path of the resource to be fetched or the program to be run, then, for programs such as Common Gateway Interface (CGI) scripts, a query string,[8][9] and an optional fragment identifier. The syntax is scheme://domain:port/path?query_string#fragment_id
The scheme name defines the namespace, purpose, and the syntax of the remaining part of the URL. Software will try to process a URL according to its scheme and context. For example, a web browser will usually dereference the URL http://example.org:80 by performing an HTTP request to the host at example.org, using port number 80. The URL mailto:bob@example.com may start an e-mail composer with the address bob@example.com in the To field.
Other examples of scheme names include https:, gopher:, wais:, ftp:. URLs with https as a scheme (such as https://example.com/) require that requests and responses will be made over a secure connection to the website. Some schemes that require authentication allow a username, and perhaps a password too, to be embedded in the URL, for example ftp://asmith@ftp.example.org. Passwords embedded in this way are not conducive to secure working, but the full possible syntax is scheme://username:password@domain:port/path?query_string#fragment_id
The domain name or IP address gives the destination location for the URL. The domain google.com, or its IP address 72.14.207.99, is the address of Google's website.
The domain name portion of a URL is not
case sensitive since DNS ignores case: http://en.example.org/ and
HTTP://EN.EXAMPLE.ORG/ both open the same page.
The
port number is optional; if omitted, the default for the scheme is used.
For example, http://vnc.example.com:5800 connects to port 5800 of
vnc.example.com, which may be appropriate for a VNC remote control
session. If the port number is omitted for an http: URL, the browser
will connect on port 80, the default HTTP port. The default port for an
https: request is 443.The path is used to specify and perhaps find the resource requested. It is case-sensitive, though it may be treated as case-insensitive by some servers, especially those based on Microsoft Windows. If the server is case sensitive and http://en.example.org/wiki/URL is correct, http://en.example.org/WIKI/URL/ or http://en.example.org/wiki/url/ will display an HTTP 404 error page, unless these URLs point to valid resources themselves.
The query string contains data to be passed to software running on the server. It may contain name/value pairs separated by ampersands, for example ?first_name=John&last_name=Doe.
The fragment identifier, if present, specifies a part or a position within the overall resource or document. When used with HTTP, it usually specifies a section or location within the page, and the browser may scroll to display that part of the page.
Hope this was helpful,
The PushYourRank Team
Author: Nicholas Coriano
About The Author: Nicholas Coriano is an Entrepreneur, Web Developer, Social Media Marketer, SEO Consultant and the founder of this blog and The NewYorkWebsiteDesignCenter.com. While developing websites for his own businesses and marketing his entrepreneurial ventures online, he began blogging useful tips and "how-to" articles on PushYourRank.com for reference purposes. To retain Nicholas for help with your Website, Social Media, SEO or other online/technology needs, email PushYourRank@Gmail.com
About PushYourRank.com: PushYourRank.com (the Blog) is a blog that helps small businesses, start-ups, developers, amateurs website builders, bloggers and entrepreneurs develop their websites, their social media presence, their search engine optimization techniques and more ....online. The Blog publishes articles about Ecommerce, Email Marketing and How To Make Money Online...as well as any topic that pertains to the Internet or Online. If you need help developing a website, SEO or Social Media outsourcing, see NewYorkWebsiteDesignCenter.com, if you would like to advertise or have us publish an article on a certain subject, please email us at PushYourRank@Gmail.com