Website report

Visit sitehttps://privacyboard.io/

Stay on top of privacy compliance: policies, records, cookie consent and privacy requests in one workspace, with a public privacy center and an AI connector.

Audit Full discovery audit·Language English (en)·Response HTTP 200·Served by Vercel

Analysed Nov 16, 2026 · 15 categories · 120 passed · 13 warnings · 1 issue · 16 informational

Audit score

C

79/100

Mixed

Agentic
100
SEO
79

What we found

1Needs a fix13Could be better120Looks good16Informational
  1. 1.Needs a fix: No dead placeholder links: needs fixing. see checkWorking, descriptive links help people find the right page.
  2. 2.Could be better: og:url and og:type: needs attention. see checkComplete link previews make your pages easier to recognize and share.
  3. 3.Could be better: Your headings skip levels. see checkA clear outline makes content easier to navigate, including with a screen reader.
  4. 4.Could be better: Your content security policy needs work. see checkThis policy limits which scripts and resources can run on your website.
  5. 5.Could be better: Question-style headings: needs attention. see checkClear, accessible information helps AI assistants understand and cite your website.

Built with 2 technologies· detected stack

Read from the public source and response headers of the sampled pages.

How it fits together

  • Next.jsFramework
  • VercelHosting / edge
Hosting and deploymentType
  • VercelHosting / edge
Frameworks and librariesType
  • Next.jsFramework

A framework or CDN signal describes the public response, not the origin host or private backend.

Site checks

120 passed · 13 warnings · 1 issues

Every observation from the crawl, grouped by what it describes. Open a row for the evidence and the recommended fix.

Metadata11Looks good

100/100
Looks good: Page title exists

Looks good · Metadata · Measured on your page

Observed evidence

Title found: "Privacyboard: privacy compliance made simple"

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 44 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 "Privacyboard: privacy compliance made simple" 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: "Stay on top of privacy compliance: policies, records, cookie consent and privacy requests …"

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 157 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/100
Looks 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://privacyboard.io/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 1548 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://privacyboard.io/

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 (privacyboard.io).

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 (27 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/100
Not measured: ReadabilityFlesch reading ease ≈ 52.

Not measured · Content · Not established

Observed evidence

Flesch reading ease ≈ 52.

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 1573 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 1573 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 15.2%.

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: privacy, compliance, made, simple.

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: No deprecated HTML tags

Looks good · Content · Measured on your page

Observed evidence

No deprecated HTML tags.

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

5 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.

Social sharing1Could be better6Looks good1Informational

92/100
Could be better: og:url and og:typeog:url is missing.

Could be better · Social sharing · Review suggested

Observed evidence

og:url is missing.

Why this matters

This is what your link looks like when someone drops it into a chat or a feed. It is there, but weaker than this check expects.

Recommended fix

Add og:url to complete the Open Graph basics.

Reference
Not measured: og:site_nameNo og:site_name tag.

Not measured · Social sharing · Not established

Observed evidence

No og:site_name 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 it. Share cards use it to label the publisher; consistent naming also gives this audit a measurable entity signal. It does not measure or guarantee citations, rankings, or traffic.

Reference
Looks good: Open Graph title

Looks good · Social sharing · Measured on your page

Observed evidence

og:title: "Privacyboard: privacy compliance made simple"

Why this matters

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Open Graph description

Looks good · Social sharing · Measured on your page

Observed evidence

og:description: "Stay on top of privacy compliance: policies, records, cookie consent and privacy requests …"

Why this matters

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Open Graph image

Looks good · Social sharing · Measured on your page

Observed evidence

og:image is set: "https://privacyboard.io/opengraph-image"

Why this matters

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Share image loads

Looks good · Social sharing · Measured on your page

Observed evidence

og:image returns 200 (image/png).

Why this matters

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Share image dimensions declared

Looks good · Social sharing · Measured on your page

Observed evidence

Dimensions declared: 1200×630.

Why this matters

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Twitter/X card

Looks good · Social sharing · Measured on your page

Observed evidence

twitter:card is "summary_large_image".

Why this matters

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Structured data5Looks good

100/100
Looks 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 9 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: Organization, WebSite.

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: Breadcrumb schema on inner pages

Looks good · Structured data · Measured on your page

Observed evidence

5/8 inner pages have breadcrumb schema.

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: TechArticle, Offer, FAQPage, HowTo, SoftwareApplication, ItemList, CollectionPage.

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.

Headings1Could be better6Looks good

91/100
Could be better: Heading levels don't skip1 heading level skip: H2 → H4 "Your data.

Could be better · Headings · Review suggested

Observed evidence

1 heading level skip: H2 → H4 "Your data. Our responsibility.".

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.

Looks good: H1 exists

Looks good · Headings · Measured on your page

Observed evidence

H1 found: "Privacy compliance made simple."

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 "Privacy compliance made simple.".

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

27 headings, averaging 4.9 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

13 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 measured
Not 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.

Mobile4Looks good2Informational

100/100
Not applicable: Responsive image markupNone of the 29 images use srcset.

Not applicable · Mobile · Measured on your page

Observed evidence

None of the 29 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

1392 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

57 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.

Language3Looks good

100/100
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: hreflang syntax

Looks good · Language · Measured on your page

Observed evidence

3 syntactically valid hreflang tags including x-default. Reciprocal links and target content were not verified.

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.

Branding2Looks good2Informational

100/100
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"> (/favicon.ico).

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.

Looks good: Apple touch icon

Looks good · Branding · Measured on your page

Observed evidence

apple-touch-icon is declared.

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

100/100

Measured from the audited response and its markup. These are source observations, not field Core Web Vitals.

Performance measurements observed during the audit
MeasureThis siteReading
Web fonts don't block text—Informational: not applicableNo Google Fonts stylesheet links detected.
Server response time244 msLooks good: goodThe audit received response headers after 244 ms from one test location.
HTML payload size259 KBLooks good: goodThe page's HTML is 259 KB uncompressed: acceptable, though under 100 KB is a good target for content pages.
No render-blocking head scripts—Looks good: goodNo synchronous render-blocking scripts in <head>.
Inline styles are bounded0.0 KBLooks good: goodInline styles total 0.0 KB.
Script/stylesheet count—Looks good: good23 total script/style resources — reasonable.
HTML served compressed—Looks good: goodHTML is compressed with br.
Iframe usage—Looks good: goodNo iframes.
Source HTML weight259.0 KBInformational: measured source, not transferred bytes259.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

100/100

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'.

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: HSTS header

Looks good · Security · Measured on your page

Observed evidence

HSTS is set: max-age=63072000.

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 'self').

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

