Archive for category SEO
I was just in Jim Corbett Flash Player Internal v2 presentation at FITC and I learned a couple new facts about SEO that I wanted to share.
First, it now seems that Google will be indexing loaded files; that was intented for a while and I will still have to make some experiments to see if it really works but Adobe says it works. Well it doesn’t really work like they would want it to work: when Google sees that the SWF is loading a file, it doesn’t load it in the currently playing Flash file but it makes a note of it and will load and reference that content later. The text in there will still be associated with the previous url, but it won’t play in the right context. That last caveat doesn’t bother me much; my biggest concern was that all the work I do is preloaded by an external preloader, so none of my content was Flash SEO friendly. Now it will get indexed.
Another interesting fact that was kinda hinted in the presentation was that the SEO Flash player is not suppose to index text when it is out of bound of the stage; when the user doesn’t see it. But, if you put a button outside of the viewable area and that button will bring the SWF in a state where text is displaying on the stage(viewable), that text will be indexed. The problem is that the headless player doesn’t check if the button is viewable or not. This is not confirmed and I will also have to make tests on this.
Well I have to get back in there now.
I have been writing a lot of post lately about search engine optimization for flash and one thing I observed was that every time I put SEO in the title of my post, I get one random link that counts in my Technorati autorithy.
Now I guess I should mention that usually this is not a really valuable link. Most of the time it’s a link for a scrapper site; a site that research the internet and create post based on other’s content. I don’t think any human is involved in the content of those site. They are done in order to do money from ads on them without having to create any content. What is funny is that a lot of them are about SEO. My guess is that people that understand how Google works created these sites and the first subject that came to their mind is what they know: SEO.
As for Technorati autorithy, in my opinion it’s not something that’s worth too much. I mean I wouldn’t write something just to improve my authority. I also don’t know if its a really good metric; my artcile on InsideRIA had a link to my blog and it didn’t even raise my authority. How much visitors did technorati brung you in the last most anyway? Me, none.
But for those of you who cares about Technorati authority and don’t care where it comes from, now you know one way to improve it. As for me I guess my authority will increase.
I had previously made an SEO experiment to see what in Flash and in Flex was getting indexed by Google and I was able to get some results. Well, I decided to push the experiment further so I created seven new test cases both in Flash and in Flex. I have to warn you that I am more proficient in Flash than in Flex so my Flex test cases might be a bit off. Here are the new test cases (numbers start at 8 because I have already made 7 test cases):
Flash8. Static texfield embedded in the HTML using SWFObject 2.0
Expected result: I really don’t know, some rumors say it gets indexed anyway, Google says it doesn’t; this will shed some light.
9. Multiple static textfield on different frames
Expected result: From what I have seen before, Google will index the multiple texfields as if it was one text, so you could write a text with one word on each frame and it will appear as one.
10. Dynamic textfield prefilled with content after a preloader on the first frame
Expected result: I did this to see if the preloader would prevent the content from being indexed. Since Google is able to index Flex content with the default preloader, I think this test case will get indexed.
11. Dynamic textfield outside the viewing area
Expected result: I read that this was working, but with the new special player it shouldn’t. Let see what happens.
12. Simple custom MXML component
Expected result: I saved a Text component in its own MXML file and used that file in my main application. I think this will work because logically it’s like writing the second file(custom component) in the first one (application).
13. Using States
Expected result: I don’t think any of the content from this swf will be indexed because states use the words addChild in its mxml and I think(logically) this gets translated into the addChild function in AS3 and content added using addChild doesn’t get indexed.
14. Using the ViewStack component
Expected result: I think this has more chances to work than states but since this is a more complex component than the Text one I cannot say for sure.
Now that everything is set up, we just have to wait for Google to crawl those pages. The results and a general recap of the experiment will be posted in an article on InsideRIA.
It’s a pretty shocking title with all the fuss about the new flash player for Google and Yahoo, but I will try to explain why I came to this conclusion. I suggest you read about the seven test cases I did because that’s mostly what my reasoning is built on. I am going to explain point by point what happened in the experiment.
My first test case was simply to put static text right on the first frame of the swf file. That’s all this flash file contained. If you search in Google for the unique expression contained in that static text, you will find the specific html embedding the swf, meaning that the content was indexed.
The second test case was similar to the first one except that instead of being a static textfield on the stage, it’s a prefilled dynamic textfield (meaning the text in the textfield was added using the Flash IDE not ActionScript). Again for this case if you search the unique expression, the good html page will come up (As for the first case, you see in the description in Google for that link the extract of text containing the expression furthermore proving that the content was indexed).
The third test case was also a dynamic textfield, but the text in it was added using ActionScript. The page is indexed in Google (do a search for ‘site:www.fleximagically-searchable.com “fleximagically searchable”‘ and click “repeat the search with the omitted results included” at the bottom of the page to see all test case indexed) but the content doesn’t show in the description of the link. Also if you did a search for the unique expression nothing relevant would come up.
The fourth test case, the last done in Flash, was a static textfield inside a Sprite added to the stage using ActionScript. Again for this case the html page is indexed, but none of the Flash content is.
The fifth test case, as all of the next test cases, was done in Flex, it’s a TextArea component in mxml filled with the text attribute in the mxml, so no ActionScript involved. In this case, if you search for the unique expression you will see that the content inside the swf is indexed, proof that some content in Flex can be indexed.
The sixth test case is a Label component in mxml filled with the text attribute int the mxml. In this case, the content didn’t show up on Google, so I guess not all components are indexable.
Lastly, the seventh test case is a Text component in mxml filled with content using the text attribute in the mxml. I think this case is really similar to the second test case; a dynamic textfield in Flash prefilled with content. In this case, the content showed up on Google, so the swf was indexed.
From this SEO experiment, we see that static textfields on the timeline, prefilled dynamic textfields and some basic Flex components (TextArea, Text) in mxml are indexed by Google. It seems to me that as soon as there is ActionScript involved to change the content, that content will not be indexed. If you look back a bit, you kinda see that Google doesn’t use any new Flash player to index swf files, it does what it always was doing; nothing new. If somebody has a proof of dynamic content being indexed by the new player I’d be glad to see it, but for now I am assuming that Google is not using the new player given by Adobe.
This brings us to the Flex Seo contest, where my Fleximagically Searchable entry is performing well, but my content is not indexed. My take is that this contest will be pretty hard to win. There might still be possibilities to make this work but I think they are a bit too far fetched. Here is what I think might still have some chances: I did all my experiments with ActionScript 3 and I believe from the results that you cannot win using ActionScript 3. Where there could still be some opportunities would be if the swf generated would be using ActionScript 2 (which would use the flash player virtual machine 1), so in order to win the contest, you would have to build your Flex application in Flex 1.5 or even before. This would mean that the new special flash player for Google would only work for Flash 8 and below. I really hope it is not the case and that it is just that Google is not using the special player yet.
Another way to win would be that Google roll out the new player before September which is the ending date of the contest. Let’s hope they do so!
All my latest post have been about the Flex SEO contest, I’m sorry for those that don’t have interest in it, but I find it very challenging and fun.
From all the information that I have gathered from the web I have new insights about how to win this contest. If I was one of the other contestant of the contest I’d be sure to read my blog because I am giving info about how to win this contest all the time.
Another interesting fact is that for searches with the filetype swf (filetype:swf) Google is giving some importance to the url and the filename of the swf file. So if I really wanted to make things right, I would rename my Flex application for the contest fleximagically-searchable.swf, but I’ll wait until my content is indexed.
So in the light of these facts, I have modified my fleximagically searchable Flex application, go and have a look, it’s a so exciting application.
From previous posts you know that I am participating in the Flex SEO contest. I got my page pretty high on Google, but it still doesn’t seem to be finding my content. There are still a lot of unknown about this new SEO technology that Adobe, Google and Yahoo worked on and I think that to make a Flex application that load the content dynamically is to go a bit too fast.
So with that in mind I made simpler swf files. I even made some using Flash to see what would get indexed and how. In each of my experiments I have included a unique search expression basically formed from Fleximagically Searchable plus another word. If you search Google with that expression and one of my experiment shows up, it means Google indexed the content. Here are my experiments:
We don’t even know what type of swf is or is not indexed by Google so I sat down down and I made the simplest ones. Since Flex is pretty complex, I made some files using Flash.
The first one is only a static textfield right on the timeline. we know Google used to index those files, let’s see how it does it.
The second one is still in Flash using a prefilled dynamic textfield.
The third one is using a dynamic textfield again filled using ActionScript.
The fourth one is using a static textfield added to the stage using ActionScript.
Since we don’t know if Flex files get indexed at all, I made three simple experiments using basic components: TextArea, Label, Text. In those experiments the content is filled using the text attribute in the MXML file.
Flex file using TextArea.
Flex file using Label.
Flex file using Text.
Now let’s wait for Google to crawl these pages and then we will be able to better understand how this all works.
If you have been following this blog, you know that I entered the contest to get a Flex application on the top of Google for the words “Fleximagically Searchable”. The next logic step was for me to add deep-linking to my application, but it’s not what I am going to do. Why you could ask? Because even if the webpage for my application is appearing on Google, the content itself doesn’t seem to be included. So there is no meaning of implementing deep-linking if my content won’t be found.
I have set my self up for Flex application development and thanks to this post about how to use Flash Develop and Flex, I was able to do so quickly.
Yesterday I had simply created the HTML pages that would hold my application, today I created the application itself. It is quite a simple application and it is clearly a Flex one because of the skin of the components ( a button and a textarea). This will serve as a base for what is to come. The next step is to create the deep-linking. It has already some kind of deep-linking in the sense that you can go directly to this Fleximagically Searchable page. This page loads exactly the same swf than the page at the root of the domain, but I pass it a variable using SWFObject to tell it to load the content. If Google find any searchable content in any of those two pages, it means it comes from the dynamically loaded content because I removed everything in the HTML code except for the title of the page.
From what I did yesterday I am already getting some results, the new domain name I bought is scoring a ten (it is the tenth page for the term Fleximagically Searchable) and all the pages before it are blog posts (including one from this blog) that will not count in the contest so I guess I have my chances. Let’s see how it all evolves.
When I saw Ryan Stewart post about the Flex SEO contest this morning, I could not wait to get home to start working on this. The trouble is: we are currently working really hard to get a project out and I don’t really have time… There is always ways to find time, but taking crystal meth is not the best one. Since this is something I really do well I think I am going to put some energy into this.
I have written some SEO post in the past and I am way better at programming Flash then Flex but Ryan mentioned the possibility to win a pass for MAX, the Adobe conference, which I would really like to attend, so I think this is worth it. The goal of the contest is to create a Flex application that Google will index as the first link for the search terms : fleximagically searchable.
In order to do this I bought a domain name which has some advantages and some disadvantages. The domain name is http://www.fleximagically-searchable.com. Well the advantages are quite obvious, the domain name contain the search terms. This domain name also has a disadvantage, since it’s a new domain name, Google will sandbox it, meaning that it won’t be really searchable until about 6 months. You’ll be able to find it if you enter the exact address in Google, but it won’t have much weight against older site. I think I might try this on another domain name that I possess and is out of the Google sandbox, but for now, I’ll just try with this one.
Right now there isn’t much on the website but I will soon put the flex application there. I wanted to create the pages and this post now because the age of a page is one of the factor that Google uses to rank pages.
I find the rules for the contest not so clear, I don’t really now what I can and what I can’t do, but I’ll try stuff and we will see what happens. I will keep you posted on this.
I was mandated by a friend to optimize a flash website he had done for search engines. I had previously given him advices on how to start and he did follow some of them, but it just wasn’t enough so that’s why he asked me to finish the job.
Alex (the client) is a garage that specializes in tires and other mechanical services. I am writing this post for two reasons, one because I think a concrete example is easier to understand when trying to learn something, two because this actual article and the links it provides to Alex will help its search engine ranking.
Alex‘s situation is special; the major part (90%) of its traffic is coming from direct visits, meaning the visitor write www.alex.ca directly in their browser instead of going trough a search engine. 5% of visitors come from search engines and the last 5% from referring links, mostly other Alex websites.
So my objective was to increase significantly the traffic coming from search engines. To do that task I was assigned very little time so I have to concentrate on the factors that will have the most impact. One of these factors is the title of the pages. As I had instructed my friend, he had already created multiple html entry pages for this flash website. Trouble is that he had given each of them the same title. So I started by creating original title for each pages in relation to the destination inside the flash file.
Lastly for the modifying the website part I cleaned up the html a bit; there was a lot of dead links in the alternative content and that is not really good. All the pages where linking to an expressinstall.html page that didn’t exist. With this done I could go on with the next part of the optimization; creating inbound links.
One of the easiest ways to create inbound links for your website is to Digg it. When you Digg a page, it actually creates an intermediate page from Digg that link to your website. The Digg page for Alex is this one. Since Digg as a really good page rank and it links to your site, this will help your ranking a lot. Another site like that is StumbleUpon. After making these easy inbound links I put the website on local business directories.
The last thing I did was to create a sitemap.xml and put it on Google webmaster tools.
Well that’s about what you can do with 6 hours; I’ll keep you updated with the results of this optimization.