Website report

Visit sitehttps://deployedyet.com/

A free, open-source Mac menu bar app that shows whether your Vercel, Cloudflare and GitHub Actions deploys are building, live or broken, across all your accounts and teams.

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

Analysed Nov 7, 2026 · 15 categories · 108 passed · 17 warnings · 1 issue · 24 informational

Audit score

C

81/100

Mixed

Agentic
100
SEO
81

What we found

1Needs a fix17Could be better108Looks good24Informational
  1. 1.Needs a fix: HTTP redirects to HTTPS: needs fixing. see checkThese protections reduce risks for your website and its visitors.
  2. 2.Could be better: Your images use older file formats. see checkEfficient image formats reduce download size.
  3. 3.Could be better: Title length: needs attention. see checkClear titles and descriptions help people choose your pages in search.
  4. 4.Could be better: Meta description length: needs attention. see checkClear titles and descriptions help people choose your pages in search.
  5. 5.Could be better: Organization or WebSite schema: needs attention. see checkStructured data helps search engines and AI assistants understand your content.

Built with 2 technologies· detected stack

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

How it fits together

  • AstroSite generator
  • CloudflareCDN / edge
InfrastructureType
  • CloudflareCDN / edge
Frameworks and librariesType
  • AstroSite generator

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

Site checks

108 passed · 17 warnings · 1 issues

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

Metadata2Could be better9Looks good

100/100
Could be better: Title lengthTitle is 74 characters, over this audit's 60-character review point (a display heuristic, not a Google limit).

Could be better · Metadata · Review suggested

Observed evidence

Title is 74 characters, over this audit's 60-character review point (a display heuristic, not a Google limit). Google may shorten it in results.

Why this matters

The title and description are the text someone reads in a search result before deciding whether to click. It is there, but weaker than this check expects.

Recommended fix

Front-load the distinctive topic and value so a shortened title still says what the page is. The first 57 characters read: "Deployed Yet? | Vercel, Cloudflare and GitHub deploys in …"

Could be better: Meta description lengthDescription is 172 characters, over this audit's 160-character review point (a preview heuristic, not a Google limit).

Could be better · Metadata · Review suggested

Observed evidence

Description is 172 characters, over this audit's 160-character review point (a preview heuristic, not a Google limit).

Why this matters

The title and description are the text someone reads in a search result before deciding whether to click. It is there, but weaker than this check expects.

Recommended fix

Front-load the useful summary because Google may generate or truncate snippets by query and device.

Looks good: Page title exists

Looks good · Metadata · Measured on your page

Observed evidence

Title found: "Deployed Yet? | Vercel, Cloudflare and GitHub deploys in your Mac menu bar"

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 "Deployed Yet? | Vercel, Cloudflare and GitHub deploys in you…" 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: "A free, open-source Mac menu bar app that shows whether your Vercel, Cloudflare and GitHub…"

Why this matters

The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Titles unique across pages

Looks good · Metadata · Measured on your page

Observed evidence

All 3 indexable sampled pages have distinct titles.

Why this matters

The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Show 5 more checks
Looks good: Homepage isn't noindexed

Looks good · Metadata · Measured on your page

Observed evidence

No blocking robots meta tag on the homepage.

Why this matters

The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Character encoding declared

Looks good · Metadata · Measured on your page

Observed evidence

UTF-8 declared in a meta tag.

Why this matters

The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: HTML5 doctype

Looks good · Metadata · Measured on your page

Observed evidence

HTML5 doctype declared.

Why this matters

The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: No meta keywords tag

Looks good · Metadata · Measured on your page

Observed evidence

No obsolete meta keywords tag.

Why this matters

The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Valid metadata order in <head>

Looks good · Metadata · Measured on your page

Observed evidence

No invalid element interrupts metadata in <head>.

Why this matters

The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Indexing16Looks good

100/100
Looks good: Single canonical declaration

Looks good · Indexing · Measured on your page

Observed evidence

One canonical declaration found.

Why this matters

These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Noindex and canonical agree

Looks good · Indexing · Measured on your page

Observed evidence

No conflicting noindex and cross-page canonical instructions.

Why this matters

These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: No meta-refresh redirect

Looks good · Indexing · Measured on your page

Observed evidence

No meta-refresh redirect.

Why this matters

These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: No soft-404 response

Looks good · Indexing · Measured on your page

Observed evidence