2 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.

AI answer readiness

100/100

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: Question-style headingsOnly 12% of 173 H2/H3 headings are question-shaped.

Could be better · AI answer readiness · Review suggested

Observed evidence

Only 12% of 173 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: Answers lead the section1 paragraph(s) open with preamble ("In this article…", "Let's dive in…").

Could be better · AI answer readiness · Review suggested

Observed evidence

1 paragraph(s) open with preamble ("In this article…", "Let's dive in…").

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

Answer the section's question before adding background. The opening-phrase heuristic does not establish what an answer engine will quote.

Could be better: Definitional openingThe opening paragraph doesn't define what the site/topic is: "For your customers…"

Could be better · AI answer readiness · Review suggested

Observed evidence

The opening paragraph doesn't define what the site/topic is: "For your customers…"

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: Question headings have concise answers8/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

8/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://privacyboard.io/features/privacy-center
  • https://privacyboard.io/for/saas
  • https://privacyboard.io/regulations/gdpr
  • https://privacyboard.io/partners
  • https://privacyboard.io/vs
  • https://privacyboard.io/security
Could be better: Markdown copies of pages3 of 3 markdown URLs answered 200 but returned HTML, not markdown.

Could be better · AI answer readiness · Measured on your page

Observed evidence

3 of 3 markdown URLs answered 200 but returned HTML, not markdown.

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

Either serve real markdown at those URLs or return 404. A 200 that hands back the HTML page wastes a retrieval and can be cached as the markdown copy.

Affected pages (3)

  • https://privacyboard.io/index.md
  • https://privacyboard.io/contact.md
  • https://privacyboard.io/index.html.md
Reference
Could be better: Accept: text/markdown negotiationThe server returns markdown for Accept: text/markdown but does not declare Vary: Accept.

Could be better · AI answer readiness · Measured on your page

Observed evidence

The server returns markdown for Accept: text/markdown but does not declare Vary: Accept.

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 Vary: Accept (or an equivalent cache-key configuration) so shared caches keep HTML and markdown representations separate.

Not measured: Authored, dated articlesNo Article/BlogPosting schema found.

Not measured · AI answer readiness · Not established

Observed evidence

No Article/BlogPosting schema found.

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 Article schema with author and datePublished so the page exposes clear provenance for retrieval. This audit does not measure or guarantee citations or rankings.

Not measured: Citable facts density131 concrete figures across 3275 words.

Not measured · AI answer readiness · Not established

Observed evidence

