Forum Moderators: bakedjake

Message Too Old, No Replies

Gigablast show the Meta in SERPs

You will also can use your own generic meta

         

Allergic

8:24 pm on Oct 12, 2003 (gmt 0)

10+ Year Member



Example results [gigablast.com]
It use the parameter &dt=metaname+metaname... and you can limit the number of caracters with : like in
&dt=author:32+keyword:72+description:100

I try also some Dublin Core meta or some other generic with no sucess.

The post on the blog [gigablast.com] of Matt Wells (owner of Gigablast)

[edited by: Allergic at 11:15 pm (utc) on Oct. 12, 2003]

bird

8:32 pm on Oct 12, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



previous topic [webmasterworld.com]

Unfortunately, Matt chose some rather non-standard meta tags to look at. Going with something established like Dublin Core would make a lot more sense.

mattdwells

8:55 pm on Oct 12, 2003 (gmt 0)

10+ Year Member



Allergic, What dublin and generic tags did you try w/o success? I suspect it is because those tags just haven't been indexed yet. I just rolled the code yesterday so it may be a while before Gigablast picks up the pages that use those tags, too.

Bird, I don't understand your post. Gigablast indexes all meta tags now, not just dublin, but any meta tag you care to invent, as long as the meta "name" is one word (string of alphanumeric characters). Therein lies the power.

Matt Wells

bird

9:04 pm on Oct 12, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Gigablast indexes all meta tags now

Well, in that case the "small" index may inded be the actual problem.

Therein lies the power.

Good for you! :)

Allergic

10:33 pm on Oct 12, 2003 (gmt 0)

10+ Year Member



I sticky mail to you Matt.

I suspect the dot in the DC meta who got the problem because the keywords, author and description are showing up, but not the dc.creator or other custom meta. Also note some DC meta also use "scheme sub-categories" sometimes.

BTW, nice work!

Allergic

5:27 pm on Oct 13, 2003 (gmt 0)

10+ Year Member



After a few searches, it appears to work fine with custom meta if the name of the meta didn't include dot (used by Dublin Core) or underscore.

It is a great tool to find the generator of the code. But sometimes it show you the wrong information like this search on generator:frontpage [gigablast.com] where some generator tag show you Adobe GoLive :-(

mattdwells

8:16 pm on Oct 13, 2003 (gmt 0)

10+ Year Member



Hi Everybody,

Ok, Gigablast now supports hyphens, underscores and periods in the name of the meta tag. Before it was only supporting alphanumeric characters. So now all the dublin core tags should work.

Allergic, the reason you were seeing an Adobe GoLive result was that the cached page you were viewing is not 100% in sync with the index. I do this to save computing resources, but you can append a "&seq=0" to the url and you will get the latest summaries, titles and metas.

Alrighty then... is everything working perfect now or what? :>

Matt Wells

Allergic

8:31 pm on Oct 13, 2003 (gmt 0)

10+ Year Member



Wow, really nice and fast. Thanks a lot, it is working great!
I wish Google working as fast as you to solve our/their problems ;-)

Robert Thivierge

4:21 am on Oct 16, 2003 (gmt 0)

10+ Year Member



Just to make Meta Tag support "perfect", I wanted to suggest the following:

1) Allow Meta Tag searches in site-specific-search forms (free or paid). Then, a webmaster could put a form on their site which would let people search their site (one domain) for any field they wanted, like the "Color" of a widget, or the "Weight" of the widget. I think Meta Tags are useless on global searches because of spam. Conversly, local site searches are of little value without meta-tags (i.e. custom fields) since they usually pull up totally unrelated pages because they happen to have a certain word anywhere in the page.

2) Apparently GigaBlast now supports a blank name Meta Tag, and retrieves the pages with words that are in the "value" of this meta tag, even when those words don't appear in visible text. I confirmed this happened by looking in the cache of the page.