ObliviOS Developer portal Project site

Home / Decisions / ADR-262

Harden the headers of oblivios.org, add structured data and the robots meta, and let the first deployment stay public.

Accepted, recorded 18 November 2026.

Decision
ADR-262
Date
2026-11-18
Status
AcceptedAccepted (owner, 2026-11-18).
Mentions
ADR-248
Mentioned by
ADR-267

1Decision

Harden the headers of oblivios.org, add structured data and the robots meta, and let the first deployment stay public.

(1) Headers: the CSP is default-src 'self'; base-uri 'none'; form-action 'none'; frame-ancestors 'self' (the three added directives are not covered by default-src), X-Frame-Options: SAMEORIGIN is added for old browsers, and Permissions-Policy lists fifteen interfaces as off (accelerometer, autoplay, camera, display capture, geolocation, gyroscope, HID, magnetometer, microphone, MIDI, payment, serial, USB, XR).

The empty Permissions-Policy of ADR-248 is replaced: the live response of 2026-11-18 had no such header, because Vercel does not serve an empty value [measured, curl -I]. bluetooth is not listed: Chromium reports it as an unrecognised feature [measured, console of the pane]. Vercel adds Access-Control-Allow-Origin: * to the static files; it is kept and the Privacy page says so, because the site holds nothing that is not public.

(2) Structured data: every page except the 404 page carries one schema.org JSON-LD block (Organization, WebSite, WebPage, and a BreadcrumbList or, on the home page, a SoftwareSourceCode that names the four repositories and isBasedOn GrapheneOS). Every value is a fact that the page or the footer already states; the block has no licence, rating, application type or price.

check-build.mjs allows exactly this block, parses it, requires it on each page but the 404 page, and still fails on any other script. (3) The robots meta is index, follow, max-image-preview:large, max-snippet:-1, and noindex on the 404 page only; check-build.mjs fails on a page where this is the other way round.

(4) The owner said on 2026-11-18 that the deployment at oblivios-docs.vercel.app may stay public until the domain is linked, that it must be secure, that SEO is done as technique now and as content later, and that the owner links the domain.

2Why and evidence

Search engines read the page, not the intent: titles, descriptions, canonical, Open Graph and the sitemap were there already, so what is left on the page is structured data, the robots meta and a sound set of headers; the larger effect on being found comes from content that answers what people search for and from links to the site, which the owner decides next. The CSP of default-src 'self' alone left framing, forms and the base address open.

Rejected: lastmod in the sitemap (one date for every page, rewritten at each regeneration, is not a modification date, and a search engine ignores a date that is not accurate); FAQPage markup (no expected effect on this site [assumption: from memory of the search engine's rules, not checked against its current documentation]); a license property (the licence of the patch repositories is not stated in one place); Cross-Origin-Resource-Policy (it could block other sites from showing the social preview image, which was not assessed); the HSTS preload submission (D-2: after the quiet week); IndexNow (it sends the page addresses to a third party); new pages for search questions (the owner chooses them next, each needs a claim review).

3Consequences

Done and read on 2026-11-18: npm run build with and without VERCEL=1, check-build: OK on 11 pages with the same 307 links; three mutation runs fail as they must (broken JSON-LD, a second script, noindex on the home page); the headers read with curl -I on the local server; the JSON-LD of the home page read; in the browser pane 44 loads (11 pages at 320, 390, 798 and 1920 px) show no overflow, no policy violation, no blocked same-origin frame, and the fonts load.

Not done: a check of the live headers (they reach Vercel with the next push and deployment); a structured-data validator or a rich-results test (both are external services and were not run); the Search Console and Bing Webmaster verification (needs the owner's accounts and the linked domain); the Enable of Web Analytics and a redeployment, which the owner does, and a read of /_vercel/insights/script.js after it; the linking of the domain, the primary domain and the redirect of the Vercel address to it (the owner); the description, topics and homepage of the four repositories and the wiki and projects switched off (R-3, the wording is not yet approved).

4Review when

A search engine reports an error in the structured data; a header breaks a feature of a browser; the licence of the code is stated in one place; the owner turns the site private or asks for the content pages.

Read from docs/governance/decision-log.md, entry ADR-262.