Google Search changes

Added the following sites to the index.

• http://eservices.ci.richmond.va.us/applications/boardscommissions/* departments
• http://eservices.ci.richmond.va.us/applications/parksearch/* departments
• http://eservices.ci.richmond.va.us/applications/PropertySalesSearch/* departments
• http://eservices.ci.richmond.va.us/applications/TaxSaleInquiry/* departments
• http://eservices.ci.richmond.va.us/applications/MBEBusinessDirectory/* departments

Speed Test

After Running Yslow I got the following results on the Assessors page.

Built a prototype that did work on CSS and JS. also had the expire header started on wwwdev. Letting it cook to see how it all goes.

New Blog for the Slave Trail Commission

The Slave Trail Commission was populated earlier in the week by Steven Skinner. the API feed was ported to http://www.richmondgov.com/content/CommissionSlaveTrail/index.aspx

Mobile Devices: RichmondGov.com to be presented on mobile devices

Source: http://webdesign.about.com/od/mobile/a/detect-mobile-devices.htm how to detect Mobile devices

Remembering that the site is separated by behavior, content and design allows for several approaches to be used and does not require awful ideas like maintaining two different sites.

Detecting browser types is a fine idea with desktop because you cover 99% of the ground with 5 or 6 browser concerns but with mobile devices this is not the case there is literally hundreds of mobile browsers. Several of them do not support JavaScript so using JavaScript to detect browser type is twice not a good idea. Most common method of solving for this problem is out.

Using CSS which is ALWAYS the preferred method of solving design problems. So there is the @media command that will adjust for a lot of the handheld devices that are not using standard browsers. this means that @handheld does not work for the iphone because it actually uses a standard version of safari and does not read as a handheld device.

There is also a more server side method using a server side programming language to detect user-agent and convert the style sheet accordingly.

Source: http://webdesign.about.com/od/mobile/a/write-web-pages-for-the-iphone.htm

Link to video: http://www.apple.com/iphone/internet/

Don't put your navigation at the very top of the screen. There is nothing more annoying than having to page through screens and screens of links to find the information you want. If you've looked at Web pages that were designed for cell phones, you'll see that the first things that show up are the content and headline. Then, below that is navigation.

What to Avoid When Designing for iPhones

There are several things you should avoid when building a mobile friendly page. As I mentioned above, if you really want to have these on your page, you can, but make sure that the site works without them.

Flash - most cell phones do not support Flash, so it's not a good idea to include it on your wireless pages.

Cookies - most cell phones have no cookie support. iPhones do have cookie support.

Frames - even if the browser supports them, think about the dimensions of the screen. Frames just don't work on mobile devices - they're very difficult or impossible to read.

Tables - don't use tables for layout on a mobile page. And try to avoid tables in general. They aren't supported on every cellphone (although iPhones and other smartphones support them) and you can end up with strange results.

Nested tables - if you must use a table, make sure not to nest it in another table. These are difficult for desktop browsers to support, and at best make the page load more slowly.

Absolute measures - in other words, don't define the dimensions of objects in absolute sizes (like pixels, millimeters, or inches). If you define something as 100px wide, on one mobile device that might be half the screen and on another it might be two times the width. Relative sizes (like ems and percentages) work best.

Fonts - don't assume that any of the fonts you're used to having access to will be available on the cell phones.

JS-Blogger-Client: inserted post

This is the body of the blog post. I can include HTML tags.

When is a 404 not a 404

After getting the Google Custom Search engine up and running on the richmondgov.com website it was only a matter of time before someone found a bad result. In my case it was my director who did a search on their name and had two bad results. One was a 404 and one was expired content. Expired content was easy I just needed to take that down but my adventure starts as I try to remove the item from the Google index.

So removing data from Google, I repeat to my self “hummmmm how do I remove a page from Google.” Well let’s start at Google webmaster tools the place that you set to groom the index for your site but a review of the central navigation of Webmaster Tools gave me no clue.

