Posted this in response to an internal email titled “What makes Google notice a blog?”, it’s pretty universal and applicable to most search engines so I thought I’d share it as a blog article.
Here’s a few suggestions, hope they help. Wayne.
1) You may want to write your blog in a manner which is spider, as well as human, friendly.
Include meta-data and micro-format information, such as tags; don’t forget that key words in headers will increase the ‘value’ of that key word (for many search engines); always make sure that “SCRIPT” HTML segments are followed by “NOSCRIPT” segments (most spiders don’t “do” JavaScript, specifically Google’s; lean web page code that is easy for spiders to ‘consume’.
Re: Tags / Meta-Data / Micro-Formats – I use the Operator plug in / add on for Firefox, this informs the user about semantic data embedded in a viewed web page.
Re: Keyword Analysis – I use the SeoQuake plug in / add on for Firefox, which allows me to do dynamic keyword (and related key word) analysis.
Here’s an article I wrote on Tag format standardization, I recommend that you standardize on a Tag format that is Search engine friendly: ‘Tic, Tag, Toe‘. Don’t over tag nor under tag, but try and match your articles tags with other similar articles, try and join in with the subject matter’s folksonomy if at all possible (i.e. the tags people are using when talking about that subject matter, technorati and delicious are both good examples).
As well as embedding all the tags for all of the articles on the front page (have a look in Operator if you decide to use it or another semantic data ‘explorer’) I also embed tags to major blog directories and social bookmarking sites on the individual page for each entry, here’s an article which demonstrates this: ‘Roller Weblogger blog post tag link code for blogs.sun.com, technorati and del.icio.us‘. I’ve superseded this code now, with a nicer layout and having added more blog directories / social bookmarking sites, you can see the example at the end of the page for any given blog article I’ve written, give me a shout if you’d like the newer code.
2) Google’s PageRank algorithms work on links, inbound, outbound, number, and the PageRank of those inbound and outbound links.
Link to sources, get inbound links from sources / reciprocal links if possible.
Don’t forget to trackback articles that you reference, if the trackback fails try leaving a comment with a link to the article that references it.
3) Make sure you let sites such as Google know you’ve updated your site and that you’d like it re-“spider”ed, indexed and advertised.
This is done by “blog pinging” search engines and blog directories so that they are informed that your site has been updated and to send over there spiders when they get chance (most search engines / blog directories want to do this quite quickly as they want to be first with any potentially newsworthy content that draws traffic).
Personally I wanted a more granular level of control over this than offered with the standard blog ping functionality embedded in roller and so I wrote my own stand alone version: ‘Free XML-RPC blog ping site submitter: “Blog Ping”‘.
4) Other things to consider…
PageRank of your site and individual pages; how well does your article compete with articles of a similar nature.
Have pages been bookmarked in del.ici.ous, technorati, etc., i.e. are they being shared.
P.S. This article doesn’t mention quality of written articles, cadence of posts, timeliness of posts to current events, etc., as it focuses purely on the current electronic mechanisms for getting noticed by a search engine like Google and not the related, but extremely important, human and social element that gains you readership.
Witness Interview(s) – The Banking Crisis – HoC Treasury Committee – www.parliamentlive.tv Treasury select committee told that the government’s top priority should be to restore the flow of credit through the economy whilst giving evidence on the banking crisis this week. …..
BBC NEWS | World | Europe | Czech EU art stokes controversy The latest art installation on display at the European Council building in Brussels has angered EU members with its lampoons of national stereotypes. …..
Web 2.0 or Blah 2.0? …..
This article was originally a guest post I did recently for Stewart Townsend over at Sun Startup Essentials describing the cloud relationship model I had developed as an artefact when discussing cloud computing.
I wanted a simply model which I could share with people and use as a discussion point, whilst still capturing the major areas of cloud computing which I considered most pertinent. I developed this model about six months ago and have since found it useful when talking with people about cloud computing.
Here’s the model and I’ll go though it’s major elements below.
In the cloud there are three major participants:
I think it’s important to talk about these communities because I keep hearing lots about the Cloud Providers, and even more about the issues and ‘needs’ of the Cloud adopters / developers, but very little in terms of Cloud “End” Users. In a computing eco-system such as this where “services” are supported by and transverse technology providers, service enablers and service consumers an end to end understanding of how this affects these reliant communities is required. Obvious issues such as SLAs for end users and businesses which rely upon high availability and high uptime from there cloud providers come to mind; however other “ilities” and systemic qualities come to mind such as security, and that’s before looking at any detailed breakdown of functional services.
The point here is that the cloud adopters / developers and interestingly the cloud “watchers” (i.e. the press, media, bloggers and experts) would be mindful to remember the needs and requirements of genuine end users; for myself it’d certainly be invigorating to hear more on this topic area.
Simon Wardley, a much more eloquent public speaker than myself, does a wonderful pitch which includes a look at the different “as a Service types” which he boils down to being a load of “*aaS” (very amusing, and informative, try and catch Simon presenting if you can).
I wholeheartedly agree that there is a large amount of befuddlement when it comes to the differing “*aaS” types and sub-types, and new ones are springing up relatively frequently, however I also think it’s important to not ignore the differences between them.
For me, and many others, I think first popularised by the “Partly Cloudy – Blue-Sky Thinking About Cloud Computing” white paper from the 451 Group, the differing “*aaS” variants are identified as billing and engagement models. That white paper also postulates the five major Cloud Computing provider models, into which the majority of minor “*aaS” variants fall. They are:
One of the best breakdowns and visual analysis of this space is the model in Peter Laird’s “Understanding the Cloud Computing/SaaS/PaaS markets: a Map of the Players in the Industry” article which is well worth a read.
Also included in the diagram are the major architectural layers that are included in each of the above billing / engagement models offered by the Cloud providers. They are:
This rather oversimplifies the architecture, as it’s important to note that each of the cloud billing / engagement models use capabilities from each of the above architectural layers; for instance their can be a lot of service simply in managing a network, however these describe the major architectural components (which support the service being procured), not simply ancillary functions, effectively what are the cloud providers customers principally paying for.
This is much more than the ‘gap’ between the cloud providers and the cloud users, wherein the cloud adopters / developers sit, the gap between the cloud providers and the end cloud users can be called the delta of effort, but also the delta of opportunity.
It is the delta of effort in terms of skills, abilities, experience and technology that the cloud adopter needs to deliver a functional service to their own “End Users”. This will be potentially a major area of cost to the cloud adopters. But it’s also the delta of opportunity;in terms of ‘room’ to innovate.
The more capability procured from the cloud provider (i.e. higher up the stack as a whole), the less you have to do (and procure) yourself. However the less procured from the cloud provider the more opportunity you have engineer a differentiating technology stack yourself. This itself has it’s disadvantages because the cloud adopters / developers could potentially not realise the true and best value of their cloud providers infrastructure.
I suspect that there is an optimum level, around the Platform Layer, which abstracts enough complexity away (i.e. you don’t have to procure servers, networks, implementation or technology operations staff), but also leaves enough room to innovate and produce software engineered value. Arguably the only current successful cloud provider, based upon market share, perception, revenue and customer take up, is Amazon Web Services (AWS) who provide a PaaS offering.
Hope you enjoyed the article, in summary if developing cloud services or even building out a cloud infrastructure I would recommend that you focus on your users and if your a cloud provider, your users’ users; remembering that only a certain percentage of those users will be customers (I won’t getting into discussing Chris Anderson’s 5% recommended conversion rate for the long tail, however I would recommend understanding what some of those calculations might be).
If you’re looking to develop services over the cloud, think carefully about where you and your teams skills lie, and where would you most want them focusing there efforts; working on installing and tuning operating systems and application platforms or writing business value focused applications and services, before choosing at which level to engage with your cloud provider(s).
I haven’t mentioned enterprise adoption of cloud based services, and
that’s because I’d like to post that in the near future in a different
article.
Hope you enjoyed the article and all the best,
Sun recently joined the BCS Group Membership Scheme and the BCS kindly produced a press release to accompany the occasion: “Sun Microsystems signs up for BCS Group Membership Scheme“.
I’m very glad that we’ve joined the scheme, for a number of reasons, primarily because it’s a great opportunity for staff enrichment and career enhancement. We’ve already had a number of individuals go forward for Charted IT Professional (CITP); interest and take up has been extremely good too.
Having spent sixteen years in the IT industry I feel that is important that we, as an industry, are promoted and represented by strong industry bodies, and reciprocally that we support them in turn; and personally I am a keen supporter of the “Professionalism in IT” agenda.
The press release has been getting some good exposure and has been picked up by PublicTechnology.net, TMCnet, Computerworld UK, M2, and even got a mention at the Parliamentary IT Commission (PITCOM) website.
There may well be more now if you Google about it.
If you have any questions you’d like to ask me about the scheme, whether your from Sun or another organisation, your welcome to get in touch.