You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems the zulip-archive has not been indexed despite being online for almost 3 weeks. It would be futile to host the zulip chats, but not get indexed by search engines 😭 .
Some say that until there's some public references to the url, google won't bother indexing it.
add links to publicly indexed websites like bytecodealliance.org
add links to READMEs of related github repos (github repos are indexed by google)
Just ask devs to share the links in social media like twitter / mastodon.
Others say that google won't index github pages, unless explicitly asked to do so.
According to stackoverflow and other blogs that got indexing working, you can explicitly trigger a crawl by proving ownership of the website in google search console by hosting a specific html file with website or adding a meta tag in index.html.
If you search for wrpc github page, it works. link: https://www.google.com/search?q=site%3Abytecodealliance.github.io%2Fwrpc
If you search for this zulip-archive page, it shows nothing. link: https://www.google.com/search?q=site%3Abytecodealliance.github.io%2Fzulip-archive
It seems the zulip-archive has not been indexed despite being online for almost 3 weeks. It would be futile to host the zulip chats, but not get indexed by search engines 😭 .
Some say that until there's some public references to the url, google won't bother indexing it.
Others say that google won't index github pages, unless explicitly asked to do so.
According to stackoverflow and other blogs that got indexing working, you can explicitly trigger a crawl by proving ownership of the website in google search console by hosting a specific html file with website or adding a meta tag in index.html.
There's always the option of raising an issue at https://github.com/zulip/zulip-archive and ask them for guidance.
The text was updated successfully, but these errors were encountered: