Web xojo and SEO

Hi everyone. I am starting to study web xojo now, it is very interesting. I am planning to create at first small apps that will be referenced by my main site by links or iframes (if possible)
My main domain server is incapable of running xojo apps, so I think I will use another domain and install all apps in another server (maybe 1701 because of price). I won’t change my primary server as it is super optimized for the CMS I am using (Drupal).
Of course development of these apps should increase my main domain visibility. They will be more visible for real people, because of their function, but how SEO works with web apps designed by xojo? How the net bots see them?
What are SEO implications in this setup?
Google will point directly to the app, or to my main domain?
If people start back linking the app instead of my main domain, isnt that bad? Any ideas to avoid that?
Does Google recognize links I create inside the app?
Any way to do in page SEO? Like meta tags, keywords, etc?
If I use iframes is it better to my main domain?
Does xojo web apps works with iframes?
Is there any way to display the URL of my main domain instead of the app URL?
Thanks a lot
Happy new year!

[quote=306475:@Alexandre Amato]Does Google recognize links I create inside the app?
Any way to do in page SEO? Like meta tags, keywords, etc?[/quote]

GoogleBot is an unsupported browser, and besides, is incapable to click buttons in the app.

The best you can do is to create a sitemap, which points to each page with parameters that point to a particular page inside the app.

http://mysite.com/cgi-bin/myapp.cgi/?page=1 http://mysite.com:8080/?page=1

No, it is not bad. The whole interest of search is to access directly what you want. Most of my visitors access out of the front page.

Yes, it works with iframes, you simply have to authorize it in App.Security.

[quote=306485:@Michel Bujardet]GoogleBot is an unsupported browser, and besides, is incapable to click buttons in the app.

The best you can do is to create a sitemap, which points to each page with parameters that point to a particular page inside the app.
[/quote]
Not true! One of the reasons we added App.HandleUrl was so that you could respond to search engine queries! You’ll have to be careful but many of the search engines have rules for adding web apps and what you should return.

At any rate, a site map is the best way for the bot to find what you want it to reference.

So, just a thought, maybe an universal sitemap module would be possible?

You want to read this :
https://static.googleusercontent.com/external_content/untrusted_dlcp/www.google.co.uk/en/uk/webmasters/docs/search-engine-optimization-starter-guide.pdf

The way bots work is by checking first that they can scan the site by reading /robots.txt, then they proceed to /sitemap.xml

sitemap.xml is just a list of the pages accessible on the site, with their URL.

Using HandleURL as recommended by Greg means delivering in pure HTML the content of the app’s page for the robot to scan and index. Meaning that if your app has, say 10 pages, each virtual directory would correspond to a page :

http://127.0.0.1:8080/Page1

and so on.

The tricky part is to recognize the browser when it hits handleURL, and if it is not a robot, send to a page of the app.

http://127.0.0.1:8080/?Page=2

This can be done in JavaScript. Then in Session Open, you want to look at parameters, and according to the page parameter value, open the corresponding WebPage.

It means you have to prepare the HTML content for HandleURL, and conceive your app so a visitor can hit any one of the pages inside, not necessarily the opening WebPage.

You will then have to fill the sitemap.xml according to the number of pages available.

I have to confess I prefer to use plain HTML for content I want indexed by search engines. So using an iFrame can be convenient in that context. Moreover, web apps usually have less indexable content (words) than regular HTML pages.

Here is an example of sitemap : http://charmenu.com/sitemap.xml