Website report
Visit sitehttps://docsalot.dev/
Publish beautiful, fast, Git-backed documentation for people and AI agents, with clean Markdown, llms.txt, skills, and hosted MCP included.
Audit Full discovery audit·Language English (en)·Response HTTP 200·Served by Cloudflare
Analysed Nov 9, 2026 · 15 categories · 112 passed · 22 warnings · 1 issue · 15 informational
Audit score
C83/100
Mixed
- Agentic
- 95
- SEO
- 83
What we found
1Needs a fix22Could be better112Looks good15Informational- 1.Needs a fix: llms.txt follows the spec: needs fixing. see checkClear, accessible information helps AI assistants understand and cite your website.
- 2.Could be better: Your headings skip levels. see checkA clear outline makes content easier to navigate, including with a screen reader.
- 3.Could be better: Your images use older file formats. see checkEfficient image formats reduce download size.
- 4.Could be better: Anchor text is meaningful: needs attention. see checkWorking, descriptive links help people find the right page.
- 5.Could be better: Your site does not enforce future HTTPS visits. see checkHSTS keeps returning visitors on a secure connection.
Built with 3 technologies· detected stack
Read from the public source and response headers of the sampled pages.
How it fits together
Next.jsFramework
CloudflareCDN / edge
- CloudflareCDN / edge
- Next.jsFramework
Google FontsFont integration
A framework or CDN signal describes the public response, not the origin host or private backend.
Site checks
Every observation from the crawl, grouped by what it describes. Open a row for the evidence and the recommended fix.
Metadata1Could be better10Looks good
100/100Could be better: No meta keywords tagA meta keywords tag is present ("AI documentation,AI-readable docs,developer documentation,AP…").
Could be better · Metadata · Review suggested
Observed evidence
A meta keywords tag is present ("AI documentation,AI-readable docs,developer documentation,AP…").
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. It is there, but weaker than this check expects.
Recommended fix
You can remove it. Google has ignored meta keywords since 2009, so the tag does nothing for search and shows competitors the terms you target.
Looks good: Page title exists
Looks good · Metadata · Measured on your page
Observed evidence
Title found: "Fast, AI-Readable Docs-as-Code Platform | DocsAlot"
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Title length
Looks good · Metadata · Review suggested
Observed evidence
Title is 50 characters, inside this audit's 15–60 review range.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Title says what the site does
Looks good · Metadata · Measured on your page
Observed evidence
Title "Fast, AI-Readable Docs-as-Code Platform | DocsAlot" says more than the site name.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Meta description exists
Looks good · Metadata · Measured on your page
Observed evidence
Meta description found: "Publish beautiful, fast, Git-backed documentation for people and AI agents, with clean Mar…"
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Meta description length
Looks good · Metadata · Review suggested
Observed evidence
Description is 139 characters and inside this audit's 70–160 preview range.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Show 5 more checks
Looks good: Titles unique across pages
Looks good · Metadata · Measured on your page
Observed evidence
All 8 indexable sampled pages have distinct titles.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Homepage isn't noindexed
Looks good · Metadata · Measured on your page
Observed evidence
No blocking robots meta tag on the homepage.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Character encoding declared
Looks good · Metadata · Measured on your page
Observed evidence
UTF-8 declared in the Content-Type header and a meta tag.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: HTML5 doctype
Looks good · Metadata · Measured on your page
Observed evidence
HTML5 doctype declared.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Valid metadata order in <head>
Looks good · Metadata · Measured on your page
Observed evidence
No invalid element interrupts metadata in <head>.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Indexing16Looks good
100/100Looks good: Single canonical declaration
Looks good · Indexing · Measured on your page
Observed evidence
One canonical declaration found.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Noindex and canonical agree
Looks good · Indexing · Measured on your page
Observed evidence
No conflicting noindex and cross-page canonical instructions.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No meta-refresh redirect
Looks good · Indexing · Measured on your page
Observed evidence
No meta-refresh redirect.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No soft-404 response
Looks good · Indexing · Measured on your page
Observed evidence
No soft-404 pattern on sampled HTTP 200 pages.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Canonical target integrity
Looks good · Indexing · Measured on your page
Observed evidence
Canonical is a valid https URL. Its host is checked by the canonical consistency check.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sampled URLs have aligned indexability signals
Looks good · Indexing · Measured on your page
Observed evidence
Indexability signals align across 9 sampled URL(s).
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Show 10 more checks
Looks good: robots.txt exists
Looks good · Indexing · Measured on your page
Observed evidence
robots.txt responds with 200.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: robots.txt doesn't block everything
Looks good · Indexing · Measured on your page
Observed evidence
The audited URL is allowed for Googlebot. Most specific matching path; allow wins equal-length conflicts.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sitemap exists
Looks good · Indexing · Measured on your page
Observed evidence
Sitemap found at https://docsalot.dev/sitemap.xml.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sitemap parses and lists URLs
Looks good · Indexing · Measured on your page
Observed evidence
Sitemap lists 446 same-origin URLs.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sitemap declared in robots.txt
Looks good · Indexing · Measured on your page
Observed evidence
robots.txt declares the sitemap.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Canonical URL set
Looks good · Indexing · Measured on your page
Observed evidence
Canonical set: https://docsalot.dev/
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Canonical is absolute and self-referencing
Looks good · Indexing · Measured on your page
Observed evidence
Canonical is absolute and points at this page.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: www vs apex consistency
Looks good · Indexing · Measured on your page
Observed evidence
Hostname is used consistently (docsalot.dev).
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: URLs are readable slugs
Looks good · Indexing · Measured on your page
Observed evidence
URL slugs are readable (21 sampled).
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sampled pages expose search-access signals
Looks good · Indexing · Measured on your page
Observed evidence
No restrictive search-access signal on 9 sampled page(s). Actual indexing is not verified.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Content10Looks good1Informational
100/100Not measured: ReadabilityFlesch reading ease ≈ 39.
Not measured · Content · Not established
Observed evidence
Flesch reading ease ≈ 39.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
60+ reads easily for most visitors. This is a heuristic, not a rule — technical audiences tolerate denser text.
Looks good: Crawlable content in source HTML
Looks good · Content · Measured on your page
Observed evidence
No recognized empty JavaScript application shell on 9 sampled page(s). The entered page exposes 1167 publisher word(s).
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Homepage content volume
Looks good · Content · Measured on your page
Observed evidence
The audited page has about 1167 words of main content.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Text-to-HTML ratio
Looks good · Content · Measured on your page
Observed evidence
Text-to-HTML ratio is 14.6%.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No placeholder text
Looks good · Content · Measured on your page
Observed evidence
No placeholder text detected on crawled pages.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No starter-template leftovers
Looks good · Content · Measured on your page
Observed evidence
No starter-template artifacts detected.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Show 5 more checks
Looks good: Title and H1 agree
Looks good · Content · Measured on your page
Observed evidence
Title and H1 share topic words: doc, fast.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Crawled pages aren't near-duplicates
Looks good · Content · Measured on your page
Observed evidence
No near-duplicate main content among 8 indexable sampled pages.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Outbound references
Looks good · Content · Measured on your page
Observed evidence
51 outbound link(s) present.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Discovery copy is distinct across sampled pages
Looks good · Content · Measured on your page
Observed evidence
No repeated description, H1, or publisher copy across 8 sampled pages.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Structured data4Looks good1Informational
100/100Looks good: JSON-LD present
Looks good · Structured data · Measured on your page
Observed evidence
1 JSON-LD block(s) found on the homepage.
Why this matters
Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: JSON-LD parses
Looks good · Structured data · Measured on your page
Observed evidence
All 1 JSON-LD block(s) parse cleanly.
Why this matters
Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Organization or WebSite schema
Looks good · Structured data · Measured on your page
Observed evidence
Identity schema present: WebSite, Organization.
Why this matters
Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Content-specific schema
Looks good · Structured data · Measured on your page
Observed evidence
Content schema found: AggregateOffer, SoftwareApplication.
Why this matters
Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Headings2Could be better5Looks good
83/100Could be better: Heading levels don't skip1 heading level skip: H2 → H5 "Company".
Could be better · Headings · Review suggested
Observed evidence
1 heading level skip: H2 → H5 "Company".
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. It is there, but weaker than this check expects.
Recommended fix
Use the next level down for each subsection (H2 under H1, H3 under H2). If a heading level was chosen for its font size, keep the level and change the styling instead.
Could be better: Element IDs are unique per document76 duplicate ID occurrence(s) across 1 document(s).
Could be better · Headings · Measured on your page
Observed evidence
76 duplicate ID occurrence(s) across 1 document(s).
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. It is there, but weaker than this check expects.
Recommended fix
Give each element a unique id and update fragment links and aria-labelledby references to point to the intended element.
Affected pages (1)
- https://docsalot.dev/changelog
Looks good: H1 exists
Looks good · Headings · Measured on your page
Observed evidence
H1 found: "Beautiful docs. Fast pages. Clean context for agents."
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Single H1
Looks good · Headings · Measured on your page
Observed evidence
Exactly one H1 on the homepage.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: H1 has real text
Looks good · Headings · Measured on your page
Observed evidence
H1 reads "Beautiful docs. Fast pages. Clean context for agents.".
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Headings are descriptive
Looks good · Headings · Measured on your page
Observed evidence
32 headings, averaging 4.1 words — descriptive.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Content is sectioned with H2s
Looks good · Headings · Measured on your page
Observed evidence
10 H2 section(s) structure the page.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Images1Could be better3Looks good
84/100Could be better: Modern image formats7 of 7 raster images are served only as PNG or JPEG: docsalot-docs.png, Screenshot 2026-01-17 001344.png, a22493dc-7376-46c4-9786-30f44638ce14.png, ….
Could be better · Images · Review suggested
Observed evidence
7 of 7 raster images are served only as PNG or JPEG: docsalot-docs.png, Screenshot 2026-01-17 001344.png, a22493dc-7376-46c4-9786-30f44638ce14.png, ….
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. It is there, but weaker than this check expects.
Recommended fix
Serve WebP or AVIF versions, which are usually 25–50% smaller at the same quality. Use <picture> with a WebP/AVIF <source> and the original as fallback, or an image CDN or framework image component that converts automatically.
Looks good: Alt text coverage
Looks good · Images · Measured on your page
Observed evidence
All 22 visible images declare alt attributes (including empty alt for decorative images). Whether each description fits its image needs a human look.
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Width/height attributes
Looks good · Images · Measured on your page
Observed evidence
All 22 visible images declare dimensions or are sized by their container.
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Lazy loading
Looks good · Images · Measured on your page
Observed evidence
21/22 images are lazy-loaded.
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Links2Could be better4Looks good
91/100Could be better: Anchor text is meaningful16 of 123 links have unclear anchor text: 16 with no text or label (e.g.
Could be better · Links · Review suggested
Observed evidence
16 of 123 links have unclear anchor text: 16 with no text or label (e.g. https://backboard-docs.docsalot.dev/).
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. It is there, but weaker than this check expects.
Recommended fix
Make each link say where it goes ("Read the pricing guide" rather than "Read more"). For icon-only links, add an aria-label. Anchor text tells crawlers and screen-reader users what the destination is about.
Affected pages (1)
- https://docsalot.dev/
Could be better: Same-page links have source targetsSame-page links point to missing source targets on 7 page(s).
Could be better · Links · Review suggested
Observed evidence
Same-page links point to missing source targets on 7 page(s).
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. It is there, but weaker than this check expects.
Recommended fix
Match each fragment to an element ID. Verify JavaScript-created targets in the browser.
Affected pages (7)
- https://docsalot.dev/privacy-policy
- https://docsalot.dev/blog
- https://docsalot.dev/tools
- https://docsalot.dev/benchmarks
- https://docsalot.dev/pricing
- https://docsalot.dev/changelog
- https://docsalot.dev/terms-and-conditions
Looks good: Internal links resolve
Looks good · Links · Measured on your page
Observed evidence
All 12 sampled internal links return < 400.
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No dead placeholder links
Looks good · Links · Measured on your page
Observed evidence
No placeholder links on the audited page.
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: External links use rel=noopener
Looks good · Links · Measured on your page
Observed evidence
All target="_blank" links carry rel="noopener".
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Homepage links into the site
Looks good · Links · Measured on your page
Observed evidence
Homepage links to 40 distinct internal pages.
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Mobile4Looks good2Informational
100/100Not applicable: Responsive image markupNone of the 38 images use srcset.
Not applicable · Mobile · Measured on your page
Observed evidence
None of the 38 images use srcset.
Why this matters
Google indexes the phone rendering, so that is the version being graded. This check does not apply to the features observed in this sample.
Recommended fix
Serve smaller variants to phones with srcset/sizes (next/image handles this) — mobile users shouldn't download desktop-sized images.
Not measured: No tiny inline font sizesNo sub-12px inline font sizes detected; stylesheet rules and rendered sizes were not measured.
Not measured · Mobile · Not established
Observed evidence
No sub-12px inline font sizes detected; stylesheet rules and rendered sizes were not measured.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Check computed font sizes in a browser across mobile widths.
Looks good: Viewport meta tag
Looks good · Mobile · Measured on your page
Observed evidence
Viewport configured: "width=device-width, initial-scale=1".
Why this matters
Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Pinch zoom not disabled
Looks good · Mobile · Measured on your page
Observed evidence
The viewport lets users zoom.
Why this matters
Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Interactive controls have source labels
Looks good · Mobile · Measured on your page
Observed evidence
860 source controls have detectable names. Browser accessibility and CSS visibility were not tested.
Why this matters
Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: ARIA references point to source elements
Looks good · Mobile · Measured on your page
Observed evidence
11 ARIA reference(s) resolve within their source documents. Rendered visibility was not tested.
Why this matters
Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Language2Looks good1Informational
100/100Not applicable: hreflang syntaxNo hreflang tags — fine for single-language sites.
Not applicable · Language · Measured on your page
Observed evidence
No hreflang tags — fine for single-language sites.
Why this matters
The declared language tells browsers and assistive tech how to read the page and who it is for. This check does not apply to the features observed in this sample.
Recommended fix
Only add hreflang if you publish the same content in multiple languages/regions.
Looks good: html lang attribute
Looks good · Language · Measured on your page
Observed evidence
Language declared: lang="en".
Why this matters
The declared language tells browsers and assistive tech how to read the page and who it is for. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Declared language matches content
Looks good · Language · Measured on your page
Observed evidence
Declared language (en) matches detected content language.
Why this matters
The declared language tells browsers and assistive tech how to read the page and who it is for. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Branding1Looks good3Informational
100/100Not measured: Apple touch iconNo apple-touch-icon link.
Not measured · Branding · Not established
Observed evidence
No apple-touch-icon link.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Add a 180×180 apple-touch-icon so iOS home-screen bookmarks show your logo instead of a screenshot.
Not measured: Web app manifestNo web manifest linked.
Not measured · Branding · Not established
Observed evidence
No web manifest linked.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Optional, but a manifest.json enables install prompts and better mobile integration.
Not measured: Theme colorNo theme-color meta tag.
Not measured · Branding · Not established
Observed evidence
No theme-color meta tag.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Add <meta name="theme-color"> to tint the mobile browser UI to your brand color. Small touch, feels polished.
Looks good: Favicon
Looks good · Branding · Measured on your page
Observed evidence
Favicon declared via <link rel="icon"> (/icon.svg?23e9896df1363fda).
Why this matters
These icons are what appear in browser tabs, bookmarks and search results. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Performance
Measured from the audited response and its markup. These are source observations, not field Core Web Vitals.
| Measure | This site | Reading |
|---|---|---|
| Server response time | 370 ms | Looks good: goodThe audit received response headers after 370 ms from one test location. |
| HTML payload size | 87 KB | Looks good: goodThe page's HTML is a lean 87 KB uncompressed. |
| No render-blocking head scripts | — | Looks good: goodNo synchronous render-blocking scripts in <head>. |
| Inline styles are bounded | 0.0 KB | Looks good: goodInline styles total 0.0 KB. |
| Script/stylesheet count | — | Looks good: good20 total script/style resources — reasonable. |
| Web fonts don't block text | — | Looks good: goodGoogle Fonts links set a non-blocking font-display value. |
| HTML served compressed | — | Looks good: goodHTML is compressed with br. |
| Iframe usage | — | Looks good: good1 iframe(s), 0 lazy-loaded. |
| Source HTML weight | 87.0 KB | Informational: measured source, not transferred bytes87.0 KB of HTML on the audited page |
From a single automated fetch of the audited page. A quick reading, not a substitute for Lighthouse or field data.
Security
HTTPS, transport security and the response headers the audited pages send.
Could be better: HSTS headerNo active Strict-Transport-Security max-age was observed.
Could be better · Security · Review suggested
Observed evidence
No active Strict-Transport-Security max-age was observed.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. It is there, but weaker than this check expects.
Recommended fix
Add HSTS (e.g. max-age=63072000; includeSubDomains) so browsers never even try HTTP after the first visit.
Could be better: X-Content-Type-OptionsX-Content-Type-Options: nosniff is not set.
Could be better · Security · Review suggested
Observed evidence
X-Content-Type-Options: nosniff is not set.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. It is there, but weaker than this check expects.
Recommended fix
Add it — one header, stops MIME-sniffing attacks. Most hosts let you set headers in config (vercel.json, netlify.toml, next.config).
Could be better: Content Security PolicyA CSP is present but its script or object restrictions need review.
Could be better · Security · Review suggested
Observed evidence
A CSP is present but its script or object restrictions need review.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. It is there, but weaker than this check expects.
Recommended fix
Restrict script origins, use nonces or hashes for inline scripts, avoid unsafe evaluation, and set object-src 'none'.
Could be better: Referrer policyReferrer-Policy is "origin-when-cross-origin", which sends full page URLs (including paths and query strings) to other sites.
Could be better · Security · Review suggested
Observed evidence
Referrer-Policy is "origin-when-cross-origin", which sends full page URLs (including paths and query strings) to other sites.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. It is there, but weaker than this check expects.
Recommended fix
Use strict-origin-when-cross-origin unless a partner integration genuinely needs full URLs.
Could be better: Browser feature permissionsNo explicit restriction on sensitive browser features was observed.
Could be better · Security · Review suggested
Observed evidence
No explicit restriction on sensitive browser features was observed.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. It is there, but weaker than this check expects.
Recommended fix
Disable unused camera, microphone, or geolocation access using Permissions-Policy.
Could be better: Server technology disclosureThe X-Powered-By header advertises "Next.js".
Could be better · Security · Review suggested
Observed evidence
The X-Powered-By header advertises "Next.js".
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. It is there, but weaker than this check expects.
Recommended fix
You can remove it (in Next.js: poweredByHeader: false; in Express: app.disable('x-powered-by')). It adds bytes to every response and tells scanners what to probe; it is not a vulnerability by itself.
Not applicable: Declared form submission targetsNo HTML forms were found.
Not applicable · Security · Measured on your page
Observed evidence
No HTML forms were found.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. This check does not apply to the features observed in this sample.
Recommended fix
Check JavaScript-generated form transport separately if present.
Not applicable: Password forms avoid URL submissionNo enabled, named password inputs in sampled HTML.
Not applicable · Security · Measured on your page
Observed evidence
No enabled, named password inputs in sampled HTML.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. This check does not apply to the features observed in this sample.
Recommended fix
Review authentication forms separately when applicable.
Looks good: Site serves over HTTPS
Looks good · Security · Measured on your page
Observed evidence
Site serves over HTTPS.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: HTTP redirects to HTTPS
Looks good · Security · Measured on your page
Observed evidence
http:// permanently redirects to https://./
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Frame embedding protection
Looks good · Security · Measured on your page
Observed evidence
Response headers restrict cross-origin framing (frame-ancestors 'none').
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No mixed content
Looks good · Security · Measured on your page
Observed evidence
No insecure subresources detected.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
AI answer readiness
Retrieval signals an answer engine relies on: crawler access, clear entities and answers it can quote. These checks do not measure citations or traffic.
Needs a fix: llms.txt follows the specllms.txt is missing markdown links in the form [name](url).
Needs a fix · AI answer readiness · Published platform rule
Observed evidence
llms.txt is missing markdown links in the form [name](url).
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. Right now the sampled pages don't provide it.
Recommended fix
Follow the published structure: a single H1, a blockquote summary, then H2 sections whose lists use [name](url): short note. Parsers read the H1 and the link lists.
Could be better: FAQ/QA schemaNo FAQPage or QAPage schema on any crawled page.
Could be better · AI answer readiness · Review suggested
Observed evidence
No FAQPage or QAPage schema on any crawled page.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
If the page answers recurring questions, use visible question-and-answer content and matching FAQPage markup. QAPage is for a single question with user-submitted answers. Google FAQ rich results are restricted to eligible authoritative government and health sites; markup does not guarantee AI citations.
Could be better: Question-style headingsOnly 12% of 187 H2/H3 headings are question-shaped.
Could be better · AI answer readiness · Review suggested
Observed evidence
Only 12% of 187 H2/H3 headings are question-shaped.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
Phrase key subheadings as the questions users actually ask ("How much does X cost?"). This improves the measured question-heading signal; the audit does not guarantee citations.
Could be better: Definitional openingThe opening paragraph doesn't define what the site/topic is: "Connect your repo and publish without maintaining a framework or deployment pipe…"
Could be better · AI answer readiness · Review suggested
Observed evidence
The opening paragraph doesn't define what the site/topic is: "Connect your repo and publish without maintaining a framework or deployment pipe…"
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
"X is a Y that does Z for W" in the first paragraph gives answer engines a liftable definition of you. Write it once, benefit everywhere.
Could be better: Freshness signalsNo dateModified schema or visible 'updated' dates found.
Could be better · AI answer readiness · Review suggested
Observed evidence
No dateModified schema or visible 'updated' dates found.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
For content where dates matter, show the actual update date and mirror it in dateModified. Do not invent dates or change them without a substantive update. Missing dates alone do not prove stale content.
Could be better: llms.txt links resolve to this sitellms.txt contains no Markdown links to discoverable pages.
Could be better · AI answer readiness · Measured on your page
Observed evidence
llms.txt contains no Markdown links to discoverable pages.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
Add Markdown links such as [Pricing](/pricing) for the pages an answer engine should retrieve first.
Affected pages (1)
- https://docsalot.dev/
Could be better: Machine-readable provenance signalsOnly 3 of 4 provenance signal types were found: contact, author, date.
Could be better · AI answer readiness · Measured on your page
Observed evidence
Only 3 of 4 provenance signal types were found: contact, author, date.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
Add the missing author, date, breadcrumb, or contact signal so machines can identify provenance and site structure.
Affected pages (8)
- https://docsalot.dev/
- https://docsalot.dev/privacy-policy
- https://docsalot.dev/blog
- https://docsalot.dev/tools
- https://docsalot.dev/benchmarks
- https://docsalot.dev/pricing
- https://docsalot.dev/changelog
- https://docsalot.dev/terms-and-conditions
Not measured: llms-full.txtNo /llms-full.txt.
Not measured · AI answer readiness · Not established
Observed evidence
No /llms-full.txt.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Optional companion to llms.txt containing your full content as one markdown file — useful for sites whose pages are JS-heavy.
Not measured: Citable facts density10 concrete figures across 1686 words.
Not measured · AI answer readiness · Not established
Observed evidence
10 concrete figures across 1686 words.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Good — keep facts specific and current, and date-stamp them.
Not applicable: Advertised machine interfaces are inspectableNo OpenAPI interface was advertised by sampled HTML.
Not applicable · AI answer readiness · Measured on your page
Observed evidence
No OpenAPI interface was advertised by sampled HTML.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. This check does not apply to the features observed in this sample.
Recommended fix
An API is optional. Add a service-desc link if you already publish a machine-readable API specification.
Looks good: llms.txt
Looks good · AI answer readiness · Measured on your page
Observed evidence
llms.txt exists (11959 chars of markdown).
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: AI crawler access
Looks good · AI answer readiness · Measured on your page
Observed evidence
The audited URL is allowed for evaluated answer-search crawlers.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Semantic HTML structure
Looks good · AI answer readiness · Measured on your page
Observed evidence
Semantic structure present: main×1, article×21, section×11, nav×1, footer×1, aside×1.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Answers lead the section
Looks good · AI answer readiness · Measured on your page
Observed evidence
Paragraphs get to the point without preamble.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Content is chunkable
Looks good · AI answer readiness · Measured on your page
Observed evidence
Paragraphs average 21 words, lists present — chunk-friendly.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Cites external sources
Looks good · AI answer readiness · Measured on your page
Observed evidence
126 outbound reference(s) across crawled pages.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Consistent brand entity
Looks good · AI answer readiness · Measured on your page
Observed evidence
Brand declared: og:site_name "DocsAlot" + identity schema.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Description reads as a liftable summary
Looks good · AI answer readiness · Measured on your page
Observed evidence
Meta description works as a standalone summary.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Entity identity agrees across signals
Looks good · AI answer readiness · Measured on your page
Observed evidence
The site is consistently named "DocsAlot" and 4 identity URL(s) stay on docsalot.dev.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Question headings have concise answers
Looks good · AI answer readiness · Measured on your page
Observed evidence
18 concise answer block(s) follow 22 question-shaped heading(s).
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Markdown copies of pages
Looks good · AI answer readiness · Measured on your page
Observed evidence
1 of 3 probed URLs returned markdown.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Accept: text/markdown negotiation
Looks good · AI answer readiness · Measured on your page
Observed evidence
The homepage answers Accept: text/markdown with markdown.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
AdSense readinessOptional
Publisher-policy signals, for sites that plan to carry ads. These checks do not affect the overall score or grade, and they do not measure or guarantee AdSense approval.
On its own, this site scores 51/100 for publisher readiness. Ignore this section if you do not run ads.
Could be better: Privacy policy advertising disclosuresFetched privacy policy lacks advertising or Google disclosure signals.
Could be better · AdSense policy · Published platform ruleCritical
Observed evidence
Fetched privacy policy lacks advertising or Google disclosure signals.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Describe data collection, sharing, and cookie use by Google and other third-party ad vendors.
Affected pages (1)
- https://docsalot.dev/privacy-policy
Could be better: Sampled publisher-content coverage1/8 editorial pages expose fewer than 250 publisher words; those 8 pages hold 10942 publisher words in total.
Could be better · AdSense policy · Review suggestedCritical
Observed evidence
1/8 editorial pages expose fewer than 250 publisher words; those 8 pages hold 10942 publisher words in total. 1 of the 9 sampled pages is a support or tool page and was excluded from this check.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Review whether each page fully serves its purpose. Expand incomplete editorial content with useful information; keep concise navigation and tool pages when they help visitors.
Affected pages (1)
- https://docsalot.dev/editor
Could be better: Policy pages linked site-wide1/9 crawled pages don't link to the privacy policy.
Could be better · AdSense policy · Review suggested
Observed evidence
1/9 crawled pages don't link to the privacy policy.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Place the privacy link in shared navigation or footer markup so users can reach disclosures from any sampled entry page.
Affected pages (1)
- https://docsalot.dev/editor
Could be better: ads.txtads.txt exists but contains no google.com pub- line.
Could be better · AdSense policy · Review suggested
Observed evidence
ads.txt exists but contains no google.com pub- line.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Add your AdSense publisher line exactly as shown in your AdSense account.
Not measured: Domain age & historyDomain age isn't visible from the site itself.
Not measured · AdSense policy · Not established
Observed evidence
Domain age isn't visible from the site itself.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Do not use age as a content-quality proxy. Verify ownership and account eligibility in AdSense; Google's general eligibility page publishes no domain-age threshold.
Looks good: Privacy policy page
Looks good · AdSense policy · Measured on your page
Observed evidence
Privacy policy found: https://docsalot.dev/privacy-policy
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Terms page
Looks good · AdSense policy · Measured on your page
Observed evidence
Terms page found: https://docsalot.dev/terms-and-conditions
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: About page
Looks good · AdSense policy · Measured on your page
Observed evidence
About page found: /llms.txt
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Contact method
Looks good · AdSense policy · Measured on your page
Observed evidence
Contact email found: mailto:faizank@docsalot.dev?subject=DocsAlot%20AI%20Visibility%20Audit%20Request&body=Company%3A%0AWebsite%3A%0AWhat%20you%20want%20reviewed%3A%0A
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: First-party contact email
Looks good · AdSense policy · Measured on your page
Observed evidence
First-party contact email found: faizank@docsalot.dev.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Thin page share
Looks good · AdSense policy · Review suggested
Observed evidence
7/8 editorial pages clear the audit's publisher-content triage threshold. 1 of the 9 sampled pages is a support or tool page and was excluded from this check.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No ads on non-content screens
Looks good · AdSense policy · Published platform rule
Observed evidence
No Google ad code detected on sampled non-content screens.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Tool pages expose explanatory content
Looks good · AdSense policy · Review suggested
Observed evidence
All 8 sampled tool-style screens include crawlable explanation.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Publisher content differs across URLs
Looks good · AdSense policy · Review suggested
Observed evidence
No high publisher-content repetition among 7 substantial sampled page(s).
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Publisher content exists in source HTML
Looks good · AdSense policy · Measured on your page
Observed evidence
No empty client-rendered publisher shell in the crawl sample.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Article-style content exists
Looks good · AdSense policy · Measured on your page
Observed evidence
Article-style content detected.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No "coming soon" or placeholder pages
Looks good · AdSense policy · Measured on your page
Observed evidence
No "coming soon", "under construction" or lorem-ipsum text on crawled pages.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Site language is AdSense-supported
Looks good · AdSense policy · Measured on your page
Observed evidence
Language "en" is AdSense-supported.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Existing ad scripts
Looks good · AdSense policy · Measured on your page
Observed evidence
No competing ad scripts on the page.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Show 4 more checks
Looks good: Latest article has real depth
Looks good · AdSense policy · Measured on your page
Observed evidence
The newest article carries 1120 words of body text.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Latest article reads as edited work
Looks good · AdSense policy · Review suggested
Observed evidence
Style pattern score 7/100 on the newest article. These are style patterns in the sampled text, not a determination of how the page was written.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Latest article names an author and a date
Looks good · AdSense policy · Measured on your page
Observed evidence
The newest article shows both an author and a date.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Hosting and infrastructure
Public endpoint facts observed at audit time. A CDN or proxy can conceal the origin infrastructure.
| Hostname | docsalot.dev |
|---|---|
| CDN / edge | Cloudflare |
| IP addresses | 172.67.177.185, 104.21.17.173, 2606:4700:3033::6815:11ad, 2606:4700:3034::ac43:b1b9 |
| DNS A | 172.67.177.185 · 104.21.17.173 |
| DNS AAAA | 2606:4700:3034::ac43:b1b9 · 2606:4700:3033::6815:11ad |
| DNS NS | rosemary.ns.cloudflare.com · lars.ns.cloudflare.com |
| DNS MX | 1 aspmx.l.google.com · 10 alt3.aspmx.l.google.com · 10 alt4.aspmx.l.google.com · 5 alt1.aspmx.l.google.com · 5 alt2.aspmx.l.google.com |
| TLS | TLSv1.3TLS_AES_256_GCM_SHA384 |
| Certificate issuer | Google Trust Services / WE1 |
| Certificate valid until | Jan 4 01:36:04 2027 GMT |
| Certificate validation | Passed |
Website anatomy and diagnostics
Explore links, resources, crawler access and site integrations.
Page architecture
Choose a page to explore its details and connections.
Page content
1167 publisher words
Page structure
html content
Observed discovery
Depth 0 · 7 incoming links
HTTP 200 · 87.0 KB source
Source interactions
130 controls · 0 unnamed
17 script / 3 stylesheet references
- Canonical declaration
- https://docsalot.dev/
- Schema types
- Organization, WebSite, SoftwareApplication, AggregateOffer
- Outgoing links in sampled graph
- /blog · /tools · /signin · /editor · /benchmarks · /tools/docsagent-score · /signin · /signin · /pricing · /changelog · /terms-and-conditions · /privacy-policy · /llms.txt · /alternatives · /compare/the-top-mintlify-alternative · /compare/the-top-gitbook-alternative · /compare/the-top-docusaurus-alternative · /compare/the-top-fumadocs-alternative · /compare/the-top-starlight-alternative · /compare/the-top-scalar-alternative · /compare · /verses/mintlify-vs-gitbook · /verses/docusaurus-vs-gitbook · /verses/fumadocs-vs-starlight · /verses/readme-vs-redocly · /verses/zendesk-vs-intercom · /verses · /features/ai-knowledge-base · /features/branded-help-center · /features/ai-readable-documentation · /features/api-docs-automation · /features/clis-for-your-saas · /features/hosted-mcp-for-documentation · /features/sdks-for-your-saas · /features · /for/founders · /for/developer-tools · /for/api-companies · /for/saas-companies · /for/support-teams · /for · /index.md
Routes: / · /privacy-policy · /blog · /tools · /editor · /benchmarks · /pricing · /changelog · /terms-and-conditions
Resource origins 8
Resources associated with your website. External resources may belong to the same organization.
- https://docsalot.dev/stylesheet, script, image · 216 references · same origin
- https://storage.googleapis.com/image · 16 references · cross origin
- https://media.brand.dev/image · 12 references · cross origin
- https://fonts.googleapis.com/stylesheet · 9 references · cross origin
- https://static.cloudflareinsights.com/script · 9 references · cross origin
- https://www.tryastraea.com/image · 2 references · cross origin
- https://humwork.ai/image · 2 references · cross origin
- https://cal.com/frame · 1 references · cross origin
Crawler policy by page
Review crawler access for your pages. Search, training and user-triggered services have different purposes; declared access does not guarantee discovery.
| Crawler / purpose | Page | Policy | Matched directive |
|---|---|---|---|
| Googlebotsearch | / | allowed | allow: / |
| Googlebotsearch | /privacy-policy | allowed | allow: / |
| Googlebotsearch | /blog | allowed | allow: / |
| Googlebotsearch | /tools | allowed | allow: / |
| Googlebotsearch | /editor | allowed | allow: / |
| Googlebotsearch | /benchmarks | allowed | allow: / |
| Googlebotsearch | /pricing | allowed | allow: / |
| Googlebotsearch | /changelog | allowed | allow: / |
| Googlebotsearch | /terms-and-conditions | allowed | allow: / |
| bingbotsearch | / | allowed | allow: / |
| bingbotsearch | /privacy-policy | allowed | allow: / |
| bingbotsearch | /blog | allowed | allow: / |
| bingbotsearch | /tools | allowed | allow: / |
| bingbotsearch | /editor | allowed | allow: / |
| bingbotsearch | /benchmarks | allowed | allow: / |
| bingbotsearch | /pricing | allowed | allow: / |
| bingbotsearch | /changelog | allowed | allow: / |
| bingbotsearch | /terms-and-conditions | allowed | allow: / |
| OAI-SearchBotsearch | / | allowed | allow: / |
| OAI-SearchBotsearch | /privacy-policy | allowed | allow: / |
| OAI-SearchBotsearch | /blog | allowed | allow: / |
| OAI-SearchBotsearch | /tools | allowed | allow: / |
| OAI-SearchBotsearch | /editor | allowed | allow: / |
| OAI-SearchBotsearch | /benchmarks | allowed | allow: / |
| OAI-SearchBotsearch | /pricing | allowed | allow: / |
| OAI-SearchBotsearch | /changelog | allowed | allow: / |
| OAI-SearchBotsearch | /terms-and-conditions | allowed | allow: / |
| PerplexityBotsearch | / | allowed | allow: / |
| PerplexityBotsearch | /privacy-policy | allowed | allow: / |
| PerplexityBotsearch | /blog | allowed | allow: / |
| PerplexityBotsearch | /tools | allowed | allow: / |
| PerplexityBotsearch | /editor | allowed | allow: / |
| PerplexityBotsearch | /benchmarks | allowed | allow: / |
| PerplexityBotsearch | /pricing | allowed | allow: / |
| PerplexityBotsearch | /changelog | allowed | allow: / |
| PerplexityBotsearch | /terms-and-conditions | allowed | allow: / |
| Claude-SearchBotsearch | / | allowed | allow: / |
| Claude-SearchBotsearch | /privacy-policy | allowed | allow: / |
| Claude-SearchBotsearch | /blog | allowed | allow: / |
| Claude-SearchBotsearch | /tools | allowed | allow: / |
| Claude-SearchBotsearch | /editor | allowed | allow: / |
| Claude-SearchBotsearch | /benchmarks | allowed | allow: / |
| Claude-SearchBotsearch | /pricing | allowed | allow: / |
| Claude-SearchBotsearch | /changelog | allowed | allow: / |
| Claude-SearchBotsearch | /terms-and-conditions | allowed | allow: / |
| GPTBottraining | / | allowed | allow: / |
| GPTBottraining | /privacy-policy | allowed | allow: / |
| GPTBottraining | /blog | allowed | allow: / |
| GPTBottraining | /tools | allowed | allow: / |
| GPTBottraining | /editor | allowed | allow: / |
| GPTBottraining | /benchmarks | allowed | allow: / |
| GPTBottraining | /pricing | allowed | allow: / |
| GPTBottraining | /changelog | allowed | allow: / |
| GPTBottraining | /terms-and-conditions | allowed | allow: / |
| ClaudeBottraining | / | allowed | allow: / |
| ClaudeBottraining | /privacy-policy | allowed | allow: / |
| ClaudeBottraining | /blog | allowed | allow: / |
| ClaudeBottraining | /tools | allowed | allow: / |
| ClaudeBottraining | /editor | allowed | allow: / |
| ClaudeBottraining | /benchmarks | allowed | allow: / |
| ClaudeBottraining | /pricing | allowed | allow: / |
| ClaudeBottraining | /changelog | allowed | allow: / |
| ClaudeBottraining | /terms-and-conditions | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | / | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | /privacy-policy | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | /blog | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | /tools | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | /editor | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | /benchmarks | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | /pricing | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | /changelog | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | /terms-and-conditions | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | / | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | /privacy-policy | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | /blog | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | /tools | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | /editor | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | /benchmarks | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | /pricing | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | /changelog | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | /terms-and-conditions | allowed | allow: / |
Advertised APIs and machine interfaces
documentation · declared
https://docsalot.dev/documentation
This interface was advertised; its runtime behavior remains unverified.
documentation · declared
https://docsalot.dev/benchmarks/docs
This interface was advertised; its runtime behavior remains unverified.
Public DNS and TLS endpoint
docsalot.dev · observed · 172.67.177.185, 104.21.17.173, 2606:4700:3033::6815:11ad, 2606:4700:3034::ac43:b1b9
- A
- 172.67.177.185 · 104.21.17.173
- AAAA
- 2606:4700:3034::ac43:b1b9 · 2606:4700:3033::6815:11ad
- CNAME
- Unavailable for this exact hostname
- NS
- rosemary.ns.cloudflare.com · lars.ns.cloudflare.com
- MX
- 1 aspmx.l.google.com · 10 alt3.aspmx.l.google.com · 10 alt4.aspmx.l.google.com · 5 alt1.aspmx.l.google.com · 5 alt2.aspmx.l.google.com
- CAA
- Unavailable for this exact hostname
TLS: TLSv1.3
Certificate validation passed for the observed endpoint.
Issuer: Google Trust Services / WE1
Certificate valid until: Jan 4 01:36:04 2027 GMT
PageSpeed measurement
Loading the PageSpeed panel…
Growth resources
Loading growth resources…
Where to take this site next
Follow-on work suggested by the observations above.
- 01
Build content depth around real keywords
Technical basics are in place — use pages that answer actual searches as the next content focus. This audit does not measure rankings.
- 02
Steal from our keyword datasets
Curated keyword collections by niche give you a content calendar without paid tools.
Apply the recommended fixes
Hand the complete evidence to a coding agent, or take the report with you.
Report notes
- 01This report covers the sampled public pages listed above. Other pages may have different results.
- 02Browser-rendered content, private backend systems and authenticated experiences may require a separate review.
- 03Unavailable observations are identified in the report. Results do not guarantee rankings, citations, security, accessibility or advertising approval.
Pages included in this report
- https://docsalot.dev/
- https://docsalot.dev/privacy-policy
- https://docsalot.dev/blog
- https://docsalot.dev/tools
- https://docsalot.dev/editor
- https://docsalot.dev/benchmarks
- https://docsalot.dev/pricing
- https://docsalot.dev/changelog
- https://docsalot.dev/terms-and-conditions