Why my GitHub fork wasn't showing up in Google

On 29 August, after sharing my Claude Desktop Fedora 44 package, I searched Google for it. Nothing. A site: search for the repo returned no results at all. The page had a noindex tag in its HTML, and the repo was a fork. Here's what I found and how I got mine out.

The project didn't start with me. I wanted Claude Desktop on Fedora, and someone had already done the hard part. In December 2024 Brandon Sneed (bsneed) made the original project, a script that took Anthropic's Windows installer and rebuilt it into a Fedora RPM. Other people sent in early fixes.

My fork's first commits are from May 2026. I fixed it for Fedora 43 and 44 and kept using it. In June Randy Johnson (randy-johnson) contributed a fix for a title bar regex that was corrupting the bundle.

Then Anthropic shipped an official Linux build, only as a .deb. Thanks to Anthropic for that. sharpandpearl sent a pull request that switched the project to repackaging the official build as a native RPM, and on 29 August I rebuilt the project around it.

Why my GitHub repo wasn't showing up in Google

The repo page's HTML had this line in it:

<meta name="robots" content="noindex, follow" />

That tag tells search engines not to index the page. Nothing in the repo controls it. The repo was a fork.

The annoying detail: in August I only saw the tag when the page was requested as Googlebot. A normal browser's view-source didn't show it. So if you checked the way most people would, you could look straight at the source and miss it.

What we saw on other forks

On 29 August we tested a small number of forks. The ones with pushes in 2026 had the tag. Forks idle since 2025 didn't, and neither did the non-forks. It was a small sample.

On 14 October we looked again. In our sample, 56 of the 65 forks we checked carried noindex, including forks last pushed in 2010. Some brand-new forks carried noindex, nofollow. We re-checked five of the repos separately.

None of the 7 non-forks had it. That includes octocat/Spoon-Knife, which is not a fork itself but has about 160k forks of its own, and my repo after it was detached. In our sample the tag lined up with being a fork, not with having forks.

A few old forks escape it. I don't know exactly why.

In October there was also no X-Robots-Tag header. It's the meta tag in the HTML.

I couldn't find any of this documented. We found no GitHub doc, changelog entry or staff statement about it. One answer in a GitHub community thread says forks are indexed, which is not what we see. In August we saw the tag only for Googlebot and only on recently pushed forks. In October we saw it with both tested user agents and on most forks we checked. We don't know what explains the difference from August.

How to check if your GitHub repo has a noindex tag

Replace OWNER/REPO with your own repo and run:

curl -s https://github.com/OWNER/REPO | grep -o '<meta name="robots"[^>]*>'

This prints the robots meta tag if the page has one. Look for noindex in it. If nothing prints, first make sure the request actually returned your repo page. A blank result by itself doesn't prove the page is indexable. You can also open the repo in a browser, view source and search for "robots".

Run it once more as Googlebot too. In August, this was the only version that showed the tag:

curl -s -A "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" https://github.com/OWNER/REPO | grep -o '<meta name="robots"[^>]*>'

How to detach a fork on GitHub

GitHub lets you leave a fork network, which is what people mean by detaching. If your fork has no forks of its own, start with GitHub's docs on detaching a fork and look for the self-serve route there. The same page covers child forks and the route through a support request.

Mine had 8 forks of its own, so the self-serve option was blocked for us. That leaves GitHub Support.

My first support ticket was closed automatically. On a free account, nobody looked at it. I took one month of GitHub Pro (about $4) and filed again on 13 October. The repo was detached on 14 October. I'm not claiming Pro is required for this; it's just what happened to us.

After the detach, the API says fork: false with no parent, the "forked from" line is gone, and the noindex tag is gone for both a browser and Googlebot. I kept every star and the 8 forks, and the URL didn't change.

The other route is deleting the repo and recreating it as a non-fork. That costs you the stars, issues, PRs and fork links. I wanted to avoid that.

Claude Desktop on Fedora (the project itself)

It is now a COPR package, claude-desktop-builder, that builds the RPM on your own machine from Anthropic's official Linux build, plus a daily timer that keeps it updated. Nothing proprietary is redistributed. The upstream payload is unmodified, the Chromium sandbox is on, and Claude Code, Cowork and MCP work.

sudo dnf copr enable dewzor/claude-desktop
sudo dnf install claude-desktop-builder

Repo: github.com/dewzor/claude-desktop-fedora. COPR: copr.fedorainfracloud.org/coprs/dewzor/claude-desktop. If you want a different route, aaddrick's claude-desktop-debian exists too.

Update

14 October 2026: not in Google yet. I'll update this when Google picks it up.