GSA query questions

[Jimbo]

Hey,

I am currently working on a project that is implementing GSA's to
search site content.
I just had a couple of questions I was hoping someone could clarify
for me as I am having a trouble locating answers in the documentation.

1) Firstly, I have meta data that I want to output to the page as meta
tags to be crawled, but the field has multiple values. What is the
correct format for the mata tag(s). Should I use one meta data tag
with the value comma delimited, i.e,

<meta name="tagname" content="tagvalue1, tagvalue2" />

or should I use two seperate tags i.e.

<meta name="tagname" content="tagvalue1" />
<meta name="tagname" content="tagvalue2" />

2) Is it possible to query for pages that contain text in the meta tag
but also include pages that do not contain the tag being queried in
the results. For example, using the above, I want query for
"tagvalue1" but also include pages that do not contain the "tagname"
meta tag at all.
One approach I know will work will be to exclude all possible values
that "tagname" can have except the one I want to query , which will
work but is not ideal, and what if don't have finite list of values?
If there is a soltion can someone let me know the syntax that is used
in the search url.

Thanks in advance for any help with the above.

Jimbo

[brianb]

Hi Jimbo,

some comments below.

On Nov 26, 1:57 pm, Jimbo <jhheywo...@gmail.com> wrote:
> Hey,
>
> I am currently working on a project that is implementing GSA's to
> search site content.
> I just had a couple of questions I was hoping someone could clarify
> for me as I am having a trouble locating answers in the documentation.
>
> 1) Firstly, I have meta data that I want to output to the page as meta
> tags to be crawled, but the field has multiple values. What is the
> correct format for the mata tag(s). Should I use one meta data tag
> with the value comma delimited, i.e,
>
>  <meta name="tagname" content="tagvalue1, tagvalue2" />
>
> or should I use two seperate tags i.e.
>
> <meta name="tagname" content="tagvalue1" />
> <meta name="tagname" content="tagvalue2" />

It probably won't work if you have two metatags with the same name. So
it would be better to use the comma delimiters. Not sure exactly what
your end goal is with this so you might want to just try it out and
see if it works.

>
> 2) Is it possible to query for pages that contain text in the meta tag
> but also include pages that do not contain the tag being queried in
> the results. For example, using the above, I want query for
> "tagvalue1" but also include pages that do not contain the "tagname"
> meta tag at all.
> One approach I know will work will be to exclude all possible values
> that "tagname" can have except the one I want to query , which will
> work but is not ideal, and what if don't have finite list of values?
> If there is a soltion can someone let me know the syntax that is used
> in the search url.

It might take some testing around but you could make use of the minus
"-" exclusion with a combination of inmeta: search or requiredfields.
For example append the following to the query:

requiredfields=-tagname|tagname=tagvalue1

I haven't thought the above through too much so I would recommend
testing it out a bit and see if it gives you results. You could also
look into the inmeta: special query term as well.

[Jimbo]

Hey Brian,

Thanks, for the above.

I get conflicting views about multiple tags as if you see the query
"metadata with multiple values", which is also in the discussion list
then it says multiple tags is the best solution.
What I'm trying to achieve is to associate a field to a document in
the website but the field can have multiple values. I am dynamically
adding the metatags to the page from associated data in a database and
I'm looking for correct format.
It is possible for document to not have values for this field and so
no meta tag, hence why my second query comes into play. To also return
pages in the results that do not contain the tag(s)

The reason why I am trying to get the best practice now is that I no
longer have access to query the GSA directly in dev and so cannot test
until is in the clients staging environment.
I'm trying get best approach now to try to decrease amount of rework
later.

Thanks,

James

> > Jimbo- Hide quoted text -
>
> - Show quoted text -- Hide quoted text -
>
> - Show quoted text -