131 concrete figures across 3275 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 (199274 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: FAQ/QA schema

Looks good · AI answer readiness · Measured on your page

Observed evidence

FAQ/QA schema found.

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×3, section×12, nav×5, 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: Content is chunkable

Looks good · AI answer readiness · Measured on your page

Observed evidence

Paragraphs average 10 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: Freshness signals

Looks good · AI answer readiness · Measured on your page

Observed evidence

dateModified present in 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: Cites external sources

Looks good · AI answer readiness · Measured on your page

Observed evidence

45 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

Identity schema present.

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 "Privacyboard" and 5 identity URL(s) stay on privacyboard.io.

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: Machine-readable provenance signals

Looks good · AI answer readiness · Measured on your page

Observed evidence

Found 4 of 4 machine-readable provenance signal types: author, contact, breadcrumb, date.

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, 9 section(s) and 1514 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.

AdSense readinessOptional

72/100

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 63/100 for publisher readiness. Ignore this section if you do not run ads.

Could be better: About pageNo about page found.

Could be better · AdSense policy · Review suggested

Observed evidence

No about page found.

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 an About page that identifies the publisher, site purpose, and relevant experience. This supports content transparency but is not a standalone AdSense requirement.

Could be better: Latest article names an author and a dateThe newest article shows a date but no author.

Could be better · AdSense policy · Measured on your page

Observed evidence

The newest article shows a date but no author.

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 the missing one in the visible page and in Article JSON-LD, so the byline and the markup agree.

Affected pages (1)

  • https://privacyboard.io/blog/page/2
Reference
Could be better: Author or publisher background4/4 attributed editorial pages provide no discoverable author or publisher background.

Could be better · AdSense policy · Review suggested

Observed evidence

4/4 attributed editorial pages provide no discoverable author or publisher background.

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

Link the byline to an author profile or About page, or add truthful structured author details. This is a transparency heuristic, not an AdSense approval rule.

Affected pages (4)

  • https://privacyboard.io/
  • https://privacyboard.io/features/privacy-center
  • https://privacyboard.io/for/saas
  • https://privacyboard.io/regulations/gdpr
Reference
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.

Reference
Looks good: Privacy policy page

Looks good · AdSense policy · Measured on your page

Observed evidence

Privacy policy found: https://privacyboard.io/docs/documents/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: 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.

Reference
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: Contact method

Looks good · AdSense policy · Measured on your page

Observed evidence

Contact page found: https://privacyboard.io/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: hello@privacyboard.io.

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: Sampled publisher-content coverage

Looks good · AdSense policy · Review suggested

Observed evidence

All 6 editorial pages expose at least 250 publisher words; those pages hold 6307 publisher words in total. 3 of the 9 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: Thin page share

Looks good · AdSense policy · Review suggested

Observed evidence

6/6 editorial pages clear the audit's publisher-content triage threshold. 3 of the 9 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.

Reference
Looks good: Tool pages expose explanatory content

Looks good · AdSense policy · Review suggested

Observed evidence

All 9 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 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: Clear navigation

Looks good · AdSense policy · Measured on your page

Observed evidence

Navigation present with 125 links.

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.

Show 4 more checks
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.

Looks good: Author bylines on content

Looks good · AdSense policy · Review suggested

Observed evidence

Author attribution appears on all 4 sampled editorial 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 change.

Reference
Looks good: Latest article has real depth

Looks good · AdSense policy · Measured on your page

Observed evidence

The newest article carries 661 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.

Hosting and infrastructure

Public endpoint facts observed at audit time. A CDN or proxy can conceal the origin infrastructure.

Hosting and infrastructure observations
Hostnameprivacyboard.io
HostingVercel
IP addresses76.76.21.21
DNS A76.76.21.21
DNS NSns1.vercel-dns.com · ns2.vercel-dns.com
DNS MX1 smtp.google.com
DNS CAA{"critical":0,"type":"CAA","issue":"letsencrypt.org"} · {"critical":0,"type":"CAA","issue":"pki.goog"} · {"critical":0,"type":"CAA","issue":"sectigo.com"}
TLSTLSv1.3TLS_AES_128_GCM_SHA256
Certificate issuerLet's Encrypt / YR2
Certificate valid untilJan 31 09:24:22 2027 GMT
Certificate validationPassed

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

1573 publisher words

Page structure

html content

Observed discovery

Depth 0 · 8 incoming links

HTTP 200 · 259.0 KB source

Source interactions

159 controls · 0 unnamed

15 script / 8 stylesheet references

Canonical declaration
https://privacyboard.io/
Schema types
WebSite, Organization, ImageObject, ContactPoint, SoftwareApplication, Offer, FAQPage, Question, Answer
Outgoing links in sampled graph
/features/privacy-center · /features/data-processing-agreement-generator · /features/subprocessor-and-vendor-list · /features/security-questionnaire-automation · /features/privacy-policy-generator · /features/cookie-consent-banner · /features/data-subject-request-management · /features/record-of-processing-activities · /features/data-breach-register · /features/dpia-and-transfer-impact-assessment · /features/gdpr-compliance-monitoring · /features/mcp-connector · /features · /for/saas · /for/privacy-consultants · /for/dpo · /regulations/gdpr · /regulations/cookie-consent-eprivacy · /regulations/eu-ai-act · /regulations/us-state-privacy-laws · /regulations/international-data-transfers · /partners · /vs · /security · /login · /regulations · /pricing · /docs · /blog · /vendors · /changelog · /integrations · /contact · /gdpr-checker · /login · /login · /login · /fr · /terms · /legal-notice

Routes: / · /contact · /docs · /features · /for · /regulations · /partners · /vs · /security

Resource origins 1

Resources associated with your website. External resources may belong to the same organization.

  • https://privacyboard.io/stylesheet, script, image · 268 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.

Robots policy for every evaluated crawler and sampled page
Crawler / purposePagePolicyMatched directive
Googlebotsearch/allowedallow: /
Googlebotsearch/contactallowedallow: /
Googlebotsearch/docs/documents/privacy-policyallowedallow: /
Googlebotsearch/features/privacy-centerallowedallow: /
Googlebotsearch/for/saasallowedallow: /
Googlebotsearch/regulations/gdprallowedallow: /
Googlebotsearch/partnersallowedallow: /
Googlebotsearch/vsallowedallow: /
Googlebotsearch/securityallowedallow: /
bingbotsearch/allowedallow: /
bingbotsearch/contactallowedallow: /
bingbotsearch/docs/documents/privacy-policyallowedallow: /
bingbotsearch/features/privacy-centerallowedallow: /
bingbotsearch/for/saasallowedallow: /
bingbotsearch/regulations/gdprallowedallow: /
bingbotsearch/partnersallowedallow: /
bingbotsearch/vsallowedallow: /
bingbotsearch/securityallowedallow: /
OAI-SearchBotsearch/allowedallow: /
OAI-SearchBotsearch/contactallowedallow: /
OAI-SearchBotsearch/docs/documents/privacy-policyallowedallow: /
OAI-SearchBotsearch/features/privacy-centerallowedallow: /
OAI-SearchBotsearch/for/saasallowedallow: /
OAI-SearchBotsearch/regulations/gdprallowedallow: /
OAI-SearchBotsearch/partnersallowedallow: /
OAI-SearchBotsearch/vsallowedallow: /
OAI-SearchBotsearch/securityallowedallow: /
PerplexityBotsearch/allowedallow: /
PerplexityBotsearch/contactallowedallow: /
PerplexityBotsearch/docs/documents/privacy-policyallowedallow: /
PerplexityBotsearch/features/privacy-centerallowedallow: /
PerplexityBotsearch/for/saasallowedallow: /
PerplexityBotsearch/regulations/gdprallowedallow: /
PerplexityBotsearch/partnersallowedallow: /
PerplexityBotsearch/vsallowedallow: /
PerplexityBotsearch/securityallowedallow: /
Claude-SearchBotsearch/allowedallow: /
Claude-SearchBotsearch/contactallowedallow: /
Claude-SearchBotsearch/docs/documents/privacy-policyallowedallow: /
Claude-SearchBotsearch/features/privacy-centerallowedallow: /
Claude-SearchBotsearch/for/saasallowedallow: /
Claude-SearchBotsearch/regulations/gdprallowedallow: /
Claude-SearchBotsearch/partnersallowedallow: /
Claude-SearchBotsearch/vsallowedallow: /
Claude-SearchBotsearch/securityallowedallow: /
GPTBottraining/allowedallow: /
GPTBottraining/contactallowedallow: /
GPTBottraining/docs/documents/privacy-policyallowedallow: /
GPTBottraining/features/privacy-centerallowedallow: /
GPTBottraining/for/saasallowedallow: /
GPTBottraining/regulations/gdprallowedallow: /
GPTBottraining/partnersallowedallow: /
GPTBottraining/vsallowedallow: /
GPTBottraining/securityallowedallow: /
ClaudeBottraining/allowedallow: /
ClaudeBottraining/contactallowedallow: /
ClaudeBottraining/docs/documents/privacy-policyallowedallow: /
ClaudeBottraining/features/privacy-centerallowedallow: /
ClaudeBottraining/for/saasallowedallow: /
ClaudeBottraining/regulations/gdprallowedallow: /
ClaudeBottraining/partnersallowedallow: /
ClaudeBottraining/vsallowedallow: /
ClaudeBottraining/securityallowedallow: /
Google-Extendedtraining and other Google AI uses/allowedallow: /
Google-Extendedtraining and other Google AI uses/contactallowedallow: /
Google-Extendedtraining and other Google AI uses/docs/documents/privacy-policyallowedallow: /
Google-Extendedtraining and other Google AI uses/features/privacy-centerallowedallow: /
Google-Extendedtraining and other Google AI uses/for/saasallowedallow: /
Google-Extendedtraining and other Google AI uses/regulations/gdprallowedallow: /
Google-Extendedtraining and other Google AI uses/partnersallowedallow: /
Google-Extendedtraining and other Google AI uses/vsallowedallow: /
Google-Extendedtraining and other Google AI uses/securityallowedallow: /
ChatGPT-Useruser-initiated; robots may not apply/allowedallow: /
ChatGPT-Useruser-initiated; robots may not apply/contactallowedallow: /
ChatGPT-Useruser-initiated; robots may not apply/docs/documents/privacy-policyallowedallow: /
ChatGPT-Useruser-initiated; robots may not apply/features/privacy-centerallowedallow: /
ChatGPT-Useruser-initiated; robots may not apply/for/saasallowedallow: /
ChatGPT-Useruser-initiated; robots may not apply/regulations/gdprallowedallow: /
ChatGPT-Useruser-initiated; robots may not apply/partnersallowedallow: /
ChatGPT-Useruser-initiated; robots may not apply/vsallowedallow: /
ChatGPT-Useruser-initiated; robots may not apply/securityallowedallow: /
Advertised APIs and machine interfaces
  • documentation · declared

    https://privacyboard.io/docs

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://privacyboard.io/docs/documents/privacy-policy

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://privacyboard.io/md/docs/documents/privacy-policy

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://privacyboard.io/docs/getting-started

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://privacyboard.io/docs/getting-started/introduction

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://privacyboard.io/docs/getting-started/quickstart

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://privacyboard.io/docs/getting-started/how-it-works

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://privacyboard.io/docs/getting-started/plans-and-pricing

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://privacyboard.io/docs/getting-started/ai-assistants

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://privacyboard.io/docs/company

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://privacyboard.io/docs/company/workspaces

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://privacyboard.io/docs/company/team-and-roles

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://privacyboard.io/docs/company/website-import

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://privacyboard.io/docs/company/company-profile

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://privacyboard.io/docs/company/branding

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://privacyboard.io/docs/company/email-settings

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://privacyboard.io/docs/company/workspace-settings

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://privacyboard.io/docs/company/partner-kit

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://privacyboard.io/docs/documents

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://privacyboard.io/docs/documents/documents-overview

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://privacyboard.io/docs/documents/vendor-list-document

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://privacyboard.io/docs/documents/data-processing-agreement

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://privacyboard.io/docs/documents/cookie-policy

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://privacyboard.io/docs/documents/governance-policy

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://privacyboard.io/docs/documents/validate-and-export

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://privacyboard.io/docs/documents/use-your-own-document

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://privacyboard.io/docs/vendors

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://privacyboard.io/docs/vendors/vendors-overview

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://privacyboard.io/docs/vendors/vendor-roles

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://privacyboard.io/docs/vendors/data-location

    This interface was advertised; its runtime behavior remains unverified.

Public DNS and TLS endpoint

privacyboard.io · observed · 76.76.21.21

A
76.76.21.21
AAAA
Unavailable for this exact hostname
CNAME
Unavailable for this exact hostname
NS
ns1.vercel-dns.com · ns2.vercel-dns.com
MX
1 smtp.google.com
CAA
{"critical":0,"type":"CAA","issue":"letsencrypt.org"} · {"critical":0,"type":"CAA","issue":"pki.goog"} · {"critical":0,"type":"CAA","issue":"sectigo.com"}

TLS: TLSv1.3

Certificate validation passed for the observed endpoint.

Issuer: Let's Encrypt / YR2

Certificate valid until: Jan 31 09:24:22 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.

  1. 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.

  2. 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.

Open in ChatGPT Open in Grok Open in Perplexity

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://privacyboard.io/
  • https://privacyboard.io/contact
  • https://privacyboard.io/docs/documents/privacy-policy
  • https://privacyboard.io/features/privacy-center
  • https://privacyboard.io/for/saas
  • https://privacyboard.io/regulations/gdpr
  • https://privacyboard.io/partners
  • https://privacyboard.io/vs
  • https://privacyboard.io/security