You have to create a Google Search Console account and add your page, then typically you just drop a "marker" file in the root (Search Console generates this) so that Google can confirm you really own the page.

Google Search Console

Instructions

(Since the instructions are long and have many links to sub-steps, I'm only providing the link.)

Also, if you're going to use a registered domain name, set that up before you register the site for search.

(Edit: Technically you don't have to do this, sooner or later Google will find you... but this will give your content a much higher-quality score.)

Hey @MMorafah, welcome to GitHub Community

To address your question, I did a quick google search on my end, and below are my findings:

First of all, your GitHub profile and GitHub personal website have already been indexed on Google Search, and is searchable by other users already.

Second of all, it takes time for Google Search engine's web crawlers to crawl through websites & index them in the search engine. This process takes time, and as quoted from this documentation by Google, "it can take anywhere from a few days to weeks". Just to let you know, there isn't much the community members here can do to help expedite the process of indexing your website on Google. Just informing you in case you intend to publish new websites, you'll just have to wait patiently for your website to be indexed.

Hope this clarifies & answers your question .

Thank you, and have a good day ahead !

It takes time for Google to crawl, cache, understand, and index a new site.

As your old site was on one of Google's platforms, that probably happens automatically - or perhaps more quickly.

You can probably help speed up indexing by:

1. Adding a sitemap.xml file;
2. Attaching the site to a search console with a GA script;
3. Using Search Console to submit the sitemap.

Even then it can take some time - Google literally has Billions of pages to crawl and process every day. It really is a waiting game.

There is a built-in search feature, since Aug 8, 2016. It is in the same search bar at the top of any of your project's github pages.

If you happened to have set the "website" setting in the "About" section of the repo, you could figure it out like this, using the GitHub CLI:

gh repo list \
    --limit 500 --json name,homepageUrl --jq 'map(select(.homepageUrl != ""))'

This shows you a list of all repos that have a homepage set.

However, that's a setting enabled manually, and you can put any URL in there, so it might not return useful results.

In that case, you could iterate over every repository, and try to request the Pages site via REST API. If that succeeds, there is a page associated with the repo.

This snippet does that, suppressing errors from the call to the /pages endpoint; remove 2> /dev/null to see all the output.

while IFS= read -r repo; do
    if url=$(gh api "repos/$repo/pages" --jq '.html_url' 2> /dev/null); then
        printf '%s uses %s\n' "$repo" "$url"
    fi
done < <(gh repo list --limit 500 | awk '{print $1}')