Forum Moderators: Robert Charlton & goodroi
Why then for some searches that feature my domain I see a Supplemental Result appearing above a non-Supplemental Result that is indented? Also I see a lot of Supplemental Results containing the search phrase in the body ranking before/in place of a non-Supplemental Result that contains the search phrase in title and H1 text.
Can anyone shed some light on this? Surely it has to be screwy.
- you might want to be aware of this thread i started [webmasterworld.com...] which also questions the resutlts that are being served on exact and broad match
It would be great if we someone could provide some insight into these result issues.
Why then for some searches that feature my domain I see a Supplemental Result appearing above a non-Supplemental Result that is indented? Also I see a lot of Supplemental Results containing the search phrase in the body ranking before/in place of a non-Supplemental Result that contains the search phrase in title and H1 text.
Apologies guys I don't know what I was on when I wrote that post. I meant:
"Why then for some searches that I see a Supplemental Result appearing above a non-Supplemental Result? Also I see a lot of results containing the search phrase in the body ranking before/in place of a result that contains the search phrase in title and H1 text."
I have seen supplemental results outrank regular. But I have only seen it with very long keyword searches such as: "blue widgets that are in houston texas"In that case you might get a supplemental result of houston texas widgets and the next result could just be a regular one about widgets.
trinorthlighting -
Yes it does seem to only happen for long searches and I like your theory. It's very odd to see Supps appearing above normal results but it could be that they try to answer their initial understanding of the query with the results they have (including Supps) and then switch to a secondary set of results which are normal results. Therefore normal results would appear below Supps. Good thinking.