Wireshark-dev: Re: [Wireshark-dev] Gitlab wiki search
From: chuck c <bubbasnmp@xxxxxxxxx>
Date: Sat, 5 Sep 2020 22:35:32 -0500
"Is there anyway to get Google to start indexing it so searches show up?"
It's doable using git to push the Google site verification file and sitemap up to the wiki:
The sitemap file shows up on the wiki sidebar.
Not sure if that's a feature or a vulnerability.
Google also supports XML: https://support.google.com/webmasters/answer/183668?hl=en
Google "chuckcraft TCP" - wiki is the first hit.
On Sun, Aug 23, 2020 at 1:34 PM Graham Bloice <graham.bloice@xxxxxxxxxxxxx> wrote:
___________________________________________________________________________On Sun, 23 Aug 2020 at 03:00, Gerald Combs <gerald@xxxxxxxxxxxxx> wrote:It looks like that applies to GitLab pages, which have their own subdomain. As I recall, Google's search console requires a unique domain name along with some sort of proof of ownership, e.g. making a uniquely named file available for download.The link from Chuck to Google's search console (or one click on at https://search.google.com/search-console/welcome) has an option for a URL prefix with multiple options for verification that seems it would work for our gitlab.com/wireshark prefix.
On 8/22/20 10:20 AM, chuck c wrote:
> https://stackoverflow.com/questions/55827354/github-repository-not-listing-in-google-search-no-way-to-submit-url
>
> https://search.google.com/search-console/about
>
> Is there is a "wiki-master" to do the Google search config?
>
> On Sat, Aug 22, 2020 at 12:06 PM Graham Bloice <graham.bloice@xxxxxxxxxxxxx <mailto:graham.bloice@xxxxxxxxxxxxx>> wrote:
>
> The search seems to operate much like a normal wiki "full text search", there doesn't seem to be the equivalent of the "title search".
>
> I guess it is what it is, GitLab is a code "management" platform not a focused Wiki platform.
>
> Is there anyway to get Google to start indexing it so searches show up? Using a Google search of "wireshark wiki submitting patches" only shows the old site (and my initial post in this thread), and adding a "site:gitlab.com <http://gitlab.com>" condition gets a "it looks like there aren't any great matches for your search" and a bunch of links to things other than what I'm looking for.
>
> On Sat, 22 Aug 2020 at 16:46, Jaap Keuter <jaap.keuter@xxxxxxxxx <mailto:jaap.keuter@xxxxxxxxx>> wrote:
>
> Indeed it’s a bit coarse. It seems improvements are planned, see https://docs.gitlab.com/ee/user/project/wiki/#customizing-sidebar, not sure what that will bring.
>
>> On 22 Aug 2020, at 13:43, Graham Bloice <graham.bloice@xxxxxxxxxxxxx <mailto:graham.bloice@xxxxxxxxxxxxx>> wrote:
>>
>> Maybe I've missed something obvious, but there doesn't seem to be any way to search the GitLab Wireshark wiki. I can get a 45 page tabinated list of all pages with no hint of where in the alphabet page nnn might be and that's not friendly.
>>
>> I'm trying to find the "Submitting Patches" page which is a sub page of Development. Eventually I found Development on page 7 of the list and the actual page I wanted on page 8 of the list.
>>
>> I've now figured out that the GitLab search defaults to showing me things from users, which had 0 results for "submitting patches" and I have to click the "bubble" for Wikis to see the 12 results all of which show diffs of the markdown but does actually have the page I want.
>>
>> IMHO not really a wiki.
>>
>
>
> --
> Graham Bloice
>
> ___________________________________________________________________________
> Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx <mailto:wireshark-dev@xxxxxxxxxxxxx>>
> Archives: https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-request@xxxxxxxxxxxxx <mailto:wireshark-dev-request@xxxxxxxxxxxxx>?subject=unsubscribe
>
>
> ___________________________________________________________________________
> Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> Archives: https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
>
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives: https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe--Graham BloiceSoftware DeveloperTrihedral UK Limited
Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives: https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
- Prev by Date: Re: [Wireshark-dev] FT_STRING, FT_STRINGZPAD, and null padding
- Next by Date: [Wireshark-dev] Updating Migration from Gerrit Issue
- Previous by thread: Re: [Wireshark-dev] FT_STRING, FT_STRINGZPAD, and null padding
- Next by thread: [Wireshark-dev] Updating Migration from Gerrit Issue
- Index(es):