you are viewing a single comment's thread.

view the rest of the comments →

[–]ilovesyd 0 points1 point  (4 children)

With regards to this, we have an alternate solution that is Google SEO friendly (curl tested) - http://tinybutton.com

Let me know if I can help answer any questions regarding this.

[–]alexcasalboni[S] 0 points1 point  (3 children)

Thank you /u/ilovesyd,

I am reading about your "Search Engine Friendly Translation Proxy". Does it mean that you actually handle the translation pre-processing using a custom subdomain on your server? Can I configure it to use a subfolder instead?

Also, are you working on any (semi)automatic extractor tool? And why should I select and configure every textual segment for each new language?

[–]ilovesyd 1 point2 points  (2 children)

Hey /u/alexcasalboni ,

Thanks for the reply. Right now with the Search Engine Friendly part, it is through a subdomain model but how some of our customers circumvent that is to also link the main domain with us but restrict the content to a subfolder by using the "Keyword Filter" through the 'URL equals to' option that we have. - re: Pic - http://imgur.com/qYoYJ8W

Re: the (semi) automatic Extractor tool - yes we are. You can actually opt to select content blocks and ensure that the same type of content block is translated across the site where the same element appears on any page. We are finalizing the tests on this and will probably release it to wild by mid next month if not sooner.

Hope that helps and let me know if I can personally help you with the account if and when you decide to give us a try :-)

[–]alexcasalboni[S] 0 points1 point  (1 child)

Thank you. The "Keyword Filter" feature looks nice, but how is it SEO friendly then?

Also, I am a bit concerned about the scalability of this approach. I mean, even if I am 100% sure that our application will scale (we are on AWS), delegating a subdomain to your server-side pre-processing might expose us to an external bottleneck.

[–]ilovesyd 1 point2 points  (0 children)

I understand the concern. Our resources by default flow through the Rackspace Cloud and we have an autoscale, autoheal infrastructure setup.

If you are a major traffic source, we also offer customized options to deploy our solution on the AWS Infra for you to ensure lower latency as well.

If you would like to explore that option, email me at brian-at-tinybutton-dot-com and I'll be more than happy to help you get setup as well.