Tsoden
Public audit for pkg.bot

What we found

Pkgbot is 8 fixes away from more package search queries.

8 things a visitor needs are missing. The ones costing you the most: no obvious button to start, Search engines can’t tell what you sell and no price anywhere on the page, plus 5 more below.

Read from 4 live pages · metadata, crawlability, trust, CTA, schema, sitemap, robots, llms.txt

Questions about this audit? Reply to the email or write to us — a human answers same day.

8 fixable leaks

The prioritized plan to fix all 8 leaks above and win more package search queries is below — free, nothing to unlock.

Walk me through the 8 fixes - free See what's leaking ↓

What buyers and AI/search engines see right now

Pages checked44 read in full
How we read itRead as crawlers doSame view buyers & bots get
Response time198msUnder the 2.5s target
Checks verified5/138 need fixing

Diagnostics

What we checked, and what we found

40 checks across six areas — search visibility, AI & answer engines, performance, security, conversion and trust — each measured against Pkgbot's live site.

12 pass 7 warn 21 fail

Of the 40 checks we ran on your page

Anything we couldn’t read is its own segment — a page that blocks our reader is our limitation, not a mark against you, and it never lowers your score.

Fine as-is — 12Needs fixing — 21Couldn’t read — 7
See the numbers
StateCountShare
On your page1230%
Missing2153%
Couldn’t read718%

Where your page is strong, and where it isn’t

Each area is scored 0–100 against what a customer needs to find before they act.

strong (75+)close (50–74)needs work (under 50)
Can they take the next step 21
Reasons to believe you 0
Can people find you 65
Can AI assistants read it 0
Speed on a phone 67
A safe, trusted connection 54
See the numbers
Part of your pageScoreHow that reads
Can they take the next step21/100needs work
Reasons to believe you0/100needs work
Can people find you65/100close
Can AI assistants read it0/100needs work
Speed on a phone67/100close
A safe, trusted connection54/100close

Priorities

Fix these first

Ranked by revenue impact. Each one is something developers — or an AI answer engine — need to see and currently can't. Fixing the top few moves your score the most.

01

No obvious button to start

Replace generic repo selector with a prominent, auto-focusing search bar labeled 'Find a package (e.g., nginx, rustc, docker)' and a 'Search packages' button above the fold.

02

Search engines can’t tell what you sell

Add structured data (LocalBusiness / Organization schema: address, hours, phone, ratings) so search engines show you with rich results.

03

No price anywhere on the page

Add a clear, non-distracting line: 'Free for everyone — no login, no limits, open source backend.'

04

AI assistants have nothing to read

Publish /llms.txt with a concise machine-readable product summary, audience, pricing, and docs links.

05

Nothing on the page proves you’re a real business

Add visible trust markers: 'Used by 12k+ devs weekly', 'Open source (GitHub)', and link to /apis and /privacy in header/footer.

06

Nothing describes you in search results

Update meta description to 'Search 2.8 million Linux packages across 129 repos — Alpine, Arch AUR, Debian, Fedora, Gentoo, Nixpkgs, openSUSE, Ubuntu, Rocky, and more. Fast, free, CLI-friendly.'

07

Search engines have no map of your site

Publish /sitemap.xml and submit it to search engines.

08

No robots.txt telling crawlers what to do

Publish /robots.txt with a sitemap reference and no accidental blocking.

What we read on your page

What a customer finds — and doesn’t

1 of the 8 things we could check are already on your page. We found only 1 of the 8 things a customer looks for before they act. Most visitors are leaving without enough reason to call, book or buy.

Below is the breakdown: what's already working (with the exact text quoted from your page as proof), and the highest-impact additions to win more package search queries — in priority order.

Scope: an automated scan of the 4 pages we could read across your site. Every “found” item quotes the exact text on your page so you can verify it. It doesn't judge copy quality or design.

Already on your page

  • An easy way to get in touch — found: “form field on page”

What to add, in order of impact

  • A headline that says what you do — Lead with one headline that names the customer and the outcome they get, not a slogan.
  • An obvious button that starts the thing — Put one clear action button on the first screen (e.g. Start free, Book a demo).
  • Reviews or proof from real customers — Add a testimonial, customer logo, star rating, or an 'N customers' proof point near the top.
  • A concrete number, not an adjective — Add a concrete number (result %, time saved, customers served). Specifics convert better than adjectives.
  • Something that removes the risk of trying you — Lower perceived risk: free trial, money-back guarantee, no credit card, or cancel-anytime.
  • A price, or at least a from-figure — Show pricing or a 'starting at' anchor so buyers can self-qualify without emailing.
  • Answers to the questions people ask before buying — Answer the top 3-5 buyer objections in an FAQ to remove hesitation before the CTA.

Deliverable

The full write-up

The full work-up for Pkgbot — every fix, with copy and code ready to paste.

Complete fix plan (every issue, step by step)

1. No obvious button to start

