Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
How to contribute a "backend" page to Google Cache Browser
Clone this wiki locally
GCB heavily relies on "backend" pages, which must be present in Google Cache. This pages are essential to gain access to cached pages, but there is always a risk, that such page might be removed from Google index. If you have a site, you might host such page for me to make GCB more reliable.
Setting up a "backend" page for GCB.
There are simple steps to follow:
- Download proxy.html file to you computer.
- Edit text in it's body. You may put any kind of text there, but it would be better to be unique. Otherwise, there are high chances that Google won't index it. This step is optional but it'll help to get the page indexed.
- Upload it anywhere at your site to make it available to web server.
- Go to GCB feedback and send me URL of the page. See below for geeky version of this step.
- That's it, thank you!
Q1: How much load it would create for my server? What about traffic?
A1: It's negligible. Actually, it will take only few kilobytes of traffic from Google's crawler to get the page indexed. All visitors will be directed to cached version of the page, delivered by Google's CDN and all GCB resources will be loaded from GCB site (actually, it's GitHub's CDN).
Q2: Is it essential to get page indexed by Google?
A2: Absolutely. We need it to appear in Google's cache, so it must be indexed before.
Q3: How could I help to get the page indexed?
A3: The most reliable way is to put a link on this page somewhere in your site. It must be already indexed page, and frequently updated pages are most desirable, since Google visits them regularly and sucks up all links he finds there.
Q4: How load should I keep this link?
A4: Only until page gets indexed. Anyway, you might want to keep it as it would decreases chances that Google removes page from index and cache as well.
Q5: May I rename the page?
A5: Sure. But keep
.html extension, please.
The geeky way to send me a backend URL
If you have a GitHub account and you are a true geek, you could save me few minutes by doing this steps:
- Navigate to backend.js.
- Click on "Edit" button. This will also fork the repository to your account.
- Add new line into the array of backends following the template (note a comma at the beginning of line):
,'http://webcache.googleusercontent.com/search?q=cache%3A<here must be url-encoded address of your page>'
- Save and send me a pull request.
- Thank you very much!