docs: link the README to the website, and print the command the front page promised - #184
Merged
Conversation
Search Console reports 16 of the site's 30 addresses indexed. URL inspection of the home page names exactly one referring page, the site's own Polish home page, so Google knows of no external link to the site. The repository's website field is served with rel="nofollow" and passes nothing. Two links, both placed where a reader benefits rather than for the crawler alone: one under the badges, and one after the quick start for readers who want a walkthrough of a single task instead of the full manual. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Both front pages said one command is enough to check that a service survives 10 percent packet loss, and then printed no command. Every other page on the site prints one, so the entry point was the only page that asked the reader to take the claim on trust. Verified by running it, not by reading the parser: --simulate --loss 10 --target myapp.exe --duration 3 exits 0 with reason=duration and drops 174 of 1851 packets, which is what the new sentence about the run stopping itself claims. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Search Console reports 16 of the site's 30 addresses indexed. The other 14 sit in
two buckets that need different remedies: 8 are "Discovered - currently not
indexed" (never fetched at all) and 6 are "Crawled - currently not indexed"
(fetched and declined).
URL inspection of the front page rules the technical layer out:
Crawl allowed: Yes,Page fetch: Successful,Indexing allowed: Yes, andGoogle-selected canonical: Inspected URL, so Google did not pick some other page as thecanonical. The decisive field is
Referring page, which names exactly one, andit is the site's own Polish front page. The repository's website field is served
with
rel="nofollow", so it passes nothing.What is here
The README links to the website. Two links, both placed where a reader
benefits rather than for a crawler alone: one under the badges, and one after the
quick start for anyone who wants a walkthrough of a single task instead of the
full manual.
The front page prints the command it promised, in both languages. It said one
command is enough to check that a service survives 10 percent packet loss and
then showed none, while all fourteen other pages show one. This one is a gap in
the page rather than an indexing fix.
What was deliberately left out
Lengthening the six pages in the "Crawled - currently not indexed" bucket, which
was the original plan. The site's own data does not support it. Median words in
<main>: indexed 411 (n=16), crawled and declined 426 (n=6), never crawled 407(n=8), so the declined pages are longer than the indexed ones. The clearest
counterexamples: one Polish guide is indexed at 335 words, another is declined at
649, and the longest page on the site at 787 words was never crawled at all.
Checks
tests/test_site.py: 49 passedruffandmypy: cleantools/check_public_text.pyover both commits: cleanthe parser:
--simulate --loss 10 --target myapp.exe --duration 3exits 0 withreason=durationand drops 174 of 1851 packets.The full suite runs here on CI rather than locally, on both runners.
🤖 Generated with Claude Code