my website is not visible on search engine

[shitikantha91]

Select Topic Area

Question

Body

I created my website on GitHub Pages a year ago. Initially, it was visible on Google and Bing search results. However, it is now available only on Bing and not on Google. Perhaps I made some changes in the settings. Could you please assist me in identifying what changes I might have made?

[skygraphixxz-digitalproduct]

. Check if your site blocks Google indexing

In your GitHub Pages repo, open the root folder and look for a file named robots.txt.

Make sure it doesn’t contain this line:

Disallow: /

If it does, delete that line or replace it with:

User-agent: *
Allow: /

2. Check for “noindex” meta tag

Open your website and view the page source (Ctrl + U).

Search for:

If you see that, remove it — it tells Google not to list your site.

3. Make sure your repository is public

Go to your repo settings → General → scroll to Danger Zone.

Confirm the repository is set to Public, not Private.

4. Verify your site in Google Search Console

Go to https://search.google.com/search-console
.

Add your site (for example, https://username.github.io).

Check if there are any coverage errors, blocked URLs, or manual actions.

5. Resubmit your sitemap (optional)

Create a simple sitemap at https://www.xml-sitemaps.com/
or manually add one.

Submit it in Google Search Console → Indexing → Sitemaps.

✅ In short:
You probably added or edited a robots.txt, noindex tag, or made the repo private. Fixing those and asking Google to re-index your site will make it appear again in search results.

[anyexpjay]

This usually happens due to indexing or SEO-related changes, not because GitHub Pages itself stopped working. Since your site still appears on Bing, the issue is almost certainly Google-specific.

Here are the most common changes that could cause this and how to check them:

1️⃣ robots.txt blocking Google
If you added or edited a robots.txt file, Google may now be blocked.
Check:
https://your-site-url/robots.txt
Make sure it does not contain:
User-agent: Googlebot
Disallow: /
or a global block:
User-agent: *
Disallow: /

2️⃣ noindex meta tag added
If you modified your HTML or theme, a noindex tag may have been introduced.
Check your section for:

If present, remove it or change it to:

3️⃣ Jekyll / theme change on GitHub Pages
If you’re using GitHub Pages with Jekyll, a theme change or _config.yml edit could affect indexing.
Check _config.yml for:
published: false
SEO plugins removed (e.g. jekyll-seo-tag)
Base URL or URL misconfiguration

4️⃣ Site not verified in Google Search Console
Google may have dropped the site if it hasn’t been verified or maintained.
Action:
Add your site to Google Search Console
Check:
Pages → “Not indexed”
Manual actions
Security issues
This is the most important step.

5️⃣ Canonical URL or domain mismatch
If you switched between:
http ↔ https
www ↔ non-www
username.github.io ↔ custom domain
Google may be indexing a different canonical version.
Check:

6️⃣ Content quality or inactivity
If the site:
Has very little content
Hasn’t been updated in a long time
Is mostly duplicate or placeholder text
Google may temporarily de-rank or de-index it, while Bing keeps it.

✅ Why Bing still shows it
Bing is generally:
Less strict about indexing
Slower to remove old pages
More tolerant of static sites
So Bing visibility is a good sign — your site is still accessible.

✅ Recommended Fix Order
Check robots.txt
Check for noindex
Verify site in Google Search Console
Inspect indexing status of key pages
Submit a sitemap (if available)

Final reassurance
This is a very common issue with GitHub Pages sites and is almost always fixable. In most cases, once Google is allowed to crawl again and the site is verified, pages reappear within a few days to weeks.

[jcduro]

A few things you can check when a GitHub Pages site disappears from Google but still shows up on Bing:

1. Confirm the site is still public

   • Make sure the repository that backs your GitHub Pages site is public and that GitHub Pages is still enabled in Settings → Pages.

2. Check for robots / noindex changes

   • See if you added a robots.txt or a <meta name="robots" content="noindex"> tag that might block Google from indexing your pages.
   • Sometimes themes or layouts can add this accidentally.

3. Verify the exact URL in Google Search Console

   • Add your GitHub Pages URL (for example: https://username.github.io/ or your custom domain) to Google Search Console and use the URL inspection tool to see why Google is not indexing it (crawling errors, noindex, etc.).
   • From there, you can request indexing again after fixing any issues.

4. Check if the URL changed

   • If you changed the repo name, branch (from master to main, or vice versa), or moved from username.github.io to a custom domain, Google may still have the old URLs indexed and needs time (plus a new sitemap / internal links) to update.

5. Be patient after fixes

   • Even when everything is correct, Google can take time to re‑crawl GitHub Pages sites. Bing and Google often behave differently here, so it is normal that one search engine shows it and the other doesn’t right away.

If you share your GitHub Pages URL and whether you’re using a custom domain or not, people here can help you check robots.txt, meta tags, and basic SEO settings.

[Odinaka-123]

I created my website on GitHub Pages a year ago. Initially, it was visible on Google and Bing search results. However, it is now available only on Bing and not on Google. Perhaps I made some changes in the settings. Could you please assist me in identifying what changes I might have made?

This usually isn’t caused by GitHub Pages itself but by indexing or visibility changes on Google’s side, often triggered by small configuration updates.

Based on my experience here are the most common things that could cause a GitHub Pages site to disappear from Google but still show on Bing:

1. robots.txt or meta tags

   • Check if a robots.txt file was added accidentally
   • Look for:
   • Google strictly obeys noindex, while Bing may still show pages temporarily

2. Google Search Console indexing status

   • Open Google Search Console (if previously verified)
   • Navigate to: Pages → Excluded
   • Look for:
     • "Page with noindex"
     • "Crawled – currently not indexed"
   • Manual URL removals or coverage issues can de-index the site

3. Repository or GitHub Pages visibility changes

   • Switching repo from public → private → public can drop indexing
   • Changing the Pages source branch can affect canonical URLs

4. Domain or URL structure changes

   • Renaming the repository
   • Changing the GitHub Pages URL
   • Adding then removing a custom domain
   • Google may treat the site as new and delay re-indexing

5. Content quality or duplication

   • Very minimal content
   • Duplicate pages
   • Long periods without updates
   • Google may silently drop the site while Bing keeps it indexed

Recommended next steps:

• Submit the homepage URL manually in Google Search Console
• Use URL Inspection to confirm the page is indexable
• Check for any noindex directives
• Add or update a simple sitemap.xml
• Ensure the repository is public and Pages is correctly configured

In most cases, once the indexing issue is resolved, Google listings return
within a few days to a few weeks.