Braio

Evidence and method

Czytaj po polsku

SEO/GEO readiness audit example - HTTP and HTML evidence

An audit should start with verifiable observations. This dated snapshot of Braio's public pages shows what the server returned, what raw HTML establishes and which conclusions it cannot support.

This HTTP/HTML snapshot was captured while auditing Braio's website. It is not a complete report generated by the SEO/GEO product or a measurement of rankings or AI recommendations. The current production site may already differ.

Content reviewed:
01

What we measured and when

On 24 October 2026, we made 21 public GET requests: PL/EN pages, samples of agents and comparisons, robots/sitemap/llms files, URL variants, a missing path, documentation hosts and the login screen. We retained statuses, redirects, selected headers, metadata and a hash of the received content.

We did not sign in, execute JavaScript or use GSC, Bing or search results to calculate rankings. This sample is not a complete crawl.

02

Selected observations

Every finding applies to that date and exact URL. Missing headers are recorded as null, rather than presented as verified settings.

  • PL/EN homepages and sampled agent/comparison pages: HTTP 200, with text and metadata in raw HTML.
  • Sitemap: HTTP 200 and 62 URLs at capture time. This does not establish that 62 pages were indexed.
  • Sampled EN pages: correct html lang, self-canonical and PL/EN/x-default alternates.
  • Viktor comparison Markdown: HTTP 200 and text/markdown; no HTTP Link canonical header.
  • An intentionally missing path returned HTTP 403 with an S3 response instead of HTML 404, identifying a specific hosting task.
  • HTTP and www redirected with 301 to HTTPS without www. No-slash and index.html variants still returned 200.
03

From an observation to an action

A finding should be reproducible: URL, date, expected outcome, actual outcome and a check to run after the fix. That makes it possible to create a concrete task and repeat the observation after deployment.

Content, the application export and edge configuration are different repair locations. Adding 404.html to a repository does not itself set CloudFront's response status. An audit should identify the owner of the change instead of promising automatic repair of every issue.

04

What these observations do not establish

HTTP 200 does not prove indexation or access by a real crawler from its network. A canonical is a preference, not evidence that a search engine selected that URL. Valid HTML does not guarantee good mobile performance.

This snapshot has no readiness score and does not measure citations or recommendations. Actual visibility requires separate search-engine data and a repeatable study of AI answers.

Questions and answers

Was this produced by Braio's SEO/GEO agent?
No. It is an explicitly labelled snapshot of public HTTP/HTML requests captured during a website audit. It demonstrates evidence and its limits without pretending to be a complete product report.
Were the sitemap's 62 URLs indexed by Google?
The study did not measure that. A sitemap describes URLs published by the site; indexation requires a separate check, for example in Search Console.