Replace generic repo selector with a prominent, auto-focusing search bar labeled 'Find a package (e.g., nginx, rustc, docker)' and a 'Search packages' button above the fold.

  1. Put one primary button on the first screen with action text (e.g. the suggested CTA below).
  2. Repeat the same CTA after the proof section and in the footer.
  3. Make the button visually dominant — one accent colour used only for the primary action.

2. Search engines can’t tell what you sell

Add structured data (LocalBusiness / Organization schema: address, hours, phone, ratings) so search engines show you with rich results.

  1. Add JSON-LD using the schema snippet below, edited with your real details.
  2. Validate it in Google's Rich Results Test before publishing.
  3. Keep it in sync with the on-page facts (name, address, phone, offers).

3. No price anywhere on the page

Add a clear, non-distracting line: 'Free for everyone — no login, no limits, open source backend.'

  1. Show pricing, packages, or a 'from …' anchor so buyers can self-qualify.
  2. If pricing is bespoke, give a starting price or a typical range.
  3. Pair each price with what's included so it reads as value, not cost.

4. AI assistants have nothing to read

Publish /llms.txt with a concise machine-readable product summary, audience, pricing, and docs links.

  1. Publish /llms.txt with a plain-text product summary, audience, pricing and key links.
  2. Keep it concise — answer engines reward clear, factual structure.
  3. Update it when your offer or pricing changes.

5. Nothing on the page proves you’re a real business

Add visible trust markers: 'Used by 12k+ devs weekly', 'Open source (GitHub)', and link to /apis and /privacy in header/footer.

  1. Add 2–3 real testimonials or case results with names/logos near the CTA.
  2. Link a privacy policy and terms page in the footer.
  3. Show any credentials, guarantees, security or compliance badges you hold.

6. Nothing describes you in search results

Update meta description to 'Search 2.8 million Linux packages across 129 repos — Alpine, Arch AUR, Debian, Fedora, Gentoo, Nixpkgs, openSUSE, Ubuntu, Rocky, and more. Fast, free, CLI-friendly.'

  1. Write a 140–155 character description that states the offer and the next step.
  2. Lead with the benefit, end with a soft call to action.
  3. Include the term a buyer would search so the snippet matches their query.

7. Search engines have no map of your site

Publish /sitemap.xml and submit it to search engines.

  1. Publish /sitemap.xml listing every indexable URL with <lastmod>.
  2. Reference it from robots.txt and submit it in Google Search Console.
  3. Regenerate it automatically whenever pages change.

8. No robots.txt telling crawlers what to do

Publish /robots.txt with a sitemap reference and no accidental blocking.

  1. Publish /robots.txt that allows crawling and points to your sitemap.
  2. Double-check you are not accidentally Disallow-ing the whole site.
  3. Remove any leftover 'Disallow: /' from staging.

Done-for-you assets — copy & paste

SEO title
Where to paste: Replace the <title> tag inside your page <head>.
pkg.bot — Fast Linux Package Search
Meta description
Where to paste: In <head>, set <meta name="description" content="…"> to this (replace the old one).
Search 2.8M+ packages across 129 Linux repos instantly — find, compare, and verify packages in seconds. Start searching now.
H1 — main page heading
Where to paste: Make this the single <h1> at the top of the homepage (real text, not an image).
Find Any Linux Package — Instantly, Across 129 Repos

— or one of these —
- Linux Package Search, Unified & Blazing Fast
- One Search. 129 Repos. 2.8 Million Packages.
Primary CTA button
Where to paste: Use as the main button on the first screen; repeat it after your proof/services section.
Search Packages
JSON-LD structured data (Organization)
Where to paste: Paste this entire block right before </head> (or before </body>).
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Pkgbot",
  "url": "https://pkg.bot/",
  "description": "pkg.bot is a free, open-source web tool that indexes and enables real-time search across 129 Linux distribution and package repository sources.",
  "makesOffer": [
    {
      "@type": "Offer",
      "itemOffered": {
        "@type": "Service",
        "name": "Cross-distribution package search (Alpine, Arch, Debian, Fedora, Ubuntu, Nix, Gentoo, etc.)"
      }
    },
    {
      "@type": "Offer",
      "itemOffered": {
        "@type": "Service",
        "name": "Real-time package version comparison across repositories"
      }
    },
    {
      "@type": "Offer",
      "itemOffered": {
        "@type": "Service",
        "name": "AUR, EPEL, nixpkgs, and community overlay indexing"
      }
    },
    {
      "@type": "Offer",
      "itemOffered": {
        "@type": "Service",
        "name": "Advanced filtering by architecture, stability, and repository"
      }
    },
    {
      "@type": "Offer",
      "itemOffered": {
        "@type": "Service",
        "name": "Public REST API for programmatic package lookups"
      }
    },
    {
      "@type": "Offer",
      "itemOffered": {
        "@type": "Service",
        "name": "Open-source data pipeline powered by Repology"
      }
    }
  ]
}
</script>
robots.txt
Where to paste: Create a plain text file at pkg.bot/robots.txt with this content.
User-agent: *
Allow: /
Sitemap: https://pkg.bot/sitemap.xml
llms.txt (for AI answer engines)
Where to paste: Create a plain text file at pkg.bot/llms.txt with this content.
# Pkgbot

