report link
Link directly to these audit results.
https://app.nyman.media/site/beomniscient.comEvaluates HTML size reasonable (< 512 KB) against its documented passing condition. The exact target appears under Expected behavior.
535 KB (consider reducing)
The uncompressed HTML response remains at or below 512 KB so crawlers can parse it without excessive transfer or memory cost.
Reliable, directly parseable responses make it more likely that AI crawlers can retrieve, attribute, and cite the intended URL.
Response integrity, canonicalization, and crawl performance affect whether search engines can index the preferred page consistently.
80.9% of audited sites pass this check. This site is warn; 19.1% of the benchmark has the same status.
Measures rendered element density and DOM depth. Excessive fragmentation can make main-content isolation less reliable.
161 elements per 1k text characters; maximum DOM depth 27
The rendered DOM keeps element density and nesting depth low enough for reliable main-content isolation.
Reliable, directly parseable responses make it more likely that AI crawlers can retrieve, attribute, and cite the intended URL.
Response integrity, canonicalization, and crawl performance affect whether search engines can index the preferred page consistently.
10.9% of audited sites pass this check. This site is warn; 89.1% of the benchmark has the same status.
Checks that the page returns HTTP 200 when fetched. If crawlers cannot reliably fetch the URL, citations and visibility signals break.
HTTP 200
The audited URL returns a successful HTTP 200 response with usable page content.
LLMs and their web crawlers (GPTBot, ClaudeBot, etc.) discard URLs that return non-200 status codes. A page that cannot be fetched simply cannot appear in AI-generated responses or citations.
A 200 response is the baseline requirement for indexing; Googlebot drops non-200 URLs from its queue, so the page earns zero organic traffic regardless of its content quality.
99.1% of audited sites pass this check. This site is pass; 99.1% of the benchmark has the same status.
Evaluates page served over HTTPS against its documented passing condition. The exact target appears under Expected behavior.
HTTPS
The canonical page is served securely over HTTPS, with HTTP requests redirected to it.
Reliable, directly parseable responses make it more likely that AI crawlers can retrieve, attribute, and cite the intended URL.
Response integrity, canonicalization, and crawl performance affect whether search engines can index the preferred page consistently.
100% of audited sites pass this check. This site is pass; 100% of the benchmark has the same status.
Evaluates redirect chain ≤ 1 hop against its documented passing condition. The exact target appears under Expected behavior.
0 redirect(s)
Requests reach the final page in no more than one redirect hop.
Reliable, directly parseable responses make it more likely that AI crawlers can retrieve, attribute, and cite the intended URL.
Response integrity, canonicalization, and crawl performance affect whether search engines can index the preferred page consistently.
86% of audited sites pass this check. This site is pass; 86% of the benchmark has the same status.
Evaluates response time < 3 s against its documented passing condition. The exact target appears under Expected behavior.
1212 ms
The initial HTML response completes in 1,500 ms or less, reducing crawler timeouts and shortening the wait before rendering begins.
Slow pages increase the likelihood that a crawl times out or is abandoned mid-response; fast pages are more likely to be fully fetched and included in AI knowledge bases.
Core Web Vitals (particularly Time to First Byte) directly influence Google's page experience signals, and slow pages are systematically demoted in competitive SERPs.
32.1% of audited sites pass this check. This site is pass; 32.1% of the benchmark has the same status.
Evaluates main content is present without running JavaScript against its documented passing condition. The exact target appears under Expected behavior.
7707 characters of text present in the served HTML
The primary page content is present in the served HTML without requiring client-side JavaScript execution.
Reliable, directly parseable responses make it more likely that AI crawlers can retrieve, attribute, and cite the intended URL.
Response integrity, canonicalization, and crawl performance affect whether search engines can index the preferred page consistently.
93.9% of audited sites pass this check. This site is pass; 93.9% of the benchmark has the same status.
Compares text available in fetched HTML with text retained after a real browser render. Large divergence can indicate a shell, replacement content, or rendering failure.
98% served-text overlap after rendering
The content exposed by a browser render substantially matches the content supplied in the initial HTML response.
Reliable, directly parseable responses make it more likely that AI crawlers can retrieve, attribute, and cite the intended URL.
Response integrity, canonicalization, and crawl performance affect whether search engines can index the preferred page consistently.
54% of audited sites pass this check. This site is pass; 54% of the benchmark has the same status.
Checks the rendered page for a main, article, or role="main" landmark containing the primary content.
4379 characters in the main-content landmark
The rendered document wraps its primary content in main, article, or an element with role="main".
Reliable, directly parseable responses make it more likely that AI crawlers can retrieve, attribute, and cite the intended URL.
Response integrity, canonicalization, and crawl performance affect whether search engines can index the preferred page consistently.
59.4% of audited sites pass this check. This site is pass; 59.4% of the benchmark has the same status.
Checks whether the X-Robots-Tag response header contains noindex, which prevents indexing at the HTTP header level.
Missing
The final HTTP response does not send an X-Robots-Tag noindex directive for a discoverable page.
Header-level noindex directives apply to all content types (HTML, PDF, images) and are respected by AI crawlers at the same level as meta tags, making them the preferred mechanism for server-rendered or dynamically generated pages.
X-Robots-Tag is the only way to suppress indexing of non-HTML resources such as PDFs; for HTML pages it has identical effect to the meta robots noindex tag.
Checks whether the X-Robots-Tag response header contains noai, blocking AI systems at the HTTP header level.
Missing
The final HTTP response does not send X-Robots-Tag directives that block intended AI use.
Delivering AI opt-out signals at the HTTP header level means they apply before the document body is even parsed, offering the earliest possible restriction on AI content use.
Like meta noai, header-level noai has negligible direct SEO impact but can create unintended signal conflicts if inconsistently paired with other directives.
Reports whether the experimental llms.txt convention is present and structured. This observation is unscored.
Present and structured (17 lines; experimental and unscored)
A non-empty llms.txt, when used, gives machines a concise title, useful sections, and links to preferred resources.
llms.txt lets sites declare preferred content, licensing terms, and usage restrictions directly to LLM agents, helping model providers make better decisions about training data and citations.
llms.txt currently has no defined SEO ranking impact, but early adoption signals technical sophistication and may influence how AI-powered search features handle your content.
Reports whether the experimental ai.txt convention is present and structured. This observation is unscored.
Present at /ai.txt/ (contains policy, contact); experimental and unscored
A non-empty AI policy file, when used, states the site policy, contact, or preferences clearly.
ai.txt offers a dedicated file for communicating AI-specific access policies, allowing granular control over which AI agents can use which content, beyond what robots.txt was designed for.
ai.txt has no established SEO ranking effect today, but positions the site to comply with evolving AI content-use regulations and gives clear opt-in or opt-out signals to model providers.
Checks whether robots.txt exists at the site root. If it is missing, crawlers may still fetch this page, but you lose a key control surface for discovery guidance.
Present
A readable robots.txt file is available at the site root when explicit crawler guidance is needed.
Without a robots.txt file, AI crawlers have no explicit guidance and may apply the most conservative behaviour (refusing to crawl) or the most permissive (crawling everything), leading to unpredictable inclusion in AI datasets.
robots.txt is the primary crawler-management layer; its absence means search engines must infer crawl policy from meta tags and server headers alone, reducing crawl efficiency.
100% of audited sites pass this check. This site is pass; 100% of the benchmark has the same status.
Evaluates robots.txt does not blanket-block all crawlers against its documented passing condition. The exact target appears under Expected behavior.
No blanket Disallow: /
Crawler directives and server behavior consistently allow the discovery policy intended for this page.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Checks whether robots.txt blocks common AI/LLM crawlers. Blocking AI agents can reduce your visibility in LLM-based discovery systems.
Allowed
The robots policy allows the AI crawlers the site intends to reach instead of selectively blocking them.
Blocking known AI user-agents (GPTBot, ClaudeBot, etc.) directly prevents those models from citing your content, summarising your pages, or recommending your site in responses.
Blanket AI agent blocks can extend to Google's AI-driven tools such as Google-Extended; misconfigurations can inadvertently impair standard indexing as well.
49.2% of audited sites pass this check. This site is pass; 49.2% of the benchmark has the same status.
Evaluates AI crawlers can fetch the page against its documented passing condition. The exact target appears under Expected behavior.
Reachable for GPTBot, ClaudeBot, PerplexityBot
Crawler directives and server behavior consistently allow the discovery policy intended for this page.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Checks whether the page has a noindex directive in meta robots. Noindex prevents search engines and AI systems from indexing the page.
index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
The page-level robots meta tag does not contain noindex when the page is intended to be discoverable.
The noindex directive is respected by most AI crawlers as a strong opt-out signal; pages carrying it are typically removed from AI training datasets and excluded from RAG pipelines.
noindex is an absolute bar to inclusion in Google's index; any page carrying this directive earns zero organic impressions regardless of its backlink profile or content quality.
97.5% of audited sites pass this check. This site is pass; 97.5% of the benchmark has the same status.
Checks whether the page has a noai or noimageai directive in meta robots, which blocks AI systems from using the page content.
index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
The page-level robots meta tag does not contain noai or noimageai when AI access is intended.
The noai directive explicitly tells AI systems not to use this page's content; it is increasingly honoured by major model providers and removes the page from AI citation pools.
noai has no direct impact on traditional organic search rankings, but misapplication can accidentally restrict page discovery if combined with other restrictive directives.
98.3% of audited sites pass this check. This site is pass; 98.3% of the benchmark has the same status.
Checks whether robots.txt references one or more sitemap URLs. Adding Sitemap directives can speed up discovery and improve crawl coverage.
No Sitemap directive (contextual and unscored)
robots.txt declares the canonical sitemap location so crawlers can discover it immediately.
Declaring sitemaps in robots.txt ensures AI crawlers can discover all content entry points in a single request, reducing the risk of large or deep sections being entirely missed.
Linking sitemaps from robots.txt is a Googlebot-recommended pattern that improves crawl coverage for pages with few inbound links and accelerates discovery of newly published content.
Checks whether the submitted page’s preferred URL appears in a directly enumerated sitemap. Sitemap indexes are not expanded and are treated as not applicable.
Sitemap is an index; child sitemap files were not fetched
The audited canonical URL is represented in the applicable sitemap when page URLs are enumerated directly.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Checks directly declared sitemap URLs for parse errors, normalized duplicates, origin conflicts, and mixed protocols without fetching those pages.
No directly enumerated page-URL inventory to assess
Directly declared sitemap URLs are parseable, unique, and consistent with the preferred site origin and protocol.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
For a non-root URL, checks for a crawlable link toward a parent, breadcrumb, or the site root. Root URLs are not applicable.
Submitted URL is the site root
A non-root page provides a crawlable path toward its parent, breadcrumb trail, or site root.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Checks whether a sitemap can be found (e.g. /sitemap.xml). Without a sitemap, crawlers rely more on internal links and can miss pages.
3 declared entries
A reachable sitemap is available and returns the expected XML content.
A sitemap provides AI crawlers with a machine-readable inventory of pages; without one, crawlers rely entirely on hyperlink traversal and can easily miss thin or orphaned pages.
Sitemaps are the primary mechanism for submitting new URLs to search engines without waiting for link discovery; they are especially critical for fresh content and large sites.
43.5% of audited sites pass this check. This site is pass; 43.5% of the benchmark has the same status.
Checks whether your sitemap content looks like valid XML rather than an HTML error page. HTML responses often mean misconfiguration or a redirect challenge.
Valid sitemap XML (text/xml; charset=UTF-8)
The sitemap is parseable XML rather than an HTML error, challenge, or fallback page.
Invalid or HTML-wrapped sitemaps are ignored by XML-parsing crawlers; AI systems that retrieve sitemaps programmatically will silently discard malformed documents.
Googlebot validates sitemap XML before processing; an invalid sitemap produces errors in Search Console and means the submitted URL list is never used to guide crawling.
83.4% of audited sites pass this check. This site is pass; 83.4% of the benchmark has the same status.
Evaluates canonical URL matches site origin against its documented passing condition. The exact target appears under Expected behavior.
Same origin
The canonical URL remains on the intended site origin unless a deliberate cross-domain canonical is required.
A canonical that points to a different domain or subdomain is interpreted as a cross-domain redirect signal by AI crawlers; incorrect canonicals can attribute page content to the wrong entity entirely.
Cross-origin canonical mismatches are a common cause of Google ignoring the canonical directive, reverting to treating both URLs as independent pages and splitting link equity.
96.6% of audited sites pass this check. This site is pass; 96.6% of the benchmark has the same status.
Evaluates canonical URL matches the current page URL against its documented passing condition. The exact target appears under Expected behavior.
Canonical URL matches the final page URL
The declared canonical resolves to the final preferred page URL after redirects and normalization.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
90.9% of audited sites pass this check. This site is pass; 90.9% of the benchmark has the same status.
Checks whether og:url matches the canonical URL. Mismatches can confuse social platforms and LLM crawlers.
og:url matches the preferred page URL
og:url and the canonical URL identify the same preferred page.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
92.2% of audited sites pass this check. This site is pass; 92.2% of the benchmark has the same status.
Evaluates internal link density supports entity graph crawling against its documented passing condition. The exact target appears under Expected behavior.
100% of anchors use resolvable web links
Important pages are reachable through valid internal links that crawlers and users can follow.
Internal links distribute authority within the AI's site model; a well-connected site graph allows AI crawlers to discover deep pages that would otherwise be isolated and missed.
Internal linking is the primary mechanism for distributing link equity across a site; pages with few inbound internal links are chronically under-indexed and under-ranked.
86.8% of audited sites pass this check. This site is pass; 86.8% of the benchmark has the same status.
Measures whether internal links on the submitted page use meaningful labels rather than empty or generic anchor text.
95% of internal links have descriptive labels
Internal destinations use labels that identify what users and crawlers will find there.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
88.2% of audited sites pass this check. This site is pass; 88.2% of the benchmark has the same status.
Compares internal destinations in served HTML with those present after browser rendering. It does not fetch any destination page.
100% source/rendered internal-link parity
Important internal navigation remains present in both fetched HTML and the browser-rendered document.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
70.9% of audited sites pass this check. This site is pass; 70.9% of the benchmark has the same status.
Having exactly one H1 heading provides a clear content hierarchy signal for crawlers and LLMs.
2
The page contains exactly one descriptive H1 that states its primary topic.
A single, descriptive H1 heading is one of the strongest in-page signals LLMs use to label the topic of a page; multiple or missing H1s create ambiguity that degrades the accuracy of AI-generated summaries.
The H1 heading is the highest-weight on-page content signal after the title tag; it informs Google's understanding of the page topic and should align closely with the target keyword.
55.8% of audited sites pass this check. This site is warn; 11.7% of the benchmark has the same status.
Checks whether OpenGraph title, description, and image tags are present so shared links render with rich previews.
title=true, desc=false, image=true
Open Graph title, description, and image metadata provide a complete, accurate share preview.
OpenGraph metadata defines how a page appears when shared across social platforms; AI systems that ingest social content use og:title and og:description as curated summaries the site owner prefers.
Rich social previews driven by og: tags increase click-through rates from social media channels and influence the share velocity that can indirectly signal content popularity to search algorithms.
53.5% of audited sites pass this check. This site is warn; 46.5% of the benchmark has the same status.
Checks whether the page has a healthy text-to-HTML ratio. Low ratios suggest thin content that AI systems may skip.
1%
Extractable page text represents at least 5% of the HTML, avoiding a markup-heavy shell with little readable content.
Pages with a low text-to-HTML ratio (code-heavy, template-heavy) yield little useful text when crawled by AI systems; the signal-to-noise ratio determines whether a page is included in a model's training corpus.
Google's quality algorithms down-rank thin pages; a healthy text-to-HTML ratio is a proxy for real content depth and signals to Googlebot that there is substantive content to index.
38.6% of audited sites pass this check. This site is warn; 61.4% of the benchmark has the same status.
Evaluates title and H1 aligned against its documented passing condition. The exact target appears under Expected behavior.
Mismatch
The title and H1 describe the same primary topic without contradicting each other.
When the title and H1 convey the same core topic, AI systems receive two corroborating signals that reinforce the page's subject; misaligned title and H1 create ambiguity that degrades topic classification.
Title–H1 alignment is a best-practice signal of topical coherence that helps Google's entity and topic models confirm the page's subject, reducing the risk of ranking for off-target queries.
17.2% of audited sites pass this check. This site is warn; 82.8% of the benchmark has the same status.
Evaluates images have alt text against its documented passing condition. The exact target appears under Expected behavior.
19/32 images (59%); some missing alt text
Meaningful images have useful alternative text, while decorative images are explicitly ignored.
Alt text allows AI vision and text models to understand what images depict, enabling accurate image-to-content associations; pages with good alt coverage build richer entity knowledge graphs.
Image alt text is a primary on-page signal for image search ranking; comprehensive alt coverage also improves accessibility, which is a direct input to Google's page experience score.
48.8% of audited sites pass this check. This site is warn; 22.6% of the benchmark has the same status.
The title tag is a primary signal for search engines and AI systems to understand page content and generate citations.
Organic Growth Agency for B2B Software Companies
The document has one concise, descriptive title that identifies the page topic.
The title tag is typically the first text signal an AI crawler stores for a URL; it anchors the page's topic in the model's internal representation and is frequently used verbatim in citations and summaries.
Google rewrites titles less frequently when the tag accurately reflects the page content; a well-crafted title tag is the single highest-impact on-page SEO element for click-through rates.
94.6% of audited sites pass this check. This site is pass; 94.6% of the benchmark has the same status.
The meta description helps search engines and AI systems summarize the page in results and responses.
Omniscient Digital is an organic growth agency that helps B2B software companies drive business grow…
The document provides a concise meta description that accurately summarizes the page.
Meta descriptions are extracted by AI systems when generating page summaries and are often used as the default snippet in RAG outputs when no better summary is available.
While not a direct ranking factor, a compelling meta description is the primary lever for improving organic click-through rate on pages that already rank well.
75.1% of audited sites pass this check. This site is pass; 75.1% of the benchmark has the same status.
The canonical URL tells search engines and LLM crawlers what the preferred URL is for this page, which helps consolidate signals and avoid duplicates.
https://beomniscient.com/
The document declares one absolute canonical URL for the preferred version of the page.
The canonical tag signals to AI crawlers which URL is the authoritative version; without it, citation links may point to duplicate or parameterised variants, diluting traffic back to the intended URL.
Canonicalisation consolidates PageRank from duplicate URLs onto the preferred version; without proper canonicals, link equity is split across variants and total ranking power is reduced.
59.7% of audited sites pass this check. This site is pass; 59.7% of the benchmark has the same status.
The HTML lang attribute helps AI systems understand the content language for proper localization and response generation.
en-US
The root html element declares the primary content language with a valid lang value.
The HTML lang attribute allows AI systems to route page content to the correct language model and apply appropriate tokenisation and summarisation pipelines for the language in question.
The lang attribute is a prerequisite for hreflang to function correctly in multilingual setups, and it influences language-specific ranking in localised search markets.
88% of audited sites pass this check. This site is pass; 88% of the benchmark has the same status.
Checks whether a viewport meta tag is present for mobile-friendly rendering.
Present
The page declares a mobile viewport so layout dimensions match the device width.
The viewport meta tag has no direct bearing on AI content extraction, but its absence is a strong indicator of poor mobile optimisation, which correlates with lower content quality signals overall.
Google uses mobile-first indexing; a missing viewport tag triggers mobile usability warnings in Search Console and can result in the mobile version being deprioritised in ranking.
88.6% of audited sites pass this check. This site is pass; 88.6% of the benchmark has the same status.
Checks whether a favicon is present. Favicons improve brand recognition in search results and browser tabs.
Present
The document references a reachable favicon that represents the site consistently.
Favicons are visual brand identifiers used in browser tabs and some search interfaces but are not parsed by AI content crawlers, so they have no direct bearing on LLM knowledge base inclusion.
Favicons appear in browser tabs, bookmarks, and some search result interfaces, contributing to brand recognisability and improving perceived credibility without impacting rankings directly.
85.6% of audited sites pass this check. This site is pass; 85.6% of the benchmark has the same status.
Evaluates sufficient on-page text against its documented passing condition. The exact target appears under Expected behavior.
7707 chars
The served page contains at least 300 characters of meaningful, extractable text.
Longer pages with substantive text give AI systems more material to extract claims, summaries, and citations from; very short pages are often classified as thin content and excluded from AI knowledge bases.
Content length correlates with topical coverage; comprehensively covering a subject increases the chance of ranking for long-tail queries and earning a "comprehensive resource" link profile.
86.5% of audited sites pass this check. This site is pass; 86.5% of the benchmark has the same status.
Evaluates title length reasonable against its documented passing condition. The exact target appears under Expected behavior.
48 chars
The title is descriptive without truncation risk, within the audit pass range of 15 to 65 characters.
Title length does not directly affect AI ingestion, but excessively long titles may be truncated in retrieval systems, reducing the clarity of the topic signal for LLMs.
Titles longer than ~60 characters are truncated in Google SERP snippets, which can hide key terms and reduce click-through rates; too-short titles may under-specify the page topic.
63.9% of audited sites pass this check. This site is pass; 63.9% of the benchmark has the same status.
Evaluates meta description length reasonable against its documented passing condition. The exact target appears under Expected behavior.
133 chars
The meta description is detailed but concise, within the audit pass range of 50 to 160 characters.
Meta description length has no bearing on AI crawling, but descriptions within the optimal range are more likely to be used verbatim in SERP snippets that AI-overview systems pull from.
Descriptions between 70–160 characters are typically displayed in full in Google snippets; outside this range they are either too brief to be informative or truncated, wasting the opportunity.
64.3% of audited sites pass this check. This site is pass; 64.3% of the benchmark has the same status.
Evaluates viewport configured for mobile devices against its documented passing condition. The exact target appears under Expected behavior.
Viewport meta tag present. Page configured for mobile rendering
The served HTML exposes the page topic and main content through valid, machine-readable markup.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Reports whether JSON-LD exists. Generic presence is unscored; syntax and the quality of detected schema are evaluated separately.
1 script(s); presence alone is unscored
The page includes parseable JSON-LD that describes the page or the entity behind it.
JSON-LD is the format AI systems most reliably parse when extracting structured facts about an entity; its absence forces LLMs to rely on heuristic text extraction, which is less accurate and less authoritative.
JSON-LD is Google's preferred structured data format; correctly implemented, it unlocks rich result types (sitelinks, FAQs, product panels) that significantly improve click-through rates.
Checks whether Organization schema is present in your JSON-LD. This helps systems identify the entity behind the page (name, logo, contact points, etc.).
Yes (unscored)
The page includes valid Organization structured data when that type accurately represents the visible content.
Organization schema gives LLMs a canonical, machine-readable definition of the entity (name, logo, sameAs links), reducing the chance of misattribution or confusion with similarly named entities.
Organisation structured data feeds the Google Knowledge Panel and entity-recognition algorithms, improving brand appearance in branded search queries and knowledge graphs.
Checks whether WebSite schema is present in your JSON-LD. This helps systems understand the site as a whole and can support sitelinks/search actions.
Yes (unscored)
The page includes valid WebSite structured data when that type accurately represents the visible content.
WebSite schema communicates the site's purpose and searchable structure to AI systems, enabling them to correctly classify the domain as a coherent entity rather than a random collection of pages.
WebSite schema enables the Sitelinks Searchbox feature in Google results and reinforces the association between a domain and its brand name in entity-based ranking systems.
Checks whether WebPage schema is present in your JSON-LD. This helps systems understand the page type and main entity being described.
Yes (unscored)
The page includes valid WebPage structured data when that type accurately represents the visible content.
WebPage schema allows AI crawlers to understand the type, author, and primary topic of a page without needing to infer these from prose, improving the accuracy of AI-generated summaries.
Page-level schema enriches Google's understanding of content type and authorship, contributing to E-E-A-T signals and supporting rich results for review, article, and FAQ pages.
Checks whether BreadcrumbList schema is present in your JSON-LD. Breadcrumbs can improve understanding of site structure and context.
Yes (unscored)
The page includes valid BreadcrumbList structured data when that type accurately represents the visible content.
BreadcrumbList schema tells AI systems where a page sits within the site hierarchy, which helps LLMs contextualise content and understand whether a page is a top-level resource or a deep sub-topic.
Breadcrumb markup enables the breadcrumb trail to appear in Google SERP snippets, improving visual clarity and typically increasing organic click-through rates.
Checks whether FAQPage schema is present in your JSON-LD. Useful when you have real FAQ content on the page.
No (unscored)
The page includes valid FAQPage structured data when that type accurately represents the visible content.
FAQPage schema presents question–answer pairs in a format LLMs are optimised to consume directly; well-structured FAQ pages dramatically increase the probability of being used as an AI answer source.
FAQ rich results expand the SERP footprint significantly; pages with FAQ schema can occupy two to three times the normal result space, substantially boosting click-through rates.
Checks whether Article/NewsArticle/BlogPosting schema is present in your JSON-LD (if applicable). Helps machines understand content type and authorship.
Yes (unscored)
The page includes valid Article structured data when that type accurately represents the visible content.
Article schema signals authorship, publication date, and content type to LLMs, making it easier for AI systems to assess freshness and credibility before citing or summarising the content.
Article schema can unlock Top Stories and news carousels in Google results, and the author/datePublished fields directly contribute to E-E-A-T signals.
Checks whether Person schema is present in your JSON-LD (if applicable). Useful for personal brands and author entities.
Yes (unscored)
The page includes valid Person structured data when that type accurately represents the visible content.
Person schema is how AI knowledge bases build named-entity graphs; without it, LLMs must guess biographical details from unstructured text, leading to factual errors in AI-generated profiles.
Person structured data strengthens author entity recognition in Google's E-E-A-T framework, improving the ranking authority of content attributed to that individual.
Checks whether Product schema is present in your JSON-LD (if applicable). Useful for ecommerce/product pages and rich understanding.
No (unscored)
The page includes valid Product structured data when that type accurately represents the visible content.
Product schema gives AI shopping and comparison agents the structured price, availability, and description data they need to reliably recommend or compare offerings.
Product markup unlocks Google's Product rich results and Merchant Center integrations, placing product details directly in search snippets and potentially in Shopping panels.
Reports whether JSON-LD exists. Generic presence is unscored; syntax and the quality of detected schema are evaluated separately.
1 script(s), all valid
Every JSON-LD block parses as valid JSON and can be consumed by structured-data tools.
Syntactically invalid JSON-LD is silently discarded by parsers; even well-intentioned structured data provides zero benefit to AI systems if the underlying JSON cannot be parsed.
Google's Rich Results Test rejects invalid JSON-LD; syntax errors mean no rich results are eligible, negating the investment made in adding structured data.
99.1% of audited sites pass this check. This site is pass; 99.1% of the benchmark has the same status.
Reports whether JSON-LD exists. Generic presence is unscored; syntax and the quality of detected schema are evaluated separately.
All detected schemas have required properties
Detected schema types include the required properties for the entities they describe.
Valid structured data gives machines an explicit representation of the page and its entities, reducing ambiguity during extraction.
Accurate structured data supports entity understanding and eligibility for applicable search-result enhancements.
94.2% of audited sites pass this check. This site is pass; 94.2% of the benchmark has the same status.
Evaluates brand/entity name appears in title against its documented passing condition. The exact target appears under Expected behavior.
Missing "Omniscient Digital"
The page title names the audited brand or entity clearly enough to connect the page to it.
Including the entity or brand name in the title tag helps AI systems connect this URL to the correct real-world brand; without it, pages are harder to attribute correctly in entity-based reasoning.
Brand-inclusive titles improve branded search recall and help Google's entity graph link the page to the correct brand entity, supporting rich results and Knowledge Panel associations.
82.5% of audited sites pass this check. This site is warn; 17.5% of the benchmark has the same status.
Evaluates brand/entity name appears in H1 against its documented passing condition. The exact target appears under Expected behavior.
Missing "Omniscient Digital"
The primary heading names the audited brand or entity where that identity is central to the page.
The H1 is the strongest in-document entity signal. Naming the brand or entity here tells LLMs that the page is an authoritative on-site resource for that organisation, product, or person.
Entity presence in H1 reinforces brand-to-page association in Google's NLP layer, improving dominance in branded SERP queries and supporting entity-based rich features.
18.5% of audited sites pass this check. This site is warn; 81.5% of the benchmark has the same status.
Compares the inferred entity name across the title, H1, Open Graph site name, and Organization schema.
2/4 sources agree; align title, H1, Open Graph, and Organization schema names
The same entity name is used consistently in the title, H1, Open Graph site name, and Organization schema.
Consistent identity signals help AI systems connect this domain, its content, and external references to the correct entity.
Clear entity information strengthens branded search interpretation and reduces ambiguity between similarly named organizations or people.
47.3% of audited sites pass this check. This site is warn; 50% of the benchmark has the same status.
Evaluates organization or LocalBusiness schema present against its documented passing condition. The exact target appears under Expected behavior.
Yes (presence is unscored)
Organization or LocalBusiness schema identifies the entity operating the site with consistent core properties.
Entity clarity is the degree to which AI systems can identify the brand, organisation, or person behind a site. A well-populated Organization schema with sameAs links, legalName, and logo gives models a canonical source of truth and reduces hallucinated profiles.
Organisation detail in structured data feeds the Knowledge Panel, reinforces branded query dominance, and provides Google with verified facts about the entity to surface in AI Overviews.
Checks whether social media profile links are present in structured data.
2 domain(s)
The site links to its authoritative external profiles using consistent entity identity.
sameAs links to social profiles help AI knowledge graphs verify that this web entity is the same brand, organisation, or person represented on other trusted platforms.
Linking to verified social profiles in structured data strengthens E-E-A-T by corroborating the entity's real-world presence and is used by Google to populate Knowledge Panel social links.
53.7% of audited sites pass this check. This site is pass; 53.7% of the benchmark has the same status.
Evaluates HTTP security headers present (HSTS, CSP, X-Content-Type, X-Frame, Referrer-Policy, Permissions-Policy) against its documented passing condition. The exact target appears under Expected behavior.
1/6 recommended headers present. Missing: Strict-Transport-Security, Content-Security-Policy, X-Frame-Options, Referrer-Policy, Permissions-Policy
The final response applies the appropriate transport, content, framing, MIME, referrer, and permissions protections for the page.
Strong security headers (CSP, HSTS, X-Frame-Options) indirectly signal to AI systems that the site is professionally maintained. They don't affect content extraction but contribute to overall domain trust.
HTTPS and security headers are part of Google's page experience framework; sites with strong security signals are treated as more trustworthy, particularly in YMYL categories.
30.4% of audited sites pass this check. This site is fail; 37.1% of the benchmark has the same status.
Evaluates internal paths are not openly accessible against its documented passing condition. The exact target appears under Expected behavior.
Openly accessible internal path(s): /server-status, /server-info
The reported trust or security condition is resolved without weakening the page response or user journey.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates third-party scripts use Subresource Integrity against its documented passing condition. The exact target appears under Expected behavior.
1 of 1 third-party resource(s) lack an integrity attribute.
The reported trust or security condition is resolved without weakening the page response or user journey.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Checks whether hreflang tags are present for multilingual or multi-regional pages.
No hreflang tags (only relevant for multilingual sites)
Language and regional alternates use valid, reciprocal hreflang annotations when alternates exist.
hreflang tags tell AI language models which URL to prefer for a given locale–language combination, reducing the chance of an AI returning the wrong language variant to a user.
Correct hreflang implementation prevents duplicate content penalties in multilingual sites and ensures the appropriate language/region variant ranks in each target market.
Evaluates speakable schema markup present against its documented passing condition. The exact target appears under Expected behavior.
No Speakable schema (optional for voice assistant targeting)
The page includes valid SpeakableSpecification structured data when that type accurately represents the visible content.
Speakable schema explicitly marks sections of content suitable for text-to-speech and voice assistant responses; this is a direct signal for AI agents to prioritise those passages in spoken or conversational output.
Speakable markup positions content for inclusion in Google Assistant audio responses, an increasingly important distribution channel as voice search and smart speakers proliferate.
Evaluates no sensitive files exposed at well-known paths against its documented passing condition. The exact target appears under Expected behavior.
Host returns a fallback response for all paths: file exposure could not be determined
The reported trust or security condition is resolved without weakening the page response or user journey.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates error pages do not leak stack traces or debug output against its documented passing condition. The exact target appears under Expected behavior.
Error-page probing unavailable
The reported trust or security condition is resolved without weakening the page response or user journey.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Checks whether an about page is linked, helping AI systems understand the entity behind the site.
Yes
A reachable About or Company page explains who operates the site and what the entity does.
An About page provides AI systems with a dedicated source for background facts, mission statements, and founding information. Content that LLMs frequently surface when answering brand or entity queries.
About pages are strong trust signals for Google's E-E-A-T framework; their presence is referenced in Google Quality Rater Guidelines as evidence of a site's transparency and legitimacy.
55.1% of audited sites pass this check. This site is pass; 55.1% of the benchmark has the same status.
Checks whether a contact page is linked, providing trust signals for AI systems.
Yes
A reachable contact route gives users a clear way to contact the organization.
A discoverable Contact page signals that the entity is a real, reachable organisation. This is a factor that AI systems use as a proxy for credibility when deciding whether to cite a source.
Contact information is explicitly cited in Google's Quality Rater Guidelines as an indicator of site quality; its absence is associated with lower trust scores and YMYL ranking penalties.
47% of audited sites pass this check. This site is pass; 47% of the benchmark has the same status.
Checks whether a privacy policy is linked, indicating compliance and trustworthiness.
Yes
A reachable privacy policy explains how the site handles personal data.
A Privacy Policy indicates regulatory compliance and intentional data governance, which some AI training pipelines use as a trust signal when evaluating whether to include a site in a dataset.
Privacy policies are required by Google Ads, Search Console, and multiple legal frameworks; their absence can trigger manual actions for sites collecting personal data.
56.2% of audited sites pass this check. This site is pass; 56.2% of the benchmark has the same status.
Checks whether terms of service are linked, indicating a legitimate and accountable entity.
Yes
Reachable terms identify the conditions governing use of the site or service.
Terms of Service are a marker of a legitimate, structured organisation; AI training data pipelines increasingly filter for sites with formal legal documentation as a quality heuristic.
Terms pages contribute to the overall trust and authority profile assessed by quality raters; YMYL sites without terms are frequently rated as low-quality in manual review.
39.8% of audited sites pass this check. This site is pass; 39.8% of the benchmark has the same status.
Checks whether testimonial or social proof language is present on the page.
Detected
Relevant claims are supported by identifiable customer evidence or case-study material.
Testimonials and social proof text provide AI systems with third-party validation signals that can strengthen the credibility score of a page when it is being evaluated as a citation candidate.
User-generated testimonials create unique content and natural language variation that can help pages rank for long-tail conversational queries related to customer outcomes.
8.9% of audited sites pass this check. This site is pass; 8.9% of the benchmark has the same status.
Checks whether press or featured-in signals exist. Third-party mentions in authoritative sources boost AI visibility.
Detected
Relevant third-party coverage or recognition is presented accurately and linked to its source.
A press or media page aggregates third-party coverage in a structured way that AI systems can discover and use to corroborate brand claims, directly boosting citation likelihood.
Press coverage links from high-authority domains are among the most powerful off-page SEO signals; a dedicated press page facilitates journalist outreach and accelerates link acquisition.
35.8% of audited sites pass this check. This site is pass; 35.8% of the benchmark has the same status.
Evaluates RSS or Atom feed discoverable against its documented passing condition. The exact target appears under Expected behavior.
RSS/Atom feed link found: enables LLM content ingestion
A reachable feed exposes current entries for sites that publish recurring content.
RSS feeds are widely consumed by AI news aggregators and LLM data pipelines to discover and ingest fresh content; sites with feeds get new articles into AI knowledge bases faster.
RSS feeds enable content syndication and speed up discovery by search engine crawlers; fresh content that enters the index quickly benefits from the freshness ranking bonus.
14.3% of audited sites pass this check. This site is pass; 14.3% of the benchmark has the same status.
Evaluates searchAction schema present (sitelinks search box) against its documented passing condition. The exact target appears under Expected behavior.
SearchAction schema found: enables sitelinks search box
The page includes valid SearchAction structured data when that type accurately represents the visible content.
SearchAction schema enables AI agents and voice assistants to surface a site's search function directly in conversational interfaces, making the site's knowledge base accessible through AI-native interaction patterns.
Implementing SearchAction schema enables Google's Sitelinks Searchbox feature, which allows users to query a site's internal search directly from the SERP, increasing direct navigation.
100% of audited sites pass this check. This site is pass; 100% of the benchmark has the same status.
Evaluates no API keys or credentials exposed in client-side code against its documented passing condition. The exact target appears under Expected behavior.
No exposed credentials detected in HTML or first-party JavaScript
The reported trust or security condition is resolved without weakening the page response or user journey.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates directory listing is disabled against its documented passing condition. The exact target appears under Expected behavior.
No open directory listings detected
The reported trust or security condition is resolved without weakening the page response or user journey.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates no mixed (insecure) content on an HTTPS page against its documented passing condition. The exact target appears under Expected behavior.
All sub-resources loaded securely over HTTPS
The reported trust or security condition is resolved without weakening the page response or user journey.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates forms submit over HTTPS against its documented passing condition. The exact target appears under Expected behavior.
No insecure form submissions detected
The reported trust or security condition is resolved without weakening the page response or user journey.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates cookies use Secure, HttpOnly, and SameSite flags against its documented passing condition. The exact target appears under Expected behavior.
Cookies set with Secure, HttpOnly, and SameSite
The reported trust or security condition is resolved without weakening the page response or user journey.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates CORS policy is not dangerously permissive against its documented passing condition. The exact target appears under Expected behavior.
No wildcard CORS exposure
The reported trust or security condition is resolved without weakening the page response or user journey.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates server software versions are not disclosed in headers against its documented passing condition. The exact target appears under Expected behavior.
No server version disclosure in response headers
The reported trust or security condition is resolved without weakening the page response or user journey.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates production source maps are not publicly exposed against its documented passing condition. The exact target appears under Expected behavior.
No exposed source maps detected
The reported trust or security condition is resolved without weakening the page response or user journey.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Measures whether distinct title and H1 terms remain supported in the rendered introduction and section content. Repetition does not increase the score.
56% topic continuity; several title/H1 concepts are not supported in the rendered content
Distinct title and H1 concepts are supported by the rendered introduction and section content.
Specific, well-structured answers are easier for retrieval systems to extract, quote, and use in generated responses.
Clear topical coverage and scannable information architecture help search engines match the page to relevant queries.
21.3% of audited sites pass this check. This site is warn; 31.3% of the benchmark has the same status.
Uses page-internal sparse retrieval to test whether each substantive heading identifies its own body more strongly than other section bodies.
52% heading/body retrieval agreement; some headings do not identify their own section reliably
Each substantive heading identifies its own body more strongly than the page’s other section bodies.
Specific, well-structured answers are easier for retrieval systems to extract, quote, and use in generated responses.
Clear topical coverage and scannable information architecture help search engines match the page to relevant queries.
12.8% of audited sites pass this check. This site is warn; 34.6% of the benchmark has the same status.
Evaluates headings use question phrasing (who, what, how…) against its documented passing condition. The exact target appears under Expected behavior.
1/12 headings are question-phrased (contextual and unscored)
Where question-led content is appropriate, at least 30% of H2 and H3 headings map a clear question to its answer.
Headings phrased as questions mirror how users phrase prompts to LLMs; structuring content this way increases the probability that a passage will be returned as a direct answer in conversational AI interactions.
Question-formatted headings align with natural language queries and improve the chance of winning People Also Ask (PAA) boxes, which command high visibility and click share.
Evaluates content includes structured elements (lists, tables) against its documented passing condition. The exact target appears under Expected behavior.
17 list/table element(s) (1.4 per 1k words; contextual and unscored)
Long-form content uses lists or tables where structure makes facts easier to extract and compare.
Structured content (lists, tables, step-by-step instructions) is significantly easier for AI systems to parse and summarise than dense prose; high-density structured content is more frequently cited in AI responses.
Lists and tables improve content scannability, dwell time, and engagement metrics; they are also more likely to be extracted as featured snippets, earning prominent above-the-fold SERP placement.
Checks whether the page has sufficient content depth for AI systems to extract meaningful information.
Median section: ~18 words (contextual and unscored)
Content sections provide enough substance to answer their topic, with a median depth of at least 40 words.
Deep, comprehensive content gives AI systems more raw material to form accurate, nuanced responses; thin content is systematically down-ranked or excluded from AI answer pools.
Content depth correlates strongly with topical authority, Google's primary long-term ranking mechanism; comprehensive pages earn more backlinks and rank for more keyword variants.
Evaluates content includes unique data points (numbers, percentages, prices) against its documented passing condition. The exact target appears under Expected behavior.
3 concrete data pattern(s) found (contextual and unscored)
The content supports claims with specific, attributable numbers, percentages, prices, or original data.
Original data, statistics, and research findings are among the most valuable signals for AI systems seeking authoritative sources; unique data dramatically increases citation likelihood and reduces the chance of being displaced by duplicate content.
Proprietary data and original research are top-tier link magnets; pages that cite unique numbers or findings earn disproportionate backlink profiles and high-authority placements.
Evaluates content uses definition patterns ("X is…", "refers to…") against its documented passing condition. The exact target appears under Expected behavior.
1 definition pattern(s) found (contextual and unscored)
Key concepts include concise, explicit definitions that can stand alone when extracted.
Pages that define terms and concepts are natural targets for AI "what is X?" queries; clear definitional structures help LLMs extract and cache concept definitions for conversational use.
Definitional content frequently wins featured snippets for informational queries; the structured "X is…" format is exactly what Google extracts for position-zero answers.
Evaluates FAQ or expandable Q&A section on page against its documented passing condition. The exact target appears under Expected behavior.
No FAQ section found (not required)
Common questions are paired with direct answers, with matching FAQPage schema when the visible content qualifies.
FAQ-style content provides a library of ready-to-use question–answer pairs that AI systems can directly surface when answering user queries, making the page a high-yield citation candidate.
FAQ content expands keyword surface area, targets long-tail question queries, and can earn PAA (People Also Ask) inclusions, all of which broaden organic visibility without additional page creation.
Reports concrete numeric patterns per thousand words as contextual evidence only. This observation is unscored.
0.2 concrete data pattern(s) per 1,000 words (3 found; contextual and unscored)
Concrete data-pattern observations accurately describe the submitted page without affecting its score.
Specific, well-structured answers are easier for retrieval systems to extract, quote, and use in generated responses.
Clear topical coverage and scannable information architecture help search engines match the page to relevant queries.
Only activates when explicit citations, sources, footnotes, or attributed quotations are present, then checks that their reference remains usable and attached to the relevant content unit.
No explicit citation, source, footnote, or attributed quotation to validate
When the page explicitly cites a source, the usable reference stays attached to the relevant retrieval unit.
Specific, well-structured answers are easier for retrieval systems to extract, quote, and use in generated responses.
Clear topical coverage and scannable information architecture help search engines match the page to relevant queries.
Reports the share of words in blocks that are short relative to the page’s typical content block. This observation is scored only through extractable section structure.
2% relative fragment word share (contextual; scored within section structure)
The contextual fragment observation reflects blocks that are short relative to this page’s own typical content block.
Specific, well-structured answers are easier for retrieval systems to extract, quote, and use in generated responses.
Clear topical coverage and scannable information architecture help search engines match the page to relevant queries.
Reports explicit definition and question-led patterns as contextual evidence only. This observation is unscored.
1 definition and 1 question-heading pattern(s) (contextual and unscored)
Definition and question-led patterns are reported as contextual evidence without changing the score.
Specific, well-structured answers are easier for retrieval systems to extract, quote, and use in generated responses.
Clear topical coverage and scannable information architecture help search engines match the page to relevant queries.
Measures heading association, relative fragmentation, coverage, and section balance in rendered main content without enforcing a fixed word-count template.
12 heading-associated unit(s); 82% word coverage; 2% relative fragment share
Rendered main content forms balanced, heading-associated units without excessive relative fragmentation.
Specific, well-structured answers are easier for retrieval systems to extract, quote, and use in generated responses.
Clear topical coverage and scannable information architecture help search engines match the page to relevant queries.
46.5% of audited sites pass this check. This site is pass; 46.5% of the benchmark has the same status.
6 completed runs · oldest to newest
Only 0 same-version Marketing & Advertising sites are available. At least 10 are required before showing a median or nearby scores.
We auto-verify ownership from your email domain. If they match, your first year of Premium is 20% off. No extra step at checkout.
Run the same deterministic checks again to refresh this report and see a valid before-and-after comparison.
Link to the full results or add a verified score card to your site.
Link directly to these audit results.
https://app.nyman.media/site/beomniscient.comShows the latest score, audit date, and Nyman Media verification.
<a href="https://app.nyman.media/site/beomniscient.com"><img src="https://app.nyman.media/api/badge/site/beomniscient.com.svg" alt="Website audit score for beomniscient.com" width="420" height="112" /></a>An always-current card with score, audit date, and link to the findings.
<iframe src="https://app.nyman.media/embed/site/beomniscient.com" width="460" height="210" frameborder="0" loading="lazy" title="Website audit results for beomniscient.com"></iframe>The branded score summary shown when this page is shared.
<meta property="og:image" content="https://app.nyman.media/site/beomniscient.com/opengraph-image" />