Forum Moderators: Robert Charlton & goodroi
I've seen unexpected Supplementals by adding -inurl:www to the search. And surprisingly, they all had "www" in them -- so I can't be sure how valid or useful those results are. Just have a play with various inurl: combinations and see what you turn up.
It seems that any search with punctuation in it fails to match properly with data in the supplemental database.
.
Ask for all pages that contain a hyphenated email address: you get a few returns.
Change the hyphen to a space, and you see hundreds of extra returns, pages that contain (or contained) the email address - and all the extra entries are supplemental results.
.
Ask for inurl:www and you see all the www pages of a site, all as normal entries, and maybe some supplemental results at the end.
Ask for -inurl:www and you immediately see loads of www pages that are all supplemental results.
site:www.example.com
returns results from main and supplemental database.
inurl:www.example.com
does not return results from supplemental database(unless few?).
site:www.example.com -inurl:www.example.com
supplemental database only, consistent with first two data sets
site:example.com -inurl:www
supplementals within example.com + any non www
in summary inurl: does not add sups. -inurl: does not remove sups.
It may not be considered "correct" but is at least predictable
site:www.domain.com inurl:page.asp
How can I see supplemental results for just page.asp (regardless of the Id parameter value)?
We are in the process of using a rewriting tool to rewrite:
page.asp?Id=1 to pageTitleX_uniqueIdNumber.asp
How will I be able to see the indexed pages for the new page.asp since the name page name will different?