> Search 2.8M+ packages across 129 Linux repos instantly — find, compare, and verify packages in seconds. Start searching now.

## Services
- Cross-distribution package search (Alpine, Arch, Debian, Fedora, Ubuntu, Nix, Gentoo, etc.)
- Real-time package version comparison across repositories
- AUR, EPEL, nixpkgs, and community overlay indexing
- Advanced filtering by architecture, stability, and repository
- Public REST API for programmatic package lookups
- Open-source data pipeline powered by Repology

## Links
- https://pkg.bot/

Page-by-page findings

PageWhat to fix
/no H1 heading
/p/aboutlooks healthy
/searchlooks healthy
/reposlooks healthy
Walk me through the 8 fixes - free

No charge and no pitch - a human reads your site and answers, usually the same day.

Rather we implement it for you? Done-for-you fix — €199

Action order

48-Hour Fix Plan

  • Replace generic repo selector with a prominent, auto-focusing search bar labeled 'Find a package (e.g., nginx, rustc, docker)' and a 'Search packages' button above the fold.
  • Add structured data (LocalBusiness / Organization schema: address, hours, phone, ratings) so search engines show you with rich results.
  • Add a clear, non-distracting line: 'Free for everyone — no login, no limits, open source backend.'
  • Publish /llms.txt with a concise machine-readable product summary, audience, pricing, and docs links.
  • Add visible trust markers: 'Used by 12k+ devs weekly', 'Open source (GitHub)', and link to /apis and /privacy in header/footer.

Why it matters

The fastest developers do not read every page. They scan the first screen, trust signals, pricing cues and how easy it is to search for a Linux package. Missing signals make the offer harder to understand and easier to ignore.

Packages

Turn this into more package search queries

You've seen the leaks, and the full plan above is yours free — every fix written out. The only thing we charge for is doing the work instead of you.

Do it yourselfFree

The complete evidence report and the prioritized, step-by-step plan for Pkgbot — every fix written out with copy & code ready to paste. It is on this page. Nothing to buy, nothing to unlock.

Read the full plan ↑
Done-for-you — 48h€199

We implement the highest-impact fixes for Pkgbot — metadata, schema, CTA, llms.txt, trust signals — in 48 hours. You keep every bit of the lift, no lock-in.

Have us do it — €199
Ongoing monitor€499/mo

Weekly re-checks of Pkgbot + drift alerts so the fixes compound and never silently slip back.

Start monitoring

Not sure which fits? Book a free 30-min call and we'll tell you straight. · 48-hour turnaround · no lock-in · every claim verified.

Verification

The exact wording we found

Every signal below was read from your live site — nothing is estimated. We checked 4 pages; “couldn’t verify” means a signal needs JavaScript to read and we won’t guess.

What we read

Titlepkg.bot - Fast Linux package search
Meta description68 chars
H1 heading Found 3/4
Structured data Missing

Crawl & AI files

robots.txt Missing
sitemap.xml Missing
llms.txt (AI) Missing
Response time198ms

Pages we checked

/
pkg.bot - Fast Linux package search
Read
/p/about
About - pkg.bot
Read
/search
Advanced search – pk.gbot
Read
/repos
Linux package repos – pkg.bot
Read

Questions about anything in here? Reply to the email, or reach us directly — we answer the same day.

CalendlyEmail

Who we are

Tsoden — a full-service web studio

We don't just audit — we build and rank websites end-to-end. Web development & design, plus SEO & AEO, so your business shows up in Google and in AI answers like ChatGPT, Perplexity and Gemini. This report is where we start; we can implement every fix below and grow your visibility on a full-service basis.

Web development & redesign — fast, conversion-first sites
SEO — rank in Google for what your buyers actually search
AEO — get found & cited by AI answer engines (ChatGPT, Perplexity, Gemini)
Ongoing monitoring & growth — we keep it improving
Work with Tsoden →or email support@tsoden.ai

Curious how a competitor scores?

Run the same free check on any site — the same buying signals, the same evidence quoted from the page itself. About a minute, no email needed to see the result.

Disclaimer

This service is a marketing and informational tool based on public website signals. It is not legal, financial, tax, investment, security, or professional advice. Scores and recommendations are estimates, not guarantees of revenue, rankings, AI visibility, deliverability, or business outcomes. You remain responsible for reviewing, approving, and implementing any changes and for complying with laws that apply to your business.

Full disclaimer · Terms · Privacy

This audit is from 16 Sept 2026 — we re-run it fresh before we touch anything Pkgbot · Grade F · 34/100
Done-for-you — €199 Walk me through the 8 fixes - free