Earlier quoted context omitted.
Another quick suggestion: Show a tally of how many pages have been indexed in the admin panel. Cheers!
Yes and yes. We do a fair amount of post-processing on the pages to handle things like boilerplate text pruning. Hopefully, it should catch what you mentioned. That said, we have bulk modification tools in the works.
Swiftype (YC W12) Builds Site Search That Doesn’t Suck
31–40 of 74 posts
Re: Swiftype (YC W12) Builds Site Search That Doesn’t Suck
#32Very cool. The only problem I see with this is that if Swiftype is down, or slow, your website search is affected too... Depends on how you and your readers value this functionality of course. Some websites don't rely on search as badly as others do. But for basic stuff this is great.
Re: Swiftype (YC W12) Builds Site Search That Doesn’t Suck
#33Also +1: more clarity on pricing, please.
Re: Swiftype (YC W12) Builds Site Search That Doesn’t Suck
#34Very cool. I hope they start to explore the implications of indexing a trusted source at some point. Google ignores most metadata on your pages because for all it knows you're using that metadata to game the system. With site search that's not an issue, so the search engine could look for certain metadata on the pages it crawls, from author to importance/boost to activating keywords. The interface currently allows yo…
Also, not sure if you caught this on the site yet, but we do have support for custom metadata: http://swiftype.com/documentation/meta_tags
Re: Swiftype (YC W12) Builds Site Search That Doesn’t Suck
#35Re: Swiftype (YC W12) Builds Site Search That Doesn’t Suck
#36Re: Swiftype (YC W12) Builds Site Search That Doesn’t Suck
#37This is so freaking awesome. I've had this problem on nearly every website and blog I've created. Also at both of my startups (Scribd and Parse -- note: Parse uses Swiftype on our documentation pages -- try it out). I've tried google site search (which sucked and wouldn't index all the Scribd pages for example, and it wasn't good enough for the parse documentation) and I've also used lucene and sphinx (pain to set up…
I don't think I would try it if I wanted to get to the online store (I would Google "apple.com store") if they removed the "store" tab to make room for something else...
That is just how low my expectation of in-site search is. The status quo is abysmal!
So, I agree there is quite a bit of room for improvement here... Just remember my laughter in the 0.2 to 0.5 seconds or however long it takes for the apple.com search field to expand... :)
Re: Swiftype (YC W12) Builds Site Search That Doesn’t Suck
#38Re: Swiftype (YC W12) Builds Site Search That Doesn’t Suck
#39I've checked out Swiftype, and I have to say that it is awesome. It's basically the "Stripe" of site search, in that it fixes a system that was just broken. Hosted site search as a market has had basically zero innovation since Google launched its site search product. That was like 6 years ago. If you've ever tried Google site search, you know how much it sucks. It's basically just a thin wrapper around a site:yourdo…
Re: Swiftype (YC W12) Builds Site Search That Doesn’t Suck
#40Very cool. I hope they start to explore the implications of indexing a trusted source at some point. Google ignores most metadata on your pages because for all it knows you're using that metadata to game the system. With site search that's not an issue, so the search engine could look for certain metadata on the pages it crawls, from author to importance/boost to activating keywords. The interface currently allows yo…
Spot on. This is one of the real advantages to leverage in a site search system. We have only scratched the surface of what's possible, but there is a lot more to this coming soon. Also, not sure if you caught this on the site yet, but we do have support for custom metadata: http://swiftype.com/documentation/meta_tags
As an example: We are foo.org but are also partnered with bar.org and baz.org. A search for "code awareness" should return a result from either of the three websites.