A complete worked example of a CrawlKind report on a fictional 12-page site. Every value here is illustrative. The format, the evidence, and the way each verification method is named are what the real kit produces.
sample-site.example · 12 pages · run 2026-10-08Plain HTML project
Blocker
2
Preventing a good experience
Improvement
5
Will make a noticeable difference
Passed
12
Already in good shape
Not checked
1
No conclusion reached
How to read this. Each finding carries a check ID, the affected URL, observable evidence, the reason it matters, a proposed fix, and a verification line that names the method used: public URL fetch, local preview, or repository inspection. A local change is never reported as a deployed change.
Access
2 findings · 3 passed
Blocker
A public page tells search engines not to index it.
ACCESS-02
URL
https://sample-site.example/services/
Evidence
services/index.html, line 7<meta name="robots" content="noindex">
Reason
The page is linked from the main navigation and describes the core offer. A noindex directive asks search engines to leave it out of results.
Fix
Confirm the page should be searchable. If so, remove the meta tag. Proposed diff:
<meta name="robots" content="noindex">
Verified
Passed after the change. Method: public URL fetch on 2026-10-08. A fresh request returned 200 with no robots meta tag and no X-Robots-Tag header.
Blocker
A navigation link returns 404.
ACCESS-05
URL
https://sample-site.example/pricing-2025/
Evidence
GET /pricing-2025/404 Not Found
linked from: /index.html (nav), /about/index.html
Reason
Two pages link to a URL that no longer exists. Visitors and crawlers both hit a dead end.
Fix
Point the links at /pricing/, or add a redirect from the old path if it was ever shared publicly.
Verified
Open. No change applied yet. The links are in two files; the redirect belongs in the host configuration, which the kit reports but does not edit.
A sitemap is not required for indexing, but an incomplete one makes it harder for crawlers to find newer pages quickly.
Fix
Regenerate the sitemap from the full page list. The kit includes a script that writes one from the files in the project.
Verified
Open. Proposed sitemap written to crawlkind/proposed/sitemap.xml for review.
Not checked
Crawler access rules at the host or CDN.
DISC-06
URL
https://sample-site.example/ (host level)
Evidence
robots.txt: allows all user agentsfirewall / CDN bot rules: not visible from the repository or a single fetch
Reason
Whether specific crawlers are blocked by a firewall cannot be established from repository inspection or one request. It needs server logs or a request from the crawler's own identity.
Fix
If you suspect blocking, check the host's bot settings and access logs. The kit lists what to look for.
Verified
Not checked. No conclusion was reached and none is implied.
Without a description, search results show whatever text the engine chooses, which is often not the summary you would pick.
Fix
Add a one-sentence description that states what is sold and the starting price. Proposed:
<meta name="description" content="Three plans for small studios, from $19 a month. No setup fee.">
Verified
Open. The proposed text uses facts confirmed on the page. Review before applying.
Improvement
Seven pages share the same title.
META-02
URL
7 article pages
Evidence
<title>Sample Studio</title>× 7
Reason
Identical titles make pages hard to tell apart in search results and browser tabs.
Fix
Use the article heading as the title, followed by the site name. Proposed diffs are listed per file.
Verified
Open.
Structured information
1 finding · 1 passed
Improvement
Organization schema lists a phone number the page does not show.
JSON-02
URL
https://sample-site.example/
Evidence
index.html, JSON-LD
"telephone": "+1 555 0100"
page text contains no phone number
Reason
Structured data should describe what is visibly on the page. A value that only exists in the markup is a mismatch.
Fix
Either show the number on the page or remove it from the schema. The kit will not add business facts it cannot confirm on the page.
Verified
Open. Needs a decision from the site owner.
Content clarity
1 suggestion · 3 passed
Improvement
The homepage does not say who the service is for.
CLAR-01
URL
https://sample-site.example/
Evidence
h1: "Design that works."
first paragraph: "We make things people love to use."
audience named:no
Reason
This is an editorial suggestion, not a technical fault. A reader or an answer engine scanning the first screen cannot tell whether the studio works with startups, agencies, or individuals.
Fix
State the audience and the offer in the first paragraph. The kit drafts a suggestion from facts on the about and services pages and marks it for your review. It does not invent clients, numbers, or claims.
Verified
Open. Editorial. Verification for this check means the owner confirmed the wording.
This is what you get after every run.
Rerun the checks after you apply changes and the verification column updates.