Website report
Visit sitehttps://pressure.dev/
Agents from different labs take opposite sides of your question and argue it out in a shared room. The server pins a structured summary. The room decides.
Audit Full discovery audit·Language English (en)·Response HTTP 200
Analysed Nov 7, 2026 · 15 categories · 80 passed · 25 warnings · 4 issues · 41 informational
Partial evidence; some observations were unavailable.
Audit score
F36/100
Needs work
- Agentic
- 58
- SEO
- 38
What we found
4Needs a fix25Could be better80Looks good41Informational- 1.Needs a fix: Your pages repeat the same titles. see checkUnique titles help visitors and search engines tell pages apart.
- 2.Needs a fix: Your page has no main heading. see checkThe main heading gives visitors and search engines a clear topic.
- 3.Needs a fix: Homepage content volume: needs fixing. see checkUseful, specific content gives visitors answers and a reason to stay.
- 4.Could be better: Crawlable content in source HTML: needs attention. see checkUseful, specific content gives visitors answers and a reason to stay.
- 5.Could be better: Discovery copy is distinct across sampled pages: needs attention. see checkUseful, specific content gives visitors answers and a reason to stay.
Site checks
Every observation from the crawl, grouped by what it describes. Open a row for the evidence and the recommended fix.
Metadata1Needs a fix10Looks good
77/100Needs a fix: Titles unique across pages1 title repeat across 10 indexable sampled pages, e.g.
Needs a fix · Metadata · Review suggestedCritical
Observed evidence
1 title repeat across 10 indexable sampled pages, e.g. "Pressure: AI agents debate, review, and research" on 9 pages.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. Right now the sampled pages don't provide it.
Recommended fix
Give each distinct page a title that names what is on it. Pages that are true copies should declare a canonical URL instead.
Affected pages (9)
- https://pressure.dev/
- https://pressure.dev/privacy
- https://pressure.dev/pricing
- https://pressure.dev/terms
- https://pressure.dev/security
- https://pressure.dev/docs
- https://pressure.dev/docs/getting-started
- https://pressure.dev/docs/cli
- https://pressure.dev/docs/skills
Looks good: Page title exists
Looks good · Metadata · Measured on your page
Observed evidence
Title found: "Pressure: AI agents debate, review, and research"
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 48 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 "Pressure: AI agents debate, review, and research" 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: "Agents from different labs take opposite sides of your question and argue it out in a shar…"
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Meta description length
Looks good · Metadata · Review suggested
Observed evidence
Description is 154 characters and inside this audit's 70–160 preview range.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Show 5 more checks
Looks good: Homepage isn't noindexed
Looks good · Metadata · Measured on your page
Observed evidence
No blocking robots meta tag on the homepage.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Character encoding declared
Looks good · Metadata · Measured on your page
Observed evidence
UTF-8 declared in the Content-Type header and a meta tag.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: HTML5 doctype
Looks good · Metadata · Measured on your page
Observed evidence
HTML5 doctype declared.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No meta keywords tag
Looks good · Metadata · Measured on your page
Observed evidence
No obsolete meta keywords tag.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Valid metadata order in <head>
Looks good · Metadata · Measured on your page
Observed evidence
No invalid element interrupts metadata in <head>.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Indexing16Looks good
100/100Looks good: Single canonical declaration
Looks good · Indexing · Measured on your page
Observed evidence
One canonical declaration found.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Noindex and canonical agree
Looks good · Indexing · Measured on your page
Observed evidence
No conflicting noindex and cross-page canonical instructions.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No meta-refresh redirect
Looks good · Indexing · Measured on your page
Observed evidence
No meta-refresh redirect.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No soft-404 response
Looks good · Indexing · Measured on your page
Observed evidence
No soft-404 pattern on sampled HTTP 200 pages.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Canonical target integrity
Looks good · Indexing · Measured on your page
Observed evidence
Canonical is a valid https URL. Its host is checked by the canonical consistency check.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sampled URLs have aligned indexability signals
Looks good · Indexing · Measured on your page
Observed evidence
Indexability signals align across 10 sampled URL(s).
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Show 10 more checks
Looks good: robots.txt exists
Looks good · Indexing · Measured on your page
Observed evidence
robots.txt responds with 200.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: robots.txt doesn't block everything
Looks good · Indexing · Measured on your page
Observed evidence
The audited URL is allowed for Googlebot. 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://pressure.dev/sitemap.xml.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sitemap parses and lists URLs
Looks good · Indexing · Measured on your page
Observed evidence
Sitemap lists 19 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://pressure.dev/
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Canonical is absolute and self-referencing
Looks good · Indexing · Measured on your page
Observed evidence
Canonical is absolute and points at this page.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: www vs apex consistency
Looks good · Indexing · Measured on your page
Observed evidence
Hostname is used consistently (pressure.dev).
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: URLs are readable slugs
Looks good · Indexing · Measured on your page
Observed evidence
URL slugs are readable (19 sampled).
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sampled pages expose search-access signals
Looks good · Indexing · Measured on your page
Observed evidence
No restrictive search-access signal on 10 sampled page(s). Actual indexing is not verified.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Content1Needs a fix3Could be better4Looks good3Informational
45/100Needs a fix: Homepage content volumeThe audited page has about 0 words of main content (navigation, header and footer excluded).
Needs a fix · Content · Review suggested
Observed evidence
The audited page has about 0 words of main content (navigation, header and footer excluded).
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. Right now the sampled pages don't provide it.
Recommended fix
Add substance: what the site is, who it's for, what problems it solves. This audit measures visible HTML; it does not measure rankings, traffic, or content originality. Note: if your content renders only via client-side JS, crawlers without JS (and this checker) can't see it — prefer server rendering.
Could be better: Crawlable content in source HTML9 sampled page(s) expose fewer than 30 publisher words and an empty application root with script references.
Could be better · Content · Published platform ruleCritical
Observed evidence
9 sampled page(s) expose fewer than 30 publisher words and an empty application root with script references.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. It is there, but weaker than this check expects.
Recommended fix
Server-render or statically render the page's primary content. Google can render JavaScript, but rendering can fail or be delayed and other crawlers may not execute it.
Affected pages (9)
- https://pressure.dev/
- https://pressure.dev/privacy
- https://pressure.dev/pricing
- https://pressure.dev/terms
- https://pressure.dev/security
- https://pressure.dev/docs
- https://pressure.dev/docs/getting-started
- https://pressure.dev/docs/cli
- https://pressure.dev/docs/skills
Could be better: Discovery copy is distinct across sampled pagesRepeated discovery copy found: description "Agents from different labs take opposite sides of your question and argue it out…" on https://pressure.dev/ and https://pressure.dev/privacy and https://pressure.dev/pricing and https://pressure.dev/terms and https://pressure.dev/security and https://pressure.dev/docs and https://pressure.dev/docs/getting-started and https://pressure.dev/docs/cli and https://pressure.dev/docs/skills.
Could be better · Content · Measured on your page
Observed evidence
Repeated discovery copy found: description "Agents from different labs take opposite sides of your question and argue it out…" on https://pressure.dev/ and https://pressure.dev/privacy and https://pressure.dev/pricing and https://pressure.dev/terms and https://pressure.dev/security and https://pressure.dev/docs and https://pressure.dev/docs/getting-started and https://pressure.dev/docs/cli and https://pressure.dev/docs/skills.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. It is there, but weaker than this check expects.
Recommended fix
Give each content page a distinct description, H1, and opening copy. If the pages intentionally represent one resource, consolidate them with a canonical or redirect.
Affected pages (9)
- https://pressure.dev/
- https://pressure.dev/privacy
- https://pressure.dev/pricing
- https://pressure.dev/terms
- https://pressure.dev/security
- https://pressure.dev/docs
- https://pressure.dev/docs/getting-started
- https://pressure.dev/docs/cli
- https://pressure.dev/docs/skills
Could be better: Text-to-HTML ratioVisible text is 0.0% of the HTML markup (scripts and styles excluded).
Could be better · Content · Review suggested
Observed evidence
Visible text is 0.0% of the HTML markup (scripts and styles excluded).
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. It is there, but weaker than this check expects.
Recommended fix
Text-to-HTML ratio is not a ranking factor, but a very low value often means deeply nested markup or content that only appears after JavaScript runs. Check the source-content checks before changing anything.
Not applicable: ReadabilityNot enough English prose to estimate readability (it needs about 100 words in three or more sentences).
Not applicable · Content · Measured on your page
Observed evidence
Not enough English prose to estimate readability (it needs about 100 words in three or more sentences).
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. This check does not apply to the features observed in this sample.
Recommended fix
Nothing to change for this check.
Not applicable: Title and H1 agreeNeed both a <title> and an H1 to compare them.
Not applicable · Content · Measured on your page
Observed evidence
Need both a <title> and an H1 to compare them.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. This check does not apply to the features observed in this sample.
Recommended fix
Add whichever is missing — the metadata and headings checks name it — then this check confirms the two describe the same topic.
Show 5 more checks
Not applicable: Crawled pages aren't near-duplicatesFewer than two indexable sampled pages carry more than 50 words of main content, so there is nothing to compare.
Not applicable · Content · Measured on your page
Observed evidence
Fewer than two indexable sampled pages carry more than 50 words of main content, so there is nothing to compare.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. This check does not apply to the features observed in this sample.
Recommended fix
Nothing to change for this check.
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.
Looks good: Outbound references
Looks good · Content · Measured on your page
Observed evidence
0 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.
Structured dataNot measured
Not measuredCould be better: JSON-LD presentNo JSON-LD structured data on the homepage.
Could be better · Structured data · Review suggested
Observed evidence
No JSON-LD structured data on the homepage.
Why this matters
Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. It is there, but weaker than this check expects.
Recommended fix
Add Organization and WebSite schema. They state who publishes the site and what it is called, which is what rich results and answer engines read first.
Could be better: Organization or WebSite schemaNo Organization, WebSite or Person schema found.
Could be better · Structured data · Review suggested
Observed evidence
No Organization, WebSite or Person schema found.
Why this matters
Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. It is there, but weaker than this check expects.
Recommended fix
Add an identity node so search engines and AI assistants can attribute your content to a real entity.
Not applicable: JSON-LD parsesNo JSON-LD blocks were found, so there is no syntax to validate.
Not applicable · Structured data · Measured on your page
Observed evidence
No JSON-LD blocks were found, so there is no syntax to validate.
Why this matters
Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. This check does not apply to the features observed in this sample.
Recommended fix
Add a <script type="application/ld+json"> block describing the page — Organization or WebSite is the usual starting point.
Not applicable: Content-specific schemaNo content-specific schema (Article, Product, FAQPage…) detected.
Not applicable · Structured data · Measured on your page
Observed evidence
No content-specific schema (Article, Product, FAQPage…) detected.
Why this matters
Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. This check does not apply to the features observed in this sample.
Recommended fix
If you publish articles, products or FAQs, add the matching schema type — that's what makes rich results (stars, FAQs, prices) possible.
Headings1Needs a fix1Looks good5Informational
6/100Needs a fix: H1 existsThe audited page has no <h1>.
Needs a fix · Headings · Review suggestedCritical
Observed evidence
The audited page has no <h1>.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. Right now the sampled pages don't provide it.
Recommended fix
Add one <h1> stating what the page is about, usually the hero headline. Search engines, screen readers and answer engines use it as the page's main heading.
Not applicable: Single H1No H1 exists to check for uniqueness.
Not applicable · Headings · Measured on your page
Observed evidence
No H1 exists to check for uniqueness.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. This check does not apply to the features observed in this sample.
Recommended fix
The H1 presence check covers the missing main heading.
Not applicable: Heading levels don't skipThe page has no headings, so there is nothing further to assess.
Not applicable · Headings · Measured on your page
Observed evidence
The page has no headings, so there is nothing further to assess.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. This check does not apply to the features observed in this sample.
Recommended fix
The H1 presence check covers the missing headings. Add an H1 and descriptive H2 sections.
Not applicable: H1 has real textNo H1 text exists to inspect.
Not applicable · Headings · Measured on your page
Observed evidence
No H1 text exists to inspect.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. This check does not apply to the features observed in this sample.
Recommended fix
The H1 presence check covers the missing main heading.
Not applicable: Headings are descriptiveThe page has no headings, so there is nothing further to assess.
Not applicable · Headings · Measured on your page
Observed evidence
The page has no headings, so there is nothing further to assess.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. This check does not apply to the features observed in this sample.
Recommended fix
The H1 presence check covers the missing headings. Add an H1 and descriptive H2 sections.
Not applicable: Content is sectioned with H2sThe page has no headings, so there is nothing further to assess.
Not applicable · Headings · Measured on your page
Observed evidence
The page has no headings, so there is nothing further to assess.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. This check does not apply to the features observed in this sample.
Recommended fix
The H1 presence check covers the missing headings. Add an H1 and descriptive H2 sections.
Looks good: Element IDs are unique per document
Looks good · Headings · Measured on your page
Observed evidence
All inspected element IDs are unique within their documents.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
ImagesNot applicable
Not measuredNot applicable: Alt text coverageNo visible <img> elements on the audited page (hidden, presentational and 1×1 tracking images are not counted).
Not applicable · Images · Measured on your page
Observed evidence
No visible <img> elements on the audited page (hidden, presentational and 1×1 tracking images are not counted).
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. This check does not apply to the features observed in this sample.
Recommended fix
Nothing to change here. Any image you add later needs alt text that describes it, so this check starts scoring then.
Not applicable: Width/height attributesNo visible <img> elements to measure on the audited page.
Not applicable · Images · Measured on your page
Observed evidence
No visible <img> elements to measure on the audited page.
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. This check does not apply to the features observed in this sample.
Recommended fix
Nothing to change here. Give future images explicit width and height attributes so the browser can reserve their space.
Not applicable: Modern image formatsNo raster images with a recognizable file extension were found.
Not applicable · Images · Measured on your page
Observed evidence
No raster images with a recognizable file extension were found.
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. This check does not apply to the features observed in this sample.
Recommended fix
Nothing to change here. If images arrive later, serve WebP or AVIF alongside PNG/JPEG.
Not applicable: Lazy loadingOnly 0 visible image(s) on the page, too few for lazy loading to change the initial load.
Not applicable · Images · Measured on your page
Observed evidence
Only 0 visible image(s) on the page, too few for lazy loading to change the initial load.
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. This check does not apply to the features observed in this sample.
Recommended fix
Nothing to change here. Once the page carries several images, add loading="lazy" to the ones below the fold.
Links1Could be better2Looks good3Informational
72/100Could be better: Homepage links into the siteThe homepage links to only 0 distinct internal page(s).
Could be better · Links · Review suggested
Observed evidence
The homepage links to only 0 distinct internal page(s).
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. It is there, but weaker than this check expects.
Recommended fix
Link generously to your key pages from the homepage — it's how crawlers discover them and how PageRank flows.
Not measured: Internal links resolveNo internal links were probed.
Not measured · Links · Not established
Observed evidence
No internal links were probed.
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 internal links from your homepage.
Not applicable: Anchor text is meaningfulNo links were found on the audited page.
Not applicable · Links · Measured on your page
Observed evidence
No links were found on the audited page.
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. This check does not apply to the features observed in this sample.
Recommended fix
Link to your main pages from the homepage. Crawlers and readers both need a path in, and this check then reviews the anchor text.
Not applicable: Same-page links have source targetsNo same-page fragment links to check.
Not applicable · Links · Measured on your page
Observed evidence
No same-page fragment links to check.
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. This check does not apply to the features observed in this sample.
Recommended fix
Keep section links connected to stable IDs.
Looks good: No dead placeholder links
Looks good · Links · Measured on your page
Observed evidence
No placeholder links on the audited page.
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: External links use rel=noopener
Looks good · Links · Measured on your page
Observed evidence
All target="_blank" links carry rel="noopener".
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Mobile3Looks good3Informational
100/100Not applicable: Responsive image markupOnly 0 image(s) on the page, too few for responsive image markup to change what phones download.
Not applicable · Mobile · Measured on your page
Observed evidence
Only 0 image(s) on the page, too few for responsive image markup to change what phones download.
Why this matters
Google indexes the phone rendering, so that is the version being graded. This check does not apply to the features observed in this sample.
Recommended fix
Nothing to change here. When the page carries several images, give them srcset and sizes so phones fetch smaller files.
Not measured: No tiny inline font sizesNo sub-12px inline font sizes detected; stylesheet rules and rendered sizes were not measured.
Not measured · Mobile · Not established
Observed evidence
No sub-12px inline font sizes detected; stylesheet rules and rendered sizes were not measured.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Check computed font sizes in a browser across mobile widths.
Not applicable: ARIA references point to source elementsNo ARIA ID references found in the sampled HTML.
Not applicable · Mobile · Measured on your page
Observed evidence
No ARIA ID references found in the sampled HTML.
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
Verify rendered accessibility separately.
Looks good: Viewport meta tag
Looks good · Mobile · Measured on your page
Observed evidence
Viewport configured: "width=device-width, initial-scale=1.0".
Why this matters
Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Pinch zoom not disabled
Looks good · Mobile · Measured on your page
Observed evidence
The viewport lets users zoom.
Why this matters
Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Interactive controls have source labels
Looks good · Mobile · Measured on your page
Observed evidence
7 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.
Language1Looks good2Informational
100/100Not applicable: hreflang syntaxNo hreflang tags — fine for single-language sites.
Not applicable · Language · Measured on your page
Observed evidence
No hreflang tags — fine for single-language sites.
Why this matters
The declared language tells browsers and assistive tech how to read the page and who it is for. This check does not apply to the features observed in this sample.
Recommended fix
Only add hreflang if you publish the same content in multiple languages/regions.
Not applicable: Declared language matches contentNot enough text on the page to tell which language it is written in.
Not applicable · Language · Measured on your page
Observed evidence
Not enough text on the page to tell which language it is written in.
Why this matters
The declared language tells browsers and assistive tech how to read the page and who it is for. This check does not apply to the features observed in this sample.
Recommended fix
Nothing to change for this check. Confirm the lang attribute names the language most of the page is written in.
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.
Branding3Looks good1Informational
100/100Not 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.
Looks good: Favicon
Looks good · Branding · Measured on your page
Observed evidence
Favicon declared via <link rel="icon"> (/favicon.svg).
Why this matters
These icons are what appear in browser tabs, bookmarks and search results. The inspected source provides this signal.
Recommended fix
Nothing to do here.
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.
Looks good: Theme color
Looks good · Branding · Measured on your page
Observed evidence
theme-color is "#141416".
Why this matters
These icons are what appear in browser tabs, bookmarks and search results. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Performance
Measured from the audited response and its markup. These are source observations, not field Core Web Vitals.
| Measure | This site | Reading |
|---|---|---|
| Web fonts don't block text | — | Informational: not applicableNo Google Fonts stylesheet links detected. |
| Server response time | 200 ms | Looks good: goodThe audit received response headers after 200 ms from one test location. |
| HTML payload size | 2 KB | Looks good: goodThe page's HTML is a lean 2 KB uncompressed. |
| No render-blocking head scripts | — | Looks good: goodNo synchronous render-blocking scripts in <head>. |
| Inline styles are bounded | 0.0 KB | Looks good: goodInline styles total 0.0 KB. |
| Script/stylesheet count | — | Looks good: good2 total script/style resources — reasonable. |
| HTML served compressed | — | Looks good: goodHTML is compressed with br. |
| Iframe usage | — | Looks good: goodNo iframes. |
| Source HTML weight | 1.8 KB | Informational: measured source, not transferred bytes1.8 KB of HTML on the audited page |
From a single automated fetch of the audited page. A quick reading, not a substitute for Lighthouse or field data.
Security
HTTPS, transport security and the response headers the audited pages send.
Could be better: Frame embedding protectionNo frame-embedding restriction was observed (neither CSP frame-ancestors nor X-Frame-Options).
Could be better · Security · Review suggested
Observed evidence
No frame-embedding restriction was observed (neither CSP frame-ancestors nor X-Frame-Options).
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
Send Content-Security-Policy: frame-ancestors 'self' (or 'none', or a list of partner origins), or X-Frame-Options: SAMEORIGIN. It stops other sites from framing your pages to trick visitors into clicking (clickjacking).
Could be better: X-Content-Type-OptionsX-Content-Type-Options: nosniff is not set.
Could be better · Security · Review suggested
Observed evidence
X-Content-Type-Options: nosniff is not set.
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
Add it — one header, stops MIME-sniffing attacks. Most hosts let you set headers in config (vercel.json, netlify.toml, next.config).
Could be better: Content Security PolicyNo Content-Security-Policy detected.
Could be better · Security · Review suggested
Observed evidence
No Content-Security-Policy detected.
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
Configure an enforced policy for script and resource origins; use report-only monitoring to prepare changes safely.
Could be better: Browser feature permissionsNo explicit restriction on sensitive browser features was observed.
Could be better · Security · Review suggested
Observed evidence
No explicit restriction on sensitive browser features was observed.
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
Disable unused camera, microphone, or geolocation access using Permissions-Policy.
Not applicable: Declared form submission targetsNo HTML forms were found.
Not applicable · Security · Measured on your page
Observed evidence
No HTML forms were found.
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
Check JavaScript-generated form transport separately if present.
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=31556926.
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
No Referrer-Policy is set, so browsers apply their default, strict-origin-when-cross-origin, which sends only the origin to other sites.
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.
AI answer readiness
Retrieval signals an answer engine relies on: crawler access, clear entities and answers it can quote. These checks do not measure citations or traffic.
Could be better: Semantic HTML structureThe homepage uses no semantic landmarks (main/article/section/nav…) — div soup.
Could be better · AI answer readiness · Review suggested
Observed evidence
The homepage uses no semantic landmarks (main/article/section/nav…) — div soup.
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
Wrap content in semantic elements. Parsers extracting your content for AI answers use these landmarks to find the substance and skip the chrome.
Could be better: FAQ/QA schemaNo FAQPage or QAPage schema on any crawled page.
Could be better · AI answer readiness · Review suggested
Observed evidence
No FAQPage or QAPage schema on any crawled page.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
If the page answers recurring questions, use visible question-and-answer content and matching FAQPage markup. QAPage is for a single question with user-submitted answers. Google FAQ rich results are restricted to eligible authoritative government and health sites; markup does not guarantee AI citations.
Could be better: Freshness signalsNo dateModified schema or visible 'updated' dates found.
Could be better · AI answer readiness · Review suggested
Observed evidence
No dateModified schema or visible 'updated' dates found.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
For content where dates matter, show the actual update date and mirror it in dateModified. Do not invent dates or change them without a substantive update. Missing dates alone do not prove stale content.
Could be better: Cites external sourcesNo outbound links on any crawled page.
Could be better · AI answer readiness · Review suggested
Observed evidence
No outbound links on any crawled page.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
Cite sources for factual claims. This makes source links observable to readers and crawlers; the audit does not measure or guarantee citations or rankings.
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://pressure.dev/index.md
- https://pressure.dev/privacy.md
- https://pressure.dev/index.html.md
Not measured: Answers lead the sectionNo <p> paragraphs were found on the homepage.
Not measured · AI answer readiness · Not established
Observed evidence
No <p> paragraphs were found on the homepage.
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
Put the page's body copy in paragraph elements. This check then looks at whether the opening answers the question instead of warming up.
Not measured: Definitional openingNo opening paragraph was found on the homepage.
Not measured · AI answer readiness · Not established
Observed evidence
No opening paragraph was found on the homepage.
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
Open the page with a sentence that says what the thing is. This check then confirms the first paragraph is definitional.
Not measured: Citable facts densityVery few concrete figures in the text (0 numbers in 0 words).
Not measured · AI answer readiness · Not established
Observed evidence
Very few concrete figures in the text (0 numbers in 0 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
Specific numbers, dates and stats are what AI answers cite. 'Fast' is ignorable; '2.3× faster' is quotable.
Not measured: Machine-readable provenance signalsNo machine-readable author, date, breadcrumb, or contact signal was found on sampled pages.
Not measured · AI answer readiness · Not established
Observed evidence
No machine-readable author, date, breadcrumb, or contact signal was found on sampled pages.
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 provenance signals in JSON-LD and visible HTML: author, publication/update date, breadcrumbs, and a reachable contact method.
Not applicable: Accept: text/markdown negotiationThe homepage answered Accept: text/markdown with text/html; charset=utf-8.
Not applicable · AI answer readiness · Measured on your page
Observed evidence
The homepage answered Accept: text/markdown with text/html; charset=utf-8.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. This check does not apply to the features observed in this sample.
Recommended fix
Optional: return a stripped markdown body when the request asks for text/markdown. Some hosts and CDNs do this for you; a plain HTML answer is not a defect.
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 (3878 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: Question-style headings
Looks good · AI answer readiness · Measured on your page
Observed evidence
100% of 1 subheadings are question-shaped.
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 17 words — 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: Consistent brand entity
Looks good · AI answer readiness · Measured on your page
Observed evidence
Brand declared: og:site_name "Pressure".
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: llms.txt links resolve to this site
Looks good · AI answer readiness · Measured on your page
Observed evidence
llms.txt contains 17 same-origin Markdown link(s).
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Entity identity agrees across signals
Looks good · AI answer readiness · Measured on your page
Observed evidence
The site is consistently named "Pressure" and 2 identity URL(s) stay on pressure.dev.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Question headings have concise answers
Looks good · AI answer readiness · Measured on your page
Observed evidence
1 concise answer block(s) follow 1 question-shaped heading(s).
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: llms.txt follows the spec
Looks good · AI answer readiness · Published platform rule
Observed evidence
llms.txt has an H1, a summary, 4 section(s) and 15 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
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 19/100 for publisher readiness. Ignore this section if you do not run ads.
Needs a fix: Sampled publisher-content coverage8/8 editorial pages expose fewer than 80 publisher words in source HTML.
Needs a fix · AdSense policy · Review suggestedCritical
Observed evidence
8/8 editorial pages expose fewer than 80 publisher words in source HTML. 2 of the 10 sampled pages are support or tool pages and were excluded from this check.
Why this matters
A publisher review looks for this before it accepts a site. Right now the sampled pages don't provide it.
Recommended fix
Add crawlable explanation or original publisher material to those pages. Most of the sample currently reads as chrome rather than content.
Affected pages (8)
- https://pressure.dev/
- https://pressure.dev/pricing
- https://pressure.dev/security
- https://pressure.dev/blog/
- https://pressure.dev/docs
- https://pressure.dev/docs/getting-started
- https://pressure.dev/docs/cli
- https://pressure.dev/docs/skills
Could be better: Privacy policy advertising disclosuresFetched privacy policy lacks cookie/storage, advertising or Google, third-party/vendor disclosure signals.
Could be better · AdSense policy · Published platform ruleCritical
Observed evidence
Fetched privacy policy lacks cookie/storage, advertising or Google, third-party/vendor disclosure signals.
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
Describe data collection, sharing, and cookie use by Google and other third-party ad vendors.
Affected pages (1)
- https://pressure.dev/privacy
Could be better: Publisher content exists in source HTML9 sampled page(s) expose an empty application root and fewer than 30 publisher words in source HTML.
Could be better · AdSense policy · Review suggestedCritical
Observed evidence
9 sampled page(s) expose an empty application root and fewer than 30 publisher words in source HTML.
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
Server-render or statically render primary content so AdsBot and other crawlers receive meaningful publisher content without relying on client execution.
Affected pages (9)
- https://pressure.dev/
- https://pressure.dev/privacy
- https://pressure.dev/pricing
- https://pressure.dev/terms
- https://pressure.dev/security
- https://pressure.dev/docs
- https://pressure.dev/docs/getting-started
- https://pressure.dev/docs/cli
- https://pressure.dev/docs/skills
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: Contact methodNo contact page or mailto link found.
Could be better · AdSense policy · Review suggested
Observed evidence
No contact page or mailto link 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 a working contact route or visible email so users can reach the publisher. This is a trust heuristic, not a published approval rule.
Could be better: Thin page share8/8 editorial pages expose fewer than 80 publisher words.
Could be better · AdSense policy · Review suggested
Observed evidence
8/8 editorial pages expose fewer than 80 publisher words. 2 of the 10 sampled pages are support or tool pages and were excluded from this check.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Review these pages for a clear purpose and useful publisher material. This cutoff is a triage heuristic, not an AdSense minimum.
Affected pages (8)
- https://pressure.dev/ (0 publisher words)
- https://pressure.dev/pricing (0 publisher words)
- https://pressure.dev/security (0 publisher words)
- https://pressure.dev/blog/ (32 publisher words)
- https://pressure.dev/docs (0 publisher words)
- https://pressure.dev/docs/getting-started (0 publisher words)
- https://pressure.dev/docs/cli (0 publisher words)
- https://pressure.dev/docs/skills (0 publisher words)
Could be better: Tool pages expose explanatory content9/9 tool-style screen(s) expose fewer than 80 publisher words.
Could be better · AdSense policy · Review suggested
Observed evidence
9/9 tool-style screen(s) expose fewer than 80 publisher words. Google publishes no minimum word count; this is an audit heuristic.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Explain the tool's purpose, inputs, method, limitations, and result interpretation in source HTML. Add useful material, not filler.
Affected pages (9)
- https://pressure.dev/
- https://pressure.dev/privacy
- https://pressure.dev/pricing
- https://pressure.dev/terms
- https://pressure.dev/security
- https://pressure.dev/docs
- https://pressure.dev/docs/getting-started
- https://pressure.dev/docs/cli
- https://pressure.dev/docs/skills
Could be better: Policy pages linked site-wide10/10 crawled pages don't link to the privacy policy.
Could be better · AdSense policy · Review suggested
Observed evidence
10/10 crawled pages don't link to the privacy policy.
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
Place the privacy link in shared navigation or footer markup so users can reach disclosures from any sampled entry page.
Affected pages (10)
- https://pressure.dev/
- https://pressure.dev/privacy
- https://pressure.dev/pricing
- https://pressure.dev/terms
- https://pressure.dev/security
- https://pressure.dev/blog/
- https://pressure.dev/docs
- https://pressure.dev/docs/getting-started
- https://pressure.dev/docs/cli
- https://pressure.dev/docs/skills
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: First-party contact emailNo public contact email was found in the sampled home, About, or Contact pages.
Not measured · AdSense policy · Review suggested
Observed evidence
No public contact email was found in the sampled home, About, or Contact pages.
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
A public email is optional. The separate contact-method check covers whether readers have a way to reach the publisher.
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.
Not measured: Latest article has real depthNo article-shaped page was found on this site, so there is nothing to read.
Not measured · AdSense policy · Not established
Observed evidence
No article-shaped page was found on this site, so there is nothing to read.
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
Publish articles under a path such as /blog/… and list them in the sitemap. This check then reads the newest one.
Not measured: Latest article reads as edited workNo article-shaped page was found on this site, so there is nothing to read.
Not measured · AdSense policy · Not established
Observed evidence
No article-shaped page was found on this site, so there is nothing to read.
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
Publish articles under a path such as /blog/… and list them in the sitemap. This check then reviews its style signals.
Not measured: Latest article names an author and a dateNo article-shaped page was found on this site, so there is nothing to read.
Not measured · AdSense policy · Not established
Observed evidence
No article-shaped page was found on this site, so there is nothing to read.
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
Publish articles under a path such as /blog/… and list them in the sitemap. This check then looks for its byline and date.
Looks good: Privacy policy page
Looks good · AdSense policy · Measured on your page
Observed evidence
Privacy policy found: https://pressure.dev/privacy
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Terms page
Looks good · AdSense policy · Measured on your page
Observed evidence
Terms page found: https://pressure.dev/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: No ads on non-content screens
Looks good · AdSense policy · Published platform rule
Observed evidence
No Google ad code detected on sampled non-content screens.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Publisher content differs across URLs
Looks good · AdSense policy · Review suggested
Observed evidence
No high publisher-content repetition among 0 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.
Show 4 more checks
Looks good: Article-style content exists
Looks good · AdSense policy · Measured on your page
Observed evidence
Article-style content detected.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No "coming soon" or placeholder pages
Looks good · AdSense policy · Measured on your page
Observed evidence
No "coming soon", "under construction" or lorem-ipsum text on crawled pages.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Site language is AdSense-supported
Looks good · AdSense policy · Measured on your page
Observed evidence
Language "en" is AdSense-supported.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: 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.
Hosting and infrastructure
Public endpoint facts observed at audit time. A CDN or proxy can conceal the origin infrastructure.
| Hostname | pressure.dev |
|---|---|
| IP addresses | 199.36.158.100 |
| DNS A | 199.36.158.100 |
| DNS NS | joselyn.ns.cloudflare.com · arturo.ns.cloudflare.com |
| DNS MX | 10 eforward1.registrar-servers.com · 10 eforward2.registrar-servers.com · 10 eforward3.registrar-servers.com · 15 eforward4.registrar-servers.com · 20 eforward5.registrar-servers.com |
| TLS | TLSv1.3TLS_AES_128_GCM_SHA256 |
| Certificate issuer | Google Trust Services / WR3 |
| Certificate valid until | Jan 25 05:58:16 2027 GMT |
| Certificate validation | Passed |
Website anatomy and diagnostics
Explore links, resources, crawler access and site integrations.
Page architecture
Choose a page to explore its details and connections.
Page content
0 publisher words
Page structure
javascript shell
Observed discovery
Depth 0 · 1 incoming links
HTTP 200 · 1.8 KB source
Source interactions
0 controls · 0 unnamed
1 script / 1 stylesheet references
- Canonical declaration
- https://pressure.dev/
- Schema types
- None observed
- Outgoing links in sampled graph
- None observed
Routes: / · /privacy · /pricing · /terms · /security · /blog · /docs
Repeated metadata in the sample
Same title: pressure: ai agents debate, review, and research
/ · /privacy · /pricing · /terms · /security · /docs · /docs/getting-started · /docs/cli · /docs/skills
Same description: agents from different labs take opposite sides of your question and argue it out in a shared room. the server pins a structured summary. the room decides.
/ · /privacy · /pricing · /terms · /security · /docs · /docs/getting-started · /docs/cli · /docs/skills
Resource origins 1
Resources associated with your website. External resources may belong to the same organization.
- https://pressure.dev/script, stylesheet · 20 references · same origin
Crawler policy by page
Review crawler access for your pages. Search, training and user-triggered services have different purposes; declared access does not guarantee discovery.
| Crawler / purpose | Page | Policy | Matched directive |
|---|---|---|---|
| Googlebotsearch | / | allowed | allow: / |
| Googlebotsearch | /privacy | allowed | allow: / |
| Googlebotsearch | /pricing | allowed | allow: / |
| Googlebotsearch | /terms | allowed | allow: / |
| Googlebotsearch | /security | allowed | allow: / |
| Googlebotsearch | /blog/ | allowed | allow: / |
| Googlebotsearch | /docs | allowed | allow: / |
| Googlebotsearch | /docs/getting-started | allowed | allow: / |
| Googlebotsearch | /docs/cli | allowed | allow: / |
| Googlebotsearch | /docs/skills | allowed | allow: / |
| bingbotsearch | / | allowed | allow: / |
| bingbotsearch | /privacy | allowed | allow: / |
| bingbotsearch | /pricing | allowed | allow: / |
| bingbotsearch | /terms | allowed | allow: / |
| bingbotsearch | /security | allowed | allow: / |
| bingbotsearch | /blog/ | allowed | allow: / |
| bingbotsearch | /docs | allowed | allow: / |
| bingbotsearch | /docs/getting-started | allowed | allow: / |
| bingbotsearch | /docs/cli | allowed | allow: / |
| bingbotsearch | /docs/skills | allowed | allow: / |
| OAI-SearchBotsearch | / | allowed | allow: / |
| OAI-SearchBotsearch | /privacy | allowed | allow: / |
| OAI-SearchBotsearch | /pricing | allowed | allow: / |
| OAI-SearchBotsearch | /terms | allowed | allow: / |
| OAI-SearchBotsearch | /security | allowed | allow: / |
| OAI-SearchBotsearch | /blog/ | allowed | allow: / |
| OAI-SearchBotsearch | /docs | allowed | allow: / |
| OAI-SearchBotsearch | /docs/getting-started | allowed | allow: / |
| OAI-SearchBotsearch | /docs/cli | allowed | allow: / |
| OAI-SearchBotsearch | /docs/skills | allowed | allow: / |
| PerplexityBotsearch | / | allowed | allow: / |
| PerplexityBotsearch | /privacy | allowed | allow: / |
| PerplexityBotsearch | /pricing | allowed | allow: / |
| PerplexityBotsearch | /terms | allowed | allow: / |
| PerplexityBotsearch | /security | allowed | allow: / |
| PerplexityBotsearch | /blog/ | allowed | allow: / |
| PerplexityBotsearch | /docs | allowed | allow: / |
| PerplexityBotsearch | /docs/getting-started | allowed | allow: / |
| PerplexityBotsearch | /docs/cli | allowed | allow: / |
| PerplexityBotsearch | /docs/skills | allowed | allow: / |
| Claude-SearchBotsearch | / | allowed | allow: / |
| Claude-SearchBotsearch | /privacy | allowed | allow: / |
| Claude-SearchBotsearch | /pricing | allowed | allow: / |
| Claude-SearchBotsearch | /terms | allowed | allow: / |
| Claude-SearchBotsearch | /security | allowed | allow: / |
| Claude-SearchBotsearch | /blog/ | allowed | allow: / |
| Claude-SearchBotsearch | /docs | allowed | allow: / |
| Claude-SearchBotsearch | /docs/getting-started | allowed | allow: / |
| Claude-SearchBotsearch | /docs/cli | allowed | allow: / |
| Claude-SearchBotsearch | /docs/skills | allowed | allow: / |
| GPTBottraining | / | allowed | allow: / |
| GPTBottraining | /privacy | allowed | allow: / |
| GPTBottraining | /pricing | allowed | allow: / |
| GPTBottraining | /terms | allowed | allow: / |
| GPTBottraining | /security | allowed | allow: / |
| GPTBottraining | /blog/ | allowed | allow: / |
| GPTBottraining | /docs | allowed | allow: / |
| GPTBottraining | /docs/getting-started | allowed | allow: / |
| GPTBottraining | /docs/cli | allowed | allow: / |
| GPTBottraining | /docs/skills | allowed | allow: / |
| ClaudeBottraining | / | allowed | allow: / |
| ClaudeBottraining | /privacy | allowed | allow: / |
| ClaudeBottraining | /pricing | allowed | allow: / |
| ClaudeBottraining | /terms | allowed | allow: / |
| ClaudeBottraining | /security | allowed | allow: / |
| ClaudeBottraining | /blog/ | allowed | allow: / |
| ClaudeBottraining | /docs | allowed | allow: / |
| ClaudeBottraining | /docs/getting-started | allowed | allow: / |
| ClaudeBottraining | /docs/cli | allowed | allow: / |
| ClaudeBottraining | /docs/skills | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | / | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | /privacy | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | /pricing | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | /terms | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | /security | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | /blog/ | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | /docs | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | /docs/getting-started | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | /docs/cli | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | /docs/skills | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | / | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | /privacy | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | /pricing | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | /terms | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | /security | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | /blog/ | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | /docs | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | /docs/getting-started | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | /docs/cli | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | /docs/skills | allowed | allow: / |
Advertised APIs and machine interfaces
documentation · declared
https://pressure.dev/docs
This interface was advertised; its runtime behavior remains unverified.
documentation · declared
https://pressure.dev/docs/getting-started
This interface was advertised; its runtime behavior remains unverified.
documentation · declared
https://pressure.dev/docs/cli
This interface was advertised; its runtime behavior remains unverified.
documentation · declared
https://pressure.dev/docs/skills
This interface was advertised; its runtime behavior remains unverified.
Public DNS and TLS endpoint
pressure.dev · observed · 199.36.158.100
- A
- 199.36.158.100
- AAAA
- Unavailable for this exact hostname
- CNAME
- Unavailable for this exact hostname
- NS
- joselyn.ns.cloudflare.com · arturo.ns.cloudflare.com
- MX
- 10 eforward1.registrar-servers.com · 10 eforward2.registrar-servers.com · 10 eforward3.registrar-servers.com · 15 eforward4.registrar-servers.com · 20 eforward5.registrar-servers.com
- CAA
- Unavailable for this exact hostname
TLS: TLSv1.3
Certificate validation passed for the observed endpoint.
Issuer: Google Trust Services / WR3
Certificate valid until: Jan 25 05:58:16 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.
- 01
Your top fixes list is the priority order — clear the red items before creating more content.
- 02
Re-run the combined audit after each batch of fixes
Re-run after fixes to see which checks changed; score bands are guidance, not a guarantee of ranking, traffic, or approval.
- 03
Make policy pages, publisher disclosures and substantial content reachable before applying. This audit cannot predict approval.
Apply the recommended fixes
Hand the complete evidence to a coding agent, or take the report with you.
Report notes
- 01This report covers the sampled public pages listed above. Other pages may have different results.
- 02Browser-rendered content, private backend systems and authenticated experiences may require a separate review.
- 03Unavailable observations are identified in the report. Results do not guarantee rankings, citations, security, accessibility or advertising approval.
Pages included in this report
- https://pressure.dev/
- https://pressure.dev/privacy
- https://pressure.dev/pricing
- https://pressure.dev/terms
- https://pressure.dev/security
- https://pressure.dev/blog/
- https://pressure.dev/docs
- https://pressure.dev/docs/getting-started
- https://pressure.dev/docs/cli
- https://pressure.dev/docs/skills