Well I had to do a web search on how to remove an page from Google. And lost to me now and I am sorry for that someone’s blog gave the address of the “Webpage removal request tool” which is a part of the Webmaster Tools, (why is that tool is not on the dash board I do not know.) here is the URL https://www.google.com/webmasters/tools/removals. Which was so very easy to use I do not feel the need to add a screen shot.

After submitting the two pages and waiting for a reply I was shocked that I was denied. In a shocked voice I repeated to myself denied, denied how dare they deny me don’t they know who I am. So after recovering my ego, I looked at the reason why. The google help tells me that you actually have to remove the item from your site to have it removed from Google’s index. So I go to my webpage and sure enough I am getting my custom 404 page telling the world that the stuff I removed form the page is no longer there. I think to myself, BAD Google I am right and you are wrong. Now how do I get them to realize my genius.

When is a 404 not a 404.

For the players at home that are not up with the new kids hip “lingo franka” what is server response codes and which one are we concerned with.

Most of the time the browser gets a 200 This status code indicates that the client's browser request was successfully received, understood, and accepted

Well the is a total of 4 other classes and if you want more information of them you can find it here http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html But the one that we want to keep in mind is the 400 class of which I will talk about here is the 404 and 410

404 – Not Found The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.

410 -- The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.

Well I am in the middle of the Google is bad research and after 16 different searches I start seeing a repeating term called a “Soft 404.” What is a soft 404 you ask, well hold on and I tell ya, Google put out an article that was titled “Farewell to soft 404’s” where they discourage the use of soft 404’s

see a good graphic of this here https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEigMSS_DFBysfX9w51wxcYi4rDg1xrBncv8J4F7s2VX4OiKlxjRZSsbITaAqeq8Ny_nr_8unz3E6et2zYqOAYUN1YyaBZGUqW1GKLmn8m0lZKfP6Hit9FLJk4BHZlEkTlp34Ws9LfByJG0/s1600-h/soft-404.png

This is what was written in the article

“As exemplified above, soft 404s are confusing for users, and furthermore search engines may spend much of their time crawling and indexing non-existent, often duplicative URLs on your site. This can negatively impact your site's crawl coverage—because of the time Googlebot spends on non-existent pages, your unique URLs may not be discovered as quickly or visited as frequently.”

http://googlewebmastercentral.blogspot.com/2008/08/farewell-to-soft-404s.html

Well of course IIS (which we use here) will be smart enough to know that the custom 404 page is a 404 and it is sending out the right server code, RIGHT? Well how do I check this. Trying to remember where I find the server response code, is it view code, nope, is it Firebug (I love firebug it has all the answers . . . ) Nope. Well back to google to find the how to see the server response code of any page. 10 Google results later I find HTTP Server Response Code Checker at http://www.searchenginepromotionhelp.com/m/http-server-response/code-checker.php

Well unlike the sample above I put in a page that should have returned a 404 but I got a 200 code. And I thought to myself “Dern! Again Google proofs themselves smart then me again.” So I know that I am putting out soft 404’s now what.

With the help of the Server Guy Justin, say hi to Justin everyone, we sit down in front of IIS and Google and try and fail, try and fail, try fail several settings and locations of files for the custom 404 file. And when your system is load balanced this is not as simple as it sounds, The amount of times that we asked “did I make that change on both machines?” boogles the mind. We figure out that the only solution was to use server code to change the “server response code.” We use asp.net and this is the code that we found worked for this problem on our machines. As always your results may vary. I am sorry I did not note whom I took this code from I would normally give credit for it. Remember never reinvent the wheel.

dim pageRequested

with request

pageRequested = _

mid(.queryString, instr(.queryString,";") + 1)

end with

response.status = "404 Not Found"

So know my next goal is to build up to the “perfect” custom 404 page, but right now it is just plan ugly.

Content update

http://www.richmondgov.com/applications/newbusinessarchive/newbusiness.asp
http://www.richmondgov.com/forms/forms/finance/EscrowApplicationForm.pdf
http://www.richmondgov.com/departments/police/fields/3rdPrecinct/S312.aspx
http://www.richmondgov.com/departments/police/index.aspx
http://www.richmondgov.com/departments/retirement/PF/presentations.aspx