Over at Nype - https://npe.cm/ we had the same issue, we moved away from GitHub Pages and we're still recovering from it.

1st issue is basically that, due to how GitHub Pages are setup everything is stored in a limited amount of servers under a limited amount of IP addresses, so this leads to a quota threshold being met and Google pausing on crawling the servers at all.

• https://support.google.com/webmasters/thread/187613472/discovered-currently-not-indexed-error-on-github-pages-hosted-site

2nd issue (my guess) is that any problem with a site is "amplified" due to the slow crawling, and Google sort of abandons a site after too many problems occur. You can check the status of your crawl stats under Google Search Console -> Your Property -> Settings -> Crawling -> Crawl Stats (Open Report) -> "Between the chart and Crawl requests breakdown there is a status button for robots, DNS, Server connectivity", after a ~month after changing servers there is still "residue" of old issues and not all check-marks are green in our back panel .

3rd issue (my guess) is that in your case, you set up your redirections on the 404 page. GoogleBot should in theory handle JavaScript and detect the location change in JS, but overall when a bad URL loads GitHub sends the 404 server status code, and only later it loads the correct page. At Nype we played around with a combination of 404 page JavaScript redirects, mkdocs-redirects plugin to create a valid page with a redirect, so the server status code is at least 200, and some duplicate pages and link rel=canonical mangling, and the results were mediocre at best, likely due to the 1st issue and slow "reassessment" Later on, as the page has now it's own server, we moved on to the proper way of sending a 301 code when redirecting, but too soon to tell anything more.

4th issue (my guess) is that in your case, you have now a lot of pages with possibly low traffic / low amount of backlinks, so Google is reluctant in adding so many links at once

We have also used the currently trending script https://github.com/goenning/google-indexing-script it helped a bit, but due to the 2nd issue manual requests for indexing were better. I personally didn't do it as I'm not the property owner.

I hope at least some of the above helps you out but yeah after working a bit with Google "docs", A LOT of things are not said directly, and users have to guess too much imo.

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 !

Your page looks indexed to me:

It's a Google thing. You can certainly manage your SEO from their console. https://search.google.com/search-console/about

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.)

Welcome here.

Yesterday, I created my GitHub pages site 

Keep calm and wait. This helps always. Then write good content. Earn good backlinks. It can take (much) time, till you see your site in SERP. Some new sites are indexed fast - some slow.

Look at the list of same threads, https://webmasters.stackexchange.com/search?q=my+site+is+not+indexed - you'll find multiple equivalent cases with same recommendations. Keep calm, again - there is nothing weird or broken with your site.

The only thing i see - your site has nearly no content. Google should get a cause to come and to index your site. Create the cause - two sentences are too pure.

As mentioned in "Customizing GitHub Pages / Search engine optimization for GitHub Pages", you will have to add some seo tags, including one about author.

That author information will help Google search to point back to your site.

Google is unlikely to think that your page is a duplicate if you move it from GitHub Pages to a paid hosting service. This is because GitHub Pages are excluded from indexing by Google by default. This means that Google's crawlers will not see your page when it is hosted on GitHub Pages, so they will not be able to compare it to the same page when it is hosted on a paid hosting service.

However, there are a few things you can do to make sure that Google does not think your page is a duplicate. First, make sure that the content of your page is unique. This means that the text, images, and other content on your page should not be available on any other website. Second, use different URLs for your page on GitHub Pages and on your paid hosting service. This will help Google to distinguish between the two pages.

Finally, you can use a robots.txt file to prevent Google from crawling your GitHub Pages page. This will ensure that Google's crawlers will not see your page, even if it is public.

To summarize, here are a few tips to avoid duplicate content issues when moving your page from GitHub Pages to a paid hosting service:

• Make sure the content of your page is unique.
• Use different URLs for your page on GitHub Pages and on your paid hosting service.
• Use a robots.txt file to prevent Google from crawling your GitHub Pages page.

Hi @nicola-attico, welcome to the GitHub Support Community! The only thing you can really do is register your site in Google’s webmaster tools. This can take time to finish though so you may just need to wait for it to finally be indexed:

Ask Google to recrawl your URLs  |  Google Search Central

Have you got any followable backlinks pointing to your profile from other sites?

Github is huge, and Google will presumably see most of its pages as low priority unless it has signals to suggest otherwise. If you only have internal links, it's unlikely Google's crawler will hit many of their pages on a frequent-enough basis to be able to find it by crawling Github alone.

I see the issue is the same on Bing and DuckDuckGo, so I think you're just not very findable.

If your GitHub profile is what you consider your homepage, then popping it in your profile on any other sites you frequent may be enough.

It won’t show up immediately on Google due to its sandbox feature — i.e. a test period in which Google want’s to ensure that a new website is not a search-engine trap. i.e. that as soon as it’s index it will change all its contents. We don’t know much about the details of how Google handles the whole process, but I remember when the sandbox feature first came out (a couple of decades ago) to counter the above mentioned practice (e.g. waiting for a site to be indexed for some given keywords, and then switch to different contents, often counterproductive to the keywords for which it appeared).

Before the sandbox era, you could pretty much count on your website showing up at specific dates (beginning of upcoming month) once it was crawled. Now it’s a matter of waiting, and only those at Google know how it works and how long you need to wait.

Usually, a couple of weeks should be enough for a new website to show up in search engines, a month at the most.