Google Plus is Google's Latest Social Network has launched on Tuesday, 29th June, 2011. It’s much like the Facebook News Feed, allowing users to share photos, videos, links or their location with friends.
Sunday, July 31, 2011
What are Keywords?
In the Search engines, you can type in one or more key words to search for the information you need. Within seconds, you got with a list of results. You can add some key words to narrow bottomward your choices, or you can start opening next and next and next page to find out if that page or site has the advice you need.
keywords that analyze what the page is about, usually acclimated in search engines. Keywords help search engines to categorize your site, and to allow people to find your pages more quickly.
keywords that analyze what the page is about, usually acclimated in search engines. Keywords help search engines to categorize your site, and to allow people to find your pages more quickly.
Saturday, July 30, 2011
List of HTTP Response Codes
1xx Informational
Request received, continuing process.
This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is terminated by an empty line. Since HTTP/1.0 did not define any 1xx status codes, servers must not send a 1xx response to an HTTP/1.0 client except under experimental conditions.
100 Continue
This means that the server has received the request headers, and that the client should proceed to send the request body (in the case of a request for which a body needs to be sent; for example, a POST request). If the request body is large, sending it to a server when a request has already been rejected based upon inappropriate headers is inefficient. To have a server check if the request could be accepted based on the request's headers alone, a client must send Expect:
100-continue as a header in its initial request and check if a 100 Continue status code is received in response before continuing (or receive 417 Expectation Failed and not continue).
101 Switching Protocols
This means the requester has asked the server to switch protocols and the server is acknowledging that it will do so.
102 Processing (WebDAV) (RFC 2518)
as a WebDAV request may contain many sub-requests involving file operations, it may take a long time to complete the request. This code indicates that the server has received and is processing the request, but no response is available yet. This prevents the client from timing out and assuming the request was lost.
122 Request-URI too long
This is a non-standard IE7-only code which means the URI is longer than a maximum of 2083 characters.
2xx Success
This class of status codes indicates the action requested by the client was received, understood, accepted and processed successfully.
200 OK
Standard response for successful HTTP requests. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request the response will contain an entity describing or containing the result of the action.
201 Created
Following a POST command, this indicates success, but the textual part of the response line indicates the URI by which the newly created document should be known.
202 Accepted
The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place.
203 Partial Information
When received in the response to a GET command, this indicates that the returned meta information is not a definitive set of the object from a server with a copy of the object, but is from a private overlaid web. This may include annotation information about the object, for example.
204 No Response
Server has received the request but there is no information to send back, and the client should stay in the same document view. This is mainly to allow input for scripts without changing the document at the same time.
205 Reset Content
The server successfully processed the request, but is not returning any content. Unlike a 204 response, this response requires that the requester reset the document view.
206 Partial Content
The server has fulfilled the partial GET request for the resource. The request MUST have included a Range header field indicating the desired range, and MAY have included an If-Range header field to make the request conditional.
If the 206 response is the result of an If-Range request that used a strong cache validator the response SHOULD NOT include other entity-headers. If the response is the result of an If-Range request that used a weak validator, the response MUST NOT include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers. Otherwise, the response MUST include all of the entity-headers that would have been returned with a 200 (OK) response to the same request.
A cache MUST NOT combine a 206 response with other previously cached content if the ETag or Last-Modified headers do not match exactly, A cache that does not support the Range and Content-Range headers MUST NOT cache 206 (Partial) responses.
207 Multi-Status (WebDAV) (RFC 4918)
The message body that follows is an XML message and can contain a number of separate response codes, depending on how many sub-requests were made.
226 IM Used (RFC 3229)
The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.
3xx Redirection
The client must take additional action to complete the request.
This class of status code indicates that further action needs to be taken by the user agent in order to fulfil the request. The action required may be carried out by the user agent without interaction with the user if and only if the method used in the second request is GET or HEAD. A user agent should not automatically redirect a request more than five times, since such redirections usually indicate an infinite loop.
300 Multiple Choices
Indicates multiple options for the resource that the client may follow. It, for instance, could be used to present different format options for video, list files with different extensions, or word sense disambiguation.
301 Moved Permanently
This and all future requests should be directed to the given URI.
302 Found
This is an example of industrial practice contradicting the standard. HTTP/1.0
specification (RFC 1945) required the client to perform a temporary redirect (the original describing phrase was "Moved Temporarily"), but popular browsers implemented 302 with the functionality of a 303 See Other. Therefore, HTTP/1.1 added status codes 303 and 307 to distinguish between the two behaviors. However, the majority of Web applications and frameworks still [as of?] use the 302 status code as if it were the 303.
303 See Other (since HTTP/1.1)
The response to the request can be found under another URI using a GET method. When received in response to a POST (or PUT/DELETE), it should be assumed that the server has received the data and the redirect should be issued with a separate GET message.
304 Not Modified
Indicates the resource has not been modified since last requested. Typically, the HTTP client provides a header like the If-Modified-Since header to provide a time against which to compare. Using this saves bandwidth and reprocessing on both the server and client, as only the header data must be sent and received in comparison to the entirety of the page being re-processed by the server, then sent again using more bandwidth of the server and client.
305 Use Proxy (since HTTP/1.1)
Many HTTP clients (such as Mozilla and Internet Explorer) do not correctly handle responses with this status code, primarily for security reasons.
306 Switch Proxy
No longer used.
307 Temporary Redirect (since HTTP/1.1)
In this occasion, the request should be repeated with another URI, but future requests can still use the original URI. In contrast to 303, the request method should not be changed when reissuing the original request. For instance, a POST request must be repeated using another POST request.
4xx Client Error
The 4xx class of status code is intended for cases in which the client seems to have erred. Except when responding to a HEAD request, the server should include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. These status codes are applicable to any request method. User agents should display any included entity to the user. These are typically the most common error codes encountered while online.
400 Bad request
The request had bad syntax or was inherently impossible to be satisfied.
401 Unauthorized
The request requires user authentication. Similar to 403 Forbidden, the page you were trying to access can not be loaded until you first log on with a valid user ID and password. If you have just logged on and received the 401 Unauthorized error, it means that the credentials you entered were invalid for some reason.
402 Payment Required
Reserved for future use. The original intention was that this code might be used as part of some form of digital cash or micro payment scheme, but that has not happened, and this code is not usually used. As an example of its use, however, Apple's MobileMe service generates a 402 error ("httpStatusCode:402" in the Mac OS X Console log) if the MobileMe account is delinquent.
403 Forbidden
The request was a legal request, but the server is refusing to respond to it. Unlike a 401 Unauthorized response, authenticating will make no difference.
404 Not Found
The requested resource could not be found but may be available again in the future. Subsequent requests by the client are permissible.
405 Method Not Allowed
A request was made of a resource using a request method not supported by that resource; for example, using GET on a form which requires data to be presented via POST, or using PUT on a read-only resource.
406 Not Acceptable
The requested resource is only capable of generating content not acceptable according to the Accept headers sent in the request.
407 Proxy Authentications Required
The Web server (running the Web site) thinks that the HTTP data stream sent from the client (e.g. your Web browser or our CheckUpDown robot) was correct, but access to the URL resource requires the prior use of a proxy server that needs some authentication which has not been provided. This typically means you must log in (enter user ID and password) with the proxy server first.
A 407 error detected via a Web browser can often be resolved by navigating to the URL in a slightly different way e.g. accessing another URL for the proxy server first. Your ISP should be able to explain the role of the proxy server in their security setup and how you should use it.
408 Request Timeout
Client stopped the request before the server finished retrieving it. A user will either hit the stop button, close the browser, or click on a link before the page loads. Usually occurs when servers are slow or file sizes are large.
409 Conflict
Indicates that the request could not be processed because of conflict in the request, such as an edit conflict.
410 Gone
Indicates that the resource requested is no longer available and will not be available again. This should be used when a resource has been intentionally removed and the resource should be purged. Upon receiving a 410 status code, the client should not request the resource again in the future. Clients such as search engines should remove the resource from their indices. Most use cases do not require clients and search engines to purge the resource, and a "404 Not Found" may be used instead.
411 Length Required
The request did not specify the length of its content, which is required by the requested resource.
412 Precondition Failed
The server does not meet one of the preconditions that the requester put on the request.
413 Request Entity Too Large
The request is larger than the server is willing or able to process.
414 Request-URI Too Long
The URI provided was too long for the server to process.
415 Unsupported Media Type
The request entity has a media type which the server or resource does not support. For example, the client uploads an image as image/svg+xml, but the server requires that images use a different format.
416 Requested Range Not Satisfiable
The client has asked for a portion of the file, but the server cannot supply that portion. For example, if the client asked for a part of the file that lies beyond the end of the file.
417 Expectation Failed
The server cannot meet the requirements of the Expect request-header field.
418 I'm a teapot
This code was defined in 1998 as one of the traditional IETF April Fools' jokes, in RFC 2324, Hyper Text Coffee Pot Control Protocol, and is not expected to be implemented by actual HTTP servers.
422 Unprocessable Entity (WebDAV) (RFC 4918)
The request was well-formed but was unable to be followed due to semantic errors.
423 Locked (WebDAV) (RFC 4918)
The resource that is being accessed is locked.
424 Failed Dependency (WebDAV) (RFC 4918)
The request failed due to failure of a previous request (e.g. a PROPPATCH).
425 Unordered Collection (RFC 3648)
Defined in drafts of "WebDAV Advanced Collections Protocol", but not present in "Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol".
426 Upgrade Required (RFC 2817)
The client should switch to a different protocol such as TLS/1.0.
444 No Response
A Nginx HTTP server extension. The server returns no information to the client and closes the connection (useful as a deterrent for malware).
449 Retry With
A Microsoft extension. The request should be retried after performing the appropriate action.
450 Blocked by Windows Parental Controls
A Microsoft extension. This error is given when Windows Parental Controls are turned on and are blocking access to the given webpage.
499 Client Closed Request
An Nginx HTTP server extension. This code is introduced to log the case when the connection is closed by client while HTTP server is processing its request, making server unable to send the HTTP header back.
5xx Server Error
The server failed to fulfill an apparently valid request.
Response status codes beginning with the digit "5" indicate cases in which the server is aware that it has encountered an error or is otherwise incapable of performing the request. Except when responding to a HEAD request, the server should include an entity containing an explanation of the error situation, and indicate whether it is a temporary or permanent condition. Likewise, user agents should display any included entity to the user. These response codes are applicable to any request method.
500 Internal Error
Couldn't retrieve the HTML document because of server-configuration problems. Contact site administrator.
501 Not Implemented
Web server doesn't support a requested feature.
502 Service Temporarily Overloaded
Server congestion; too many connections; high traffic. Keep trying until the page loads.
503 Service Unavailable
Server busy, site may have moved, or you lost your dial-up Internet connection.
504 Gateway Timeout
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
505 HTTP Version Not Supported
The server does not support the HTTP protocol version used in the request.
506 Variant Also Negotiates (RFC 2295)
Transparent content negotiation for the request results in a circular reference.
507 Insufficient Storage (WebDAV) (RFC 4918)
The Exchange server size limits are smaller than the size of the item we are attempting to migrate. For example, the size limit of the server is 10MB but the item has a 20MB attachment.
By default, Exchange Server has message size limits of 10MB. Although the Exchange server may accept delivery of items larger than 10MB via SMTP, MigrationWiz delivers emails using an email API which is subject to different size limits.
509 Bandwidth Limit Exceeded (Apache bw/limited extension)
This status code, while used by many servers, is not specified in any RFCs.
510 Not Extended (RFC 2774)
Further extensions to the request are required for the server to fulfill it.
Request received, continuing process.
This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is terminated by an empty line. Since HTTP/1.0 did not define any 1xx status codes, servers must not send a 1xx response to an HTTP/1.0 client except under experimental conditions.
100 Continue
This means that the server has received the request headers, and that the client should proceed to send the request body (in the case of a request for which a body needs to be sent; for example, a POST request). If the request body is large, sending it to a server when a request has already been rejected based upon inappropriate headers is inefficient. To have a server check if the request could be accepted based on the request's headers alone, a client must send Expect:
100-continue as a header in its initial request and check if a 100 Continue status code is received in response before continuing (or receive 417 Expectation Failed and not continue).
101 Switching Protocols
This means the requester has asked the server to switch protocols and the server is acknowledging that it will do so.
102 Processing (WebDAV) (RFC 2518)
as a WebDAV request may contain many sub-requests involving file operations, it may take a long time to complete the request. This code indicates that the server has received and is processing the request, but no response is available yet. This prevents the client from timing out and assuming the request was lost.
122 Request-URI too long
This is a non-standard IE7-only code which means the URI is longer than a maximum of 2083 characters.
2xx Success
This class of status codes indicates the action requested by the client was received, understood, accepted and processed successfully.
200 OK
Standard response for successful HTTP requests. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request the response will contain an entity describing or containing the result of the action.
201 Created
Following a POST command, this indicates success, but the textual part of the response line indicates the URI by which the newly created document should be known.
202 Accepted
The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place.
203 Partial Information
When received in the response to a GET command, this indicates that the returned meta information is not a definitive set of the object from a server with a copy of the object, but is from a private overlaid web. This may include annotation information about the object, for example.
204 No Response
Server has received the request but there is no information to send back, and the client should stay in the same document view. This is mainly to allow input for scripts without changing the document at the same time.
205 Reset Content
The server successfully processed the request, but is not returning any content. Unlike a 204 response, this response requires that the requester reset the document view.
206 Partial Content
The server has fulfilled the partial GET request for the resource. The request MUST have included a Range header field indicating the desired range, and MAY have included an If-Range header field to make the request conditional.
If the 206 response is the result of an If-Range request that used a strong cache validator the response SHOULD NOT include other entity-headers. If the response is the result of an If-Range request that used a weak validator, the response MUST NOT include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers. Otherwise, the response MUST include all of the entity-headers that would have been returned with a 200 (OK) response to the same request.
A cache MUST NOT combine a 206 response with other previously cached content if the ETag or Last-Modified headers do not match exactly, A cache that does not support the Range and Content-Range headers MUST NOT cache 206 (Partial) responses.
207 Multi-Status (WebDAV) (RFC 4918)
The message body that follows is an XML message and can contain a number of separate response codes, depending on how many sub-requests were made.
226 IM Used (RFC 3229)
The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.
3xx Redirection
The client must take additional action to complete the request.
This class of status code indicates that further action needs to be taken by the user agent in order to fulfil the request. The action required may be carried out by the user agent without interaction with the user if and only if the method used in the second request is GET or HEAD. A user agent should not automatically redirect a request more than five times, since such redirections usually indicate an infinite loop.
300 Multiple Choices
Indicates multiple options for the resource that the client may follow. It, for instance, could be used to present different format options for video, list files with different extensions, or word sense disambiguation.
301 Moved Permanently
This and all future requests should be directed to the given URI.
302 Found
This is an example of industrial practice contradicting the standard. HTTP/1.0
specification (RFC 1945) required the client to perform a temporary redirect (the original describing phrase was "Moved Temporarily"), but popular browsers implemented 302 with the functionality of a 303 See Other. Therefore, HTTP/1.1 added status codes 303 and 307 to distinguish between the two behaviors. However, the majority of Web applications and frameworks still [as of?] use the 302 status code as if it were the 303.
303 See Other (since HTTP/1.1)
The response to the request can be found under another URI using a GET method. When received in response to a POST (or PUT/DELETE), it should be assumed that the server has received the data and the redirect should be issued with a separate GET message.
304 Not Modified
Indicates the resource has not been modified since last requested. Typically, the HTTP client provides a header like the If-Modified-Since header to provide a time against which to compare. Using this saves bandwidth and reprocessing on both the server and client, as only the header data must be sent and received in comparison to the entirety of the page being re-processed by the server, then sent again using more bandwidth of the server and client.
305 Use Proxy (since HTTP/1.1)
Many HTTP clients (such as Mozilla and Internet Explorer) do not correctly handle responses with this status code, primarily for security reasons.
306 Switch Proxy
No longer used.
307 Temporary Redirect (since HTTP/1.1)
In this occasion, the request should be repeated with another URI, but future requests can still use the original URI. In contrast to 303, the request method should not be changed when reissuing the original request. For instance, a POST request must be repeated using another POST request.
4xx Client Error
The 4xx class of status code is intended for cases in which the client seems to have erred. Except when responding to a HEAD request, the server should include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. These status codes are applicable to any request method. User agents should display any included entity to the user. These are typically the most common error codes encountered while online.
400 Bad request
The request had bad syntax or was inherently impossible to be satisfied.
401 Unauthorized
The request requires user authentication. Similar to 403 Forbidden, the page you were trying to access can not be loaded until you first log on with a valid user ID and password. If you have just logged on and received the 401 Unauthorized error, it means that the credentials you entered were invalid for some reason.
402 Payment Required
Reserved for future use. The original intention was that this code might be used as part of some form of digital cash or micro payment scheme, but that has not happened, and this code is not usually used. As an example of its use, however, Apple's MobileMe service generates a 402 error ("httpStatusCode:402" in the Mac OS X Console log) if the MobileMe account is delinquent.
403 Forbidden
The request was a legal request, but the server is refusing to respond to it. Unlike a 401 Unauthorized response, authenticating will make no difference.
404 Not Found
The requested resource could not be found but may be available again in the future. Subsequent requests by the client are permissible.
405 Method Not Allowed
A request was made of a resource using a request method not supported by that resource; for example, using GET on a form which requires data to be presented via POST, or using PUT on a read-only resource.
406 Not Acceptable
The requested resource is only capable of generating content not acceptable according to the Accept headers sent in the request.
407 Proxy Authentications Required
The Web server (running the Web site) thinks that the HTTP data stream sent from the client (e.g. your Web browser or our CheckUpDown robot) was correct, but access to the URL resource requires the prior use of a proxy server that needs some authentication which has not been provided. This typically means you must log in (enter user ID and password) with the proxy server first.
A 407 error detected via a Web browser can often be resolved by navigating to the URL in a slightly different way e.g. accessing another URL for the proxy server first. Your ISP should be able to explain the role of the proxy server in their security setup and how you should use it.
408 Request Timeout
Client stopped the request before the server finished retrieving it. A user will either hit the stop button, close the browser, or click on a link before the page loads. Usually occurs when servers are slow or file sizes are large.
409 Conflict
Indicates that the request could not be processed because of conflict in the request, such as an edit conflict.
410 Gone
Indicates that the resource requested is no longer available and will not be available again. This should be used when a resource has been intentionally removed and the resource should be purged. Upon receiving a 410 status code, the client should not request the resource again in the future. Clients such as search engines should remove the resource from their indices. Most use cases do not require clients and search engines to purge the resource, and a "404 Not Found" may be used instead.
411 Length Required
The request did not specify the length of its content, which is required by the requested resource.
412 Precondition Failed
The server does not meet one of the preconditions that the requester put on the request.
413 Request Entity Too Large
The request is larger than the server is willing or able to process.
414 Request-URI Too Long
The URI provided was too long for the server to process.
415 Unsupported Media Type
The request entity has a media type which the server or resource does not support. For example, the client uploads an image as image/svg+xml, but the server requires that images use a different format.
416 Requested Range Not Satisfiable
The client has asked for a portion of the file, but the server cannot supply that portion. For example, if the client asked for a part of the file that lies beyond the end of the file.
417 Expectation Failed
The server cannot meet the requirements of the Expect request-header field.
418 I'm a teapot
This code was defined in 1998 as one of the traditional IETF April Fools' jokes, in RFC 2324, Hyper Text Coffee Pot Control Protocol, and is not expected to be implemented by actual HTTP servers.
422 Unprocessable Entity (WebDAV) (RFC 4918)
The request was well-formed but was unable to be followed due to semantic errors.
423 Locked (WebDAV) (RFC 4918)
The resource that is being accessed is locked.
424 Failed Dependency (WebDAV) (RFC 4918)
The request failed due to failure of a previous request (e.g. a PROPPATCH).
425 Unordered Collection (RFC 3648)
Defined in drafts of "WebDAV Advanced Collections Protocol", but not present in "Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol".
426 Upgrade Required (RFC 2817)
The client should switch to a different protocol such as TLS/1.0.
444 No Response
A Nginx HTTP server extension. The server returns no information to the client and closes the connection (useful as a deterrent for malware).
449 Retry With
A Microsoft extension. The request should be retried after performing the appropriate action.
450 Blocked by Windows Parental Controls
A Microsoft extension. This error is given when Windows Parental Controls are turned on and are blocking access to the given webpage.
499 Client Closed Request
An Nginx HTTP server extension. This code is introduced to log the case when the connection is closed by client while HTTP server is processing its request, making server unable to send the HTTP header back.
5xx Server Error
The server failed to fulfill an apparently valid request.
Response status codes beginning with the digit "5" indicate cases in which the server is aware that it has encountered an error or is otherwise incapable of performing the request. Except when responding to a HEAD request, the server should include an entity containing an explanation of the error situation, and indicate whether it is a temporary or permanent condition. Likewise, user agents should display any included entity to the user. These response codes are applicable to any request method.
500 Internal Error
Couldn't retrieve the HTML document because of server-configuration problems. Contact site administrator.
501 Not Implemented
Web server doesn't support a requested feature.
502 Service Temporarily Overloaded
Server congestion; too many connections; high traffic. Keep trying until the page loads.
503 Service Unavailable
Server busy, site may have moved, or you lost your dial-up Internet connection.
504 Gateway Timeout
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
505 HTTP Version Not Supported
The server does not support the HTTP protocol version used in the request.
506 Variant Also Negotiates (RFC 2295)
Transparent content negotiation for the request results in a circular reference.
507 Insufficient Storage (WebDAV) (RFC 4918)
The Exchange server size limits are smaller than the size of the item we are attempting to migrate. For example, the size limit of the server is 10MB but the item has a 20MB attachment.
By default, Exchange Server has message size limits of 10MB. Although the Exchange server may accept delivery of items larger than 10MB via SMTP, MigrationWiz delivers emails using an email API which is subject to different size limits.
509 Bandwidth Limit Exceeded (Apache bw/limited extension)
This status code, while used by many servers, is not specified in any RFCs.
510 Not Extended (RFC 2774)
Further extensions to the request are required for the server to fulfill it.
What is Keyword Density?
Keyword density is an SEO term that refers to a combination of the percentage of times a keyword or phrase, in proportion with other words, appears on a web page compared to the total number of words on the page.
Friday, July 29, 2011
Seo Abbreviations
A
Anchor
ABMs
Automated Bid Managers
ACS
Access Control Server
ACSS
Aural Cascading Style Sheets
AJ
Ask Jeeves (a search engine)
AOL
America Online (a search engine)
API
Application Programming Interface
ASCII
American Standard Code for Information Interchange
ASP
Microsoft Active Server Pages
Application Service Provider
ASPX
Microsoft Active Server Page Framework
ATW
AlltheWeb (a search engine)
AV
AltaVista (a search engine)
B2B
Business to Business
BL
Backlink
BO
Backlinks Obsession
BOW
Best of the Web
BSE
Bulk Solicited Email
CAPTCHA
Completely Automated Public Turing Tests to Tell Computers and Humans Apart
CGI-BIN
Common Gateway Interface
CMS
Content Management System
CPA
Cost Per Acquisition
Cost Per Action
CPC
Cost Per Click
CPL
Cost Per Lead
CPM
Cost Per Thousand
CPS
Cost Per Sale
CSS
Cascading Style Sheets
CTR
click thru rate
DNS
Domain Name System
DOS
Disk Operating System
EPC
Earnings Per Click
EXE
Executable
FAQ
Frequently Asked Question
FTP
File Transfer Protocol
G
Google
GAP
Google Advertising Professionals
GB - GIGABYTE
1,000,000,000 Bytes = 1,000 Megabytes
GIF
Graphics Interchange Format
GOOGOL
10100 = 1 followed by 100 zeros
GUI
Graphical User Interface
HTTP
Hypertext Transfer Protocol
HTTPS
HyperText Transfer Protocol Secure
IBL
Inbound Link
ICRA
Internet Content Rating Association
ILQ
Inbound link Quality
IM
Instant Messaging
In-House SEO
Any SEO working from home in their underwear or similar attire.
IP
Internet Protocol
ISAPI
Internet Server Application Program Interface
ISP
Internet Service Provider
IT
Information Technology
IYP
Internet Yellow Pages
JPG
Three letter file extension for Joint Photographic Experts Group
JS
Javascript (file.js)
JSP
Java Server Pages (file.jsp)
KB - KILOBYTE
1,024 Bytes
KBD
Keyboard: Text to be entered by the user.
KDA
Keyword Density Analyzer
KEI
Keyword Effectiveness Index (Wordtracker)
KW
Keyword
LAMP
Linux, Apache, MySQL, PHP / Perl / Python
LAN
Local Area Network
LPO
Landing Page Optimization
LSA
Latent Semantic Analysis
LSI
Latent Semantic Indexing
MB - MEGABYTE
1,000,000 Bytes
META
Generic Metadata: Information about information.
Metadata
Data about Data
MIME
Multipurpose Internet Mail Extensions
MMC
Microsoft Management Console
MSP
Managed Service Provider
MSSQL
Microsoft Sequel Server
MySQL
Popular Open Source Database
OBL
Outbound Link
ODP
Open Directory Project (a directory)
ORM
Online Reputation Management
OS
Operating System
PDF
Portable Document Format
PNG
Portable Network Graphics
PPC
Pay Per Click
PPV
Pay Per Visitor
PR
Google PageRank
PR0
PageRank Zero
PSD
PhotoShop Document
QWERTY (Pronounced KWER'TEE)
English Language Keyboard
Top Left Row of Keys
RAM
Random Access Memory
REP
Robots Exclusion Protocol
ROM
Read Only Memory
RSS
Really Simple Syndication
Rich Site Summary
RTF
Rich Text Format (file.rtf)
SAMP
Sample: Program output, scripts, etc.
SCRIPT
Script Statements: The SCRIPT element places a script within a document.
SE
Search Engine
SEM
Search Engine Marketeer
Search Engine Marketer
Search Engine Marketing
SEMPO
Search Engine Marketing Professional Organization
SEO
Search Engine Optimization
Search Engine Optimizer
Search Engine Overengineering
Semantic Emotion Optimization
Semantic Engagement Optimization
Semantically Enhanced Optimization
Sewage Enforcement Officer
SEP
Search Engine Placement
Search Engine Positioning
Search Engine Promotion
SERPs
Search Engine Results Pages
SEs
Search Engines
SES
Search Engine Strategies (a conference)
SEU
Search Engine Usability
SGML
Standard Generalized Markup Language
SIT
Stuffit Archive (file.sit) Macintosh File Compression Format
SMM
Social Media Marketing
SMO
Social Media Optimization
SMP
Social Media Profile
Social Media Profiling
SMTP
Simple Mail Transfer Protocol
SOAP
Simple Object Access Protocol
SOC
Source Ordered Content
SPAM
Sites Positioned Above Me
SPAM Food Products from Hormel Foods Corporation
SQL
Structured Query Language
SSI
Server Side Includes (file.shtml)
STATS
Statistics
SWF
Shockwave Flash (file.swf)
SYSOP
System Operator
T&C
Terms and Conditions
TCP
Transmission Control Protocol
TIF
Three letter file extension for Tagged Image File Format (file.tif)
TIFF
Tagged Image File Format (file.tiff)
TIF
Three letter file extension for Tagged Image File Format (file.tif)
TIFF
Tagged Image File Format (file.tiff)
TXT
Text File (file.txt)
UGC
User Generated Content
URI
Uniform Resource Indicator
URL
Uniform Resource Locator
URN
Uniform Resource Name
VBS
Visual Basic Script (file.vbs)
VEO
Visitor Engagement Optimization
W3
World Wide Web
W3C
World Wide Web Consortium
WAI
Web Accessibility Initiative
WAIS
Wide Area Information System
WAN
Wide Area Network
WAP
Wireless Application Protocol
WCAG
Web Content Accessibility Guidelines
WebDAV
Web-based Distributed Authoring and Versioning
WECA
Wireless Ethernet Compatibility Alliance
WiFi™
Wireless Fidelity (aka 802.11 Wireless Networking)
WIMP
Windows, Icons, Menus and Pointing Devices
WINDOWS NT
Windows New Technology
WML
Wireless Markup Language (file.wml)
WWW
World Wide Web
WYSINWOG
What You See Is Not What Others Get
WYSIWYG (Pronounced Wizzy'Wig)
What You See Is What You Get - Acronym associated with various HTML editors such as; FrontPage and Dreamweaver which are classified as WYSIWYG editors.
XAML
Extensible Application Markup Language (Microsoft Vista)
XHTML
Extensible Hypertext Markup Language
XML
Extensible Markup Language (file.xml)
XMLP
XML Protocol
XMP
Adobe Extensible Metadata Platform
XSL
Extensible Scripting Language (file.xsl)
XSLT
XSL Transformations (a language for transforming XML)
Y!
Yahoo! (a directory)
YB - YOTTABYTE
1,000,000,000,000,000,000,000,000 Bytes = 1,024 Zettabytes
ZB - ZETTABYTE
1,000,000,000,000,000,000,000 Bytes = 1,024 Exabytes
ZIP
Zipped File (file.zip) Windows File Compression Format
Anchor
ABMs
Automated Bid Managers
ACS
Access Control Server
ACSS
Aural Cascading Style Sheets
AJ
Ask Jeeves (a search engine)
AOL
America Online (a search engine)
API
Application Programming Interface
ASCII
American Standard Code for Information Interchange
ASP
Microsoft Active Server Pages
Application Service Provider
ASPX
Microsoft Active Server Page Framework
ATW
AlltheWeb (a search engine)
AV
AltaVista (a search engine)
B2B
Business to Business
BL
Backlink
BO
Backlinks Obsession
BOW
Best of the Web
BSE
Bulk Solicited Email
CAPTCHA
Completely Automated Public Turing Tests to Tell Computers and Humans Apart
CGI-BIN
Common Gateway Interface
CMS
Content Management System
CPA
Cost Per Acquisition
Cost Per Action
CPC
Cost Per Click
CPL
Cost Per Lead
CPM
Cost Per Thousand
CPS
Cost Per Sale
CSS
Cascading Style Sheets
CTR
click thru rate
DNS
Domain Name System
DOS
Disk Operating System
EPC
Earnings Per Click
EXE
Executable
FAQ
Frequently Asked Question
FTP
File Transfer Protocol
G
GAP
Google Advertising Professionals
GB - GIGABYTE
1,000,000,000 Bytes = 1,000 Megabytes
GIF
Graphics Interchange Format
GOOGOL
10100 = 1 followed by 100 zeros
GUI
Graphical User Interface
HTTP
Hypertext Transfer Protocol
HTTPS
HyperText Transfer Protocol Secure
IBL
Inbound Link
ICRA
Internet Content Rating Association
ILQ
Inbound link Quality
IM
Instant Messaging
In-House SEO
Any SEO working from home in their underwear or similar attire.
IP
Internet Protocol
ISAPI
Internet Server Application Program Interface
ISP
Internet Service Provider
IT
Information Technology
IYP
Internet Yellow Pages
JPG
Three letter file extension for Joint Photographic Experts Group
JS
Javascript (file.js)
JSP
Java Server Pages (file.jsp)
KB - KILOBYTE
1,024 Bytes
KBD
Keyboard: Text to be entered by the user.
KDA
Keyword Density Analyzer
KEI
Keyword Effectiveness Index (Wordtracker)
KW
Keyword
LAMP
Linux, Apache, MySQL, PHP / Perl / Python
LAN
Local Area Network
LPO
Landing Page Optimization
LSA
Latent Semantic Analysis
LSI
Latent Semantic Indexing
MB - MEGABYTE
1,000,000 Bytes
META
Generic Metadata: Information about information.
Metadata
Data about Data
MIME
Multipurpose Internet Mail Extensions
MMC
Microsoft Management Console
MSP
Managed Service Provider
MSSQL
Microsoft Sequel Server
MySQL
Popular Open Source Database
OBL
Outbound Link
ODP
Open Directory Project (a directory)
ORM
Online Reputation Management
OS
Operating System
Portable Document Format
PNG
Portable Network Graphics
PPC
Pay Per Click
PPV
Pay Per Visitor
PR
Google PageRank
PR0
PageRank Zero
PSD
PhotoShop Document
QWERTY (Pronounced KWER'TEE)
English Language Keyboard
Top Left Row of Keys
RAM
Random Access Memory
REP
Robots Exclusion Protocol
ROM
Read Only Memory
RSS
Really Simple Syndication
Rich Site Summary
RTF
Rich Text Format (file.rtf)
SAMP
Sample: Program output, scripts, etc.
SCRIPT
Script Statements: The SCRIPT element places a script within a document.
SE
Search Engine
SEM
Search Engine Marketeer
Search Engine Marketer
Search Engine Marketing
SEMPO
Search Engine Marketing Professional Organization
SEO
Search Engine Optimization
Search Engine Optimizer
Search Engine Overengineering
Semantic Emotion Optimization
Semantic Engagement Optimization
Semantically Enhanced Optimization
Sewage Enforcement Officer
SEP
Search Engine Placement
Search Engine Positioning
Search Engine Promotion
SERPs
Search Engine Results Pages
SEs
Search Engines
SES
Search Engine Strategies (a conference)
SEU
Search Engine Usability
SGML
Standard Generalized Markup Language
SIT
Stuffit Archive (file.sit) Macintosh File Compression Format
SMM
Social Media Marketing
SMO
Social Media Optimization
SMP
Social Media Profile
Social Media Profiling
SMTP
Simple Mail Transfer Protocol
SOAP
Simple Object Access Protocol
SOC
Source Ordered Content
SPAM
Sites Positioned Above Me
SPAM Food Products from Hormel Foods Corporation
SQL
Structured Query Language
SSI
Server Side Includes (file.shtml)
STATS
Statistics
SWF
Shockwave Flash (file.swf)
SYSOP
System Operator
T&C
Terms and Conditions
TCP
Transmission Control Protocol
TIF
Three letter file extension for Tagged Image File Format (file.tif)
TIFF
Tagged Image File Format (file.tiff)
TIF
Three letter file extension for Tagged Image File Format (file.tif)
TIFF
Tagged Image File Format (file.tiff)
TXT
Text File (file.txt)
UGC
User Generated Content
URI
Uniform Resource Indicator
URL
Uniform Resource Locator
URN
Uniform Resource Name
VBS
Visual Basic Script (file.vbs)
VEO
Visitor Engagement Optimization
W3
World Wide Web
W3C
World Wide Web Consortium
WAI
Web Accessibility Initiative
WAIS
Wide Area Information System
WAN
Wide Area Network
WAP
Wireless Application Protocol
WCAG
Web Content Accessibility Guidelines
WebDAV
Web-based Distributed Authoring and Versioning
WECA
Wireless Ethernet Compatibility Alliance
WiFi™
Wireless Fidelity (aka 802.11 Wireless Networking)
WIMP
Windows, Icons, Menus and Pointing Devices
WINDOWS NT
Windows New Technology
WML
Wireless Markup Language (file.wml)
WWW
World Wide Web
WYSINWOG
What You See Is Not What Others Get
WYSIWYG (Pronounced Wizzy'Wig)
What You See Is What You Get - Acronym associated with various HTML editors such as; FrontPage and Dreamweaver which are classified as WYSIWYG editors.
XAML
Extensible Application Markup Language (Microsoft Vista)
XHTML
Extensible Hypertext Markup Language
XML
Extensible Markup Language (file.xml)
XMLP
XML Protocol
XMP
Adobe Extensible Metadata Platform
XSL
Extensible Scripting Language (file.xsl)
XSLT
XSL Transformations (a language for transforming XML)
Y!
Yahoo! (a directory)
YB - YOTTABYTE
1,000,000,000,000,000,000,000,000 Bytes = 1,024 Zettabytes
ZB - ZETTABYTE
1,000,000,000,000,000,000,000 Bytes = 1,024 Exabytes
ZIP
Zipped File (file.zip) Windows File Compression Format
Thursday, July 28, 2011
Who is Matt Cutts?
Matt Cutts joined Google as a software engineer in January 2000, at the time the company had less than 100 employees.. He is currently the head of Google's Web-spam team.
Before Google, He worked on Ph.D. in computer graphics at the University of North Carolina at Chapel Hill. He have an M.S. from UNC-Chapel Hill, and B.S. degrees in both mathematics and computer science from the University of Kentucky.
He wrote the first version of Safe-search, which is Google's family filter, and works for the Search Quality group in Google, specializing in search engine optimization issues.
He is well known in the SEO community for enforcing the Google Webmaster Guidelines and cracking down on link spam.
Matt Cutts also advises the public on how to get better website visibility in Google as well as webmaster issues in general, and is generally an outspoken and public face of Google.
Before Google, He worked on Ph.D. in computer graphics at the University of North Carolina at Chapel Hill. He have an M.S. from UNC-Chapel Hill, and B.S. degrees in both mathematics and computer science from the University of Kentucky.
He wrote the first version of Safe-search, which is Google's family filter, and works for the Search Quality group in Google, specializing in search engine optimization issues.
He is well known in the SEO community for enforcing the Google Webmaster Guidelines and cracking down on link spam.
Matt Cutts also advises the public on how to get better website visibility in Google as well as webmaster issues in general, and is generally an outspoken and public face of Google.
Wednesday, July 27, 2011
Social Profile Creation
Profile creation account is One of the main techniques builds high volumes of inbound links to your website by utilizing the assorted social platforms available on the web, an advancing object is to register and create multiple forum profiles on social platforms, forums, discussion blogs, community websites and other available sources.
Individually these links are relatively low value, but the accumulated after effect of multiple profiles actual bound builds link juice, they frequently appearance a very quick movement in the search engine rankings as a result.
Individually these links are relatively low value, but the accumulated after effect of multiple profiles actual bound builds link juice, they frequently appearance a very quick movement in the search engine rankings as a result.
Article Sites with PageRank
Subscribe to:
Posts (Atom)
Top Stories
-
The Fascinating Dimension about Forum Posting Discussion Boards or Forums are online networking communities. The fascinating dimension ...
-
Google publishes a report that shares how it catches fake business reviews and profile. Google published a blog post that shared that they...
-
What is Digital (online) Marketing? How it matters? In Marketing your goals of your business is satisfying your customers and keep th...
-
Accelerated Mobile Pages (AMP) is out and has been speculated to have two benefits for SEO . One is it will have a “Fast” label designatio...
-
Welcome Back Guys after a very long time!! Learn how to improve your website's ranking on search engines with these top SEO techniques....
-
What is web hosting? How it Works?? Web Hosting Web hosting is a service that permits business and people to feed a web site or websi...
-
Link Risk Management: Are You Using This Critical SEO Tactic? Columnist Stephan Spencer warns that if you don't regularly monitor y... -
Google News-driven results send over 24 billion clicks per month to publishers. Here's how to claim your share. Let’s set the record ... -
How to Use Google Analytics Site Search Reports If your website has a search bar, you need to ensure you’re making the most of this v...
-
As a SEO Professional you will know all the major importance of SEO and what you have to do for a website to generate and increase traffi...
