Using Google's custom 404 page widget
- From the Select language: drop-down, select your language.
You can review our article on creating a custom 404 error page, if you're unsure of how you would creating or editing this file.
You also want to make sure that you're replacing the code you copied from Google, for the following:
var GOOG_FIXURL_SITE = 'http://www.example.com'
So that it uses your actual domain name instead of example.com, then just click on Save Changes if you're using the cPanel File Manager.
- Now if someone tried to access a page for instance on your domain such as /HowToContactUs that didn't exist, they'll be presented a Google search box for your website with those words already typed in. If Google has indexed a page of yours that mentions how to contact you, chances are the visitor will be able to find this using the Google search, instead of the visitor just being serverd a generic messages asking them to try a different page.
Now that you've successfully setup the Google custom 404 page widget, you might wish to also adjust the style of it to better fit in with the style of your website. You can do this by modifying the CSS code which is exaplained in Google's customizing the 404 widget page.
We value your feedback!
There is a step or detail missing from the instructions.
The information is incorrect or out-of-date.
It does not resolve the question/problem I have.
new! - Enter your name and email address above and we will post your feedback in the comments on this page!
2014-05-10 11:03 am
You might want to review this. The linked Google page has no dropdown, so it's basically useless.
2014-05-11 12:03 am
The link to the Google page does indeed seem to be missing the dropdown. However, the list of languages and their respective code snippets are there, although they are confusing. Each language has its own snippet so you will need to find it on the page.
It appears to be rather messy so we will investigate with Google to see if the current design is a mistake or intentional before we change the article here.
Thank you so much for pointing the discrepancy out!