Google Algorithm - What are the 200 Variables?

At PubCon, Matt Cutts mentioned that there were over 200 variables in the Google Algorithm.
I thought I’d start a list...
Domain
- Age of Domain
- History of domain
- KWs in domain name
- Sub domain or root domain?
- TLD of Domain
- IP address of domain
- Location of IP address / Server
Architecture
- HTML structure
- Use of Headers tags
- URL path
- Use of external CSS / JS files
Content
- Keyword density of page
- Keyword in Title Tag
- Keyword in Meta Description (Not Meta Keywords)
- Keyword in KW in header tags (H1, H2 etc)
- Keyword in body text
- Freshness of Content
Per Inbound Link
- Quality of website linking in
- Quality of web page linking in
- Age of website
- Age of web page
- Relevancy of page’s content
- Location of link (Footer, Navigation, Body text)
- Anchor text if link
- Title attribute of link
- Alt tag of images linking
- Country specific TLD domain
- Authority TLD (.edu, .gov)
- Location of server
- Authority Link (CNN, BBC, etc)
Cluster of Links
- Uniqueness of Class C address.
Internal Cross Linking
- No of internal links to page
- Location of link on page
- Anchor text of FIRST text link (Bruce Clay’s point at PubCon)
Penalties
- Over Optimisation
- Purchasing Links
- Selling Links
- Comment Spamming
- Cloaking
- Hidden Text
- Duplicate Content
- Keyword stuffing
- Manual penalties
- Sandbox effect (Probably the same as age of domain)
Miscellaneous
- JavaScript Links
- No Follow Links
Pending
- Performance / Load of a website
- Speed of JS
Misconceptions
- XML Sitemap (Aids the crawler but doesn’t help rankings)
- PageRank (General Indicator of page’s performance) 

Source

Web Application Vulnerability Scanner - Webvulscan

http://linuxpoison.blogspot.ca/2012/05/web-application-vulnerability-scanner.html
WebVulScan is a web application vulnerability scanner. It is a web application itself written in PHP and can be used to test remote, or local, web applications for security vulnerabilities. As a scan is running, details of the scan are dynamically updated to the user. These details include the status of the scan, the number of URLs found on the web application, the number of vulnerabilities found and details of the vulnerabilities found.

After a scan is complete, a detailed PDF report is emailed to the user. The report includes descriptions of the vulnerabilities found, recommendations and details of where and how each vulnerability was exploited.

The vulnerabilities tested by WebVulScan are:
 * Reflected Cross-Site Scripting
 * Stored Cross-Site Scripting
 * Standard SQL Injection
 * Broken Authentication using SQL Injection
 * Autocomplete Enabled on Password Fields
 * Potentially Insecure Direct Object References
 * Directory Listing Enabled
 * HTTP Banner Disclosure
 * SSL Certificate not Trusted
 * Unvalidated Redirects

WebVulScan Features:
 * Crawler: Crawls a website to identify and display all URLs belonging to the website.
 * Scanner: Crawls a website and scans all URLs found for vulnerabilities.
 * Scan History: Allows a user to view or download PDF reports of previous scans that they performed.
 * Register: Allows a user to register with the web application.
 * Login: Allows a user to login to the web application.
 * Options: Allows a user to select which vulnerabilities they wish to test for (all are enabled by default).
 * PDF Generation: Dynamically generates a detailed PDF report.
 * Report Delivery: The PDF report is emailed to the user as an attachment.

WebVulScan Installation:
Download the WebVulScan - here
NOTE: WebVulScan requires the following are installed:
A web server capable of running PHP web applications such as Apache, MySQL and PHP.

Place the folder containing the source code into the folder that your web server looks for to serve on your domain. In Apache this is the “/var/www” folder.
 * Import the database named “webvulscan.sql”, which is contained in the source code folder into your MySQL database.
 * The database credentials that the scanner is using are the “root” user with no password. If you want to change this it can be edited in “webvulscan_vx.xx/scanner/functions/databaseFunctions.php” in the connectToDb() function. The second and third parameter passed into the mysqli constructor are the username and password of a MySQL database user.  e.g. “root” and “”.
*For whatever user you are using in the connectToDb() function, you must ensure there is a corresponding database user in the database and they have sufficient privileges to read/write from/to the webvulscan database.

Once all done ... Using your browser, request “http://localhost/webvulscan_vx.xx”, where “webvulscan_vx.xx” is the folder containing the source code, and you will be brought to the homepage of the web application vulnerability scanner.