docs: correct the document outline, and say what crawlers may do - #37
Merged
Conversation
Semantics
The nav was not inside any landmark, so a reader jumping by landmark had a
main and a footer but no header. It is now wrapped in <header>.
Two pages skipped a heading level. check.html went h1 straight to h3 for the
four checks, which ARE the page's top-level sections, so they are h2 now.
changelog.html did the same, and worse: the release version was a <span>, so
the "Fixed"/"Added"/"Changed" groups floated with no release heading above
them and any tool building an outline saw eight sibling h3s belonging to
nothing. Release versions are h2 now, the groups sit under them, and the CSS
mirrors the old span rule so nothing moves visually.
All nine pages: exactly one h1, no skipped levels, one main, one header, one
footer.
Structured data
Only index.html had any. Every page now carries a BreadcrumbList, and three
carry the type that fits what someone is actually asking:
infected.html HowTo, four steps with anchors — "how do I remove this
malware" is what gets typed mid-incident
install.html SoftwareApplication with the current version
check.html FAQPage covering the three questions people ask: how do I
know, why did npm audit miss it, and does a clean process
check mean I am safe
Crawlers
robots.txt named 29 crawlers explicitly rather than leaving search engines
and AI answering engines to infer permission from a bare wildcard, and says
in a comment why: the point of this site is that people find it before they
are compromised.
llms.txt gives an assistant a compact authoritative summary — the threat,
the response order, and the two things people reliably get wrong — instead
of leaving it to reconstruct one from nine pages of HTML.
sitemap.xml gained lastmod, so a crawler can tell what changed.
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
2 participants
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.
Semantics
<header>— the nav sat in no landmark, so landmark navigation gave youmainandfooterbut nothing for the nav. Now wrapped.check.htmlwent h1 → h3 for the four checks, which are its top-level sections.changelog.htmldid the same, and worse: the release version was a<span>, so the Fixed/Added/Changed groups floated with no release heading above them — any tool building an outline saw eight sibling h3s belonging to nothing. Versions are h2 now, CSS mirrored so nothing moves visually.All 9 pages: exactly one h1, no skipped levels, one
main/header/footer.Structured data
Only
index.htmlhad any. Now every page has a BreadcrumbList, plus:infected.htmlinstall.htmlcheck.htmlCrawlers
lastmod.Validated: 0 HTML parse errors, 0 invalid JSON-LD, sitemap parses as XML, snare scans itself clean, selftest 10/10.