Website report
Visit sitehttps://safegrd.dev/
Encrypted, immutable backups for PostgreSQL, MySQL, MongoDB, files and mail, restored on a schedule to prove they work, with a signed record of each test.
Audit Full discovery audit·Language English (en)·Response HTTP 200·Served by Nginx
Analysed Nov 7, 2026 · 15 categories · 119 passed · 12 warnings · 19 informational
Audit score
B91/100
Strong
- Agentic
- 100
- SEO
- 91
What we found
12Could be better119Looks good19Informational- 1.Could be better: No render-blocking head scripts: needs attention. see checkFaster pages help visitors reach your content sooner.
- 2.Could be better: Your content security policy needs work. see checkThis policy limits which scripts and resources can run on your website.
- 3.Could be better: FAQ/QA schema: needs attention. see checkClear, accessible information helps AI assistants understand and cite your website.
- 4.Could be better: Question-style headings: needs attention. see checkClear, accessible information helps AI assistants understand and cite your website.
- 5.Could be better: Your introduction needs a clearer explanation. see checkA clear opening helps visitors and AI assistants understand what you offer.
Built with 1 technology· detected stack
Read from the public source and response headers of the sampled pages.
NginxServer
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.
Metadata11Looks good
100/100Looks good: Page title exists
Looks good · Metadata · Measured on your page
Observed evidence
Title found: "SafeGrd: Database backups with automated restore testing"
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 56 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 "SafeGrd: Database backups with automated restore testing" 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: "Encrypted, immutable backups for PostgreSQL, MySQL, MongoDB, files and mail, restored on a…"
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 154 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.
Looks good: Titles unique across pages
Looks good · Metadata · Measured on your page
Observed evidence
All 9 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.
Show 5 more checks
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: No meta keywords tag
Looks good · Metadata · Measured on your page
Observed evidence
No obsolete meta keywords 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: 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 10 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. No path rule matches this URL.
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://safegrd.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 87 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://safegrd.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 (safegrd.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 (26 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 10 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 ≈ 49.
Not measured · Content · Not established
Observed evidence
Flesch reading ease ≈ 49.
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 10 sampled page(s). The entered page exposes 1740 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 1740 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 31.0%.
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: database, backup.
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 9 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
8 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 9 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 2 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: Offer, 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.
Headings7Looks good
100/100Looks good: H1 exists
Looks good · Headings · Measured on your page
Observed evidence
H1 found: "Database backups, tested by restoring them."
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: Heading levels don't skip
Looks good · Headings · Measured on your page
Observed evidence
Heading hierarchy is sequential across 29 headings.
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 "Database backups, tested by restoring them.".
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
29 headings, averaging 5.7 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.
Looks good: Element IDs are unique per document
Looks good · Headings · Measured on your page
Observed evidence
All inspected element IDs are unique within their documents.
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.
ImagesNot applicable
Not measuredNot applicable: Alt text coverageNo visible <img> elements on the audited page (hidden, presentational and 1×1 tracking images are not counted).
Not applicable · Images · Measured on your page
Observed evidence
No visible <img> elements on the audited page (hidden, presentational and 1×1 tracking images are not counted).
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. This check does not apply to the features observed in this sample.
Recommended fix
Nothing to change here. Any image you add later needs alt text that describes it, so this check starts scoring then.
Not applicable: Width/height attributesNo visible <img> elements to measure on the audited page.
Not applicable · Images · Measured on your page
Observed evidence
No visible <img> elements to measure on the audited page.
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. This check does not apply to the features observed in this sample.
Recommended fix
Nothing to change here. Give future images explicit width and height attributes so the browser can reserve their space.
Not applicable: Modern image formatsNo raster images with a recognizable file extension were found.
Not applicable · Images · Measured on your page
Observed evidence
No raster images with a recognizable file extension were found.
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. This check does not apply to the features observed in this sample.
Recommended fix
Nothing to change here. If images arrive later, serve WebP or AVIF alongside PNG/JPEG.
Not applicable: Lazy loadingOnly 0 visible image(s) on the page, too few for lazy loading to change the initial load.
Not applicable · Images · Measured on your page
Observed evidence
Only 0 visible image(s) on the page, too few for lazy loading to change the initial load.
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. This check does not apply to the features observed in this sample.
Recommended fix
Nothing to change here. Once the page carries several images, add loading="lazy" to the ones below the fold.
Links6Looks good
100/100Looks 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: Anchor text is meaningful
Looks good · Links · Measured on your page
Observed evidence
92 of 92 links have descriptive text or labels.
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 45 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.
Looks good: Same-page links have source targets
Looks good · Links · Measured on your page
Observed evidence
8 same-page fragment link(s) have source targets.
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 markupOnly 0 image(s) on the page, too few for responsive image markup to change what phones download.
Not applicable · Mobile · Measured on your page
Observed evidence
Only 0 image(s) on the page, too few for responsive image markup to change what phones download.
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
Nothing to change here. When the page carries several images, give them srcset and sizes so phones fetch smaller files.
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.0".
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
938 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
6 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"> (/static/favicon.svg).
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 |
|---|---|---|
| No render-blocking head scripts | — | Could be better: needs attention1 synchronous script(s) in <head> block rendering: /static/js/analytics.js. |
| Web fonts don't block text | — | Informational: not applicableNo Google Fonts stylesheet links detected. |
| Server response time | 300 ms | Looks good: goodThe audit received response headers after 300 ms from one test location. |
| HTML payload size | 47 KB | Looks good: goodThe page's HTML is a lean 47 KB uncompressed. |
| Inline styles are bounded | 0.0 KB | Looks good: goodInline styles total 0.0 KB. |
| Script/stylesheet count | — | Looks good: good8 total script/style resources — reasonable. |
| HTML served compressed | — | Looks good: goodHTML is compressed with gzip. |
| Iframe usage | — | Looks good: goodNo iframes. |
| Source HTML weight | 47.1 KB | Informational: measured source, not transferred bytes47.1 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: 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'.
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: HSTS header
Looks good · Security · Measured on your page
Observed evidence
HSTS is set: max-age=15768000.
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: Referrer policy
Looks good · Security · Measured on your page
Observed evidence
Referrer-Policy is strict-origin-when-cross-origin.
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: Browser feature permissions
Looks good · Security · Measured on your page
Observed evidence
A Permissions-Policy disables at least one sensitive browser feature.
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
Review remaining features and allow only origins the application needs.
Looks good: X-Content-Type-Options
Looks good · Security · Measured on your page
Observed evidence
nosniff is set.
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.
Looks good: Server technology disclosure
Looks good · Security · Measured on your page
Observed evidence
No X-Powered-By disclosure.
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: Declared form submission targets
Looks good · Security · Measured on your page
Observed evidence
3 declared form(s) submit over HTTPS to this site. Runtime submission behavior is untested.
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: Password forms avoid URL submission
Looks good · Security · Measured on your page
Observed evidence
No password form declares GET submission in the sampled source. Runtime handling was not tested.
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.
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 167 H2/H3 headings are question-shaped.
Could be better · AI answer readiness · Review suggested
Observed evidence
Only 12% of 167 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: "SafeGrd backs up your databases, files and mail, encrypts and locks each copy, a…"
Could be better · AI answer readiness · Review suggested
Observed evidence
The opening paragraph doesn't define what the site/topic is: "SafeGrd backs up your databases, files and mail, encrypts and locks each copy, a…"
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 has 69 same-origin link(s) and 1 invalid or off-site link(s).
Could be better · AI answer readiness · Measured on your page
Observed evidence
llms.txt has 69 same-origin link(s) and 1 invalid or off-site link(s).
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
Keep llms.txt discovery links on the audited origin and use absolute or root-relative HTTP(S) URLs.
Affected pages (1)
- https://safegrd.dev/
Could be better: Question headings have concise answers11/20 question-shaped heading(s) have a 20–500 character paragraph immediately after them.
Could be better · AI answer readiness · Measured on your page
Observed evidence
11/20 question-shaped heading(s) have a 20–500 character paragraph immediately after them.
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
Put a direct 20–500 character answer paragraph immediately after each question heading so retrieval systems can quote it cleanly.
Affected pages (6)
- https://safegrd.dev/
- https://safegrd.dev/privacy
- https://safegrd.dev/integrations
- https://safegrd.dev/pricing
- https://safegrd.dev/docs
- https://safegrd.dev/trust
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 (5)
- https://safegrd.dev/
- https://safegrd.dev/about
- https://safegrd.dev/contact
- https://safegrd.dev/privacy
- https://safegrd.dev/trust
Could be better: Markdown copies of pagesNo markdown copy answered at /index.md or /about.md or /index.html.md.
Could be better · AI answer readiness · Measured on your page
Observed evidence
No markdown copy answered at /index.md or /about.md or /index.html.md.
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
Publish a clean markdown copy of each key page at /page.md (or /page.html.md). It strips navigation and scripts, so a retriever spends its budget on your content.
Affected pages (2)
- https://safegrd.dev/
- https://safegrd.dev/about
Not measured: Citable facts density99 concrete figures across 2181 words.
Not measured · AI answer readiness · Not established
Observed evidence
99 concrete figures across 2181 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: Accept: text/markdown negotiationThe homepage answered Accept: text/markdown with text/html; charset=utf-8.
Not applicable · AI answer readiness · Measured on your page
Observed evidence
The homepage answered Accept: text/markdown with text/html; charset=utf-8.
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
Optional: return a stripped markdown body when the request asks for text/markdown. Some hosts and CDNs do this for you; a plain HTML answer is not a defect.
Looks good: llms.txt
Looks good · AI answer readiness · Measured on your page
Observed evidence
llms.txt exists (12762 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: llms-full.txt
Looks good · AI answer readiness · Measured on your page
Observed evidence
llms-full.txt is published.
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×2, section×9, nav×1, header×1, footer×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
56 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 "SafeGrd" + 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 "SafeGrd" and 6 identity URL(s) stay on safegrd.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: llms.txt follows the spec
Looks good · AI answer readiness · Published platform rule
Observed evidence
llms.txt has an H1, a summary, 8 section(s) and 70 link(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: Advertised machine interfaces are inspectable
Looks good · AI answer readiness · Measured on your page
Observed evidence
1 advertised specification(s) have recognizable OpenAPI structure and operations. Authentication and operation success are untested.
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 64/100 for publisher readiness. Ignore this section if you do not run ads.
Could be better: Sampled publisher-content coverage1/7 editorial pages expose fewer than 250 publisher words; those 7 pages hold 5237 publisher words in total.
Could be better · AdSense policy · Review suggestedCritical
Observed evidence
1/7 editorial pages expose fewer than 250 publisher words; those 7 pages hold 5237 publisher words in total. 3 of the 10 sampled pages are support or tool pages and were 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://safegrd.dev/login
Could be better: Tool pages expose explanatory content1/10 tool-style screen(s) expose fewer than 80 publisher words.
Could be better · AdSense policy · Review suggested
Observed evidence
1/10 tool-style screen(s) expose fewer than 80 publisher words. Google publishes no minimum word count; this is an audit heuristic.
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
Explain the tool's purpose, inputs, method, limitations, and result interpretation in source HTML. Add useful material, not filler.
Affected pages (1)
- https://safegrd.dev/login
Not measured: ads.txtNo ads.txt yet.
Not measured · AdSense policy · Not established
Observed evidence
No ads.txt yet.
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
When AdSense provides your publisher entry, publish it exactly at /ads.txt and monitor authorization status in your 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://safegrd.dev/privacy
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: Privacy policy advertising disclosures
Looks good · AdSense policy · Published platform rule
Observed evidence
Fetched privacy policy contains cookie/storage, advertising, and third-party/vendor disclosure signals.
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: /terms
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: https://safegrd.dev/about
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 page found: https://safegrd.dev/contact
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: support@safegrd.dev, security@safegrd.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
6/7 editorial pages clear the audit's publisher-content triage threshold. 3 of the 10 sampled pages are support or tool pages and were 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: Publisher content differs across URLs
Looks good · AdSense policy · Review suggested
Observed evidence
No high publisher-content repetition among 8 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: Policy pages linked site-wide
Looks good · AdSense policy · Measured on your page
Observed evidence
All 10 crawled pages link to the 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: 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 1403 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 0/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 | safegrd.dev |
|---|---|
| Server | Nginx |
| IP addresses | 159.223.162.104, 2604:a880:400:d1:0:5:24df:b001 |
| DNS A | 159.223.162.104 |
| DNS AAAA | 2604:a880:400:d1:0:5:24df:b001 |
| DNS NS | ns2.digitalocean.com · ns3.digitalocean.com · ns1.digitalocean.com |
| DNS MX | 1 smtp.google.com |
| TLS | TLSv1.3TLS_AES_256_GCM_SHA384 |
| Certificate issuer | Let's Encrypt / YE2 |
| Certificate valid until | Dec 18 13:38:30 2026 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
1740 publisher words
Page structure
html content
Observed discovery
Depth 0 · 9 incoming links
HTTP 200 · 47.1 KB source
Source interactions
101 controls · 0 unnamed
6 script / 2 stylesheet references
- Canonical declaration
- https://safegrd.dev/
- Schema types
- Organization, WebSite, SoftwareApplication, Offer, UnitPriceSpecification
- Outgoing links in sampled graph
- /integrations · /pricing · /guides · /docs · /trust · /login · /signup · /dashboard · /docs/install · /docs/attestation · /docs/mcp · /docs/agents · /guides/test-database-backup-restore · /compare/aws-backup · /compare/simplebackups · /compare/ottomatik · /docs/surfaces/postgres · /compliance · /dpa · /postgresql-backup · /mysql-backup · /mongodb-backup · /supabase-backup · /coolify-backup · /backup-verification · /guides/postgres-backup-s3 · /guides/immutable-backups-s3-object-lock · /compare/pgbackrest · /compare/barman · /compare/backupdrill · /compare/databasus · /docs/api · /openapi.json · /llms.txt · /install.sh · /tools/backup-file-checker · /tools/pg-dump-command-builder · /tools/object-lock-cost-calculator · /about · /changelog · /contact · /terms · /privacy · /subprocessors · /refunds
Routes: / · /about · /contact · /privacy · /integrations · /pricing · /guides · /docs · /trust · /login
Resource origins 1
Resources associated with your website. External resources may belong to the same organization.
- https://safegrd.dev/stylesheet, script, media, image · 81 references · same 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 | Declared policy for this page. |
| Googlebotsearch | /about | allowed | Declared policy for this page. |
| Googlebotsearch | /contact | allowed | Declared policy for this page. |
| Googlebotsearch | /privacy | allowed | Declared policy for this page. |
| Googlebotsearch | /integrations | allowed | Declared policy for this page. |
| Googlebotsearch | /pricing | allowed | Declared policy for this page. |
| Googlebotsearch | /guides | allowed | Declared policy for this page. |
| Googlebotsearch | /docs | allowed | Declared policy for this page. |
| Googlebotsearch | /trust | allowed | Declared policy for this page. |
| Googlebotsearch | /login | allowed | Declared policy for this page. |
| bingbotsearch | / | allowed | Declared policy for this page. |
| bingbotsearch | /about | allowed | Declared policy for this page. |
| bingbotsearch | /contact | allowed | Declared policy for this page. |
| bingbotsearch | /privacy | allowed | Declared policy for this page. |
| bingbotsearch | /integrations | allowed | Declared policy for this page. |
| bingbotsearch | /pricing | allowed | Declared policy for this page. |
| bingbotsearch | /guides | allowed | Declared policy for this page. |
| bingbotsearch | /docs | allowed | Declared policy for this page. |
| bingbotsearch | /trust | allowed | Declared policy for this page. |
| bingbotsearch | /login | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | / | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /about | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /contact | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /privacy | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /integrations | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /pricing | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /guides | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /docs | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /trust | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /login | allowed | Declared policy for this page. |
| PerplexityBotsearch | / | allowed | Declared policy for this page. |
| PerplexityBotsearch | /about | allowed | Declared policy for this page. |
| PerplexityBotsearch | /contact | allowed | Declared policy for this page. |
| PerplexityBotsearch | /privacy | allowed | Declared policy for this page. |
| PerplexityBotsearch | /integrations | allowed | Declared policy for this page. |
| PerplexityBotsearch | /pricing | allowed | Declared policy for this page. |
| PerplexityBotsearch | /guides | allowed | Declared policy for this page. |
| PerplexityBotsearch | /docs | allowed | Declared policy for this page. |
| PerplexityBotsearch | /trust | allowed | Declared policy for this page. |
| PerplexityBotsearch | /login | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | / | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /about | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /contact | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /privacy | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /integrations | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /pricing | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /guides | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /docs | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /trust | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /login | allowed | Declared policy for this page. |
| GPTBottraining | / | allowed | Declared policy for this page. |
| GPTBottraining | /about | allowed | Declared policy for this page. |
| GPTBottraining | /contact | allowed | Declared policy for this page. |
| GPTBottraining | /privacy | allowed | Declared policy for this page. |
| GPTBottraining | /integrations | allowed | Declared policy for this page. |
| GPTBottraining | /pricing | allowed | Declared policy for this page. |
| GPTBottraining | /guides | allowed | Declared policy for this page. |
| GPTBottraining | /docs | allowed | Declared policy for this page. |
| GPTBottraining | /trust | allowed | Declared policy for this page. |
| GPTBottraining | /login | allowed | Declared policy for this page. |
| ClaudeBottraining | / | allowed | Declared policy for this page. |
| ClaudeBottraining | /about | allowed | Declared policy for this page. |
| ClaudeBottraining | /contact | allowed | Declared policy for this page. |
| ClaudeBottraining | /privacy | allowed | Declared policy for this page. |
| ClaudeBottraining | /integrations | allowed | Declared policy for this page. |
| ClaudeBottraining | /pricing | allowed | Declared policy for this page. |
| ClaudeBottraining | /guides | allowed | Declared policy for this page. |
| ClaudeBottraining | /docs | allowed | Declared policy for this page. |
| ClaudeBottraining | /trust | allowed | Declared policy for this page. |
| ClaudeBottraining | /login | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | / | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /about | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /contact | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /privacy | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /integrations | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /pricing | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /guides | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /docs | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /trust | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /login | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | / | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /about | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /contact | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /privacy | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /integrations | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /pricing | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /guides | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /docs | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /trust | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /login | allowed | Declared policy for this page. |
Advertised APIs and machine interfaces
documentation · declared
https://safegrd.dev/docs
This interface was advertised; its runtime behavior remains unverified.
documentation · declared
https://safegrd.dev/docs/install
This interface was advertised; its runtime behavior remains unverified.
documentation · declared
https://safegrd.dev/docs/attestation
This interface was advertised; its runtime behavior remains unverified.
documentation · declared
https://safegrd.dev/docs/mcp
This interface was advertised; its runtime behavior remains unverified.
documentation · declared
https://safegrd.dev/docs/agents
This interface was advertised; its runtime behavior remains unverified.
documentation · declared
https://safegrd.dev/docs/surfaces/postgres
This interface was advertised; its runtime behavior remains unverified.
documentation · declared
https://safegrd.dev/docs/api
This interface was advertised; its runtime behavior remains unverified.
openapi · verified · 23 operations declared
https://safegrd.dev/openapi.json
Published interface document available. Operation success and authentication are unverified.
documentation · declared
https://safegrd.dev/docs/surfaces/mysql
This interface was advertised; its runtime behavior remains unverified.
documentation · declared
https://safegrd.dev/docs/surfaces/mongodb
This interface was advertised; its runtime behavior remains unverified.
documentation · declared
https://safegrd.dev/docs/surfaces/sqlite
This interface was advertised; its runtime behavior remains unverified.
documentation · declared
https://safegrd.dev/docs/surfaces/files
This interface was advertised; its runtime behavior remains unverified.
documentation · declared
https://safegrd.dev/docs/surfaces/email
This interface was advertised; its runtime behavior remains unverified.
documentation · declared
https://safegrd.dev/docs/surfaces/wordpress
This interface was advertised; its runtime behavior remains unverified.
documentation · declared
https://safegrd.dev/docs/surfaces/laravel
This interface was advertised; its runtime behavior remains unverified.
documentation · declared
https://safegrd.dev/docs/storage
This interface was advertised; its runtime behavior remains unverified.
documentation · declared
https://safegrd.dev/docs/alerts
This interface was advertised; its runtime behavior remains unverified.
documentation · declared
https://safegrd.dev/docs/surfaces
This interface was advertised; its runtime behavior remains unverified.
documentation · declared
https://safegrd.dev/docs/account
This interface was advertised; its runtime behavior remains unverified.
documentation · declared
https://safegrd.dev/docs/daemon
This interface was advertised; its runtime behavior remains unverified.
documentation · declared
https://safegrd.dev/docs/verify
This interface was advertised; its runtime behavior remains unverified.
documentation · declared
https://safegrd.dev/docs/hosted
This interface was advertised; its runtime behavior remains unverified.
documentation · declared
https://safegrd.dev/docs/threat-shield
This interface was advertised; its runtime behavior remains unverified.
documentation · declared
https://safegrd.dev/docs/security
This interface was advertised; its runtime behavior remains unverified.
documentation · declared
https://safegrd.dev/docs/surfaces/databases
This interface was advertised; its runtime behavior remains unverified.
documentation · declared
https://safegrd.dev/docs/deploy
This interface was advertised; its runtime behavior remains unverified.
documentation · declared
https://safegrd.dev/docs/cli
This interface was advertised; its runtime behavior remains unverified.
documentation · declared
https://safegrd.dev/docs/config
This interface was advertised; its runtime behavior remains unverified.
documentation · declared
https://safegrd.dev/docs/runbooks
This interface was advertised; its runtime behavior remains unverified.
documentation · declared
https://safegrd.dev/docs/troubleshooting
This interface was advertised; its runtime behavior remains unverified.
Public DNS and TLS endpoint
safegrd.dev · observed · 159.223.162.104, 2604:a880:400:d1:0:5:24df:b001
- A
- 159.223.162.104
- AAAA
- 2604:a880:400:d1:0:5:24df:b001
- CNAME
- Unavailable for this exact hostname
- NS
- ns2.digitalocean.com · ns3.digitalocean.com · ns1.digitalocean.com
- MX
- 1 smtp.google.com
- CAA
- Unavailable for this exact hostname
TLS: TLSv1.3
Certificate validation passed for the observed endpoint.
Issuer: Let's Encrypt / YE2
Certificate valid until: Dec 18 13:38:30 2026 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
Earn visibility: submit to directories and communities
This audit cannot measure backlinks or resulting rankings. Relevant directories and communities are options for improving discovery signals.
- 02
With decent structure and content, affiliate programs are an option to research; this audit does not measure revenue.
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://safegrd.dev/
- https://safegrd.dev/about
- https://safegrd.dev/contact
- https://safegrd.dev/privacy
- https://safegrd.dev/integrations
- https://safegrd.dev/pricing
- https://safegrd.dev/guides
- https://safegrd.dev/docs
- https://safegrd.dev/trust
- https://safegrd.dev/login