No soft-404 pattern on sampled HTTP 200 pages.

Why this matters

These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Canonical target integrity

Looks good · Indexing · Measured on your page

Observed evidence

Canonical is a valid https URL. Its host is checked by the canonical consistency check.

Why this matters

These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Sampled URLs have aligned indexability signals

Looks good · Indexing · Measured on your page

Observed evidence

Indexability signals align across 3 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://deployedyet.com/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 3 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://deployedyet.com/

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 (deployedyet.com).

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 (3 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 3 sampled page(s). Actual indexing is not verified.

Why this matters

These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Content10Looks good1Informational

100/100
Not measured: ReadabilityFlesch reading ease ≈ 60.

Not measured · Content · Not established

Observed evidence

Flesch reading ease ≈ 60.

Why this matters

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Recommended fix

60+ reads easily for most visitors. This is a heuristic, not a rule — technical audiences tolerate denser text.

Looks good: Crawlable content in source HTML

Looks good · Content · Measured on your page

Observed evidence

No recognized empty JavaScript application shell on 3 sampled page(s). The entered page exposes 1150 publisher word(s).

Why this matters

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Homepage content volume

Looks good · Content · Measured on your page

Observed evidence

The audited page has about 1150 words of main content.

Why this matters

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Text-to-HTML ratio

Looks good · Content · Measured on your page

Observed evidence

Text-to-HTML ratio is 11.7%.

Why this matters

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: No placeholder text

Looks good · Content · Measured on your page

Observed evidence

No placeholder text detected on crawled pages.

Why this matters

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: No starter-template leftovers

Looks good · Content · Measured on your page

Observed evidence

No starter-template artifacts detected.

Why this matters

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Show 5 more checks
Looks good: Title and H1 agree

Looks good · Content · Measured on your page

Observed evidence

Title and H1 share topic words: menu, bar.

Why this matters

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Crawled pages aren't near-duplicates

Looks good · Content · Measured on your page

Observed evidence

No near-duplicate main content among 3 indexable sampled pages.

Why this matters

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: No deprecated HTML tags

Looks good · Content · Measured on your page

Observed evidence

No deprecated HTML tags.

Why this matters

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Outbound references

Looks good · Content · Measured on your page

Observed evidence

12 outbound link(s) present.

Why this matters

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Discovery copy is distinct across sampled pages

Looks good · Content · Measured on your page

Observed evidence

No repeated description, H1, or publisher copy across 3 sampled pages.

Why this matters

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Social sharing8Looks good

100/100
Looks good: Open Graph title

Looks good · Social sharing · Measured on your page

Observed evidence

og:title: "Deployed Yet? | Vercel, Cloudflare and GitHub deploys in your Mac menu bar"

Why this matters

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

Recommended fix

Nothing to do here.

Looks good: Open Graph description

Looks good · Social sharing · Measured on your page

Observed evidence

og:description: "A free, open-source Mac menu bar app that shows whether your Vercel, Cloudflare and GitHub…"

Why this matters

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

Recommended fix

Nothing to do here.

Looks good: Open Graph image

Looks good · Social sharing · Measured on your page

Observed evidence

og:image is set: "https://deployedyet.com/og.jpg"

Why this matters

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

Recommended fix

Nothing to do here.

Looks good: Share image loads

Looks good · Social sharing · Measured on your page

Observed evidence

og:image returns 200 (image/jpeg).

Why this matters

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

Recommended fix

Nothing to do here.

Looks good: Share image dimensions declared

Looks good · Social sharing · Measured on your page

Observed evidence

Dimensions declared: 1200×630.

Why this matters

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

Recommended fix

Nothing to do here.

Looks good: og:url and og:type

Looks good · Social sharing · Measured on your page

Observed evidence

og:url and og:type ("website") are set.

Why this matters

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

Recommended fix

Nothing to do here.

Looks good: Twitter/X card

Looks good · Social sharing · Measured on your page

Observed evidence

twitter:card is "summary_large_image".

Why this matters

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

Recommended fix

Nothing to do here.

Looks good: og:site_name

Looks good · Social sharing · Measured on your page

Observed evidence

og:site_name: "Deployed Yet?".

Why this matters

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

Recommended fix

Nothing to do here.

Structured data1Could be better3Looks good1Informational

100/100
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.

Reference
Not measured: Breadcrumb schema on inner pagesNone of the 2 crawled inner pages declare BreadcrumbList schema.

Not measured · Structured data · Not established

Observed evidence

None of the 2 crawled inner pages declare BreadcrumbList schema.

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 BreadcrumbList to inner pages — Google shows breadcrumbs in results and it clarifies site structure.

Affected pages (2)

  • https://deployedyet.com/privacy
  • https://deployedyet.com/changelog
Reference
Looks good: JSON-LD present

Looks good · Structured data · Measured on your page

Observed evidence

1 JSON-LD block(s) found on the homepage.

Why this matters

Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: JSON-LD parses

Looks good · Structured data · Measured on your page

Observed evidence

All 3 JSON-LD block(s) parse cleanly.

Why this matters

Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Content-specific schema

Looks good · Structured data · Measured on your page

Observed evidence

Content schema found: Offer, FAQPage, SoftwareApplication.

Why this matters

Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Headings7Looks good

100/100
Looks good: H1 exists

Looks good · Headings · Measured on your page

Observed evidence

H1 found: "Your menu bar knows if it shipped."

Why this matters

Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Single H1

Looks good · Headings · Measured on your page

Observed evidence

Exactly one H1 on the homepage.

Why this matters

Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Heading levels don't skip

Looks good · Headings · Measured on your page

Observed evidence

Heading hierarchy is sequential across 15 headings.

Why this matters

Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: H1 has real text

Looks good · Headings · Measured on your page

Observed evidence

H1 reads "Your menu bar knows if it shipped.".

Why this matters

Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Headings are descriptive

Looks good · Headings · Measured on your page

Observed evidence

15 headings, averaging 4.7 words — descriptive.

Why this matters

Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Content is sectioned with H2s

Looks good · Headings · Measured on your page

Observed evidence

5 H2 section(s) structure the page.

Why this matters

Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Element IDs are unique per document

Looks good · Headings · Measured on your page

Observed evidence

All inspected element IDs are unique within their documents.

Why this matters

Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Images1Could be better2Looks good1Informational

81/100
Could be better: Modern image formats1 of 1 raster images are served only as PNG or JPEG: icon-192.png.

Could be better · Images · Review suggested

Observed evidence

1 of 1 raster images are served only as PNG or JPEG: icon-192.png.

Why this matters

Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. It is there, but weaker than this check expects.

Recommended fix

Serve WebP or AVIF versions, which are usually 25–50% smaller at the same quality. Use <picture> with a WebP/AVIF <source> and the original as fallback, or an image CDN or framework image component that converts automatically.

Reference
Not applicable: Lazy loadingOnly 1 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 1 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.

Looks good: Alt text coverage

Looks good · Images · Measured on your page

Observed evidence

All 1 visible images declare alt attributes (including empty alt for decorative images). Whether each description fits its image needs a human look.

Why this matters

Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Width/height attributes

Looks good · Images · Measured on your page

Observed evidence

All 1 visible images declare dimensions or are sized by their container.

Why this matters

Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Mobile4Looks good2Informational

100/100
Not applicable: Responsive image markupOnly 1 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 1 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.

Looks good: Viewport meta tag

Looks good · Mobile · Measured on your page

Observed evidence

Viewport configured: "width=device-width, initial-scale=1".

Why this matters

Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Pinch zoom not disabled

Looks good · Mobile · Measured on your page

Observed evidence

The viewport lets users zoom.

Why this matters

Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Interactive controls have source labels

Looks good · Mobile · Measured on your page

Observed evidence

52 source controls have detectable names. Browser accessibility and CSS visibility were not tested.

Why this matters

Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: ARIA references point to source elements

Looks good · Mobile · Measured on your page

Observed evidence

5 ARIA reference(s) resolve within their source documents. Rendered visibility was not tested.

Why this matters

Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Language2Looks good1Informational

100/100
Not 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.

Looks good: html lang attribute

Looks good · Language · Measured on your page

Observed evidence

Language declared: lang="en".

Why this matters

The declared language tells browsers and assistive tech how to read the page and who it is for. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Declared language matches content

Looks good · Language · Measured on your page

Observed evidence

Declared language (en) matches detected content language.

Why this matters

The declared language tells browsers and assistive tech how to read the page and who it is for. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Branding3Looks good1Informational

100/100
Not measured: Web app manifestNo web manifest linked.

Not measured · Branding · Not established

Observed evidence

No web manifest linked.

Why this matters

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Recommended fix

Optional, but a manifest.json enables install prompts and better mobile integration.

Looks good: Favicon

Looks good · Branding · Measured on your page

Observed evidence

Favicon declared via <link rel="icon"> (/icon-32.png).

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 "#0b0c0f".

Why this matters

These icons are what appear in browser tabs, bookmarks and search results. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Performance

100/100

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

Performance measurements observed during the audit
MeasureThis siteReading
Web fonts don't block text—Informational: not applicableNo Google Fonts stylesheet links detected.
Server response time175 msLooks good: goodThe audit received response headers after 175 ms from one test location.
HTML payload size63 KBLooks good: goodThe page's HTML is a lean 63 KB uncompressed.
No render-blocking head scripts—Looks good: goodNo synchronous render-blocking scripts in <head>.
Inline styles are bounded0.0 KBLooks good: goodInline styles total 0.0 KB.
Script/stylesheet count—Looks good: good6 total script/style resources — reasonable.
HTML served compressed—Looks good: goodHTML is compressed with br.
Iframe usage—Looks good: goodNo iframes.
Source HTML weight63.0 KBInformational: measured source, not transferred bytes63.0 KB of HTML on the audited page

From a single automated fetch of the audited page. A quick reading, not a substitute for Lighthouse or field data.

Security

70/100

HTTPS, transport security and the response headers the audited pages send.

Needs a fix: HTTP redirects to HTTPSThe http:// version serves content instead of redirecting.

Needs a fix · Security · Review suggestedCritical

Observed evidence

The http:// version serves content instead of redirecting.

Why this matters

HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. Right now the sampled pages don't provide it.

Recommended fix

301-redirect all HTTP traffic to HTTPS — otherwise you have duplicate origins and users can land on the insecure one.

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

Looks good · Security · Measured on your page

Observed evidence

HSTS is set: max-age=31536000; includeSubDomains.

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: Content Security Policy

Looks good · Security · Measured on your page

Observed evidence

An enforced CSP restricts scripts and object embedding.

Why this matters

HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.

Recommended fix

Review the complete policy against the application's resource and inline-script needs.

Looks good: Frame embedding protection

Looks good · Security · Measured on your page

Observed evidence

Response headers restrict cross-origin framing (frame-ancestors 'none').

Why this matters

HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Referrer policy

Looks good · Security · Measured on your page

Observed evidence

Referrer-Policy is strict-origin-when-cross-origin.

Why this matters

HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Browser feature permissions

Looks good · Security · Measured on your page

Observed evidence

A Permissions-Policy disables at least one sensitive browser feature.

Why this matters

HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.

Recommended fix

Review remaining features and allow only origins the application needs.

Looks good: X-Content-Type-Options

Looks good · Security · Measured on your page

Observed evidence

nosniff is set.

Why this matters

HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: No mixed content

Looks good · Security · Measured on your page

Observed evidence

No insecure subresources detected.

Why this matters

HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Server technology disclosure

Looks good · Security · Measured on your page

Observed evidence

No X-Powered-By disclosure.

Why this matters

HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.

Recommended fix

Nothing to do here.

AI answer readiness

100/100

Retrieval signals an answer engine relies on: crawler access, clear entities and answers it can quote. These checks do not measure citations or traffic.

Could be better: llms.txtNo /llms.txt file.

Could be better · AI answer readiness · Review suggested

Observed evidence

No /llms.txt file.

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

Optional: publish an llms.txt index of useful pages. This proposal is not a requirement for Google AI features, and its absence does not reduce the core score.

Reference
Could be better: Question-style headingsOnly 0% of 37 H2/H3 headings are question-shaped.

Could be better · AI answer readiness · Review suggested

Observed evidence

Only 0% of 37 H2/H3 headings are question-shaped.

Why this matters

This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.

Recommended fix

Phrase key subheadings as the questions users actually ask ("How much does X cost?"). This improves the measured question-heading signal; the audit does not guarantee citations.

Could be better: Definitional openingThe opening paragraph doesn't define what the site/topic is: "One little icon that watches your Vercel, Cloudflare and GitHub deploys.…"

Could be better · AI answer readiness · Review suggested

Observed evidence

The opening paragraph doesn't define what the site/topic is: "One little icon that watches your Vercel, Cloudflare and GitHub deploys.…"

Why this matters

This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.

Recommended fix

"X is a Y that does Z for W" in the first paragraph gives answer engines a liftable definition of you. Write it once, benefit everywhere.

Could be better: 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: Machine-readable provenance signalsOnly 1 of 4 provenance signal types were found: author.

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

Observed evidence

Only 1 of 4 provenance signal types were found: author.

Why this matters

This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.

Recommended fix

Add the missing author, date, breadcrumb, or contact signal so machines can identify provenance and site structure.

Affected pages (2)

  • https://deployedyet.com/
  • https://deployedyet.com/privacy
Could be better: Markdown copies of pagesNo markdown copy answered at /index.md or /privacy.md or /index.html.md.

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

Observed evidence

No markdown copy answered at /index.md or /privacy.md or /index.html.md.

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

Publish a clean markdown copy of each key page at /page.md (or /page.html.md). It strips navigation and scripts, so a retriever spends its budget on your content.

Affected pages (2)

  • https://deployedyet.com/
  • https://deployedyet.com/privacy
Reference
Not measured: llms-full.txtNo /llms-full.txt.

Not measured · AI answer readiness · Not established

Observed evidence

No /llms-full.txt.

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 companion to llms.txt containing your full content as one markdown file — useful for sites whose pages are JS-heavy.

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

Not measured · AI answer readiness · Not established

Observed evidence

No Article/BlogPosting schema found.

Why this matters

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Recommended fix

Add Article schema with author and datePublished so the page exposes clear provenance for retrieval. This audit does not measure or guarantee citations or rankings.

Not measured: Citable facts density42 concrete figures across 1224 words.

Not measured · AI answer readiness · Not established

Observed evidence

42 concrete figures across 1224 words.

Why this matters

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Recommended fix

Good — keep facts specific and current, and date-stamp them.

Not measured: Question headings have concise answersNo question-shaped H2/H3 headings were available to pair with answer paragraphs.

Not measured · AI answer readiness · Not established

Observed evidence

No question-shaped H2/H3 headings were available to pair with answer paragraphs.

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

Write the questions your audience asks as H2/H3 headings, then answer each in a concise paragraph immediately below it.

Not measured: llms.txt follows the specNo readable /llms.txt, so its structure cannot be checked.

Not measured · AI answer readiness · Not established

Observed evidence

No readable /llms.txt, so its structure cannot be checked.

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 llms.txt first — the llms.txt check covers that — then this one verifies the structure.

Reference
Not applicable: Accept: text/markdown negotiationThe homepage answered Accept: text/markdown with text/html.

Not applicable · AI answer readiness · Measured on your page

Observed evidence

The homepage answered Accept: text/markdown with text/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

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: AI crawler access

Looks good · AI answer readiness · Measured on your page

Observed evidence

The audited URL is allowed for evaluated answer-search crawlers.

Why this matters

This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: FAQ/QA schema

Looks good · AI answer readiness · Measured on your page

Observed evidence

FAQ/QA schema found.

Why this matters

This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Semantic HTML structure

Looks good · AI answer readiness · Measured on your page

Observed evidence

Semantic structure present: main×1, article×6, section×6, nav×2, footer×1, aside×1.

Why this matters

This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Answers lead the section

Looks good · AI answer readiness · Measured on your page

Observed evidence

Paragraphs get to the point without preamble.

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 12 words, lists present — chunk-friendly.

Why this matters

This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Cites external sources

Looks good · AI answer readiness · Measured on your page

Observed evidence

27 outbound reference(s) across crawled pages.

Why this matters

This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Consistent brand entity

Looks good · AI answer readiness · Measured on your page

Observed evidence

Brand declared: og:site_name "Deployed Yet?".

Why this matters

This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Description reads as a liftable summary

Looks good · AI answer readiness · Measured on your page

Observed evidence

Meta description works as a standalone summary.

Why this matters

This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Entity identity agrees across signals

Looks good · AI answer readiness · Measured on your page

Observed evidence

The site is consistently named "Deployed Yet?" and 2 identity URL(s) stay on deployedyet.com.

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

40/100

Publisher-policy signals, for sites that plan to carry ads. These checks do not affect the overall score or grade, and they do not measure or guarantee AdSense approval.

On its own, this site scores 47/100 for publisher readiness. Ignore this section if you do not run ads.

Could be better: Privacy policy advertising disclosuresFetched privacy policy lacks third-party/vendor disclosure signals.

Could be better · AdSense policy · Published platform ruleCritical

Observed evidence

Fetched privacy policy lacks 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://deployedyet.com/privacy
Reference
Could be better: Terms pageNo terms of use page found.

Could be better · AdSense policy · Review suggested

Observed evidence

No terms of use 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

Consider adding terms that identify the service rules and publisher. This is a transparency heuristic, not an AdSense requirement.

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: Author or publisher background2/2 attributed editorial pages provide no discoverable author or publisher background.

Could be better · AdSense policy · Review suggested

Observed evidence

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

Why this matters

A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.

Recommended fix

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

Affected pages (2)

  • https://deployedyet.com/
  • https://deployedyet.com/changelog
Reference
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: ads.txtNo ads.txt yet.

Not measured · AdSense policy · Not established

Observed evidence

No ads.txt yet.

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

When AdSense provides your publisher entry, publish it exactly at /ads.txt and monitor authorization status in your account.

Reference
Not measured: Domain age & historyDomain age isn't visible from the site itself.

Not measured · AdSense policy · Not established

Observed evidence

Domain age isn't visible from the site itself.

Why this matters

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Recommended fix

Do not use age as a content-quality proxy. Verify ownership and account eligibility in AdSense; Google's general eligibility page publishes no domain-age threshold.

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

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

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

Reference
Looks good: Privacy policy page

Looks good · AdSense policy · Measured on your page

Observed evidence

Privacy policy found: https://deployedyet.com/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: Sampled publisher-content coverage

Looks good · AdSense policy · Review suggested

Observed evidence

All 2 editorial pages expose at least 250 publisher words; those pages hold 2433 publisher words in total. 1 of the 3 sampled pages is a support or tool page and was excluded from this check.

Why this matters

A publisher review looks for this before it accepts a site. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Thin page share

Looks good · AdSense policy · Review suggested

Observed evidence

2/2 editorial pages clear the audit's publisher-content triage threshold. 1 of the 3 sampled pages is a support or tool page and was excluded from this check.

Why this matters

A publisher review looks for this before it accepts a site. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: No ads on non-content screens

Looks good · AdSense policy · Published platform rule

Observed evidence

No Google ad code detected on sampled non-content screens.

Why this matters

A publisher review looks for this before it accepts a site. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Reference
Looks good: Tool pages expose explanatory content

Looks good · AdSense policy · Review suggested

Observed evidence

All 1 sampled tool-style screens include crawlable explanation.

Why this matters

A publisher review looks for this before it accepts a site. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Publisher content differs across URLs

Looks good · AdSense policy · Review suggested

Observed evidence

No high publisher-content repetition among 2 substantial sampled page(s).

Why this matters

A publisher review looks for this before it accepts a site. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Publisher content exists in source HTML

Looks good · AdSense policy · Measured on your page

Observed evidence

No empty client-rendered publisher shell in the crawl sample.

Why this matters

A publisher review looks for this before it accepts a site. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Clear navigation

Looks good · AdSense policy · Measured on your page

Observed evidence

Navigation present with 13 links.

Why this matters

A publisher review looks for this before it accepts a site. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Article-style content exists

Looks good · AdSense policy · Measured on your page

Observed evidence

Article-style content detected.

Why this matters

A publisher review looks for this before it accepts a site. The inspected source provides this signal.

Recommended fix

Nothing to do here.

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

Looks good: Author bylines on content

Looks good · AdSense policy · Review suggested

Observed evidence

Author attribution appears on all 2 sampled editorial pages.

Why this matters

A publisher review looks for this before it accepts a site. The inspected source provides this signal.

Recommended fix

Nothing to change.

Reference

Hosting and infrastructure

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

Hosting and infrastructure observations
Hostnamedeployedyet.com
CDN / edgeCloudflare
IP addresses172.67.201.34, 104.21.52.155, 2606:4700:3034::ac43:c922, 2606:4700:3032::6815:349b
DNS A172.67.201.34 · 104.21.52.155
DNS AAAA2606:4700:3034::ac43:c922 · 2606:4700:3032::6815:349b
DNS NSlady.ns.cloudflare.com · rob.ns.cloudflare.com
TLSTLSv1.3TLS_AES_256_GCM_SHA384
Certificate issuerGoogle Trust Services / WE1
Certificate valid untilJan 25 12:54:02 2027 GMT
Certificate validationPassed

Website anatomy and diagnostics

Explore links, resources, crawler access and site integrations.

Page architecture

Choose a page to explore its details and connections.

Page content

1150 publisher words

Page structure

html content

Observed discovery

Depth 0 · 2 incoming links

HTTP 200 · 63.0 KB source

Source interactions

23 controls · 0 unnamed

4 script / 2 stylesheet references

Canonical declaration
https://deployedyet.com/
Schema types
SoftwareApplication, Offer, FAQPage, Question, Answer
Outgoing links in sampled graph
/changelog · /privacy

Routes: / · /privacy · /changelog

Resource origins 3

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

  • https://deployedyet.com/stylesheet, script, image · 8 references · same origin
  • https://scripts.simpleanalyticscdn.com/script · 3 references · cross origin
  • https://static.cloudflareinsights.com/script · 3 references · cross origin
Crawler policy by page

Review crawler access for your pages. Search, training and user-triggered services have different purposes; declared access does not guarantee discovery.

Robots policy for every evaluated crawler and sampled page
Crawler / purposePagePolicyMatched directive
Googlebotsearch/allowedallow: /
Googlebotsearch/privacyallowedallow: /
Googlebotsearch/changelogallowedallow: /
bingbotsearch/allowedallow: /
bingbotsearch/privacyallowedallow: /
bingbotsearch/changelogallowedallow: /
OAI-SearchBotsearch/allowedallow: /
OAI-SearchBotsearch/privacyallowedallow: /
OAI-SearchBotsearch/changelogallowedallow: /
PerplexityBotsearch/allowedallow: /
PerplexityBotsearch/privacyallowedallow: /
PerplexityBotsearch/changelogallowedallow: /
Claude-SearchBotsearch/allowedallow: /
Claude-SearchBotsearch/privacyallowedallow: /
Claude-SearchBotsearch/changelogallowedallow: /
GPTBottraining/allowedallow: /
GPTBottraining/privacyallowedallow: /
GPTBottraining/changelogallowedallow: /
ClaudeBottraining/allowedallow: /
ClaudeBottraining/privacyallowedallow: /
ClaudeBottraining/changelogallowedallow: /
Google-Extendedtraining and other Google AI uses/allowedallow: /
Google-Extendedtraining and other Google AI uses/privacyallowedallow: /
Google-Extendedtraining and other Google AI uses/changelogallowedallow: /
ChatGPT-Useruser-initiated; robots may not apply/allowedallow: /
ChatGPT-Useruser-initiated; robots may not apply/privacyallowedallow: /
ChatGPT-Useruser-initiated; robots may not apply/changelogallowedallow: /
Advertised APIs and machine interfaces

No supported machine interfaces were advertised in the sampled HTML. An API or MCP server is optional; undiscovered interfaces remain unknown.

Public DNS and TLS endpoint

deployedyet.com · observed · 172.67.201.34, 104.21.52.155, 2606:4700:3034::ac43:c922, 2606:4700:3032::6815:349b

A
172.67.201.34 · 104.21.52.155
AAAA
2606:4700:3034::ac43:c922 · 2606:4700:3032::6815:349b
CNAME
Unavailable for this exact hostname
NS
lady.ns.cloudflare.com · rob.ns.cloudflare.com
MX
Unavailable for this exact hostname
CAA
Unavailable for this exact hostname

TLS: TLSv1.3

Certificate validation passed for the observed endpoint.

Issuer: Google Trust Services / WE1

Certificate valid until: Jan 25 12:54:02 2027 GMT

PageSpeed measurement

Loading the PageSpeed panel…

Growth resources

Loading growth resources…

Where to take this site next

Follow-on work suggested by the observations above.

  1. 01

    Build content depth around real keywords

    Technical basics are in place — use pages that answer actual searches as the next content focus. This audit does not measure rankings.

  2. 02

    Steal from our keyword datasets

    Curated keyword collections by niche give you a content calendar without paid tools.

Apply the recommended fixes

Hand the complete evidence to a coding agent, or take the report with you.

Open in ChatGPT Open in Grok Open in Perplexity

Report notes

  • 01This report covers the sampled public pages listed above. Other pages may have different results.
  • 02Browser-rendered content, private backend systems and authenticated experiences may require a separate review.
  • 03Unavailable observations are identified in the report. Results do not guarantee rankings, citations, security, accessibility or advertising approval.
Pages included in this report
  • https://deployedyet.com/
  • https://deployedyet.com/privacy
  • https://deployedyet.com/changelog